Re: Getting started



On Sat, Jul 14, 2012 at 5:46 PM, Colin Walters <walters verbum org> wrote:
> On Sat, 2012-07-14 at 13:52 +0100, Sam Thursfield wrote:
>
>> First - what is the recommended "host" system? I'm guessing this
>> should be in a VM, and after noticing the lchown() call in the source
>> code, am I right in thinking that all the commands should be run as
>> root?
>
> To do a bootable OS install, yes; the repo that ostadmin creates is
> "bare", which means files are stored as themselves; to retrieve a file
> is just a matter of making a hard link.  But you can also make an
> "archive mode" repository as any user; that's how the "ostbuild" build
> system works.

Is there a flag to enable this mode? Currently in ostree-pull lchown()
is called anyway, and it returns an error (EPERM) to the main loop.
I've commented it out for now.

I pushed a branch 'wip/error-handling' which can show what is
happening a little better.

> "archive mode" stores the real metadata (uid, gid) out of band.  This
> is also the same way the http://ostree.gnome.org server is configured.
> It's a little bit like how you can copy around .rpm/.deb files as any
> user, except the OSTree storage model is significantly more
> space-efficient over time than a pile of .rpm/.deb files, because
> it deduplicates.

Nice :)

... snip ...

>> Secondly, having done this setup, I'm consistently getting "Connection
>> terminated unexpectedly" when I run ostree-pull.
>
> I think this is the ostree.gnome.org apache configuration hitting
> concurrent download limits, so it's terminating the connection.  But I
> can't reproduce the problem here though =/
>
> The libsoup Request API is pretty new, but I'm happy to depend on it
> and work out the bugs, and help make GNOME better.
>
> Ah, I did just get the connection terminated error, rerunning in gdb now
> with breakpoints configured like this:
>
> b g_set_error if ! (err->domain == 118 && err->code == 27)
> b g_set_error_literal if ! (err->domain == 118 && err->code == 20)

I'm not sure what's changed, but after running in the debugger to trap
the connection failed errors, they recurred but were no longer fatal.
Maybe it depends when they happen.

I think https://bugzilla.gnome.org/show_bug.cgi?id=679527 is fixed
too, which is also super helpful. So I now have an OS tree checked
out!

Thanks
Sam


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]