On Sun, Apr 21, 2013 at 7:25 AM, Dirk Eddelbuettel <[email protected]> wrote: > On 21 April 2013 at 00:12, Dave Steele wrote: > | On Sat, Apr 20, 2013 at 7:34 PM, Dirk Eddelbuettel <[email protected]> wrote: > I just disable (!!) the PrintWarnings() calls (that > | > want the no-longer-exported Rf_PrintWarnings() function: > | >... > | > > | > Shall we do that? > | > > | > | Ok, I can work this. If you'd like, I could act as DM, and shepherd it > | to removal. > > I have no problem uploading as a long-time DD but I was wondering if you > could test the suggested fix with the packages you were trying? >
Ok. With your changes, the module now loads. Now I am seeing the same failure as with python-rpy2. The 'palette()' call in the code throws an exception, saying... No protocol specified Warning message: In (function (display = "", width, height, pointsize, gamma, bg, : unable to open connection to X11 display '' piuparts-report responds by omitting the chart on e.g. http://piuparts.debian.org/sid/. When running interactively, the palette call causes a window to be opened, which is not easily dismissed. I got python-rpy2 working by removing the palette and dev_off commands. What is the magic to setting a palette without establishing a window? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
