On Tue, Jun 16, 2009 at 4:33 PM, Baho Utot<baho-utot@xxxxxxxxxxxxxxx> wrote:
> On Tue, 2009-06-16 at 10:28 -0500, Aaron Griffin wrote:
>> On Mon, Jun 15, 2009 at 6:43 PM, Baho Utot<baho-utot@xxxxxxxxxxxxxxx> wrote:
>> > On Mon, 2009-06-15 at 12:20 -0500, Aaron Griffin wrote:
>> >> On Mon, Jun 15, 2009 at 3:37 AM, Baho Utot<baho-utot@xxxxxxxxxxxxxxx> wrote:
>> >> > On Mon, 2009-06-15 at 11:28 +1000, Allan McRae wrote:
>> >> >> Baho Utot wrote:
>> >> >> > On Mon, 2009-06-15 at 10:46 +1000, Allan McRae wrote:
>> >> >> >
>> >> >> >> Baho Utot wrote:
>> >> >> >>
>> >> >> >>> I have setup a new computer with a clean install with
>> >> >> >>> kernel26-2.6.29.4-1 does this kernel support unionfs?
>> >> >> >>> This is the second system I have had trouble with.
>> >> >> >>>
>> >> >> >>> Devtools always complains like this
>> >> >> >>>
>> >> >> >>> building union chroot
>> >> >> >>> ERROR: No unionfs available. Abandon ship!
>> >> >> >>> FAILURE: vsftpd-2.1.0-2-i686.pkg.tar.gz
>> >> >> >>>
>> >> >> >>> I am using devtools 0.6.4-1 the latest I think
>> >> >> >>>
>> >> >> >>> When I use devtools with kernel26 2.6.27.10-1 on an older system
>> >> >> >>> devtools works
>> >> >> >>>
>> >> >> >>> Anyone got a clue what is wrong?
>> >> >> >>>
>> >> >> >>>
>> >> >> >> The same as previously... recent kernels do no support unionfs so you
>> >> >> >> need a git version of makechrootpkg with fixes it to use unionfs.
>> >> >> >>
>> >> >> >> Allan
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> > Can you tell Aaron I found an error with his latest git version of
>> >> >> > devtools the makechrootpkg
>> >> >> >
>> >> >> > devtools-360fcd2f0ecaba3c8bb0e56e7fc6014dacfb3ec7
>> >> >> >
>> >> >> > line 227 on the version I just fetched
>> >> >> > near the bottom of the script (makechrootpkg)
>> >> >> >
>> >> >> > is
>> >> >> > pkgfile=${chrootdir}/union/pkgdest/${pkgname}-${pkgver}-${pkgrel}-*
>> >> >> > ${PKGEXT}
>> >> >> >
>> >> >> > should be
>> >> >> >
>> >> >> > pkgfile=${chrootdir}/rw/pkgdest/${pkgname}-${pkgver}-${pkgrel}-*
>> >> >> > ${PKGEXT}
>> >> >> >
>> >> >> > It fails to copy the completed/built package from the chroot to the
>> >> >> > directory where you have the PKGBUILD file
>> >> >> >
>> >> >>
>> >> >> I have no problems, and if you think about it, the union dir is a union
>> >> >> between the root and rw directories so this is the same thing...
>> >> >>
>> >> >> Allan
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> > Then why doesn't it work?
>> >> >
>> >> > The package is left in rw/pkgdest
>> >> > after I change it the package is moved to the dir the PKGBUILD is in.
>> >>
>> >> The only reason it wouldn't work is that rw and union are _not_ the
>> >> same at that point in time.
>> >
>> > Don't understand what you are saying there???
>> >
>> > Then my fix it is OK?
>> >
>> > I understand the rw overlays ../root what does the union do?
>>
>> root is read-only
>> rw is read-write
>> union is used to combine the two (to mount anything, you need a destination dir)
>>
>> So, root + rw = union
>
> Pk but that adds to the mystery why the compiled packages is missing in
> union and present in rw
My guess is that the union failed to mount, and the script carries on
just fine as if rw and union were normal dirs.
