search for: ustar

...at the tar format used by SMBCLIENT only supports a 100 character path name. Some of the new Microsoft Software generates longer file names. This causes an error when you attempt to write these files out to the tar device. I have developed a patch that will cause SMBCLIENT to write these files in USTAR format (an extension of tar format). These USTAR files should be fairly portable, our sun systems seems to be able to read them with no problem. I guess I would like to know, would this patch (which is currently based on 1_9_16p11) be useful to the Samba community? If so, what should I do with i...

...r/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... no checking whether make supports nested variables... no checking whether UID '1492654' is supported by ustar format... yes checking whether GID '1049089' is supported by ustar format... yes checking how to create a ustar tar archive... pax checking for style of include used by make... none checking for gcc... cl -nologo checking whether the C compiler works... no configure: error: in `/d/xapian_pr...

...r/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... no checking whether make supports nested variables... no checking whether UID '1492654' is supported by ustar format... yes checking whether GID '1049089' is supported by ustar format... yes checking how to create a ustar tar archive... pax checking for style of include used by make... none checking for gcc... cl -nologo checking whether the C compiler works... yes checking for C compiler default o...

Hello, I try to compile pigeonhole ( hg clone from yesterday ) on SLES9 I get the following error: ---- snip cd dovecot-2.0-pigeonhole ./autogen.sh configure.in:17: option `tar-ustar' not recognized autoreconf: automake failed with exit status: 1 --- snap automake-1.8.3 autoconf-2.59 I found something similar here: http://osdir.com/ml/science.robotics.orocos.devel/2006-03/msg00029.html "It seems this option (tar-ustar) is automake 1.9 only" Is the a workaround...

I just downloaded 2.04a, and when attempting to examine it, I received: [...] -rwxr-xr-x 1 1002 1002 282323 May 17 16:27 samba-2.0.4a/source/configure tar: End of archive volume 1 reached tar: ustar vol 1, 687 files, 10711040 bytes read. ATTENTION! tar archive volume change required. Ready for archive volume: 2 Input archive name or "." to quit tar. Archive name > . Quitting tar! tar: Premature end of file on archive read Doesn't look like a download problem... Mine: 21422...

