From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Context minimals on linux armhf
Date: Sat, 16 Dec 2017 21:04:04 +0100 [thread overview]
Message-ID: <CALBOmsb703rFA=vKBB-iOPHY03bx6qXZzQF9_J=QpcE9AQaNXA@mail.gmail.com> (raw)
In-Reply-To: <BFB20177-101B-4447-8207-83BD2CB259F1@toppkieker.info>
On 15 December 2017 at 16:06, Lutz Haseloff wrote:
> Hi all,
>
> since some days, everytime I want to run first-setup.sh I get following
> error message.
>
> @ERROR: chroot failed
> rsync error: error starting client-server protocol (code 5) at main.c(1653)
> [Receiver=3.1.1]
>
> Is there something wrong with the rsync server?
Can you please retry?
I would say that it's weird that nobody reported it earlier, but it's
probably because if one runs the update on top of existing
distribution, the error skips by.
It looks as if the sysadmin was changing some paths on the system and
accidentally made one search-and-replace replacement too much.
Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-12-16 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 15:06 Lutz Haseloff
2017-12-16 17:19 ` Jorge Manuel
2017-12-16 20:04 ` Mojca Miklavec [this message]
2017-12-16 21:26 ` Jorge Manuel
-- strict thread matches above, loose matches on Subject: below --
2017-03-02 7:41 ConTeXt " Lutz Haseloff
2017-03-02 7:47 ` luigi scarso
2017-03-02 9:33 ` Hans Hagen
2017-03-02 10:01 ` Lutz Haseloff
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='CALBOmsb703rFA=vKBB-iOPHY03bx6qXZzQF9_J=QpcE9AQaNXA@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/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;
as well as URLs for NNTP newsgroup(s).