forwarded from http://bugs.openembedded.org/show_bug.cgi?id=4145
It seems that when installing a package (with its dependencies automatically
drawn in), the package and the dependencies are configured in alphabetical
order, instead of in dependency order.
Take the following example:
ipkg install nfs-utils
Installing nfs-utils (1.0.6-r7) to root...
Downloading http://***/nfs-utils_1.0.6-r7_mipsel.ipk
Installing kernel-module-nfsd (2.6.12.6-r11) to root...
Downloading http://***/kernel-module-nfsd_2.6.12.6-r11_mipsel.ipk
Installing portmap (5-9-r5) to root...
Downloading http://***/portmap_5-9-r5_mipsel.ipk
Configuring kernel-module-nfsd
Configuring nfs-utils
Adding system startup for /etc/init.d/nfsserver ...
/etc/rc2.d/S20nfsserver -> ../init.d/nfsserver
/etc/rc3.d/S20nfsserver -> ../init.d/nfsserver
creating NFS state directory: done
starting 8 nfsd kernel threads: done
starting mountd: Cannot register service: RPC: Unable to receive; errno =
Connection refused
done
/etc/rc4.d/S20nfsserver -> ../init.d/nfsserver
/etc/rc5.d/S20nfsserver -> ../init.d/nfsserver
/etc/rc0.d/K20nfsserver -> ../init.d/nfsserver
/etc/rc1.d/K20nfsserver -> ../init.d/nfsserver
/etc/rc6.d/K20nfsserver -> ../init.d/nfsserver
Configuring portmap
Adding system startup for /etc/init.d/portmap ...
/etc/rcS.d/S43portmap -> ../init.d/portmap
/etc/rc0.d/S32portmap -> ../init.d/portmap
/etc/rc6.d/S32portmap -> ../init.d/portmap
/etc/rc1.d/K81portmap -> ../init.d/portmap
Attempting to start nfsserver, without a running portmapper, takes a very long
time before it eventually times out.
Tested with ipkg 0.99-163-r8 (but all 0.99 versions show the same behaviour)
Original issue reported on code.google.com by rolf.leg...@gmail.com on 11 Jan 2010 at 1:37
Original issue reported on code.google.com by
rolf.leg...@gmail.com
on 11 Jan 2010 at 1:37