Mailing List Archive: Maemo: Developers

Maemo-Optify & Builder Bots = Broken?

1 2

View All

Index | Next | Previous | View Threaded

nathan at andersonsplace

Oct 21, 2009, 8:30 AM

Post #1 of 34 (919 views)
Permalink

Maemo-Optify & Builder Bots = Broken?

Devs,

Ok, I have been trying to be a good boy and optify all the items I
have been putting into the fremantle extras. Up to now they have been
standalone libraries and the build bots have done their job and optified the
package (and then I've been able to install them in my sdk properly).

However, I have finally submitted a library which depends on two
other libraries that I did and optified. Well when it did the depends step
to pull all the libraries; this is the output:

---
Try to install static depends: libcurl3 libcurl3-dev libicu42 libicu42-dev
clucene-core clucene-core-dev zlib1g-dev python2.5 python2.5-dev
[2009-10-21 12:30:46] fakeroot apt-get -y -q -o
APT::Get::AllowUnauthenticated=1 install --no-remove libcurl3 libcurl3-dev
libicu42 libicu42-dev clucene-core clucene-core-dev zlib1g-dev python2.5
python2.5-dev </dev/null
.... (My depends are listed properly) ....
Unpacking libssl0.9.8 (from .../libssl0.9.8_0.9.8g-15maemo4+0m5_armel.deb)
...
Selecting previously deselected package libreadline4.
Unpacking libreadline4 (from .../libreadline4_4.3-10.1+0m5_armel.deb) ...
Selecting previously deselected package clucene-core.
Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
dpkg: error processing
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb (--unpack):
trying to overwrite `/opt', which is also in package base-files
^^^^
Uhm, this is not good. Each of my "optified" packages throws this error.
That kinda makes optifing the libraries a pointless exercise if I can't use
them later in the buildbot. And Lib-icu is about 16 MEGS of libraries, so I
would think it would be a great canidate for optification. Do I need to
resubmit everything w/o optification, or are the build bots broken?

The packages that I have optified has depends on maemo-optify and has
"maemo-optify" as the step between (dh_gencontrol and dh_md5sums).

dh_gencontrol
maemo-optify
dh_md5sums

What do I need to do to solve this issue? I have no issues resubmitting
the packages I have done again to test things, but I would rather have a
"known" way to make it work since Lib-icu is a 2.5 hour (yes, 2 hours 30
minutes) build process on the builders; so if I would prefer not to have to
tie up a buildbot for that length of time again until we have a known
working solution.

Nathan.

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 21, 2009, 9:09 AM

Post #2 of 34 (874 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Welcome to the club :) I have the same problem.

Regards:
Bundyo

On Wed, Oct 21, 2009 at 6:30 PM, Nathan Anderson
<nathan [at] andersonsplace>wrote:

> Devs,
>
> Ok, I have been trying to be a good boy and optify all the items I
> have been putting into the fremantle extras. Up to now they have been
> standalone libraries and the build bots have done their job and optified
> the
> package (and then I've been able to install them in my sdk properly).
>
> However, I have finally submitted a library which depends on two
> other libraries that I did and optified. Well when it did the depends step
> to pull all the libraries; this is the output:
>
> ---
> Try to install static depends: libcurl3 libcurl3-dev libicu42 libicu42-dev
> clucene-core clucene-core-dev zlib1g-dev python2.5 python2.5-dev
> [2009-10-21 12:30:46] fakeroot apt-get -y -q -o
> APT::Get::AllowUnauthenticated=1 install --no-remove libcurl3 libcurl3-dev
> libicu42 libicu42-dev clucene-core clucene-core-dev zlib1g-dev python2.5
> python2.5-dev </dev/null
> .... (My depends are listed properly) ....
> Unpacking libssl0.9.8 (from .../libssl0.9.8_0.9.8g-15maemo4+0m5_armel.deb)
> ...
> Selecting previously deselected package libreadline4.
> Unpacking libreadline4 (from .../libreadline4_4.3-10.1+0m5_armel.deb) ...
> Selecting previously deselected package clucene-core.
> Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb)
> ...
> dpkg: error processing
> /var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb (--unpack):
> trying to overwrite `/opt', which is also in package base-files
> ^^^^
> Uhm, this is not good. Each of my "optified" packages throws this error.
> That kinda makes optifing the libraries a pointless exercise if I can't use
> them later in the buildbot. And Lib-icu is about 16 MEGS of libraries, so
> I
> would think it would be a great canidate for optification. Do I need to
> resubmit everything w/o optification, or are the build bots broken?
>
> The packages that I have optified has depends on maemo-optify and has
> "maemo-optify" as the step between (dh_gencontrol and dh_md5sums).
>
> dh_gencontrol
> maemo-optify
> dh_md5sums
>
> What do I need to do to solve this issue? I have no issues resubmitting
> the packages I have done again to test things, but I would rather have a
> "known" way to make it work since Lib-icu is a 2.5 hour (yes, 2 hours 30
> minutes) build process on the builders; so if I would prefer not to have to
> tie up a buildbot for that length of time again until we have a known
> working solution.
>
> Nathan.
>
>
>
>
>
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

julle.luukko at quicknet

Oct 21, 2009, 9:45 AM

Post #3 of 34 (877 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Nathan Anderson wrote:
> Try to install static depends: libcurl3 libcurl3-dev libicu42 libicu42-dev
> clucene-core clucene-core-dev zlib1g-dev python2.5 python2.5-dev
> [2009-10-21 12:30:46] fakeroot apt-get -y -q -o
> APT::Get::AllowUnauthenticated=1 install --no-remove libcurl3 libcurl3-dev
> libicu42 libicu42-dev clucene-core clucene-core-dev zlib1g-dev python2.5
> python2.5-dev </dev/null
> .... (My depends are listed properly) ....
> Unpacking libssl0.9.8 (from .../libssl0.9.8_0.9.8g-15maemo4+0m5_armel.deb)
> ...
> Selecting previously deselected package libreadline4.
> Unpacking libreadline4 (from .../libreadline4_4.3-10.1+0m5_armel.deb) ...
> Selecting previously deselected package clucene-core.
> Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
> dpkg: error processing
> /var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb (--unpack):
> trying to overwrite `/opt', which is also in package base-files
> ^^^^

Hi Nathan,

I reported the same problem a few days ago:

http://lists.maemo.org/pipermail/maemo-developers/2009-October/021512.html

No solution was found!

--
Julius

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

nathan at andersonsplace

Oct 21, 2009, 10:09 AM

Post #4 of 34 (877 views)
Permalink

RE: Maemo-Optify & Builder Bots = Broken? [In reply to]

Julius,

Thanks -- I thought I saw something on the list about it a couple
days ago -- but I was thinking it was relating to something else.
Well, I guess it is "good" to know that it isn't just my problem. But I
know this basically "halts" what I'm doing.

I've added it as a bug to the bugtracker:
https://bugs.maemo.org/show_bug.cgi?id=5674

Nathan

-----Original Message-----
From: Julius Luukko [mailto:julle.luukko [at] quicknet]
Sent: Wednesday, October 21, 2009 11:45 AM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
Subject: Re: Maemo-Optify & Builder Bots = Broken?

Nathan Anderson wrote:
> Try to install static depends: libcurl3 libcurl3-dev libicu42
> libicu42-dev clucene-core clucene-core-dev zlib1g-dev python2.5
> python2.5-dev
> [2009-10-21 12:30:46] fakeroot apt-get -y -q -o
> APT::Get::AllowUnauthenticated=1 install --no-remove libcurl3
> libcurl3-dev
> libicu42 libicu42-dev clucene-core clucene-core-dev zlib1g-dev
> python2.5 python2.5-dev </dev/null .... (My depends are listed
> properly) ....
> Unpacking libssl0.9.8 (from
> .../libssl0.9.8_0.9.8g-15maemo4+0m5_armel.deb)
> ...
> Selecting previously deselected package libreadline4.
> Unpacking libreadline4 (from .../libreadline4_4.3-10.1+0m5_armel.deb) ...
> Selecting previously deselected package clucene-core.
> Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb)
...
> dpkg: error processing
> /var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb (--unpack):
> trying to overwrite `/opt', which is also in package base-files
> ^^^^

Hi Nathan,

I reported the same problem a few days ago:

http://lists.maemo.org/pipermail/maemo-developers/2009-October/021512.html

No solution was found!

--
Julius

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bartosh at gmail

Oct 21, 2009, 11:26 AM

Post #5 of 34 (873 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
...
> Selecting previously deselected package clucene-core.
> Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
> dpkg: error processing
> /var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb (--unpack):
> trying to overwrite `/opt', which is also in package base-files
> ^^^^
> Uhm, this is not good. Each of my "optified" packages throws this error.
> That kinda makes optifing the libraries a pointless exercise if I can't use
> them later in the buildbot. And Lib-icu is about 16 MEGS of libraries, so I
> would think it would be a great canidate for optification. Do I need to
> resubmit everything w/o optification, or are the build bots broken?
>
Have you tried to reproduce this issue in your build environment by
installing your library and base-files locally inside scratchbox?

Below are my attempts to reproduce and fix the problem:

This is what I see in autobulder environment:
> grep /opt$ /var/lib/dpkg/info/base-files.list
/opt
It means that /opt belongs to base-files package.
And I can easily reproduce the error if I try to install any package
with /opt directory inside it:
> fakeroot apt-get install clucene-core
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
clucene-core
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 319kB of archives.
After unpacking 1085kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
clucene-core
Install these packages without verification [y/N]? y
Get:1 http://osso.stage.dmz fremantle/free clucene-core 0.9.21b-0maemo1 [319kB]
Fetched 319kB in 0s (329kB/s)
/scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such
file or directory
Selecting previously deselected package clucene-core.
(Reading database ... 6395 files and directories currently installed.)
Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
dpkg: error processing
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb
(--unpack):
trying to overwrite `/opt', which is also in package base-files
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb
E: Sub-process /scratchbox/devkits/debian-etch/bin/dpkg returned an
error code (1)

Hmm. Let's remove /opt from base-files.list and see what happens:
Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
dpkg: error processing
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb
(--unpack):
error creating directory `./opt': Permission denied
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb

It didn't help, but we can see that dpkg tries to create directory
/opt and fails because symlink /opt already exists.
OK, then. Let's put /opt back to base-files.list and create directory
/opt instead of symlink:
$ sudo rm /scratchbox/users/ed/opt
$ sudo mkdir /scratchbox/users/ed/opt
$ sudo chown ed /scratchbox/users/ed/opt
And try again:
> fakeroot apt-get install clucene-core
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
clucene-core
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0B/319kB of archives.
After unpacking 1085kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
clucene-core
Install these packages without verification [y/N]? y
/scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such
file or directory
(Reading database ... 6395 files and directories currently installed.)
Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
Setting up clucene-core (0.9.21b-0maemo1) ...

It works! Hurray! :)

So, my conclusion is this is scratchbox problem, not autobuilder one.
It's not autobuilder, who creates /opt symlinks. They're created by
scratchbox for each user.
May be scratchbox guys can explain how to fix it properly. Of course I
can remove symlinks and create directories instead for all builders,
but may be there is better way to solve the problem?

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

nathan at andersonsplace

Oct 21, 2009, 12:12 PM

Post #6 of 34 (878 views)
Permalink

RE: Maemo-Optify & Builder Bots = Broken? [In reply to]

Ed,

I have actually installed all the packages I have built and
submitted to extras _inside_ my scratchbox from extras(-devel/testing)
without any issues; in fact I needed install a dozen or so packages (some
mine, some not) to make up all the dependancies on the one I was actually
having the issues with and reported. This is the first package I've built
that has relied upon a optified deb library. I had to actually "wait" to
package this package up until I could get the optified ICU4.21 into the
extras because I wanted to make sure that my scratchbox environment would
match what the autobuilder would get. I never did a local install from the
sources, I only did a "apt-get install <package>" to get my newly build
packages back from the extras(-devel/testing) repositories.

I can also build the source, armel and x86 of this package in my
scratchbox using the dependancies I got from extra(dev/test). However,
when I submit my nice source.deb to the autobuilder it fails with the /opt
error I listed below. So even it their was some issue with scratchbox;
there is still an serious issue with the autobuilder since it is not able to
install optified deb packages it built using the "maemo-optify" program.

Now as to if there is also a issue with scratchbox -- I can't see
how; as I stated above I can (& have) installed the packages that the
autobulder built and stuck into extras-develop for me. I have no issues
inside my scratchbox.

I do not have access to a n900 to test to see what happens on a real
n900. Anyone who has a n900 want to try "apt-get install clucene-core" (you
will need extras-devel enabled) and see if you get pretty much everything in
/opt/maemo/usr/lib)

Please remember the autobuilder built and optified all the .deb
packages I am depending on. If I skipped the maemo-optify step in all my
packages; we would not be having this discussion. ;-)

So right now my choice is to rebuild and turn off the optifing step and
theirby putting about _20_ megs of libraries into the /usr/lib folder or not
do anything until a solution is found on why the autobuilder is having
issues with .deb packages it built and optified. I'm not particlarly
happy, having to wait, but having these packages optified makes a lot more
sense to me. ;-) So I'm currently blocked. (Please note I am note the
only person who has had this issue. I know of at least two others as of
this moment.)

If I do need to change something in my packages, I will! But I
need to know what. Afaik, the only "weirdity" to these packages is adding
the "maemo-optify" before the md5 generation step.

Nathan.

-----Original Message-----
From: Ed Bartosh [mailto:bartosh [at] gmail]
Sent: Wednesday, October 21, 2009 1:26 PM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
Subject: Re: Maemo-Optify & Builder Bots = Broken?

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
...
> Selecting previously deselected package clucene-core.
> Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb)
...
> dpkg: error processing
> /var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb (--unpack):
> trying to overwrite `/opt', which is also in package base-files
> ^^^^
> Uhm, this is not good. Each of my "optified" packages throws this error.
> That kinda makes optifing the libraries a pointless exercise if I
> can't use them later in the buildbot. And Lib-icu is about 16 MEGS of
libraries, so I
> would think it would be a great canidate for optification. Do I need
to
> resubmit everything w/o optification, or are the build bots broken?
>
Have you tried to reproduce this issue in your build environment by
installing your library and base-files locally inside scratchbox?

Below are my attempts to reproduce and fix the problem:

This is what I see in autobulder environment:
> grep /opt$ /var/lib/dpkg/info/base-files.list
/opt
It means that /opt belongs to base-files package.
And I can easily reproduce the error if I try to install any package with
/opt directory inside it:
> fakeroot apt-get install clucene-core Reading package lists... Done
Building dependency tree... Done The following NEW packages will be
installed:
clucene-core
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 319kB of archives.
After unpacking 1085kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
clucene-core
Install these packages without verification [y/N]? y
Get:1 http://osso.stage.dmz fremantle/free clucene-core 0.9.21b-0maemo1
[319kB] Fetched 319kB in 0s (329kB/s)
/scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such file
or directory Selecting previously deselected package clucene-core.
(Reading database ... 6395 files and directories currently installed.)
Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
dpkg: error processing
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb
(--unpack):
trying to overwrite `/opt', which is also in package base-files
dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were
encountered while processing:
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb
E: Sub-process /scratchbox/devkits/debian-etch/bin/dpkg returned an error
code (1)

Hmm. Let's remove /opt from base-files.list and see what happens:
Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
dpkg: error processing
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb
(--unpack):
error creating directory `./opt': Permission denied
dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were
encountered while processing:
/var/cache/apt/archives/clucene-core_0.9.21b-0maemo1_armel.deb

It didn't help, but we can see that dpkg tries to create directory /opt and
fails because symlink /opt already exists.
OK, then. Let's put /opt back to base-files.list and create directory /opt
instead of symlink:
$ sudo rm /scratchbox/users/ed/opt
$ sudo mkdir /scratchbox/users/ed/opt
$ sudo chown ed /scratchbox/users/ed/opt And try again:
> fakeroot apt-get install clucene-core
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
clucene-core
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0B/319kB of archives.
After unpacking 1085kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
clucene-core
Install these packages without verification [y/N]? y
/scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such file
or directory (Reading database ... 6395 files and directories currently
installed.) Unpacking clucene-core (from
.../clucene-core_0.9.21b-0maemo1_armel.deb) ...
Setting up clucene-core (0.9.21b-0maemo1) ...

It works! Hurray! :)

