From: akuster808 <akuster808@gmail.com>
To: OE-core <openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>
Subject: google mercurial repo issues
Date: Wed, 24 Jun 2015 20:00:55 -0700 [thread overview]
Message-ID: <558B6EE7.5090107@gmail.com> (raw)
Hello all,
I have run into an issue trying to build vim.
/usr/bin/env hg pull
/home/akuster/oss/downloads/hg/vim.googlecode.com/hg/vim
| DEBUG: Python function base_do_unpack finished
| DEBUG: Python function do_unpack finished
| ERROR: Function failed: Fetcher failure: Fetch command failed with
exit code 255, output:
| abort: repository
/home/akuster/oss/downloads/hg/vim.googlecode.com/hg/vim not found!
there is a note on google regarding their hg repos: "We have some known
issues with hg repositories."
https://groups.google.com/forum/#!topic/google-code-hosting/Gh3kl9MrzY4
is anyone else seeing this?
- armin
next reply other threads:[~2015-06-25 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 3:00 akuster808 [this message]
2015-06-25 10:59 ` [OE-core] google mercurial repo issues Martin Jansa
2015-06-25 10:59 ` Martin Jansa
2015-07-03 2:16 ` [OE-core] " akuster808
2015-07-03 2:16 ` akuster808
2015-07-03 6:16 ` [OE-core] " Martin Jansa
2015-07-03 6:16 ` Martin Jansa
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=558B6EE7.5090107@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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.
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.