Hi, Please read my last message. The issue is fixed. Nobody should do anything except of SDK guys.
2009/10/22 Kamen Bundev <[email protected]>: > Hi guys, > > I've played around with maemo-optify yesterday and decided to instead of > creating the paths in the package subdir, to create a symlink to /opt and > drop everything there before packaging. Wrong move, dpkg-deb doesn't follow > symlinks, it packages them :) So, the logical step was to instead of symlink > to /opt, to create home/opt in the package subdir and symlink opt/ to it. > That worked and I have a package ready that will work in the device, but I'm > hesitant to try it in the autobuilder because if the autobuilder is like > scratchbox, then the package will be installed to /home/opt but the /opt > symlinks will point to somewhere else (/targets/links/opt) and the build > will fail anyway. > > So my question is - is this the right way to go about this and can I control > where the /opt dir is symlinked to in the autobuilder? > > Regards: > Bundyo > > On Thu, Oct 22, 2009 at 2:35 AM, Nathan Anderson <[email protected]> > wrote: >> >> Kamen, >> >> I build both binary target and source targets debs in my scratchbox >> before I upload. For instance last night I had to rebuild the binary debs >> about 20 times (trying to get a weird make file rule to work). Once I got >> it working then I would copy my rules to a fresh copy and re-run a source >> deb then re-run a binary once more just to make sure it wasn't "left" over >> stuff causing a success. ;-) >> >> So, I don't think it has anything to do with the scratchbox. I suspect >> it as Ed found something to do with the symlink -> directory or something in >> their on the auto-builder. >> >> Nathan. >> ________________________________ >> From: Kamen Bundev [mailto:[email protected]] >> Sent: Wednesday, October 21, 2009 6:14 PM >> To: Nathan Anderson >> Cc: [email protected] >> Subject: Re: Maemo-Optify & Builder Bots = Broken? >> >> Nah, that's not enough. Still fails. >> >> Another difference is that I'm building my optified package in scratchbox >> before upload and the other people are using the autobuilder, so the problem >> should be somewhere else. >> >> Regards: >> Bundyo >> >> On Thu, Oct 22, 2009 at 2:09 AM, Kamen Bundev <[email protected]> wrote: >>> >>> Nah, that's not enough. Still fails. >>> >>> Regards: >>> Bundyo >>> >>> On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <[email protected]> wrote: >>>> >>>> Looks like the only difference here is that my /opt should be pointing >>>> to /targets/links/opt which is symlinked to the proper target on target >>>> change. Uploading the new package to extras now. >>>> >>>> Regards: >>>> Bundyo >>>> >>>> On Thu, Oct 22, 2009 at 12:39 AM, Nathan Anderson >>>> <[email protected]> wrote: >>>>> >>>>> Ed, >>>>> >>>>> I believe this is what you are asking: >>>>> FREMANTLE_ARMEL cs2007q3-glibc2.5-arm7 >>>>> FREMANTLE_X86 cs2007q3-glibc2.5-i486 >>>>> >>>>> >>>>> Nathan >>>>> >>>>> -----Original Message----- >>>>> From: Ed Bartosh [mailto:[email protected]] >>>>> Sent: Wednesday, October 21, 2009 4:03 PM >>>>> To: Nathan Anderson >>>>> Cc: [email protected] >>>>> Subject: Re: Maemo-Optify & Builder Bots = Broken? >>>>> >>>>> 2009/10/21 Nathan Anderson <[email protected]>: >>>>> > Ed, >>>>> > >>>>> > Sure can (and following the chain). >>>>> > >>>>> > ls -l / | grep opt >>>>> > lrwxrwxrwx 1 root root 18 Oct 6 22:36 opt -> >>>>> > /targets/links/opt >>>>> > >>>>> > ls -l /targets/links/ | grep opt >>>>> > lrwxrwxrwx 1 maemo 1000 26 Oct 19 16:55 opt -> >>>>> > /targets/FREMANTLE_X86/opt >>>>> > >>>>> I've found the difference! >>>>> In your environment /targets/<target>/opt is a directory. In >>>>> autobuilder >>>>> environment it's a symlink: >>>>> >>>>> > ls -l /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ >>>>> > |grep opt >>>>> lrwxrwxrwx 1 builder1 builder1 9 Oct 21 23:50 opt -> /home/opt >>>>> >>>>> And it looks like it becomes symlink after rootstrap unpacking. Look: >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > sb-conf >>>>> re >>>>> -f >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > ls -l >>>>> /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt >>>>> drwxrwxr-x 2 1005 1006 4096 Oct 21 23:56 opt >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > sb-conf >>>>> in >>>>> --etc --devkits >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > ls -l >>>>> /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt >>>>> drwxrwxr-x 2 builder1 builder1 4096 Oct 21 23:56 opt >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > sb-conf >>>>> in >>>>> --fakeroot Installing fakeroot version 1.4.2.1... >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > ls -l >>>>> /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt >>>>> drwxrwxr-x 2 builder1 builder1 4096 Oct 21 23:56 opt >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > sb-conf >>>>> rs >>>>> /scratchbox/packages/maemo-sdk-rootstrap_5.0_armel.tgz >>>>> Unpacking rootstrap... >>>>> [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] > ls -l >>>>> /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt >>>>> lrwxrwxrwx 1 1005 1006 9 Oct 21 23:57 opt -> /home/opt >>>>> >>>>> So, the difference is in rootstraps. Tell me which rootstrap do you use >>>>> and >>>>> I'll compare it with the one autobuilder uses. >>>>> >>>>> -- >>>>> BR, >>>>> Ed >>>>> >>>>> _______________________________________________ >>>>> maemo-developers mailing list >>>>> [email protected] >>>>> https://lists.maemo.org/mailman/listinfo/maemo-developers >>>> >>> >> > > > _______________________________________________ > maemo-developers mailing list > [email protected] > https://lists.maemo.org/mailman/listinfo/maemo-developers > > -- BR, Ed _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
