>
>
> Otherwise it's a bug.
>
>
I was not using a system package for R. While Matthias' link may
conceivably be relevant as well, I'm currently leaning toward the other
option. On the old run (upgrading R) I have in the log the first time
(unsuccessful):
Warning: No files to uninstall for 'r'
Uninstalling existing 'r'
While on the second (unsuccessful) and most recent (successful) run I see:
Package 'r' is currently not installed
No legacy uninstaller found for 'r'; nothing to do
Perhaps that helps someone who understands the uninstaller logic - that
came after I had to stop keeping track of build system developments.
> On Linux I see
> $ grep libR local/var/lib/sage/installed/r-3.6.2.p0
> "lib/R/lib/libR.so",
> "lib/pkgconfig/libR.pc",
>
>
>
It's the Mac equivalent. (I don't think any system packages are used for
my install, or very few.) Unfortunately I don't have the state before this
upgrade any more.
$ grep libR local/var/lib/sage/installed/r-3.6.2.p0
"lib/R/lib/libR.dylib",
"lib/pkgconfig/libR.pc",
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-release/161201ad-43ba-4f12-b917-6617d111b89bo%40googlegroups.com.
