Hello John Baptist!

Thanks for injecting some positive energy into this bug report. The previous 
comments has been really demotivating for me.
I'd like to help clear up some confusion, which will hopefully help you out in 
your quest to find the problem ...

* gvfs (and thus nautilus) uses libarchive, "mount" uses kernel built-in
iso filesystem support, file-roller uses genisoimage (e.g. isoinfo).
Completely separate implementations. Any problems they share or not are
purely by chance. If you want a command-line frontend to libarchive for
testing like you're doing with isoinfo for genisoimage, install bsdtar
and look at the libarchive specific flags in the bsdtar manpage.

* You're right the ;1 is a version appended to the filename in the
image. Rock Ridge is not that common nowadays though. The "Rock Ridge
version numbering scheme", if you can call it that, is also used in
Joliet Extension (which most isos have nowadays for long filenames which
also works on MS Windows).

* Unfortunately sometimes standard documents are a bit vague which
results in different iso creating programs doing things differently,
which means iso readers have to implement all cases. Upstream libarchive
has a test-suite which also tests iso files and all (current) tests
ofcourse passes. This means people who have problems need to report
which program they used to generate the iso and provide a testcase so
the testsuite can be expanded and libarchive support more ways of
writing isos. Comments like "This STILL doesn't work?" are completely
useless, because it works FOR ALL KNOWN testcases. Unless you (the bug
reporter) know which program generated the iso you're having problems
with and are able to provide a testcase, noone will be able to help out.

* Please make sure you're testing with the latest libarchive version
installed, currently 2.8.4-1 (available in maverick atleast).


// Andreas Henriksson, debian maintainer of libarchive.

-- 
Iso's don't mount correctly through 'archive mounter' 
https://bugs.launchpad.net/bugs/299956
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to