So, my conclusion is this is scratchbox problem, not autobuilder one.
It's not autobuilder, who creates /opt symlinks. They're created by
scratchbox for each user.
May be scratchbox guys can explain how to fix it properly. Of course I can
remove symlinks and create directories instead for all builders, but may be
there is better way to solve the problem?

--
BR,
Ed

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bartosh at gmail

Oct 21, 2009, 12:22 PM

Post #7 of 34 (862 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> Ed,
>
> I have actually installed all the packages I have built and
> submitted to extras _inside_ my scratchbox from extras(-devel/testing)
Good. In this case we just need to understand what's the difference between
your environment and autobuilder one.

Can you show me output of the following commands run inside scratchbox:
ls -l / |grep opt
dpkg -l base-files

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

nathan at andersonsplace

Oct 21, 2009, 12:42 PM

Post #8 of 34 (861 views)
Permalink

RE: Maemo-Optify & Builder Bots = Broken? [In reply to]

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

ls -l /targets/FREMANTLE_X86 | grep opt
drwxr-xr-x 4 maemo sbox 4096 Oct 7 11:39 opt

Dpkg -l base-files
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-========================-========================-======================
==========================================
ii base-files 3.1.osso2+3.1.10.osso23+ Debian base system
miscellaneous files

Nathan
P.S. I also put a bug report in earlier today at
https://bugs.maemo.org/show_bug.cgi?id=5674 if you are handling it. ;-)

