From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36931@debbugs.gnu.org
Subject: bug#36931: guile-bash repository no longer exists?
Date: Mon, 05 Aug 2019 19:23:41 -0600 [thread overview]
Message-ID: <37c6444ff28cc0c8a87ad7051312496ce6534da8.camel@gmail.com> (raw)
In-Reply-To: <87ftmfznhs.fsf@elephly.net>
On Mon, 2019-08-05 at 16:38 +0200, Ricardo Wurmus wrote:
> Jesse Gibbons <jgibbons2357@gmail.com> writes:
>
> > guile-bash fails to build. The site https://anonscm.debian.org/cgit
> > /use
> > rs/kaction-guest/retired/dev.guile-bash.git says it is not on the
> > web
> > server.
>
> Perhaps a copy of the sources can be found in the Software Heritage
> archive?
>
> --
> Ricardo
>
I don't know if it's exactly the same, but I found something similar at
https://archive.softwareheritage.org/browse/origin/https://github.com/k
action/guile-bash/directory/
Thanks for the suggestion.
I requested a tarball, and received this statement in the email:
"Please keep in mind that this link might expire at some point, in
which case you will need to request the bundle again."
Do you have any recommendations on where to host the tarball? If
necessary, I am willing to create a repository for the code on my
github.
prev parent reply other threads:[~2019-08-06 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:18 bug#36931: guile-bash repository no longer exists? Jesse Gibbons
2019-08-05 14:38 ` Ricardo Wurmus
2019-08-05 20:39 ` Björn Höfling
2019-08-23 16:30 ` Ludovic Courtès
2019-08-23 16:32 ` Ludovic Courtès
2019-08-26 11:20 ` Björn Höfling
[not found] ` <87imqn4zfq.fsf@gnu.org>
2019-08-26 14:24 ` bug#36931: [swh-devel] " Nicolas Dandrimont
[not found] ` <20190826142435.beivr3d7ydo2rxmb@werner.olasd.eu>
2019-08-27 15:27 ` Ludovic Courtès
2019-08-06 1:23 ` Jesse Gibbons [this message]
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=37c6444ff28cc0c8a87ad7051312496ce6534da8.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=36931@debbugs.gnu.org \
--cc=rekado@elephly.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).