similar to: R -- for help

A new version of pqR is now available at pqR-project.org, which fixes several bugs that are also present in the latest R Core patch release (r66002). A number of bugs found previously during pqR development are also unfixed in the latest R Core release. Here is the list of these bugs that are unfixed in r66002 (including documentation deficiencies), taken from the pqR bug fix and documentation

Hi, about an year ago i was reporting a bug in mailbox aliases, which remains unfixed and unasnwered (probably totally ignored, don't understand why). I thought it was because the bug is old and already fixed but yesterday i upgraded to Dovecot 2.2.24 and problem persists. Here is the original report, everything, except the Dovecot version, is still correct:

On Sat, Jul 23, 2011 at 5:09 PM, Talin <viridia at gmail.com> wrote: > So this was working fine for me until a few days ago when I checked out the > most recent LLVM - the one with the new type system. Now I am getting the > same error that I was getting previously. > Is it possible that your fix got unfixed when they merged in the new branch? I wouldn't be surprised if

Ian Jackson writes ("64bit PV guest breakout [XSA-213]"): > Source: xen > Version: 4.4.1-9 > Severity: important > Tags: security upstream fixed-upstream > > See > https://xenbits.xen.org/xsa/advisory-213.html Ian Jackson writes ("grant transfer allows PV guest to elevate privileges [XSA-214]"): > Source: xen > Version: 4.4.1-9 > Severity:

On Sat, Jul 23, 2011 at 6:32 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Sat, Jul 23, 2011 at 5:09 PM, Talin <viridia at gmail.com> wrote: >> So this was working fine for me until a few days ago when I checked out the >> most recent LLVM - the one with the new type system. Now I am getting the >> same error that I was getting previously. >> Is it

Hi. I've been looking at the BTS and PTS and security tracker, and it looks like maybe you could do with some help ? Issues I noticed include: * 4.7, the latest Xen upstream release, is not in sid * Even leaving that aside, sid doesn't seem to have all the security fixes which ought to be expected. * The BTS could do with a bit of gardening, perhaps. Please let me know what, if

> CentOS repos. There are others that do. Some of the repos that overwrite > core packages do so with little packages like sqlite (yum uses sqlite so > changing the version of it is not a Good Thing for system stabilty). > Other repos in that list have been effectively unmaintained for a number > of years so they contain packages that may have severe unfixed security >

Hello, I'm trying to use rjson to parse a JSON object. The object can be found here http://pastebin.com/np0s5hgM (you'll probably need to add quotes around the content) fromJSON returns the error glibc detected home/sguha/lib64/R/bin/exec/R: realloc(): invalid next size: 0x000000000209e210 *** Is there a fix coming soon? Maybe CRAN should also have an outstanding bug field -

Hi, all, I''m a newbie on dtrace and the problem I am having is: For processes which have been running for more than a couple of hours, dtrace doesn''t seem to be able to trace(I waited for at least one hour and didn''t see anything happening). However, it works every time for a relatively new process. Any insight or help will be appreciated. This is my machine:

hi, two questions... 1. what happens with points()? after the split.screen function points() start not at x = 1 (at x = - something) graphics.off() x11() split.screen(c(3, 1)) split.screen(c(2, 1), 1) screen(3) plot(dat, type = "n") screen(4) plot(dat, type = "n") screen(2) plot(dat, type = "n") dat <- rnorm(1000) for (i in 1:length(dat)){ screen(3)

Full_Name: Tom Callaway Version: 2.7.2 OS: Fedora 10 (Linux/x86_64) Submission from: (NULL) (96.233.67.230) Recently, Debian identified a security issue with the javareconf script in R. I confirmed that this is still unfixed in R 2.7.2. The following patch resolves the issue: diff -up R-2.7.2/src/scripts/javareconf.BAD R-2.7.1/src/scripts/javareconf --- R-2.7.2/src/scripts/javareconf.BAD

Hi, I''ve been using send_file in my Rails application with WEBrick happily to send files of various sizes and kinds. The same code fails to send anything but a 500 error when run under Apache, and a log file message "warning: syswrite for buffered IO". Looking back through the mailing list archives I see that there have been send_file bugs in the past. Can some knowledgeable

On Oct 10, 2008, at 2:06 PM, John Regehr wrote: > With respect to random testing LLVM pre-2.4 is doing extremely well, > we > have no unreported bugs right now. That's great John! For my info, are there any reported bugs that are unfixed in 2.4? -Chris

> For my info, are there any reported bugs that are unfixed in 2.4? Looks like there is one outstanding correctness bug (2697) and three crash bugs (2735, 2775, 2797). I haven't reverified these lately, though. John

Hello, Nicolas > Thanks a lot for the heads up. I hadn't run into any problems yet with my > hack because I haven't used other callee-saved registers so far. Anyway, I'm > looking forward to your fix! I've commited the first series of patches to ToT to unbreak win64, basically: 1. Honour register save area 2. Enable proper passing of __m128 and __m64 arguments 3. Minor

> On 18 Sep 2016, at 21:49, azurit at pobox.sk wrote: >> >> Hi, >> >> about an year ago i was reporting a bug in mailbox aliases, which >> remains unfixed and unasnwered (probably totally ignored, don't >> understand why). I thought it was because the bug is old and >> already fixed but yesterday i upgraded to Dovecot 2.2.24 and >>

Janne Hyv?rinen wrote: > I re-did the patch with these limitations. I also noticed I had left > stat() and fstat() functions unfixed previously. And encoder was limited > to 4G in many places when printing status info. Unfortunately, this patch did not apply cleanly. There were two problems; one in src/flac/main.c that was easy and obvious to fix, the other in include/share/compat.h.

Good day all, I've recently added a new piece of hardware to my collection - it's a Compaq Proliant 1600R with a Smart Array 2DH controller and dual processors. Unfortunately these features don't seem to play well together. Installing FreeBSD 4.8 was very smooth. After doing a CVSup, one of my first tasks was to compile a new kernel with SMP support. The compile went fine, but when I

Sorry to ask, here Bind is configured to not allow zone transfer except for some IPs. I did tried to transfer AD zone from a machine which is not allowed to transfer zones according to Bind configuration file, and that machine was able to transfer what it should not... Is there other points where Bind configuration file are useless? Is documented somewhere? This to avoid relying on Bind

So this was working fine for me until a few days ago when I checked out the most recent LLVM - the one with the new type system. Now I am getting the same error that I was getting previously. Is it possible that your fix got unfixed when they merged in the new branch? On Thu, Jun 30, 2011 at 2:21 PM, Talin <viridia at gmail.com> wrote: > Cool, I'll check it out - thanks! > >