similar to: [PATCH 0/2] crash: Bundle of fixes for Xen

WTF... how to solve? (REE ruby/Ubuntu 10.04) $ dpkg -l |grep ruby ii ruby-enterprise - 1.8.7-2011.03 - Ruby Enterprise Edition. $ bundle exec /usr/local/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/cli.rb:344:in `exec'': wrong number of arguments (ArgumentError) from /usr/local/lib/ruby/gems/1.8/gems/bundler-1.0.21/lib/bundler/cli.rb:344:in `exec'' from

On Dec 2, 2011, at 12:40 PM, Evan Cheng wrote: > ---------------- > | Bundle * | (A MI with special opcode "Bundle") > ---------------- > | > ---------------- > | MI * | > ---------------- >

It?s official, folks! After talking with my partner, Greg Narain, as well as Allan Odgaard, the creator of TextMate, we (syncPEOPLE) have decided to release our Rails bundle under the MIT license so that it can nest itself nicely within its new home, the TextMate Subversion Bundle Repository. What this means for the rest of us is that all of these great features we?ve been madly

On Wed, Dec 07, 2011 at 10:14:22AM -0800, Andrew Trick wrote: > > On Dec 6, 2011, at 3:10 PM, Krzysztof Parzyszek wrote: > > > - How about having bundles that contain branch targets (other than the > > first instruction) from the outside of the bundle? This seems like something > > that has a potential for causing trouble, but I can't think of any specific >

Sometime in Feb, yum updated something to do with ca-bundle. I didn't notice at the time, but it put these two files on my machine: /etc/pki/tls/certs/ca-bundle.trust.crt.rpmnew and /etc/pki/tls/certs/ca-bundle.crt.rpmnew Both of those on the existing system are symbolic links ca-bundle.trust.crt -> /etc/pki/ca-trust/extracted/openssl/ca-bundle-trust.crt and ca-bundle.crt ->

On Dec 2, 2011, at 12:40 PM, Evan Cheng wrote: > There have been quite a bit of discussions about adding machine instruction bundle to support VLIW targets. I have been pondering what the right representation should be and what kind of impact it might have on the LLVM code generator. I believe I have a fairly good plan now and would like to share with the LLVM community. Let me add some

Hi [MacOsX 10.4.6; R-2.2.1] I have a bundle that comprises three packages. I want to run R CMD check on each one individually, as it takes a long time to run on all three. I am having problems. The bundle as a whole passes R CMD check, but fails when I cd to the bundle directory and run R CMD check on a package directory. The whole bundle passes: octopus:~/scratch% R CMD check

Hi Quentin and llvm-dev, I've got a regalloc-related question that you might have an opinion or answer about. In our out-of-tree target we've been doing some bundling before register allocation for quite some time now, and last night a new problem popped up. What the fix should be depends on if this bundle is legal or not: BUNDLE %vreg39<imp-def,dead> *

Dear R-core, Thank you for your great effort! I am finalising a bundle that works both in R and Splus. But I faced the following minor problems with R CMD under both UNIX and LINUX. 1. R CMD build denies to work with bundles. It reports * checking `DESCRIPTION' package entry ... ERROR: no package entry in `DESCRIPTION' Surely, there is no one, but there is Contains entry. Next, according

> On Jun 27, 2017, at 2:10 PM, Matthias Braun <mbraun at apple.com> wrote: > >> >> On Jun 27, 2017, at 4:55 AM, Mikael Holmén via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi Quentin and llvm-dev, >> >> I've got a regalloc-related question that you might have an opinion or answer about. >> >> In our out-of-tree

Hello, I wonder if it is unwise to name a bundle the same as one of its packages. For instance, I now have a huge package called 'aroma' that I basically want to split up in several smaller packages, say 'aroma.core', 'aroma.io', 'aroma.explore', 'aroma.trial', 'aroma.deprecated' etc, which simplifies maintenance but also the overview. For

From my understanding, Gemfile.lock lists all the gems installed for the application along with the specific versions used. This means your app will only use the versions mentioned here and no others, even if updates for those gems are available. When you are deploying your application to staging or production, your application is going on a separate server so you want to make sure all the same

>>> groups of instructions between .bundle_lock and >>> .bundle_unlock directives cannot cross a bundle boundary >> >> Can this be relaxed to: A data instruction cannot fall on a bundle >> boundary. ? > > I'm not sure what you mean, can you elaborate? Nevermind, what I suggested was not strict enough. I see now that the purpose of unlock/lock is to

Hi Recently I sent a modified version of the GetBundle bundle to textmate-dev. It was failing because the RSpec bundle was from another repo (ie RubyForge). One of the replies said that the RSpec bundle was now in the MacroMates repo, which it is. Is that an officially handled thing? If so, what version of the RSpec bundle is being maintained there - CURRENT? It''s

Hi Eli, > we are splitting the effort to manageable chunks that can > be committed, tested and reviewed separately as > independently as feasible I'd be interested in experimenting with this stuff sooner than later. Could you dump all the patches in a publicly accessible repo? How about Github? Thanks, Greg On Tue, Dec 4, 2012 at 3:53 PM, Eli Bendersky <eliben at

I just signed up to this mailing list so I don't have the original email with the proposal to reply to. I got the text forwarded to me though, and here are my thoughts on it: - The requirement that it should be easy for a pass to be oblivious to bundles isn't well defined. If this means that a pass should be able to run as if the bundles weren't present, then such a pass can easily

Newer Xen versions (at least 4.2) use per_cpu__init_tss instead of init_tss array. Take into account that. Signed-off-by: Daniel Kiper <daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> diff -Npru crash-6.1.0.orig/x86.c crash-6.1.0/x86.c --- crash-6.1.0.orig/x86.c 2012-11-13 14:45:58.000000000 +0100 +++ crash-6.1.0/x86.c 2012-11-13 14:48:13.000000000 +0100 @@ -5471,9 +5471,16 @@

per_cpu data is dynamically allocated since 21416 changeset (x86: Dynamically allocate percpu data area when a CPU comes online). Take into account that and read variables from correct address. Signed-off-by: Daniel Kiper <daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> diff -Npru crash-6.0.8.orig/xen_hyper.c crash-6.0.8/xen_hyper.c --- crash-6.0.8.orig/xen_hyper.c 2012-07-05

'R CMD build --binary BUNDLE' and Windows. When using R version 2.9.0 beta for 'R CMD build --binary CoCo' on Windows only the first package of the 'Contains' field of the bundle DESCRIPTION file ends up in the zip file. (Same result for the bundle 'VR' by R version 2.9.0 beta.) The check of the CoCo bundle version 0.1.7.5 by R version 2.9.0 beta is OK (on

I am fighting with this for 5 days... i''m getting crazy! Here is my deploy.rb: require "bundler/capistrano" require "rvm/capistrano" # Load RVM''s capistrano plugin. set :rvm_ruby_string, :local # Or whatever env you want it to run in. ''1.9.3'' set :domain, ''www.xxx.com'' set :application,