-----Original Message-----
From: Ed Bartosh [mailto:bartosh [at] gmail]
Sent: Wednesday, October 21, 2009 2:23 PM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
Subject: Re: Maemo-Optify & Builder Bots = Broken?

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> Ed,
>
> I have actually installed all the packages I have built and
> submitted to extras _inside_ my scratchbox from extras(-devel/testing)
Good. In this case we just need to understand what's the difference between
your environment and autobuilder one.

Can you show me output of the following commands run inside scratchbox:
ls -l / |grep opt
dpkg -l base-files

--
BR,
Ed

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bartosh at gmail

Oct 21, 2009, 12:50 PM

Post #9 of 34 (866 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> 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
>
> ls -l /targets/FREMANTLE_X86 | grep opt
> drwxr-xr-x 4 maemo sbox 4096 Oct 7 11:39 opt
>
>
> Dpkg -l base-files
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name Version Description
> +++-========================-========================-======================
> ==========================================
> ii base-files 3.1.osso2+3.1.10.osso23+ Debian base system
> miscellaneous files
>
Looks the same as in autobuilder environment.

Can you show versions of scratchbox packages?
This is what I have on autobuilder host:
$ dpkg -l |grep scratchbox
ii scratchbox-core 1.0.16
Scratchbox base system
ii scratchbox-devkit-apt-https 1.0.10
APT HTTPS devkit for Scratchbox
ii scratchbox-devkit-cputransp 1.0.9
CPU transparency methods
ii scratchbox-devkit-debian 1.0.10
Debian tools for Scratchbox
ii scratchbox-devkit-doctools 1.0.13
Doctools for Scratchbox
ii scratchbox-devkit-git 1.0.1
Git for Scratchbox
ii scratchbox-devkit-maemo3 1.0.3
Maemo 3 devkit for Scratchbox
ii scratchbox-devkit-perl 1.0.4
Perl modules for Scratchbox
ii scratchbox-devkit-qemu 0.10.0-0sb5
Qemu scratchbox devkit
ii scratchbox-devkit-svn 1.0
Subversion devkit for Scratchbox
ii scratchbox-libs 1.0.16
Scratchbox libraries
ii scratchbox-toolchain-cs2005q3.2-glibc2.5-arm 1.0.7.2
cs2005q3.2-glibc2.5-arm compiler for Scratch
ii scratchbox-toolchain-cs2005q3.2-glibc2.5-i386 1.0.7
cs2005q3.2-glibc2.5-i386 compiler for Scratc
ii scratchbox-toolchain-cs2007q3-glibc2.5-arm7 1.0.12-10
cs2007q3-glibc2.5-arm7 compiler for Scratchb
ii scratchbox-toolchain-cs2007q3-glibc2.5-i486 1.0.12-8
cs2007q3-glibc2.5-i486 compiler for Scratchb
ii scratchbox-toolchain-host-gcc 1.0.16
Scratchbox host-gcc toolchain

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bartosh at gmail

