From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 'Shadow' package home page and tarball no longer accessible
Date: Sat, 05 Apr 2014 20:50:00 -0400 [thread overview]
Message-ID: <87k3b3uvrb.fsf@yeeloong.lan> (raw)
In-Reply-To: <87ob0g6et9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 04 Apr 2014 22:05:22 +0200")
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> FYI, for well over a month now, our 'shadow' package cannot be built
>> because the tarball URL is no longer accessible. The home page is no
>> longer accessible either. I finally looked into this, and found this
>> post on the mailing list:
>>
>> https://lists.alioth.debian.org/pipermail/pkg-shadow-devel/2014-February/010041.html
>>
>> The git repository is still accessible, however:
>>
>> git://git.debian.org/git/pkg-shadow/shadow
>
> Fixed in commit aaff68e.
This new 'shadow' package fails to build on the Loongson 3A machine,
even though the old tarball version worked (after I manually added the
tarball to the store from an existing copy).
I've attached the failed build log. Any ideas?
Mark
[-- Attachment #2: Failed build log for new 'shadow' package on Loongson 3A. --]
[-- Type: application/octet-stream, Size: 10378 bytes --]
next prev parent reply other threads:[~2014-04-06 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 6:29 'Shadow' package home page and tarball no longer accessible Mark H Weaver
2014-03-21 14:05 ` Ludovic Courtès
2014-04-04 20:05 ` Ludovic Courtès
2014-04-06 0:50 ` Mark H Weaver [this message]
2014-04-06 19:11 ` Ludovic Courtès
2014-04-06 19:30 ` Ludovic Courtès
2014-04-06 21:46 ` Mark H Weaver
2014-04-07 16:19 ` 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=87k3b3uvrb.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=guix-devel@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).