Comment 1 Quim Gil 2009-03-23 16:27:10 UTC

did you install the pre-alpha 2 or the alpha?

Also, are you aware x86 is not officially supported? There are some workarounds
here in b.m.o (can't find them now since I'm on the go.

(In reply to comment #1)
> did you install the pre-alpha 2 or the alpha?

Sorry, alpha of course. Seems I took the wrong version by accident.

> Also, are you aware x86 is not officially supported? There are some workarounds
> here in b.m.o (can't find them now since I'm on the go.

Hmm, does this mean I can only use the arm target in scratchbox? Didn't know
that...

Comment 3 Ryan Abel 2009-03-24 10:12:40 UTC

Same issue here, same setup.

ryan@Minerva:~/Documents$ scratchbox apt-get -f install
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
/scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such file or
directory
Setting up makedev (2.3.2~2.3.1-80osso9) ...
/scratchbox/devkits/debian-etch/bin/invoke-rc.d: line 1: /sbin/runlevel: No
such file or directory
/scratchbox/tools/bin/ln: creating symbolic link `/dev/MAKEDEV' to
`/sbin/MAKEDEV': Permission denied
invoke-rc.d: initscript makedev, action "start" failed.
dpkg: error processing makedev (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of maemo-core-runtime:
 maemo-core-runtime depends on makedev; however:
  Package makedev is not configured yet.
dpkg: error processing maemo-core-runtime (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maemo-core-dev:
 maemo-core-dev depends on maemo-core-runtime (= 0.6); however:
  Package maemo-core-runtime is not configured yet.
dpkg: error processing maemo-core-dev (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maemo-sdk-runtime:
 maemo-sdk-runtime depends on maemo-core-runtime; however:
  Package maemo-core-runtime is not configured yet.
dpkg: error processing maemo-sdk-runtime (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maemo-sdk-dev:
 maemo-sdk-dev depends on maemo-sdk-runtime (= 1.7); however:
  Package maemo-sdk-runtime is not configured yet.
 maemo-sdk-dev depends on maemo-core-dev; however:
  Package maemo-core-dev is not configured yet.
dpkg: error processing maemo-sdk-dev (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 makedev
 maemo-core-runtime
 maemo-core-dev
 maemo-sdk-runtime
 maemo-sdk-dev
E: Sub-process /scratchbox/devkits/debian-etch/bin/dpkg returned an error code
(1)

OK, I tried again installing intrepid instead of jaunty into the virtual
machine and this time the installation succeeded. This error message is still
present though it seems unrelated:

/scratchbox/devkits/debian-etch/bin/invoke-rc.d: line 1: /sbin/runlevel: No
such file or directory


So, to conclude, this seems to be a problem in jaunty or the scratchbox version
that jaunty ships.

Comment 5 Janne Johansson 2009-03-25 10:39:32 UTC

I just tried to install the maemo 5.0 alpha on Ubuntu Jaunty and for me the
installation worked fine. Was the installation script used by the bug filer and
is this still a problem for anyone?

For comment #3 I can only say that using apt without fakeroot will fail with
certain packages.

Comment 6 Ryan Abel 2009-03-25 12:43:50 UTC

(In reply to comment #5)
> For comment #3 I can only say that using apt without fakeroot will fail with
> certain packages.
> 

It failed just as spectacularly with the installation script.

Comment 7 Janne Johansson 2009-03-25 14:05:17 UTC

Ryan, could you try to remove the rootstraps from the sb home directory and try
the installation again. Also I'd like to know the versions of the sb packages
you are using, just in case I have a different environment set up on my Jaunty
machine.

Comment 8 Janne Johansson 2009-03-31 14:49:22 UTC

OK, the problem seem pretty clear now.

When installing the makedev package, the post installation script tries to
create a symlink /dev/MAKEDEV that points to /sbin/MAKEDEV (that much was clear
already). The /dev is shared with the host side so obviously the sb side
doesn't have rights to make modifications and when it tries to it fails.

The reason it didn't occur before or even now on my machine is that the symlink
in question was there already in Debian based systems and systems upgraded to
Jaunty but not in fresh installations of Jaunty. I'm assuming that people with
problems had fresh installations, right?

I don't think we'll fix this for alpha, since beta is getting closer. Makedev
seems kinda obsolete, so we'll try to drop it before beta or fix it if dropping
is out of the question. Until then I assume that creating that symlink manually
on the host side will be a good enough workaround.

Comment 9 Janne Johansson 2009-04-17 11:06:24 UTC

Fixed for beta.

(In reply to comment #9)
> Fixed for beta.
> 

 liblocation-dev
 rtcom-accounts-ui
 librtcom-accounts-ui-client-dev
 libosso-abook-dev
 librtcom-accounts-ui-dev
 librtcom-accounts-widgets-dev
 osso-applet-textinput
 osso-bookmark-engine-dev
 ui-fonts
 librtcom-eventlogger-ui0
 librtcom-eventlogger-ui-dev
 nokia-binaries
E: Sub-process /scratchbox/devkits/debian-etch/bin/dpkg returned an error code
(1)

getting the same error for Ubuntu 64 bit 9.01.

Comment 11 Andre Klapper 2009-10-17 13:52:58 UTC

(In reply to comment #10)
> getting the same error for Ubuntu 64 bit 9.01.

Unhelp without knowing the exact steps before. Also, 9.01 does not exist.