All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: ken.masumitsu@accenture.com
Cc: SELinux@tycho.nsa.gov
Subject: Re: fail to get seandroid code
Date: Fri, 18 May 2012 07:07:20 -0400	[thread overview]
Message-ID: <1337339240.24439.2.camel@moss-pluto> (raw)
In-Reply-To: <4FB623F8.2060403@accenture.com>

On Fri, 2012-05-18 at 10:30 +0000, ken.masumitsu@accenture.com wrote:
> Hi,
> 
> When I ran "repo sync" to install seandroid in reference to
> http://selinuxproject.org/page/SEAndroid, I got an error like
> ---------------------------------------------------
> Fetching projects: 10% (24/239) fatal:
> http://selinuxproject.org/~seandroid/git/device/samsung/tuna/info/refs
> not found: did you run git update-server-info on the server?
> ---------------------------------------------------
> 
> Though I checked the URL
> (http://selinuxproject.org/~seandroid/git/device/samsung/tuna/info/refs)
> by a browser, there is not such a directory.
> 
> Why the directory does not exist on the server?

Thanks for the report - this should now be fixed.  When we added the
tuna project, we didn't set up the http-based access for it.

BTW, it has been recently pointed out that the tuna/sepolicy.* files
actually need to be copied over to maguro/ or toro/ in order to be
picked up during the build.  We'll fix that, but in the interim, you can
do that manually.

-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      reply	other threads:[~2012-05-18 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 10:30 fail to get seandroid code ken.masumitsu
2012-05-18 11:07 ` Stephen Smalley [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1337339240.24439.2.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=SELinux@tycho.nsa.gov \
    --cc=ken.masumitsu@accenture.com \
    /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.