On Wed, Mar 07, 2007 at 11:22:36PM +0000, olly wrote: > docs/Makefile.am: Stop shipping docs/apidoc/latex/* in the > xapian-core tarballs since it's just useless bloat. Removing it > more than halves the size of the tarball (55% reduction!) Hmm, this is very odd. I tried unpacking the last xapian-core snapshot tarball, deleting the junk files, and rebuilding the tarball, and I got

...None - in - let ret = - if get 0 6 = Some "\2537zXZ\000" then `XZ - else if get 0 4 = Some "PK\003\004" then `Zip - else if get 0 4 = Some "PK\005\006" then `Zip - else if get 0 4 = Some "PK\007\008" then `Zip - else if get 257 6 = Some "ustar\000" then `Tar - else if get 257 8 = Some "ustar\x20\x20\000" then `Tar - else if get 0 2 = Some "\x1f\x8b" then `GZip - else `Unknown in - close_in chan; - ret + with_open_in filename ( + fun chan -> + let get start size = + try + see...

Hi, I am unable to build the letor module. I am generating the configure file using autoconf. The configure file generated is throwing the error ./configure: line 2057: syntax error near unexpected token `1.10.1' ./configure: line 2057: `AM_INIT_AUTOMAKE(1.10.1 -Wportability tar-ustar)` I am not too sure what to do with this. Need help with this. Thank You Regards Karthik On Mon, Sep 29, 2014 at 7:17 PM, karthik iyer <karthikiyer2000 at gmail.com> wrote: > Ok sorry, my bad. Just checked the INEX 2014 website. I believe that is > where we get the data set from. &g...

...1.14. While tarring my /usr/local/samba in preparation for this I got a number of message about not being able to backup a socket. So I switched and used pax to create the tar archive. I got the same message in addition to the message about not backing up the socket I get messages like this: pax: ustar header field is too small for ./var/locks/sysvol/ ad.heritageacademyaz.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/GPT.INI So my question is -- 1) can the socket file be safely erase I did see the following diff --git a/source4/scripting/bin/samba_backup b/source4/scripting/bin/samba_ba...

...alized constant DEF_INDENTATION c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__'': ./script/../config/../lib/technorati.rb:1: parse error, unexpected tINTEGER, expecting $ (SyntaxError) technorati-ruby/ 0000755 0000000 0000000 00000000000 10377133241 0015243 5 ustar viewcvs viewcvs 0000001 0000000 ^ from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require'' from c:/ruby/lib/ruby/gems/1.8/...

..._ "bundle" anything with GPL that it doesn't require. > like artwork that happens to be on the same disk and there is no > requirement to make it easy to separate the 'merely aggregated' > parts, though. What do you mean by "embedded"? RPM is merely just a USTAR 5KB block size (cpio System-V) archive. Even an ISO9660 "Yellow Book" track (data CD) can be considered an "archive." Do you _really_ want to open up that "subjective" door? At this point, ask the FSF. I think you're just going to argue this until you get the an...

...='#' am__fastdepCC_FALSE='#' am__fastdepCC_TRUE='' am__fastdepCXX_FALSE='#' am__fastdepCXX_TRUE='' am__include='include' am__isrc=' -I$(srcdir)' am__leading_dot='.' am__nodep='_no' am__quote='' am__tar='tar --format=ustar -chf - "$$tardir"' am__untar='tar -xf -' bindir='${exec_prefix}/bin' build='x86_64-unknown-linux-gnu' build_alias='' build_cpu='x86_64' build_os='linux-gnu' build_vendor='unknown' datadir='${datarootdir}' datarootdir='...

I reported the following vulnerability to AUSCERT, but they weren''t interested. People on this list might be, though! GNU tar is lazy about file creation modes and file owners when unpacking a tar file. Because GNU tar defaults to creating files owned by the userid running tar when the username is not found on your system, it can be possible to inadvertantly create setuid root

List, I have attempted to make my own megaraid driver disk for a Dell PowerEdge 2300. The procedure I'm using is detailed at the end of this message. In short, I followed samples that I collected after Googling around. The problem I face is that the CentOS 4 installer can't seem to mount the driver disk after I have created it. It gives no information other than, "Cannot

Hi, I have started getting a hang of the xapian codebase. I think I would like to try my hands on the letor module of xapian. Could you please suggest some free data set for the training and testing of letor features. I am not able to get the INEX data set from anywhere (the one mentioned by parth gupta in his GSOC 2011 projecct. Regards Karthik On Mon, Sep 22, 2014 at 4:23 PM, Olly Betts

Guys recently I had this question asked in a technical interview. How do I find out the package owning a particular file, when no package managers are installed? I am assuimg SRPMs are used to install the software? Is this actually possible? Install the Linux OS without a package manager? I know "rpm -qf filename" gives the package owning the file. But how to get the package name

...opt XAPIAN_CONFIG=/opt/bin/xapian-config checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking...

...opt XAPIAN_CONFIG=/opt/bin/xapian-config checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking...

...opt XAPIAN_CONFIG=/opt/bin/xapian-config checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking...

...R VERSION 2.15.3: NEW FEATURES: o lgamma(x) for very small x (in the denormalized range) is no longer Inf with a warning. o image() now sorts an unsorted breaks vector, with a warning. o The internal methods for tar() and untar() do a slightly more general job for 'ustar'-style handling of paths of more than 100 bytes. o Packages compiler and parallel have been added to the reference index (refman.pdf). o untar(tar = "internal") has some support for pax headers as produced by e.g. gnutar --posix (which seems prevalent on...