You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
require'rubygems'require'archive/tar/minitar'file="Amazon.com- Mind Performance Hacks- Tips & Tools for Overclocking Your Brain (Hacks)- Books- RonHale-Evans.webloc"out=Archive::Tar::Minitar::Output.new("compress.tar")Archive::Tar::Minitar::pack_file(file,out)out.close
I get the errors as seen below:
/opt/local/lib/ruby/gems/1.8/gems/archive-tar-minitar-0.5.2/lib/archive/tar/minitar.rb:432:in `split_name': undefined
method `size' for nil:NilClass (NoMethodError)
from /opt/local/lib/ruby/gems/1.8/gems/archive-tar-minitar-0.5.2/lib/archive/tar/minitar.rb:430:in `loop'
from /opt/local/lib/ruby/gems/1.8/gems/archive-tar-minitar-0.5.2/lib/archive/tar/minitar.rb:430:in `split_name'
from /opt/local/lib/ruby/gems/1.8/gems/archive-tar-minitar-0.5.2/lib/archive/tar/minitar.rb:329:in `add_file_simple'
from /opt/local/lib/ruby/gems/1.8/gems/archive-tar-minitar-0.5.2/lib/archive/tar/minitar.rb:914:in `pack_file'
from compress.rb:34
Something seems to be wrong with the filename of my file.
The script I used and the file to be compressed are under the same directory.
archive-tar-minitar (0.5.2)
ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]
The text was updated successfully, but these errors were encountered:
Note that this will still error out, but it will now correctly raise Archive::Tar::Minitar::FileNameTooLong. The filename is 114 characters long in the example provided; in default tar behaviour, files can only be 100 characters long.
Submitted by Takaaki Kato (http://rubyforge.org/users/samuraicoder)
I was running the following script.
I get the errors as seen below:
Something seems to be wrong with the filename of my file.
The script I used and the file to be compressed are under the same directory.
archive-tar-minitar (0.5.2)
ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]
The text was updated successfully, but these errors were encountered: