unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: Netpbm
Date: Sat, 19 Jan 2013 23:24:49 +0100	[thread overview]
Message-ID: <201301192324.50088.andreas@enge.fr> (raw)
In-Reply-To: <87bockygi0.fsf@gnu.org>

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

Am Samstag, 19. Januar 2013 schrieb Ludovic Courtès:
> Andreas Enge <andreas@enge.fr> skribis:
> > Could someone else please test the package?
> I just tried, and it builds perfectly as
> /nix/store/agjc4rdsvi4wvbz6dymgid5pb85nqcf7-netpbm-10.61.01.

Thanks! For me also, it builds well, but I cannot install it:

$ guix-package -i netpbm
error: build failed: build of `/nix/store/h2s02132641hvaqr03q96i97dydlqm4i-
user-environment.drv' failed.

Maybe because of the extraneous files?

> There are extraneous file in the root of that directory:
>   bin/  config_template  include/  lib/  link/  man/  misc/  pkginfo 
> README  VERSION
> Ideally, it’d be great to (re)move them.

Okay.

> As for the source tarball: could you add a comment that specifies from
> which revision it was obtained?

Well, it was simply obtained from the download link of the "Advanced" field 
at
   http://netpbm.sourceforge.net/getting_netpbm.php
The link is
   http://netpbm.svn.sourceforge.net/viewvc/netpbm/advanced?view=tar
which would download a tarball with the name "advanced?view=tar", and with 
the hash changing every time (I did not understand why). So I downloaded it 
manually and renamed it. It is really an official release with a regular 
version number, not simply an svn/git checkout. The version number is 
recorded in a file in the tarball (which was part of the download, I did 
not add anything).

> (Eventually, we’ll have an ‘subversion-fetch’ method, in addition to
> ‘url-fetch’, which could be used in such situations.)

Before that, https would be nice!

> Thanks, and congratulations given how painful it looked!

Yes, it was quite amazing; once more, we should be grateful to the GNU 
build system...

Andreas

[-- Attachment #2: Type: text/html, Size: 7985 bytes --]

  reply	other threads:[~2013-01-19 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 17:03 Netpbm Andreas Enge
2013-01-19 22:06 ` Netpbm Ludovic Courtès
2013-01-19 22:24   ` Andreas Enge [this message]
2013-01-20 14:02     ` Netpbm Ludovic Courtès
2013-01-20 15:31       ` Netpbm Andreas Enge
2013-01-20 22:08         ` Netpbm Ludovic Courtès
2013-01-20 22:40           ` Netpbm Andreas Enge
2013-01-20 23:17             ` Netpbm Andreas Enge
2013-01-21 10:27               ` Netpbm Ludovic Courtès
2013-01-21 21:00                 ` Netpbm Andreas Enge
2013-01-21 22:44                   ` Netpbm Ludovic Courtès
2013-01-21 10:25             ` Netpbm 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=201301192324.50088.andreas@enge.fr \
    --to=andreas@enge.fr \
    --cc=bug-guix@gnu.org \
    --cc=ludo@gnu.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 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).