Oct 21, 2009, 12:59 PM

Post #10 of 34 (862 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

nathan at andersonsplace

Oct 21, 2009, 1:08 PM

Post #11 of 34 (861 views)
Permalink

RE: Maemo-Optify & Builder Bots = Broken? [In reply to]

Ed,

Here is my output. Looking through the list I do not appear to he
-cputransp and -maemo3

ii scratchbox-core 1.0.16
Scratchbox base system
ii scratchbox-devkit-apt-https 1.0.10
APT HTTPS devkit for Scratchbox
ii scratchbox-devkit-debian 1.0.10
Debian tools for Scratchbox
ii scratchbox-devkit-doctools 1.0.13
Doctools for Scratchbox
ii scratchbox-devkit-git 1.0.1
Git for Scratchbox
ii scratchbox-devkit-perl 1.0.4
Perl modules for Scratchbox
ii scratchbox-devkit-qemu 0.10.0-0sb5
Qemu scratchbox devkit
ii scratchbox-devkit-svn 1.0
Subversion devkit for Scratchbox
ii scratchbox-libs 1.0.16
Scratchbox libraries
ii scratchbox-toolchain-cs2007q3-glibc2.5-arm7 1.0.12-10
cs2007q3-glibc2.5-arm7 compiler for Scratchb
ii scratchbox-toolchain-cs2007q3-glibc2.5-i486 1.0.12-8
cs2007q3-glibc2.5-i486 compiler for Scratchb
ii scratchbox-toolchain-host-gcc 1.0.16
Scratchbox host-gcc toolchain

