From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] problem syncing the science overlay
Date: Tue, 21 Apr 2015 09:58:17 +0500 [thread overview]
Message-ID: <20150421095817.eafc5f62a163fc71231fbe0a@gentoo.org> (raw)
In-Reply-To: <alpine.LRH.2.11.1504210806580.15452@star.inp.nsk.su>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
Hi,
On Tue, 21 Apr 2015 08:09:08 +0600 (NOVT) grozin@gentoo.org wrote:
> Hello *,
>
> Today I get
>
> dns ~ # layman -s science
>
> * Fetching remote list...
> * Fetch Ok
>
> * Syncing selected overlay(s)...
> * Running Git... # ( cd /var/lib/layman/science && /usr/bin/git pull )
> Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> * Failure result returned from Git
> *
> * Errors:
> * ------
> * Failed to sync overlay "science".
> * Error was: Syncing overlay "science" returned status 1!
> * db.sync()
> *
>
> * CLI: Errors occurred processing action sync
> *
> * Errors:
> * ------
> * Failed to sync overlay "science".
> * Error was: Syncing overlay "science" returned status 1!
> * db.sync()
> *
>
> Other overlays (lisp, sunrise) sync normally.
You should really read news sometimes...
See gentoo-dev-announce or gentoo-dev mail lists about anongit
changes.
Long story short:
layman -f && layman -d science && layman -a science
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-04-21 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 2:09 [gentoo-science] problem syncing the science overlay grozin
2015-04-21 4:58 ` Andrew Savchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-15 10:29 grozin
2018-01-15 10:40 ` François Bissey
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=20150421095817.eafc5f62a163fc71231fbe0a@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-science@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox