Catalyst showed to me this message: --- Running action sequence: setup_overlay --- Running action sequence: create_iso 9192+0 records in 9192+0 records out 9412608 bytes (9.4 MB) copied, 0.0838082 s, 112 MB/s /usr/lib/catalyst/targets/support/create-iso.sh: line 231: mkdosfs: command not found mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so So, if catalyst needs mkdosfs maybe it would depend on dosfstools or something that check whether you need dosfstools. Reproducible: Always Steps to Reproduce: 1.catalyst -v -f livecd-stage2.spec 2. 3. Expected Results: catalyst should tell you to emerge what you need.
mkdosfs is used only on ia64, and catalyst has a dependency "ia64? ( sys-fs/dosfstools )" which has been in place since 2006. I'm not sure why you hit this problem. Catalyst's dependencies seem correct. It looks like the scope of the bug has been changed to the more generic "we should do run-time checks" for dependency programs, so I suppose this bug should be left open?
(In reply to comment #1) > mkdosfs is used only on ia64, and catalyst has a dependency "ia64? ( > sys-fs/dosfstools )" which has been in place since 2006. > > I'm not sure why you hit this problem. Catalyst's dependencies seem correct. > > It looks like the scope of the bug has been changed to the more generic "we > should do run-time checks" for dependency programs, so I suppose this bug > should be left open? No, this bug should be closed because things are already depped properly. Users installing with --nodeps should be executed and their bugs closed as invalid. Like this.