Nathan.

>
Looks the same as in autobuilder environment.

Can you show versions of scratchbox packages?
This is what I have on autobuilder host:
$ dpkg -l |grep scratchbox
ii scratchbox-core 1.0.16
Scratchbox base system
ii scratchbox-devkit-apt-https 1.0.10
APT HTTPS devkit for Scratchbox
ii scratchbox-devkit-cputransp 1.0.9
CPU transparency methods
ii scratchbox-devkit-debian 1.0.10
Debian tools for Scratchbox
ii scratchbox-devkit-doctools 1.0.13
Doctools for Scratchbox
ii scratchbox-devkit-git 1.0.1
Git for Scratchbox
ii scratchbox-devkit-maemo3 1.0.3
Maemo 3 devkit for Scratchbox
ii scratchbox-devkit-perl 1.0.4
Perl modules for Scratchbox
ii scratchbox-devkit-qemu 0.10.0-0sb5
Qemu scratchbox devkit
ii scratchbox-devkit-svn 1.0
Subversion devkit for Scratchbox
ii scratchbox-libs 1.0.16
Scratchbox libraries
ii scratchbox-toolchain-cs2005q3.2-glibc2.5-arm 1.0.7.2
cs2005q3.2-glibc2.5-arm compiler for Scratch
ii scratchbox-toolchain-cs2005q3.2-glibc2.5-i386 1.0.7
cs2005q3.2-glibc2.5-i386 compiler for Scratc
ii scratchbox-toolchain-cs2007q3-glibc2.5-arm7 1.0.12-10
cs2007q3-glibc2.5-arm7 compiler for Scratchb
ii scratchbox-toolchain-cs2007q3-glibc2.5-i486 1.0.12-8
cs2007q3-glibc2.5-i486 compiler for Scratchb
ii scratchbox-toolchain-host-gcc 1.0.16
Scratchbox host-gcc toolchain

--
BR,
Ed

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

nathan at andersonsplace

Oct 21, 2009, 1:14 PM

Post #12 of 34 (864 views)
Permalink

RE: Maemo-Optify & Builder Bots = Broken? [In reply to]

Ed,

Just tried on the armel target.

[sbox-FREMANTLE_ARMEL: ~] > apt-get install clucene-core clucene-core-dev
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
clucene-core clucene-core-dev
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1043kB of archives.
After unpacking 5292kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
clucene-core clucene-core-dev
Install these packages without verification [y/N]? y
Get:1 http://repository.maemo.org fremantle/free clucene-core
0.9.21b-0maemo1 [319kB]
Get:2 http://repository.maemo.org fremantle/free clucene-core-dev
0.9.21b-0maemo1 [725kB]
Fetched 1043kB in 3s (312kB/s)
/scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such file
or directory
Selecting previously deselected package clucene-core.
(Reading database ... 27948 files and directories currently installed.)
Unpacking clucene-core (from .../clucene-core_0.9.21b-0maemo1_armel.deb) ...
Selecting previously deselected package clucene-core-dev.
Unpacking clucene-core-dev (from
.../clucene-core-dev_0.9.21b-0maemo1_armel.deb) ...
Setting up clucene-core (0.9.21b-0maemo1) ...
Setting up clucene-core-dev (0.9.21b-0maemo1) ...

