I am seeing a little problem when installing by nfs using the network.img floppy on the current cooker (as on the mirror site at Feb 24 0300 UTC).
The server has the cooker path as:
(server):/mirror/mdk/cooker/cooker/i586/Mandrake/RPMS
contrib is located at:
(server):/mirror/mdk/cooker/contrib/i586/
The contrib directory is symbolically linked as:
(server):/mirror/mdk/cooker/cooker/i586/Mandrake/RPMS2
-> ../../../contrib/i586/
This is the same as on the mirror site.When the install starts, and the install path is specified as:
Server: (server) Path: /mirror/mdk/cooker/cooker/i586
... the mount is made as:
(server):/mirror/mdk/cooker/contrib/i586 mounted on /tmp/image
The install proceeds, but gives package errors when it comes to installing anything from the contrib (RPMS2) area (for instance apache-1.3), because the RPMS2 symbolic link to contrib is outside the scope of the mount point.
Install should mount at a higher level, such as:
(server):/mirror/mdk/cooker/ mounted on /tmp/image/cooker/i586
and then: cooker would be found at /tmp/image/coooker/i586/Mandrake
and contribs would be properly found at /tmp/image/contrib/i586 (via the symbolic link from RPMS2)
*Or* should we be possibly be specifying a different directory path originally, such that the installer would be able to figure this out properly?
Of course it is possible to work around this by moving contrib around to get rid of the RPMS2 backward symbolic link just before installation, and restoring it afterwards so that the mirroring still works, but it would be better to have things "just work" using the directory structure on the mirrors...
Thanks for any ideas on this one...
Alvin
