On Friday 24 January 2014 09:27:30 Fabian Groffen wrote:
> All,
>
> With the original overlays.gentoo.org Subversion repo back up, we were
> able to grab all history, and convert it into a mercurial form.  Since
> this history was not available when I started the prefix-overlay, we
> have two sets of history now.  I want to replace the existing
> prefix-overlay with the one I created that contains the merger of all
> history + mercurial commits.  This requires everyone that has cloned
> this repo, to clone the new one.  Therefore, I have revoked commit
> rights to the prefix-overlay, as new commits shouldn't go there.
>
> The conversion of old history was more complex than simply importing it
> due to some operations like big renames in the past.  I took the time to
> actually get this right, and glue everything together in a nice way.
> Because the current prefix-overlay has just a minimal amount of commits,
> I think that now is the time that we still can easily avoid ugly merge
> constructs and multiple initial commits in our repo, by converting
> everything into a single repo.  However, since this changes the
> changesets involved, this repo is a new and unrelated one to the current
> prefix-overlay.  Therefore, everyone needs to reclone it.
>
> Please take a look at:
>   http://prefix.gentooexperimental.org/hg/prefix-tree
> It has history back to:
>   http://prefix.gentooexperimental.org/hg/prefix-tree/log?rev=0
>
> Those who got push access to the prefix-overlay, got it for this new
> prefix-tree repo.
>
> Sorry for the inconvenience,
>
> Fabian

Something went seriously wrong here: lots of patches are missing from the 
overlay. Bootstrapping with LATEST_TREE_YES=1 fails when building sed due to 
a missing sed-4.1.4-makeinfo-c-locale.patch, and bash runs into the same 
problem.

I already fixed missing patches in sys-libs/readline, but found out 
immediately afterwards that the problem is more widespread. I don't know how 
widespread exactly, but you probably want to have a look at what exactly went 
wrong in the import process.

-- Ruud


Reply via email to