From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] 9front, git and mercurial.
Date: Fri, 20 May 2022 11:00:27 -0400 [thread overview]
Message-ID: <289a96d3-bc5d-ca4d-0aec-3ab2de52731e@fjrhome.net> (raw)
In-Reply-To: <00CC98CA88A7D37BA632C5576D07323F@eigenstate.org>
Bingo - I didn't think to do a fresh build of git after it finally
retrieved that initial revision and i did not read that error message as
something that could be related to the version of git.
When I tried doing an "mk all" again something failed during compilation
due to files being out of sync.
Figuring that some of the files might actually *be* out of sync, I did a
cd cmd/git then mk all && mk install from there, which worked.
Now sysupdate ran (from /sys/src) and apparently pulled some files down,
and the next run appears to have been clean with no further updates.
As mk all still gave me compilation errors, I ran an mk clean to get a
fresh start hoping that it would pull things back into sync, then
started mk all again, which is now running. I've seen errors like those
before and an mk clean and fresh start on mk all cleared them up, so I
am hopeful this will take care of it.
In any case, the source seems to finally be up-to-date, so this issue at
least appears to be resolved.
Thank you!
On 5/20/22 10:30 AM, ori@eigenstate.org wrote:
> Quoth Frank D. Engel, Jr. <fde101@fjrhome.net>:
>
>> I tried running sysupdate again and continue to receive the error:
>>
>> glenda@brains1% /bin/sysupdate
>> end of line for hg: moving to git.
>> fetching snapshot...
>> fs 281324: warning: process exceeds 100 file descriptors
>> pulling with git...
>> /bin/git/pull: no remote to pull from
>> got git: you may remove /dist/plan9front/.hg
>> glenda@brains1% rm -rf /dist/plan9front/.hg
>> glenda@brains1% sysupdate
>> /bin/git/pull: no remote to pull from
>> glenda@brains1%
>>
>>
> you had a previous git installed; I don't know
> what version that was. you probably want to
> install the system version of git:
>
> cd /sys/src && mk all && mk install
> sysupdate
>
> if that still errors, attach:
>
> /dist/plan9front/.git/config
>
> and the contents of the sysupdate script
> that you're currently on.
>
>
next prev parent reply other threads:[~2022-05-20 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89F3ABF218EE52FAE7605F9B07728487@eigenstate.org>
[not found] ` <1275338a-65f0-61c2-8162-ba7c93fa2493@fjrhome.net>
[not found] ` <YoU7OpruuHGcQYUj@wopr>
[not found] ` <dbbd3656-69c9-b71b-2d08-07912ad5326d@fjrhome.net>
2022-05-18 19:48 ` Frank D. Engel, Jr.
2022-05-18 20:03 ` Frank D. Engel, Jr.
2022-05-19 1:51 ` ori
2022-05-19 8:20 ` Frank D. Engel, Jr.
2022-05-19 17:46 ` Kurt H Maier
2022-05-19 18:41 ` Frank D. Engel, Jr.
2022-05-20 1:33 ` Jacob Moody
2022-05-20 2:25 ` Frank D. Engel, Jr.
2022-05-20 4:37 ` ori
2022-05-20 9:15 ` Frank D. Engel, Jr.
2022-05-20 14:30 ` ori
2022-05-20 15:00 ` Frank D. Engel, Jr. [this message]
2022-05-20 1:02 ` Amavect
2022-05-20 2:35 ` Frank D. Engel, Jr.
2022-05-20 2:59 ` Jacob Moody
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=289a96d3-bc5d-ca4d-0aec-3ab2de52731e@fjrhome.net \
--to=fde101@fjrhome.net \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).