similar to: possible internal (un)tar bug

Displaying 20 results from an estimated 5000 matches similar to: "possible internal (un)tar bug"

2018 May 01
1
possible internal (un)tar bug
>>>>> 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.
2011 Apr 01
1
"R CMD check" accepts but "R CMD INSTALL" rejects a tar ball.
I have somehow managed to made a source tar ball which "R CMD check" accepts but "R CMD INSTALL" rejects with: ------------------ Warning in untar2(tarfile, files, list, exdir) : checksum error for entry 'pax_global_header' Error in untar2(tarfile, files, list, exdir) : unsupported entry type ?g? ------------------ This happens with both R 2.12.2 (x86 linux) and R
2010 Dec 17
2
installing package from source with Linux
Dear list, this may not be related to R but rather to my OS, but I do not understand the issue of compiling R packages deeply enough to figure out the exact cause of the problem. I am trying to install a R package from source as it is not yet available under Cran (Rssa, downloaded here: https://github.com/asl/rssa). Running sudo R CMD INSTALL asl-rssa-6f458e4.tar.gz from the console
2013 May 03
1
untar() error
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",
2010 May 19
2
Error in untar2(tarfile, files, list, exdir) : unsupported entry type ‘x’
Hi R gurus, I'm getting the following error when trying to build and install an R package: Error in untar2(tarfile, files, list, exdir) : unsupported entry type ?x? I build the package like so: R --no-init-file CMD build mypackage Then try to install it: sudo R --no-init-file CMD INSTALL mypackage.tar.gz ...which dies with the above error. I can extract the archive fine with tar -zxf, so
2014 Sep 30
1
R's internal tar ignores files in sub-directories
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")
2013 Sep 15
0
building R, rJava, & Rserve on Centos without admin privileges (or support)
I am trying to build R on a Centos server without admin privileges (or support), so I can call R functions from NetLogo models (via the NetLogo R extension or possibly Rserve), but I'm getting stuck near the end of make. Any suggestions? Here's the setup... $ R_SHELL=/bin/sh $ R_HOME=~/R-devel $ cd $R_HOME; ./configure; make returns ... begin installing recommended package MASS
2010 Oct 04
2
For help on Open .tar.gz file in R under Windows
Hey All, I am new in R. Need help on code that can open the .tar.gz file in R under Windows. Can any one help. Thanks in Advance. Wayne [[alternative HTML version deleted]]
2016 Nov 04
10
[PATCH 0/5] Import directly from OVA tar archive if possible
This is still a draft, not ready for commit yet. But feedback is welcomed. This series is related to the problem of inefficient import of OVA files. The needed enhancements of QEMU was merged into the codebase and should be available in QEMU 2.8. From there we can use 'size' and 'offset' options in raw driver to tell QEMU to use only subset of a file as an image. The first three
2009 Oct 13
1
beta build problem
I am having the following problem building R-beta_2009-10-12_r50045.tar.gz on Ubuntu 9.04 - the Jaunty Jackalope Paul ________ ... make[2]: Entering directory `/home/paul/toolchain/R/R-beta/src/library/Recommended' begin installing recommended package boot gzip: invalid option -- 'x' Try `gzip --help' for more information. tar: This does not look like a tar archive
2013 Aug 25
0
"block incomplete" error when compiling R
Dear list, I am trying to compile R on a 64-bit Ubuntu 13.04 machine and get the following error: make[2]: Entering directory `/home/kaiyin/opt/R-2.15.0/src/library/Recommended' begin installing recommended package MASS Error in untar2(tarfile, files, list, exdir) : incomplete block on file make[2]: *** [MASS.ts] Error 1 make[2]: Leaving directory
2016 Nov 12
9
[PATCH v2 0/5] Import directly from OVA tar archive if possible
This series is related to the problem of inefficient import of OVA files. The needed enhancements of QEMU were merged into the codebase and should be available in QEMU 2.8. From there we can use 'size' and 'offset' options in raw driver to tell QEMU to use only subset of a file as an image. The patch set is more or less complete. The only outstanding issue is the missing detection
2009 Aug 21
4
tar and gunzip help
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?
2016 Oct 07
1
unzip does not like a / at the end of path.
dir("inst/extdata/") dir("./inst/extdata/") dir("inst/extdata") works all fine, listing the directory content. but: unzip(tmp[1],exdir = "inst/extdata/") Error in unzip(tmp[1], exdir = "inst/extdata/") : 'exdir' does not exist unzip(tmp[1],exdir = "./inst/extdata/") Error in unzip(tmp[1], exdir = "inst/extdata/") :
2017 Jan 11
3
[PATCH v5 0/3] Import directly from OVA tar archive if possible
v5: - rebase, patches 1,3,5 were merged - 1/3: we still need to discuss whether to detect compressed discs - 2/3: - renamed argument noempty to keep_empty - tests were not run - 3/3: - using JSON module to generate JSON (as suggested by Pino) - all the other comments raised by Pino v4: - rebase to more recent master - 1/6: using just "quote" instead of
2017 Jan 30
6
[PATCH v6 0/3] Import directly from OVA tar archive if possible
v6: - just rebase v5: - rebase, patches 1,3,5 were merged - 1/3: we still need to discuss whether to detect compressed discs - 2/3: - renamed argument noempty to keep_empty - tests were not run - 3/3: - using JSON module to generate JSON (as suggested by Pino) - all the other comments raised by Pino v4: - rebase to more recent master - 1/6: using just "quote" instead of
2017 Feb 03
3
[PATCH v7 0/1] Import directly from OVA tar archive if possible
v7: - rebased because patch 1/3 has been pushed - changes to nsplit have been dropped (2/3) - addressed Richard's comments, notably the subfolder function was moved to mllib and renamed to subdirectory v6: - just rebase v5: - rebase, patches 1,3,5 were merged - 1/3: we still need to discuss whether to detect compressed discs - 2/3: - renamed argument noempty to keep_empty - tests were
2017 Mar 13
4
[PATCH 0/2] v2v: -i ova: A couple of cleanup patches.
A couple of patches cleaning up the -i ova code. These are both just refactoring (or should be at any rate). The second patch is best viewed with 'git show -w' to exclude whitespace changes. Rich.
2005 Sep 03
2
tar question
Basic tar question: I have created a ar file with tar -prvf /tmp/ib_backup.tar /opt/interbase/data/* The file has been copied to another box and I want to untar the file into /opt/interbase/data/ I am not sure about the syntax; how to specify where I want the data to be placed. Here is my start of the command: tar -xvf /tmp/ib_backup.tar #The tar file is in /tmp Todd --
2008 May 13
2
b89 xVM Source tar bundle is corrupted on the on download site
Apparently the b89 xvm-src.tar.bz2 tar bz2 archive is corrupted / truncated on the b89 source download page: http://dlc.sun.com/osol/on/downloads/b89/ http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 In the past, the xvm-src.tar.bz2 file had a size of ~ 100 mbytes; with b89 the size of the downloadable archive is only 72 mbytes. And bzip2 complains: % bzip2 -tv