There is a really simple solution for your problem: Install revent
original software.
The problem you describe has been fixed 4 years ago.
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a memb
The bug (message from gneisoimage) is still there on gnomebaker from
ubuntu 10.10.
There is an option in gnomebaker GUI that says 'Ignore directories too
deep'. However if you select the option, it does not stay on.
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launc
Fist a note: the problem was not found in mkisofs but in genisoimage.
The problem has however been in mkisofs too and as genisoimage is just
a very old version of mkisofs, it suffers from the problem.
While mkisofs did fix the related problem by rewriting major parts of the
code in October 2006 (
Hi Steve,
You can get an updated version of Brasero from getdeb.net:
http://www.getdeb.net/app/Brasero
This solved the problem for me.
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a member
I got here by following the duplicate bug#89012, which is what bit me,
on Intrepid.
This is pretty nasty. I'm just trying to back up some software:
$ mkisofs -JR -V "WinBackup" -o win.img /media/windows/
I: -input-charset not specified, using utf-8 (detected in locale settings)
genisoimage: Dire
This bug is still present in Intrepid. I have the following packages:
genisoimage: 1.1.8-1ubuntu1
gnomebaker: 6.4-1
Same problem also occurs with Brasero, 0.8.2-0ubuntu1
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug no
It was fixed in the latest version.
http://sourceforge.net/forum/forum.php?forum_id=837187
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Should be fixed for Intrepid
http://launchpad.net/distros/ubuntu/intrepid/+source/cdrkit/9:1.1.8-1ubuntu1
** Changed in: cdrkit (Ubuntu)
Assignee: (unassigned) => Matthias Klose (doko)
Status: New => Fix Released
--
genisoimage error "directories too deep" using Rock Ridge
https://b
Automatic merging from debian found a conflict:
http://merges.ubuntu.com/c/cdrkit/REPORT
(debian has 1.1.8 now)
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Perhaps this is fixed in cdrkit 1.1.7, from the changelog:
cdrkit (1.1.7) RELEASED; urgency=low
[ Harald Hoyer ]
* lots of fixes to prevent gcc warnings
* Fix for Joliet directory length bug in genisoimage
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad
This is of cource not a bug in GnomeBaker but in genisoimage from
cdrkit, changing.
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: gnomebaker => cdrkit
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification becaus
I'm in Arch Don't Panic, XFCE 4.4.2, with GnomeBaker 0.6.2. Taking
things to make a backup... when i burn on, it fails:
Executing 'mkisofs -gui -V ex-pen -A GnomeBaker -p My Complete Name -iso-level
3 -l -r -hide-rr-moved -J -joliet-long -graft-points --path-list
/tmp/GnomeBaker-user/gnomebaker-
This bug is still present in Ubuntu 7.10 Gutsy with GnomeBaker 0.6.2.
Changing the backend to "wodim" doesn't solve the problem.
No progress has been made with the bug on Sourceforge.net tracker
(http://sourceforge.net/tracker/index.php?func=detail&aid=1605160&group_id=127397&atid=708499)
This
In GnomeBaker 0.6.2 you can choose which backend to use in
the Advanced tab of the preferences dialog.
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
ryanmbruce <[EMAIL PROTECTED]> writes:
> Unfortunately, both my ubuntu computers have failed with hardware
> problems, so I can't try installing mkisofs ATM, but would gnomebaker
> automatically use mkisofs/cdrtools instead of genisoimage/cdrkit? Is
> there any thing else needed to make this swit
Well shucks...
Reinhard,
Unfortunately, both my ubuntu computers have failed with hardware problems, so
I can't try installing mkisofs ATM, but would gnomebaker automatically use
mkisofs/cdrtools instead of genisoimage/cdrkit? Is there any thing else needed
to make this switch?
Cheers,
-Ryan
The pointer you added contains claims from laymen not from lawyers.
Lawyers do not see a problem.
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
Hmm... That thread seemed slightly divisive. I wonder if there has
been any change of heart? I'm probably antagonizing the situation and
making a fool of myself in the name of futility, but Jörg, would you
be willing to reconsider the use of CDDL to have your wonderful
software put back into the
ryanmbruce <[EMAIL PROTECTED]> writes:
> So I guess the question is why does Ubuntu use genisoimage instead of
> mkisofs? What was the reasoning behind moving away from mkisofs and
> migrating to genisoimage?
Because of licencing issues. If you are using gutsy, you can find
a reasonably recent v
Ouch! I really care about GPL too.what's a boy to do?
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
It's all about licensing.
See this message
http://lists.debian.org/debian-devel-announce/2006/09/msg2.html
for the reasoning about the fork.
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are
So I guess the question is why does Ubuntu use genisoimage instead of
mkisofs? What was the reasoning behind moving away from mkisofs and
migrating to genisoimage?
Cheers,
-Ryan
On 8/29/07, Schily <[EMAIL PROTECTED]> wrote:
> You are most likely not using mkisofs but a defective fork called
> "g
You are most likely not using mkisofs but a defective fork called
"genisoimage". It is based on a 2+ year old mkisofs version with additional
bugs added.
The problem you describe is a well known bug from older mkisofs versions
that happens with the specific command line you are using. As ther
It's certainly a bug in genisoimage.
You can reproduce by doing the following:
1 - create a file (let's name it pathlist) with the following contents:
/a/b/c/d/e/f/g/h/a.txt=a.txt
2 - execute this command:
genisoimage -o a.iso -graft-points -path-list pathlist
You'll get this output:
genisoim
This bug has also been filed in cdrtools, but I'm unsure of where it
actually lies.
https://bugs.launchpad.net/ubuntu/+source/cdrtools/+bug/89012
Any help sorting our the true source would be helpful.
Cheers,
-Ryan
--
genisoimage error "directories too deep" using Rock Ridge
https://bugs.launc
25 matches
Mail list logo
