I have just used the NuGet Package Manager to see what updates are available and it informed be about 10.0.3 - 11.0.1:
I understand that a main version number change can be code breaking. How can I ascertain the issues I will have if I upgrade the package? I could not see any information.
I see similar questions but they were for version 6x.
Related
Background: I experienced what appeared to be a bug in System.CommandLine and noticed the Nuget package that I used (System.CommandLine.Experimental 0.3.0-alpha.19405.1) hadn't been updated for 3 months. I felt I should try out a nightly build before I file a bug report.
Then I followed their README which stated
Daily builds are available if you add this feed to your nuget.config: https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json.
and as I was using Paket for my toy project (primarily for learning purposes) that needed System.CommandLine, I instead updated packet.dependencies
source https://www.nuget.org/api/v2
nuget FSharp.Core
source https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json
nuget System.CommandLine.Experimental
However when I ran paket update
$ paket update
Paket version 5.224.0
Resolving packages for group Main:
Possible Performance degradation, could not retrieve 'https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json/Packages?semVerLevel=2.0.0&$filter=Id eq 'System.CommandLine.Experimental'', ignoring further warnings for this source
- FSharp.Core 4.7.0
- System.CommandLine.Experimental 0.3.0-alpha.19405.1
- system.memory 4.5.3
- Microsoft.CSharp 4.6.0
- System.Runtime.CompilerServices.Unsafe 4.6.0
- System.Buffers 4.5.0
- System.Numerics.Vectors 4.5.0
/home/nodakai/prog/CommandLineFSharp/paket.lock is already up-to-date
...snip...
And all I got was a 3-months old version from Nuget 0.3.0-alpha.19405.1 which made me sad.
What did I do wrong?
FWIW when I opened the source URL https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json with my web browser, it didn't seem to directly refer to System.CommandLine. But I'm not familiar with Nuget and/or Paket ecosystem so I'm not sure if there was anything wrong with the source data itself.
Try specifying prerelease in paket.dependencies i.e.:
nuget System.CommandLine.Experimental prerelease
The available versions are listed here:
https://dotnetfeed.blob.core.windows.net/dotnet-core/flatcontainer/system.commandline.experimental/index.json
I'm coming to ask a question, maybe stupid, but I can't find a good explanation about it..
For this example, I'll take for example a Xamarin Forms - Portable Project and look at the Project.Droid part. Also, I'm gonna take the following packages:
Xamarin.Forms.Map 2.3.1.114
and
Xamarin.Android.Support.Vector.Drawable 23.3.0
Xamarin.Android.Support.v7.RecyclerView 23.3.0
Xamarin.Android.Support.v7.MediaRouter 23.3.0
Xamarin.Android.Support.v7.CardView 23.3.0
Xamarin.Android.Support.v7.AppCompat 23.3.0
Xamarin.Android.Support.v4 23.3.0
Xamarin.Android.Support.Design 23.3.0
Xamarin.Android.Support.Animated.Vector.Drawable 23.3.0
As you can see, the Xamarin.Forms.Map package is version 2.3.1.114 and the others, 23.3.0. However, an update is available, but when I make it, the package of 23.3.0 version update to 23.4.0.1 while Xamarin.Forms.Map is downgrading to 1.5.1.6471 ...
Why does it work like it? why everything doesn't up to the last update? What are the differents effects of this update/downgrade? Also, what's the best choice? Does it's better to update the Xamarin.Android.Support.xxx packages and downgrade the Xamarin.Forms.Map one or do the reverse?
Thank in advance for your answer/explanation :)
Some package are update and not compatible with the last version of Xamarin.form, because the updates are not at the same frequency the principal reason, are all the new versions of Xamarin.form need to be probe, and be stable and may be exist a delay between one and other.
for Example if you try to install Xamarin.Android.Support.Design
Attempting to resolve dependencies for package 'Xamarin.Android.Support.Design.23.4.0.1' with DependencyBehavior 'Lowest'
One or more unresolved package dependency constraints detected in the existing packages.config file. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'Xamarin.Android.Support.Design 23.3.0'
Unable to resolve dependencies. 'Xamarin.Android.Support.Design 23.4.0.1' is not compatible with 'Xamarin.Forms 2.3.1.114 constraint: Xamarin.Android.Support.Design (= 23.3.0)'.
'Xamarin.Android.Support.Design 23.4.0.1' is not compatible with 'Xamarin.Forms 2.3.1.114 constraint: Xamarin.Android.Support.Design (= 23.3.0)'.
Xamarin Form 2.3.1.114 say I'm compatible with the version = 23.3.0
Regards.
The nuget manager allowing you to update packages to the version compatible with target SDK version selected in the project properties. If you need to upgrade to the newer version you have to install newer version of android SDK and update it in project properties to be able to upgrade nuget packages.
Currently the latest public version of the Spiderable package is 1.0.7 (atmosphere link). However on Github the version has been bumped to 1.0.8 (4 days ago).
I need the features from the 1.0.8 update. What's the best way for me to use the 1.0.8 version? I've tried:
meteor add spiderable#1.0.8
But it didn't work, the output was: error: no such version spiderable#1.0.8 .
This version of spiderable has not yet been published by MDG. This is why it says no such version.
While a package is being developed the version may be higher than the version available for use. When it has been tested its usually published along the next meteor version.
There may still be more changes to the package until its published.
If you want to use the package anyway you can copy the spiderable directory from github into a packages/spiderable directory. This may not work with certain dependency errors depending on whether another package using spiderable is required.
The second is to use the github version of meteor. Which is to clone the meteor project using git clone https://github.com/meteor/meteor then use the meteor binary (with the full absolute path) to run your project instead of meteor on its own.
I have this in a package:
api.use([
'kestanous:herald#1.1.3',
'kestanous:herald-email',
]);
As expected, Meteor uses version 1.1.3 of the Herald package.
If I remove the #1.1.3 version, the package's versions.json doesn't change.
But now if I run meteor update kestanous:herald, here's what I get:
$ meteor update kestanous:herald
Changes to your project's package version selections from updating package versions:
kestanous:herald downgraded from 1.1.3 to 1.0.1
It doesn't make sense to me that upgrading a package would actually downgrade it. Especially since kestanous:herald is used nowhere else in the app. Even stranger, there are still no changes to the package's versions.json file despite the message.
So it seems either I don't understand how package versioning works, or else something is not working correctly?
I'm not sure if i'm right on this 100% because the system used is quite weird & has changed so many times until very recently.
Meteor's new package system works on a constraint solver. Each package declares the version of Meteor its designed for, e.g if you designed it for Meteor 0.9.2 and you run it on Meteor 0.1.0 there is a slight difference in the blaze package.
So if a package one of your other packages is dependent on has uses this older version of blaze then the other packages will be downgraded so that it can match this constraint, such that the latest versions of all included packages are used as long as the constraint is matched.
So this can happen if herald has a constraint on it of some older Meteor package or version, or has a dependency on some older package.
While the package doesn't have to be defined explicitly it can be defined implicitly from api.versionsFrom("XXX") too.
Meteor then upgrades or downgrades the packages accordingly.
Additionally there is a "leeway" allowed with the packages allowed depending on the semver spec, minor package version updates are okay, but the major ones force a downgrade, since the new version is deemed incompatible. There's a bit of a discussion on this too.
This is the package.js file for the package for kestanous:herald:
api.versionsFrom('METEOR#0.9.2');
api.use(['check', 'underscore', 'tracker','accounts-base', 'blaze', 'artwells:queue#0.0.3']);
This means that all packages in your meteor project will attempt to be downgraded so that all of them can be compatible with these other dependencies.
If you upgraded the versionsFrom, then meteor would be more accepting to newer versions in other packages.
https://github.com/Meteor-Reaction/Herald/blob/master/package.js#L9
After installing Aptana Studio3 (version 3.3.2) in my Ubuntu 12.10 I find out that the preview button did not work properly. Meaning, I was not able to see the preview in the opened tab. As if internal browser was not working.
Instead of that , I obtained a copy of my index.html which is the doc I am trying to preview.
I find out that Xulrunner was not instaled in my system and therefore I suspect this could be the issue.
Downloaded XULrunner version required by Aptana, with
wget -O xulrunner.deb http://launchpadlibrarian.net/70321329/xulrunner-1.9.2_1.9.2.17%2Bbuild3%2Bnobinonly-0ubuntu1_amd64.deb
But when I tried to install this package I obtained a dependency error asking for ibhunspell-1.2-0
xulrunner-1.9.2 depends on libhunspell-1.2-0
I will appreciate your help to put some light over this issue.
Am I missing something/s here?
Eventually, suggest where to obtain the missing package (libhunspell-1.2-0 ppa or whatever reliable source) and any specific installing instructions if necessary.
Many thanks in advance
UPDATE
Packages installed but problem remains.
I obtained the libhunspell-1.2-0_1.2.11-1_amd64.deb from debian.org
Once succesfully installed I proceed to install the xulrunner.deb
Everything Ok as well!
Now they are all there...but... Internal browser still doesn`t work
If anybody from Aptana or with any experience about this matter, is in the neighborhood , please help.
It is a reported issue of Aptana 3.2.2 (actual version March 2013)
Solution: revert to 3.2.x version or wait until 3.4.x is available (where is already fixed)
Detailed Info
After several checkings and research , I find out that there is a reported issue with the actual version 3.3.2
Issue labeled as:
Aptana Studio APSTUD-7636
Cannot show preview (embedded WebKit browser)
This can be seen here at appcelerator issue tracker where states the following
Expected Result:
Preview should be opened exactly as in previous versions of Aptana. Preview worked without errors in Aptana 3.2.X before updating to 3.3.1.
This was corrected for version 3.3.4 which at present (march 2013) I am not able to obtain. So I reverted to 3.2.2 which I downloaded from appacelerator wiki
Full package name: Aptana_Studio_3_Setup_Linux_x86_64_3.2.2.zip
I installed and the preview is working as it should
So: Until version 3.4.x is not available ill keep this old one 3.2.2
I hope that my research will be useful to someone else.