As you can see no issues.

---

In the meantime I had also posted on Talk; and just got confirmation that
both clucene-core and clucene-core-dev installed fine on a real n900.
http://talk.maemo.org/showthread.php?p=354509

Nathan.

-----Original Message-----
From: Ed Bartosh [mailto:bartosh [at] gmail]
Sent: Wednesday, October 21, 2009 3:00 PM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
Subject: Re: Maemo-Optify & Builder Bots = Broken?

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> 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
>
> ls -l /targets/FREMANTLE_X86 | grep opt
> drwxr-xr-x 4 maemo sbox 4096 Oct 7 11:39 opt
>
Oops, sorry. I've overlooked that you're using X86 target.
Autobuilder used armel target when it failed. You can see it here:
https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/armel.root.l
og.FAILED.txt

Try to install your packages in armel target, please.

--
BR,
Ed

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 21, 2009, 1:21 PM

Post #13 of 34 (865 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Mine is installing normally in the armel target and on the device. Here is
the output from apt-get on the device /don't mind the broken xournal/:

Nokia-N900-41-10:~# apt-get install libwebkit-1.0-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
libwebkit-1.0-1
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
Need to get 4009kB/4190kB of archives.
After this operation, 12,6MB of additional disk space will be used.
Get:1 http://repository.maemo.org fremantle/non-free libwebkit-1.0-1
1.0-svn41137-15 [4009kB]
Fetched 4009kB in 7s
(519kB/s)

(Reading database ... 26333 files and directories currently installed.)
Preparing to replace xournal 0.4.2.1-1fremantle10 (using
.../xournal_0.4.2.1-1fremantle10_armel.deb) ...
Unpacking replacement xournal ...
Unknown media type in type 'sketch/png'

gtk-update-icon-cache: Failed to open file
/usr/share/icons/hicolor/.icon-theme.cache : File exists
dpkg: warning - old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Unknown media type in type 'sketch/png'

gtk-update-icon-cache: Failed to open file
/usr/share/icons/hicolor/.icon-theme.cache : File exists
dpkg: error processing
/var/cache/apt/archives/xournal_0.4.2.1-1fremantle10_armel.deb (--unpack):
subprocess new post-removal script returned error exit status 1
Unknown media type in type 'sketch/png'

gtk-update-icon-cache: Failed to open file
/usr/share/icons/hicolor/.icon-theme.cache : File exists
dpkg: error while cleaning up:
subprocess post-removal script returned error exit status 1
Selecting previously deselected package libwebkit-1.0-1.
Unpacking libwebkit-1.0-1 (from
.../libwebkit-1.0-1_1.0-svn41137-15_armel.deb) ...
Errors were encountered while processing:
/var/cache/apt/archives/xournal_0.4.2.1-1fremantle10_armel.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

It is optified and working fine after that.

I can provide other output as well.

Regards:
Bundyo

On Wed, Oct 21, 2009 at 10:59 PM, Ed Bartosh <bartosh [at] gmail> wrote:

> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> > 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
> >
> > ls -l /targets/FREMANTLE_X86 | grep opt
> > drwxr-xr-x 4 maemo sbox 4096 Oct 7 11:39 opt
> >
> Oops, sorry. I've overlooked that you're using X86 target.
> Autobuilder used armel target when it failed. You can see it here:
>
> https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/armel.root.log.FAILED.txt
>
> Try to install your packages in armel target, please.
>
> --
> BR,
> Ed
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

bartosh at gmail

Oct 21, 2009, 2:03 PM

Post #14 of 34 (863 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> 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
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

nathan at andersonsplace

Oct 21, 2009, 2:39 PM

Post #15 of 34 (861 views)
Permalink

RE: Maemo-Optify & Builder Bots = Broken? [In reply to]

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:bartosh [at] gmail]
Sent: Wednesday, October 21, 2009 4:03 PM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
Subject: Re: Maemo-Optify & Builder Bots = Broken?

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> 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
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 21, 2009, 2:39 PM

Post #16 of 34 (860 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Hmm, yes, that seems to be the problem. In the final SDK /opt is a symlink
but in the latest beta SDK it is not. I didn't upgrade my development
machine, but I have the final on another so I can compare. I'll report back
if successful.

Regards:
Bundyo

On Thu, Oct 22, 2009 at 12:03 AM, Ed Bartosh <bartosh [at] gmail> wrote:

> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> > 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
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

bundyo at gmail

Oct 21, 2009, 2:52 PM

Post #17 of 34 (861 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

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 <nathan [at] andersonsplace
> 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:bartosh [at] gmail]
> Sent: Wednesday, October 21, 2009 4:03 PM
> To: Nathan Anderson
> Cc: maemo-developers [at] maemo
> Subject: Re: Maemo-Optify & Builder Bots = Broken?
>
> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> > 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
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

bundyo at gmail

Oct 21, 2009, 4:14 PM

Post #18 of 34 (861 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

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 <bundyo [at] gmail> wrote:

