[haiku] [haiku-development] Re: Re: R1/beta1: Here We Go (at last)
- From: "Thomas Mueller" <mueller6723@xxxxxxx>
- To: Haiku ML <haiku@xxxxxxxxxxxxx>, Haiku Development ML <haiku-development@xxxxxxxxxxxxx>
- Date: Tue, 28 Aug 2018 08:24:29 +0000
The release has been branched. Alex has not quite finished tweaking
the buildbot to generate release RCs, but rest assured that will
happen very quickly. We are still waiting for some EFI fixes for
x86_64, but otherwise, the "real testing" can begin. As the branch
will not diverge from master in terms of actual bugfixes, anyone who
wants to get testing right away for 32-bit can do so with a current
nightly build. Otherwise, wait a day or so for the release-profile
images to start appearing.
What happens to the git tree structure on Github (haikuports, haikuports.cross
and haikuporter) and on git.haiku-os.org (haiku and buildtools)?
I was successful updating (git pull) haikuports, haikuporter and
haikuports.cross (latter two were Already up-to-date), was successful with
buildtools, but not with haiku tree:
$ git pull
error: wrong index v2 file size in
error: Unable to find 988504fade20d5c6da03383e2737794c4b94ad13 under
Cannot obtain needed tree 988504fade20d5c6da03383e2737794c4b94ad13
while processing commit b5c9e6620ee731bd33d8cb3ef6ac01749122b6b3.
error: fetch failed.
I didn't see any special notice of the branch on git.haiku-os.org web
interface, but I guess it was too early and you didn't get that far yet.
Other related posts: