On Sun, Nov 27, 2016 at 10:52 AM, Norbert Thiebaud <nthiebaud@gmail.com> wrote:
On Sun, Nov 27, 2016 at 9:29 AM, Jason Marshall
I am not certain that it is the root cause of the problme.. but
certainly that is
likely to cause trouble.
actually thinking more about I'm quite certain that it was the root cause:
lode create a local mirror of core.git (in LODE_HOME/mirrors/core.git
and use it as an 'alternate source' to clone core.git for /dev/core
(and toher working checkout you way want to create
using ./setup -new <name>
This is to save disk when one has multiple dev environement (lode was
originaly created for Continuous Integration which can have half a
dozen of such workspace)
This works by having LODE_HOME/dev/core/.git/objects/info/alternate
containint the path tot he object of the local mirror
in you case that would have been
/home/Json and Emma/lode/mirrors/core.git/objects
and I'm pretty sure that confused the heck out of git to have spaces there
Norbert
PS: even if there is a way to unconfuse git there... there are bound
to be other place in the build and the many scripts involved that do
not play well with space in filename... so, let's not seek pain for
the sake of it and just work around the issue :-)
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.