> Nah, that's not enough. Still fails.
>
> Regards:
> Bundyo
>
>
> On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <bundyo [at] gmail> 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 <
>> nathan [at] andersonsplace> 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:bartosh [at] gmail]
>>> Sent: Wednesday, October 21, 2009 4:03 PM
>>> To: Nathan Anderson
>>> Cc: maemo-developers [at] maemo
>>> Subject: Re: Maemo-Optify & Builder Bots = Broken?
>>>
>>> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
>>> > 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
>>> maemo-developers [at] maemo
>>> https://lists.maemo.org/mailman/listinfo/maemo-developers
>>>
>>
>>
>

nathan at andersonsplace

Oct 21, 2009, 4:35 PM

Post #19 of 34 (848 views)
Permalink

RE: Maemo-Optify & Builder Bots = Broken? [In reply to]

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:bundyo [at] gmail]
Sent: Wednesday, October 21, 2009 6:14 PM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
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 <bundyo [at] gmail> wrote:

Nah, that's not enough. Still fails.

Regards:
Bundyo

On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <bundyo [at] gmail> 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
<nathan [at] andersonsplace> 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:bartosh [at] gmail]

Sent: Wednesday, October 21, 2009 4:03 PM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
Subject: Re: Maemo-Optify & Builder Bots = Broken?

2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> 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
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 21, 2009, 11:36 PM

Post #20 of 34 (840 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

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
<nathan [at] andersonsplace>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:bundyo [at] gmail]
> *Sent:* Wednesday, October 21, 2009 6:14 PM
>
> *To:* Nathan Anderson
> *Cc:* maemo-developers [at] maemo
> *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 <bundyo [at] gmail> wrote:
>
>> Nah, that's not enough. Still fails.
>>
>> Regards:
>> Bundyo
>>
>>
>> On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <bundyo [at] gmail> 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 <
>>> nathan [at] andersonsplace> 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:bartosh [at] gmail]
>>>> Sent: Wednesday, October 21, 2009 4:03 PM
>>>> To: Nathan Anderson
>>>> Cc: maemo-developers [at] maemo
>>>> Subject: Re: Maemo-Optify & Builder Bots = Broken?
>>>>
>>>> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
>>>> > 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
>>>> maemo-developers [at] maemo
>>>> https://lists.maemo.org/mailman/listinfo/maemo-developers
>>>>
>>>
>>>
>>
>

bartosh at gmail

Oct 21, 2009, 11:37 PM

Post #21 of 34 (841 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

2009/10/22 Kamen Bundev <bundyo [at] gmail>:
> Hmm, yes, that seems to be the problem. In the final SDK /opt is a symlink
> but in the latest beta SDK it is not. I didn't upgrade my development
> machine, but I have the final on another so I can compare. I'll report back
> if successful.
>
You're right.
Autobuilder uses latest SDK and /opt is in the rootstrap:
tar -ztf /scratchbox/packages/maemo-sdk-rootstrap_5.0_armel.tgz | grep '^\./opt'
./opt

I removed it from there and now packages with /opt directory should be
installable.
Try to re-upload your packages to autobuilder. It should work now.

Thank you for your help.

PS: Is someone willing to file a bug for SDK :) ?

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bartosh at gmail

Oct 21, 2009, 11:38 PM

Post #22 of 34 (841 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Hi,

Please read my last message. The issue is fixed. Nobody should do
anything except of SDK guys.

2009/10/22 Kamen Bundev <bundyo [at] gmail>:
> 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 <nathan [at] andersonsplace>
> 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:bundyo [at] gmail]
>> Sent: Wednesday, October 21, 2009 6:14 PM
>> To: Nathan Anderson
>> Cc: maemo-developers [at] maemo
>> 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 <bundyo [at] gmail> wrote:
>>>
>>> Nah, that's not enough. Still fails.
>>>
>>> Regards:
>>> Bundyo
>>>
>>> On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <bundyo [at] gmail> 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
>>>> <nathan [at] andersonsplace> 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:bartosh [at] gmail]
>>>>> Sent: Wednesday, October 21, 2009 4:03 PM
>>>>> To: Nathan Anderson
>>>>> Cc: maemo-developers [at] maemo
>>>>> Subject: Re: Maemo-Optify & Builder Bots = Broken?
>>>>>
>>>>> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
>>>>> > 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
>>>>> maemo-developers [at] maemo
>>>>> https://lists.maemo.org/mailman/listinfo/maemo-developers
>>>>
>>>
>>
>
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>
>

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 21, 2009, 11:40 PM

Post #23 of 34 (843 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Yup, just read it :) Thanks.

Regards:
Bundyo

On Thu, Oct 22, 2009 at 9:38 AM, Ed Bartosh <bartosh [at] gmail> wrote:

