Hi, Dan, this is where the terrific logstash source meets the (us)tar limitation of 100 chars for the file name (patch filename is 109 chars). See pax(1).
On 08/18, dan mclaughlin wrote: > i make my own snapshots tarballs after cvs, and just noticed this (though it > is nothing new apparently): > > ... > ports/sysutils/logstash/logstash/patches/patch-bin_logstash_lib_sh > ports/sysutils/logstash/logstash/patches/patch-vendor_bundle_jruby_1_9_gems_logs > tash-core-1_5_3-java_lib_logstash_patches_stronger_openssl_defaults_rb > tar: File name too long for ustar > ports/sysutils/logstash/logstash/patches/patch > -vendor_bundle_jruby_1_9_gems_logstash-core-1_5_3-java_lib_logstash_patches_stro > nger_openssl_defaults_rb > ports/sysutils/logstash/logstash/pkg > ... > > i checked a ports.tar.gz snapshot and this is not a local problem. > > don't know if this is actually considered an issue since cvs is the preferred > method of updating, and it may be difficult to fix based on how the patch > names are generated, but thought i'd bring it to others' attention in case > it was missed, as this does effect what is on the cds as well. -- With best regards, Pavel Korovin
