UCK build failed

Asked by Karthik Krishnan

I get Build failed error with two lines in the build log stating "No such File or Directory" for SquashFS and iso-source2

I am using UCK v1.4

Please see attached the snippet of the Log.

Checking if unmounting directory /home/msuser1/tmp/remaster-root/lib/modules/2.6.17-10-generic/volatile is necessary...
/home/msuser1/tmp/remaster-root/lib/modules/2.6.17-10-generic/volatile is not a mountpoint
Directory /home/msuser1/tmp/remaster-root/lib/modules/2.6.17-10-generic/volatile not mounted.
Checking if unmounting directory /home/msuser1/tmp/remaster-root/proc is necessary...
/home/msuser1/tmp/remaster-root/proc is not a mountpoint
Directory /home/msuser1/tmp/remaster-root/proc not mounted.
Checking if unmounting directory /home/msuser1/tmp/remaster-root/sys is necessary...
/home/msuser1/tmp/remaster-root/sys is not a mountpoint
Directory /home/msuser1/tmp/remaster-root/sys not mounted.
Checking if unmounting directory /home/msuser1/tmp/remaster-root/dev/pts is necessary...
/home/msuser1/tmp/remaster-root/dev/pts is not a mountpoint
Directory /home/msuser1/tmp/remaster-root/dev/pts not mounted.
Checking if unmounting directory /home/msuser1/tmp/squashfs-source is necessary...
mountpoint: /home/msuser1/tmp/squashfs-source: No such file or directory
Directory /home/msuser1/tmp/squashfs-source not mounted.
Checking if unmounting directory /home/msuser1/tmp/iso-source2 is necessary...
mountpoint: /home/msuser1/tmp/iso-source2: No such file or directory
Directory /home/msuser1/tmp/iso-source2 not mounted.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Customization Kit Edit question
Assignee:
No assignee Edit question
Solved by:
Karthik Krishnan
Solved:
Last query:
Last reply:
Revision history for this message
Krzysztof Lichota (krzysiek-launchpad-ubuntu-com) said :
#1

These lines are irrelevant, the real problem is somewhere else. Please post the full log.

Revision history for this message
Best Karthik Krishnan (me-karthiks) said :
#2

Yes, I too realized and when browsing thru the build log, found the real cause of the problem.

It was due to some wrong entries in the sources.list. After correcting the same, now the build went thru without any problem. Thanks a lot.

A great tool :)