> Hi,
>
> Please read my last message. The issue is fixed. Nobody should do
> anything except of SDK guys.
>
> 2009/10/22 Kamen Bundev <bundyo [at] gmail>:
> > 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 <
> nathan [at] andersonsplace>
> > 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:bundyo [at] gmail]
> >> Sent: Wednesday, October 21, 2009 6:14 PM
> >> To: Nathan Anderson
> >> Cc: maemo-developers [at] maemo
> >> 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 <bundyo [at] gmail> wrote:
> >>>
> >>> Nah, that's not enough. Still fails.
> >>>
> >>> Regards:
> >>> Bundyo
> >>>
> >>> On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <bundyo [at] gmail>
> 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
> >>>> <nathan [at] andersonsplace> 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:bartosh [at] gmail]
> >>>>> Sent: Wednesday, October 21, 2009 4:03 PM
> >>>>> To: Nathan Anderson
> >>>>> Cc: maemo-developers [at] maemo
> >>>>> Subject: Re: Maemo-Optify & Builder Bots = Broken?
> >>>>>
> >>>>> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> >>>>> > 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
> >>>>> maemo-developers [at] maemo
> >>>>> https://lists.maemo.org/mailman/listinfo/maemo-developers
> >>>>
> >>>
> >>
> >
> >
> > _______________________________________________
> > maemo-developers mailing list
> > maemo-developers [at] maemo
> > https://lists.maemo.org/mailman/listinfo/maemo-developers
> >
> >
>
>
>
> --
> BR,
> Ed
>

bartosh at gmail

Oct 22, 2009, 12:17 AM

Post #24 of 34 (840 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Hi,

I restarted Nathan's build and autobuilder seems to be able to install
all build-deps.
You can see autobuilder logs here soon:
https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/

2009/10/22 Ed Bartosh <bartosh [at] gmail>:
> Hi,
>
> Please read my last message. The issue is fixed. Nobody should do
> anything except of SDK guys.
>
> 2009/10/22 Kamen Bundev <bundyo [at] gmail>:
>> 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 <nathan [at] andersonsplace>
>> 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:bundyo [at] gmail]
>>> Sent: Wednesday, October 21, 2009 6:14 PM
>>> To: Nathan Anderson
>>> Cc: maemo-developers [at] maemo
>>> 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 <bundyo [at] gmail> wrote:
>>>>
>>>> Nah, that's not enough. Still fails.
>>>>
>>>> Regards:
>>>> Bundyo
>>>>
>>>> On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <bundyo [at] gmail> 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
>>>>> <nathan [at] andersonsplace> 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:bartosh [at] gmail]
>>>>>> Sent: Wednesday, October 21, 2009 4:03 PM
>>>>>> To: Nathan Anderson
>>>>>> Cc: maemo-developers [at] maemo
>>>>>> Subject: Re: Maemo-Optify & Builder Bots = Broken?
>>>>>>
>>>>>> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
>>>>>> > 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
>>>>>> maemo-developers [at] maemo
>>>>>> https://lists.maemo.org/mailman/listinfo/maemo-developers
>>>>>
>>>>
>>>
>>
>>
>> _______________________________________________
>> maemo-developers mailing list
>> maemo-developers [at] maemo
>> https://lists.maemo.org/mailman/listinfo/maemo-developers
>>
>>
>
>
>
> --
> BR,
> Ed
>

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 22, 2009, 12:21 AM

Post #25 of 34 (838 views)
Permalink

Re: Maemo-Optify & Builder Bots = Broken? [In reply to]

Yes, mine too, though failed because of missing mce dep afterwards :)

Regards:
Bundyo

On Thu, Oct 22, 2009 at 10:17 AM, Ed Bartosh <bartosh [at] gmail> wrote:

> Hi,
>
> I restarted Nathan's build and autobuilder seems to be able to install
> all build-deps.
> You can see autobuilder logs here soon:
> https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/
>
> 2009/10/22 Ed Bartosh <bartosh [at] gmail>:
> > Hi,
> >
> > Please read my last message. The issue is fixed. Nobody should do
> > anything except of SDK guys.
> >
> > 2009/10/22 Kamen Bundev <bundyo [at] gmail>:
> >> 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 <
> nathan [at] andersonsplace>
> >> 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:bundyo [at] gmail]
> >>> Sent: Wednesday, October 21, 2009 6:14 PM
> >>> To: Nathan Anderson
> >>> Cc: maemo-developers [at] maemo
> >>> 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 <bundyo [at] gmail>
> wrote:
> >>>>
> >>>> Nah, that's not enough. Still fails.
> >>>>
> >>>> Regards:
> >>>> Bundyo
> >>>>
> >>>> On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev <bundyo [at] gmail>
> 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
> >>>>> <nathan [at] andersonsplace> 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:bartosh [at] gmail]
> >>>>>> Sent: Wednesday, October 21, 2009 4:03 PM
> >>>>>> To: Nathan Anderson
> >>>>>> Cc: maemo-developers [at] maemo
> >>>>>> Subject: Re: Maemo-Optify & Builder Bots = Broken?
> >>>>>>
> >>>>>> 2009/10/21 Nathan Anderson <nathan [at] andersonsplace>:
> >>>>>> > 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
> >>>>>> maemo-developers [at] maemo
> >>>>>> https://lists.maemo.org/mailman/listinfo/maemo-developers
> >>>>>
> >>>>
> >>>
> >>
> >>
> >> _______________________________________________
> >> maemo-developers mailing list
> >> maemo-developers [at] maemo
> >> https://lists.maemo.org/mailman/listinfo/maemo-developers
> >>
> >>
> >
> >
> >
> > --
> > BR,
> > Ed
> >
>
>
>
> --
> BR,
> Ed
>

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads