search for: sourcelines

OK, I am just sending it here too as it looks like r-devel at r-project.org is not the right place: =EF=BB=BFOn Fri, 2008-04-25 at 08:48 +0200, Soeren Sonnenburg wrote: > While trying to fix swig & R2.7 I actually discovered that there is a > bug in R 2.7 causing a crash (so R & swig might actually work): >=20 > the bug is in ./src/main/gram.c line 3038: >=20 >

While trying to fix swig & R2.7 I actually discovered that there is a bug in R 2.7 causing a crash (so R & swig might actually work): the bug is in ./src/main/gram.c line 3038: } else { /* over-long line */ fixthis --> char *LongLine = (char *) malloc(nc); if(!LongLine) error(_("unable to allocate space for source line %d"),

...b") } } class apt-stable { package { "apt" : ensure => present } apt-sources-list { the_stability => 1, the_freeness => 3 } } #-------------------------- And this sources.list.erb template file: #---------- sources.list.erb ---------------- <%= def sourcelines(stability=1,freeness=1,url="http://mirror.phy.bnl.gov/debian/") dists = ["sarge","etch","sid","experimental"] frees = ["main","contrib","non-free"] ret = "" for d in 0...stability ret = ret + &quot...

On Sat, 2008-04-26 at 09:38 +0200, Peter Dalgaard wrote: > bugreports at nn7.de wrote: > > OK, I am just sending it here too as it looks like r-devel at r-project.org > > is not the right place: > > > I think it was seen there too, just that noone got around to reply. In > R-bugs, there's a filing system so that it won't be completely forgotten... Looks like

bugreports at nn7.de wrote: > OK, I am just sending it here too as it looks like r-devel at r-project.or= g > is not the right place: > =20 I think it was seen there too, just that noone got around to reply. In=20 R-bugs, there's a filing system so that it won't be completely forgotten.= =2E. However, your mail seems to have gotten encoded in quoted-printable, you = might want

You will see the current code is different, and your 'fix' is not needed nor applies in R-devel. You failed to provide an example to reproduce the alleged bug, but the issue does seem to be using lines beyond the documented line length. So it would have only affected people who did that .... And generating a new report (PR#11438) was distinctly unfriendly. If after studing the R FAQ

Full_Name: Albrecht Gebhardt Version: 0.90.0 OS: osf4.0 Submission from: (NULL) (143.205.61.73) I had to apply the following patch to be able to compile on an alpha with DU 4.0E: ############################################### --- ./src/main/gram.y.mkString-patch Tue Nov 23 12:16:29 1999 +++ ./src/main/gram.y Tue Nov 23 12:16:59 1999 @@ -56,7 +56,8 @@ SEXP mkFloat(char *); SEXP

hi, when using the execution engine (no matter, if JIT or Interpreter) i get the following assertion as soon as i use boost::shared_ptr: /build/buildd/llvm-2.5/lib/Target/X86/X86CodeEmitter.cpp:522: void<unnamed>::Emitter::emitInstruction(const llvm::MachineInstr&, const llvm::TargetInstrDesc*): Assertion `0 && "JIT does not support inline asm!\n"' failed.

Dear all, We have a few reasons to have various PuppetDBs (and Masters, one per cluster) in our datacenter and, eventually, there may be a need to share *only* a few exported resources between clusters, like a few ssh-keys or nagios tests. Is there a mechanism to pull and push some exported resources from one PuppetDB to another? I guess this could be done with the API, but has anybody tried it,

I have multiple puppetdb severs pointed at the same database. Would setting gc-interval to 0 disable it on the extra puppetdb nodes? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4DEyx0IXbLsJ. To post to this group, send email to