search for: l685

...efore running library(): "Loading required package: %s" https://github.com/r-devel/r-svn/blob/4198a2941b702d965bb2374c2b908f48c369f40a/src/library/base/R/library.R#L967-L968 https://github.com/r-devel/r-svn/blob/4198a2941b702d965bb2374c2b908f48c369f40a/src/library/base/R/library.R#L684-L685 Shouldn't "Loading" be "Attaching" instead? My understanding is "a package is loaded" is equivalent to "isNamespaceLoaded()", i.e., loadNamespace() was run. And that "a package is attached" is equivalent to "pkg %in% .packages()", i....

...> "Loading required package: %s" > https://github.com/r-devel/r-svn/blob/4198a2941b702d965bb2374c2b908f48c369f40a/src/library/base/R/library.R#L967-L968 > https://github.com/r-devel/r-svn/blob/4198a2941b702d965bb2374c2b908f48c369f40a/src/library/base/R/library.R#L684-L685 > Shouldn't "Loading" be "Attaching" instead? Good question... I had asked myself as well a couple of times. The vagueness is mostly "historical" in the sense that originally R (nor S) had namespaces. OTOH, attach(.) has always worked for data frames (a...

Dear R Support Team, I am experiencing an issue with my R package during the `R CMD check` process. A non-standard file named `vert.txt` is being generated in the check directory, causing a NOTE in the check results. Despite adding `vert.txt` to `.Rbuildignore`, the file is still appearing. And, there are no commands in any part of my package's code that would generate this file. Here

...b881d83b1#file-libvirtd-log-L257-L266 > [4] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L296 > [5] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302 > [6] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685 > [7] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799 > [8] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1075 > [9] > https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1090 > [10] > http://lib...

....github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L257-L266 [4] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L296 [5] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302 [6] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685 [7] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799 [8] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1075 [9] https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1090 [10] http://libvirt.org/git/?p=libvirt.git;a=blob;f=src...

Further followups! We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2 code to try to figure out what libvirt is doing under the hood. Even though we have the log level set to 1 (info) in our libvirtd.conf, we are not seeing the VIR_DEBUG() [1] statements being printed out. There are tons of other presumably-debug lines of output showing up in our log. We are sort of