search for: untarring

Hello, I'm running some code that requires untaring many files in the first step. This takes a lot of time and I'd like to do this in parallel, if possible. If it's the disk reading speed that is the bottleneck I guess I should not expect an improvement, but perhaps it's the processor. So I want to try this out. I'm working on windows 7 with R 2.15.1 and the latest foreach

This is a not too old R-devel on Linux, it already fails in R 3.4.4, and on macOS as well. The tar file seems valid, external tar can untar it, so maybe an untar() bug. setwd(tempdir()) dir.create("pkg") cat("foobar\n", file = file.path("pkg", "NAMESPACE")) cat("this: that\n", file = file.path("pkg", "DESCRIPTION"))

Dear List, I have a list of 600+ *.gz files that I would like to extract and read the geotiffs contained within them. I tried using the untar() function to simplify this task but I am stumped by an error. I've combed the Internet for a solution without luck. The details are below, and any help in solving this matter is appreciated. > files = list.files(path = "J:/GIMMS/NDVI",

Hoping someone can help me fix something that I apparently messed up, i have the issue that when I untar a file as root the uid and gid that get set are not roots'. I had change a user uid and gid to 1000 via usermo -u etc.... but somehow it appears to have effected the root user. When I touch files as root the correct uid and gid are root, however when untaring an archive the directory and

HI All, I have a directory tree that when the user un-gzips/untars it does into /opt by default. The directory tree is like: ugui | |-- <misc files> |-- source |-----framework |------ <misc files> so when unzipped I want to end it with /opt/ugui and all the stuff below it. How do I do this? Can I also issue one command that will unzip and untar the archive at the same time?

>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>> on Tue, 1 May 2018 16:14:43 +0200 writes: >>>>> G?bor Cs?rdi <csardi.gabor at gmail.com> >>>>> on Tue, 1 May 2018 12:05:32 +0000 writes: >> This is a not too old R-devel on Linux, it already fails >> in R 3.4.4, and on macOS as well.

Move the untar function so it can be used later in the code. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index db884d9..f76fe82 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -38,6 +38,12 @@ object method as_options = "-i ova

Move the untar function so it can be used later in the code. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index 61930f0..85954a3 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -38,6 +38,12 @@ object method as_options = "-i ova

E.g. I am seeing: dir <- file.path(tempdir(), "test-tar") dir.create(dir) setwd(dir) dir.create("foo", showWarnings = FALSE) file.create("foo/bar.R") tar("test.tar", files = "foo/bar.R") dir.create("untarred") untar("test.tar", exdir = "untarred")

https://bugzilla.redhat.com/show_bug.cgi?id=1448739

These functions obscure the true flow of the code, so hoist them out of the source () method to the top of the file. No change, just refactoring. --- v2v/input_ova.ml | 139 +++++++++++++++++++++++++++---------------------------- 1 file changed, 69 insertions(+), 70 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index 72a63d3..9a6a615 100644 --- a/v2v/input_ova.ml +++

Hi to all R people!!! I'mtryed to untar R-0.63.0.tgz but .... C:\Archivio\R\R-0.63.0>tar -x -z -f R-0.63.0.tgz tar: R-0.63/aux: Could not create directory: No such file or directory (ENOENT) tar: R-0.63/aux/GETSYMBOLS: Could not create file: No such file or directory (EN OENT) tar: R-0.63/aux/config.sub: Could not create file: No such file or directory (EN OENT) tar:

Hi, I have been trying to untar the source file for R and having no success. I have used decompression utilities that handle .tar and .tgz file but I keep getting an error that there is a "Header CRC Error". So, I am wondering if this is just me and I am not using the right decompression utility or whether there is an error in the headers for the zip file. Anyone have any advice?

..." directory, which is empty. I touched "/scard/Makefile.in", and configure then ran to completion. So, two things... 1. Is there a blocksize option on tar when the snapshots were created? My extract command is: gzcat openssh-SNAP-20020228.tar.gz | tar xvof - Separately unzipping and untarring gives the same error. 2. Is the /scard stuff missing from the CVS? I think I saw something about this on the list previously, so forgive my faulty memory. I'm very pleased with OpenSSH 3.0.2, and am glad to contribute to testing on my platforms. -Tom Rudnick -- ----------------/-----------...

Hello again, as stated earlier there is a problem with mtime setting on directories during healing in replication setup. Today I tested 2.0.5 and found out that the handling is more or less generally buggy for directory mtimes. Simply try this: untar some kernel archive on your local disk and look at the mtime of the created top directory. now untar the same archive on an exported gluster fs and

On Saturday, 12 November 2016 16:37:52 CET Tomáš Golembiovský wrote: > We don't have to always extract all files from the OVA archive. The OVA, > as defined in the standard, is plain tar. We can work directly over the > tar archive if we use correct 'offset' and 'size' options when defining > the backing file for QEMU. > > This leads to improvements in speed

I had a couple of problems getting R 0.90.0. In case anyone has similar problems, I though I would mention them. 1/ I can't use "ftp cvs.r-project.org" from either home or work. The ftp service does not seem to be available. Perhaps this is intended. I only discovered it because I thought the file I got through Netscape might be corrupted. (I don't understand why Netscape

We don't have to always extract all files from the OVA archive. The OVA, as defined in the standard, is plain tar. We can work directly over the tar archive if we use correct 'offset' and 'size' options when defining the backing file for QEMU. This leads to improvements in speed and puts much lower requirement on available disk space. Signed-off-by: Tomáš Golembiovský

I just installed build 41 of Nevada on a SunBlade 1500 with 2GB of ram. I wanted to check out zfs since the delay of S10U2 I really could not wait any longer :) I installed it on my system and created a zpool out of an approximately 40GB disk slice. I then wanted to build a version of thunderbird that contains a local patch that we like. So I download the source tar ball. I try to untar it on the

I'm trying to build a package to create a directory and install some files. My rpmbuild keeps failing, unable to cd into the directory, "no such". Now, in the tmpfile, I *see* it cd'ing into BUILD/opt, and the source was unzipped and untared into BUILD/opt/smipmicfg-1.27.0. In the spec file, I've even added a cd $RPM_BUILD_ROOT/opt, and I see it cd to there... and then it