Simple:
Poetry is in version 1.2.x and I want to downgrade it to 1.1.x.
Is there a way to simply auto-downgrade poetry on itself?
Ok, really simple answer: poetry self update#1.1.15
Related
I need to update old dependencies because of security reasons in a project, that uses Yarn and I would like to know the best way to do this. I have used yarn add package-name#latest and yarn upgrade package-name#latest with the same result. The old version package definition remains. Is that acceptable? Since I have to update the old version for security, I think the old version should be removed. Is there a command that updates a package to a specific version and removes the old package definition?
The situation you are describing should only arise if you also have transitive dependencies that come from other dependencies.
So you may have another package that depends on acorn in a lower version.
If this is not the case I would try:
yarn upgrade package-name --latest
To update all packages to the latest versions, I recommend:
yarn upgrade-interactive --latest
We built a project using pycnn. Currently it has been replaced by dynet.Now how can we get pycnn back?
Install it from Github:
pip install git+https://github.com/clab/cnn-v1#egg=pycnn&subdirectory=pycnn
Trying to install the KnpGaufretteBundle in a Symfony 2.3 project, I'm having no luck. The problem is:
minimum-stability:stable (in composer.json);
the bundle I require is dev-master version still.
Reading this in the Symfony docs was frustrating:
If you know of a cool bundle or PHP library that still requires a dev
minimum stability, talk to the lead developer and convince him to tag
a stable release.
I'm not changing the minimum stability of the whole project to dev, as it would certainly make a huge mess - I mean, can't I use stable packages and dev packages side by side?
Am I missing something about composer maybe?
Edit (14 August 2013)
According to Sven's answer below, I've edited my composer.json (you can find it here) and it started to work. Anyway, this is a partial solution, because inline aliases do not work for dependencies - so in my case I'd have to specify all dependencies of "less-than-stable" packages first, and alias them one by one.
just use
"knplabs/knp-gaufrette-bundle": "dev-master#dev"
if you need the latest dev version
you can also change minimum-stability to dev and add "prefer-stable": true like this:
"minimum-stability": "dev",
"prefer-stable": true,
then composer will always try to find a stable version and if nothing found install dev, so your symfony packages will be still stable.
But in your case composer will install v0.1.4 (latest stable of knplabs/knp-gaufrette-bundle), so you need dev-master#dev anyway. prefer-stable is just a hint for you.
Have a look at aliases: http://getcomposer.org/doc/articles/aliases.md
They are supposed to allow you to address a branch (which by definition is always in development, because you can only access the latest commit) in a way that that branch should be the logical extension of a version tag.
For a yet untagged project, a proper assumed tag version would be like "0.0.0".
You should try the inline alias for the bundle.
I was able to install couchdb's latest version on Mac OS using Homebrew.Is there a way i could install the previous version (0.10.0).I have tried using iriscouch but could not clone the repositories.
What about installing versions like 1.1.1 is there a way to do that using homebrew?
Thanks
The current release is 1.2.0, and the previous one is 1.1.1. 0.10.0 is a long way back in CouchDB history. Are you sure you need that far back? What's the issue you are having?
For 1.1.1 you can simply revert to the previous formula (check it out via git) or simply edit the couchdb.rb file directly.
If you need 0.10.0, another alternative is to try https://github.com/iriscouch/build-couchdb.
Finally, try building Erlang R14B01 from source, spidermonkey 1.7.0 and then using a similar configuration as in the 0.10.0 homebrew recipe:
require 'brewkit'
class Couchdb
depends_on 'spidermonkey'
depends_on 'icu4c'
depends_on 'erlang'
def install
system "./configure", "--prefix=#{prefix}",
"--localstatedir=#{var}",
"--sysconfdir=#{etc}",
"--with-erlang=#{HOMEBREW_PREFIX}/lib/erlang/usr/include"
system "make"
system "make install"
(var+'lib'+'couchdb').mkpath
(var+'log'+'couchdb').mkpath
end
end
Both CouchDB, Mac OS X, Erlang, Spidermonkey & other dependencies have evolved significantly since late 2009 when 0.10.0 was released. Expect some bumps in the road.
So, I got a small site started in node.js (my first one) using Express. Pretty happy with it, until I tried to deploy to Heroku and found that I had 0.4.9 installed and they only support 0.4.7.
Is uninstalling 0.4.9 and installing 0.4.7 my only option, or is there a way to do a side-by-side on the two?
You can override the version of node.js and npm by customizing the Heroku build pack:
http://blog.superpat.com/2011/11/15/running-your-own-node-js-version-on-heroku/
Actually...you do not have to remove anything.
Just ensure you are using features of node compliant with node 0.4.7 and when you make your package.json which specifies your dependencies has the correct version number or range specified.
I had a similar issue where one of our developers made is packacge and set the dependency to node 0.4.8 however it didn't require this it was just what version he was using at the time, we ended up updating his package.json to list node 0.4.7 instead and then my package which depended on his deployed to heroku just fine.
It seems Heroku only supports 0.4.7 at the moment and even suggests to develop strictly on that version.
If you have to use heroku then you have to uninstall 0.4.9, install 0.4.7.
If you don't have to use heroku. You can always setup a VPS yourself, and you will have the freedom to install whatever version that pleases you. :D