> | > stackloss
> | Fehler: Objekt 'stackloss' nicht gefunden
> | > data(stackloss)
> | Warning message:
> | In data(stackloss) : data set 'stackloss' not found
> | no data sets found
> | Any idea? Let me know what I can do to help.
>
> Hm.
>
> Sounds like we'd need an arm box to do development on to look at the R code
> / metadata ?
(sorry for the delay, I was on the phone for quite a while)
Well, I believe I could let you log into my NAS if I I configure my router
appropriately :) It is running Debian stable and the abovementioned sid
chroot.
Meanwhile, I have had a go at debugging using debug(). The problem appears in
the function fileExt defined in the very beginning of data().
fileExt <- function(x) {
db <- grepl("\\.[^.]+\\.(gz|bz2|xz)$", x)
ans <- sub(".*\\.", "", x)
ans[db] <- sub(".*\\.([^.]+\\.)(gz|bz2|xz)$", "\\1\\2",
x[db])
ans
}
Guess what, adding perl=TRUE to the second line gives the right extension.
I just verified that after
> fix(data)
and doing the abovementioned change using my favorite text editor
I can load the data using
> data(stackloss)
However, I do not fully understand what the code does (the first line results
in db being FALSE, and I do not see how it makes sense later to index ans
using FALSE...)
So I have the feeling maybe it should be discussed upstream why regular
expressions on arm behave so different (broken) and what should be done about
it (use PCRE, considering Adam Conrads viewpoint on #679180 ?).
Beware that lazyloading still does not work after this workaround.
Cheers,
Johannes
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
