I have several versions of Ruby installed via RVM. I have been using Ruby 2.5.0 for a while, but also working on projects at 2.3.3. Every time I open the terminal or a new tab, it switches to version 2.3.3. I have set the default to 2.5.0, but it doesn't respect this.
I finally pushed my last commit that needed 2.3.3 so I thought I could just nuke it and maybe that would fix my problem. One the one hand, it now correctly defaults to 2.5.0, but always with the error:
Required ruby-2.3.3 is not installed.
What does it take to make RVM switch to the default and stay there? Why would it be hung up on this specific version?
I had the same problem and it drove me nearly crazy. All symlinks and config files under /usr/local/rvm/config where pointing to 2.5.3, as I set it up to, but I got the same message as you. Turned out there was a .ruby-version file in the project directory that overrode all settings. Updating this file to the correct version did it for me. Hope it helps you too.
Related
everybody, did you happen to encounter such an error while running the pod install command?
Link to the error itself
Since I tried to reinstall ruby by this method already:
rvm install ruby-2.6.3
rvm use ruby-2.6.3
rvm --default use 2.6.3
And still, unsuccessfully.
and cocoapods are also unsuccessful anyway, there is simply no place to look for an answer.
This error flies away only when working with an Obj-c project (and quite ancient ones), because I am now looking at the cryptoPro library and the standard project is not launched there.
There are no such problems with new projects at the moment.
Fixed an error. I will tell you what it was about me. I noticed this line in the bug:
untimeError - [Xcodeproj] Consistency issue: build setting ARCHS has multiple values: {"Debug"=>"$(ARCHS_UNIVERSAL_IPHONE_OS)", "Release"=>"$(ARCHS_STANDARD_32_BIT)"}.
After that I got into the Targets -> Build Settings -> Architectures project itself.
Specify there $(ARCHS_STANDARD) for both cases and then everything worked!
Some time after the release of Elm19 I published a library, which I needed for an Elm18 code base: thought2/elm-wikimedia-commons.
This worked well, it's listed in the community driven Elm18 package database: https://dmy.github.io/elm-0.18-packages/, can be installed and all good. Except the fact that the documentation is not shown in the package details, but that I heard is a known bug there. (But still I think this is very bad)
But the main problem is now, how to migrate the library to Elm 19: The actual migration steps are done and live in the master branch of the repo: http://github.com/thought2/elm-wikimedia-commons
The Elm18 versions proceeded to 1.1.0 in the meanwhile and after the migration there had to be done an API change, so I'd assume the latest version to become 2.0.0. If I add this to elm.json, the command elm publish tells me that this would be the first version and I should change this. Which is not right.
After a bit of research, I found out that the package (among other 18 ones that have been published in the same time period) is not listed in this json: https://package.elm-lang.org/all-packages This should contain all packages regardless of versions.
Any ideas what to do? This is really blocking my development, as I'm stuck in both lands now: 18 and 19. Would appreciate a lot if someone has some hints or solutions for me!
You shouldn't need to mess with the version number specified in elm.json.
If you set it back to the version of the package that is already published and run elm bump the elm program will look at the changes you've made to the package's API and set the new version accordingly.
Looking at https://github.com/thought2/elm-wikimedia-commons it doesn't look like any of your upgrade changes were breaking changes to your package API so the version won't be a 2.x.x, it will be a 1.x.x.
You'll need to remove the 2.0.0 git tag as well and instead add a tag for the version that elm bump tells you that your package is.
Im having a very annoying issue with qtcreator and cmake projects: qtcreator fails to find the executable. It just prints "No executable specified" when trying to launch any executable from the IDE. Everything works fine after configuring the project (first time only). The issue manifests when loading the project afterwards. Only workaround is deleting the "CMakeLists.txt.user" before every use. This is tedious and unnecessary.
This is happening to projects that were running just fine for years, both my own and my colleagues, on multiple machines running ubuntu 14.04 & 14.10. Problems started with qtcreator version 3 and higher from ubuntu 14.04 upwards.
Assuming that the issue is triggered by some changes in the "CMakeLists.txt.user", after the project is closed the first time, I replaced the file with a copy of it right after it was created the first time. This worked, thus confirming that there is either something wrong with the file itself, or changes to it trigger an existing bug in qt-creator. Unfortunately it is just as tedious as deleting the file in the first place.
My Challenge:
Unfortunately I am not familiar with the inner workings of qtcreaor, however I managed to identify the specific config lines that are responsible. What does qtcreator actually change here?
Please note that "racoon" is the project name and the above diff screenshot is much larger than formatted by stackoverflow (right-click to view full resolution).
Thank you.
i had exactly the same problem using Ubuntu 14.10 and resolved it by doing the following:
Get ftp://ftp.pbone.net/mirror/ftp.sourceforge.net/pub/sourceforge/a/an/anthonos/mirror/os3-next/os3-rpm/q/qtcreator-3.1.2-0.x86_64.rpm
Extract the file /usr/lib/qtcreator/plugins/QtProject/libCMakeProjectManager.so
Overwrite this file at
/usr/lib/x86_64-linux-gnu/qtcreator/plugins/ ( at least on x64)
in your system
This will replace the cmake plugin which is currently version 3.1.1 with 3.1.2 which will make the problem disappear !
I installed qtcreator using Qt's own installer instead of the one provided by Ubuntu. It installs version 5.3.1 and fixes the problem.
I have an application using JRuby 1.6.7, Ruby 1.9.2, Rails 3.1.3 and Warbler 1.4.0.beta2
For a while now, I have been trying to update the application to use JRuby 1.7.x. Every time I tried (with versions 1.7.3, 1.7.4, and most recently 1.7.6) I would get the following error:
org.jruby.rack.RackInitializationException: No such file or directory - /home/production/var/tmp/Jetty_0_0_.war/webapp/WEB-INF/lib/gems.jar!/gems/activesupport-3.1.3/lib/active_support/locale/en.yml
After some help from this question here: Warble not including active support locale files, pin pointed that that issue was with the warbler configuration in my application. We had enabled the following configuration:
config.features = %w(gemjar executable compiled)
Specifically, the gemjar feature was the one causing the issue. With that feature disabled, everything works fine (the WAR deploys perfectly)
I am wondering, if anyone else has run into this, or if anyone knows what the issue might be?
And then more specifically, what are the disadvantages to disabling the gemjar feature of Warbler? From what I can tell, there shouldn't theoretically be anything devastating by disabling it... but I may be overlooking something.
(I do also wonder if the full warbler 1.4.0 release might fix this... but I can't find anything about when a release might be coming out)
there are none - actually running a .war with gemjar might have issues on some servers (esp. if they do not expand the deployed .war, since then it's quite hard to reference files/resources packaged in a .war while still inside a .jar). on the other hand it should roll fine if things are expanded (even with gemjar) ...
you should definitely report this with Warbler's repository (if not reported already).
it should not be hard to fix - likely a one liner, I know a PR would be most welcome :)
NOTE: on the other hand if it worked in a previous JRuby and updating 1.7.x is the issue, than it might be a "regression" on JRuby's side and they might actually fix this if they knew about it ...
After a fresh install of Lion and Xcode 4.1 from the Mac App Store, I would like to install another version of Xcode alongside.
I heard that this perfectly safe to install it in another directory (considering the first to be on /Developer). The only thing to remember is that running xcodebuild would result in launching the last one installed.
But I have another issue while installing it, even f I changed the directory it clearly says that it will upgrade Xcode Toolset, System Tools and UNIX Development and that they can only be located is /Developer and for one installation per system, here is a screenshot :
So how to have another clean instance of Xcode and SDKs without screwing up the production one ?
Thanks a lot.
It doesn't seem to be possible to install the System Tools on both versions. I've never had success with that.
One thing to note, if you install an older version of xCode side-by-side with the latest version, the "Build Archive" function in the Organizer will not function. The only remedy I found was to remove both xCodes and reinstall the one I wanted to use for building the archive. It was a painful process.
Actually you can do this (or at least I seem to be able to). At times I have had three separate instances of XCode installed - an older XCode 3.x (which I've subsequently gotten rid of), an XCode 4 production, an XCode 5 beta; all in separate directories.
The key thing for me was calling the command line tool to tell which system is the "primary" xcode for the purposes of running xcodebuild, instruments, agvtool and a bunch of others: xcode-select -switch /Developer (just man xcode-select ftw).
So, I have a 4.0.2 build as primary now, and keep upgrading the iOS5 betas. I try them out, but when I want to cut a production build using 4.0.2, I ensure that my system knows that /Developer is current, switching it if I need to. FWIW, there is risk that the single-set-of-System-tools could be broken when you replace them with the latest set, but that's (so far) never hit me.
Also, for reference there is another discussion along similar lines here: Install xCode 3.2.3 w/ iPhone SDK 4, get "Base SDK missing", can't see other SDKs