Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NuGet install fails #54

Closed
mavnn opened this issue Jan 8, 2014 · 18 comments
Closed

NuGet install fails #54

mavnn opened this issue Jan 8, 2014 · 18 comments

Comments

@mavnn
Copy link
Contributor

mavnn commented Jan 8, 2014

With error: An item with the same key has already been added.

On Visual Studio 2012, Nuget package manager version 2.7.41101.299. Same error with the 2.7 command line exe.

@haf
Copy link
Contributor

haf commented Jan 8, 2014

Can you run rake?

@mavnn
Copy link
Contributor Author

mavnn commented Jan 8, 2014

No, I get:

Bundler::GemspecError: Could not read gem at C:/Ruby193/lib/ruby/gems/1.9.1/cache/nokogiri-1.6.0-x86-mingw32.gem. It may be corrupted.
An error occurred while installing nokogiri (1.6.0), and Bundler cannot
continue.
Make sure that `gem install nokogiri -v '1.6.0'` succeeds before bundling.

The original issue occurs when trying to install from nuget.org to another project, not while building suave.

@haf
Copy link
Contributor

haf commented Jan 8, 2014

If you make sure that gem install nokogiri -v '1.6.0' succeeds -- you should be able to run

bundle
rake

I haven't seen this one before though. Are you just opening it in visual studio and getting the 'same key' error?

@mavnn
Copy link
Contributor Author

mavnn commented Jan 8, 2014

gem install nokogiri -v '1.6.0' fails with

ERROR:  Error installing nokogiri:
        invalid gem format for C:/Ruby193/lib/ruby/gems/1.9.1/cache/nokogiri-1.6.0-x86-mingw32.gem

Unfortunately, I'm not really enough of a ruby person to get any further without research.

The same key error occurs when I create a new F# library project in Visual Studio and try and add Suave as a NuGet reference. It also occurs if I try and run nuget install from the command line.

@haf
Copy link
Contributor

haf commented Jan 8, 2014

I see...

The reason for that is a bugged suave nuget. #45 is relevant too.

I think we should push a new nuget asap, what do you say @ademar ? Would you like to give me permissions and do you think it's a good idea?

@ademar
Copy link
Member

ademar commented Jan 8, 2014

yeah I was about to say that package was corrupted ...

@haf sure go for it

@haf
Copy link
Contributor

haf commented Jan 8, 2014

@ademar I just mailed from the e-mail I have on nuget

@haf
Copy link
Contributor

haf commented Jan 8, 2014

Here's an example NuGet I own if you didn't receive the mail from nuget.org: https://www.nuget.org/packages/NLog.RabbitMQ/ you should be able to find my user from there?

@ademar
Copy link
Member

ademar commented Jan 8, 2014

I added you as owner as soon as i received the message .. I also responded to the mail which had your from

@ademar
Copy link
Member

ademar commented Jan 8, 2014

on nuget says henrik feldt (pending approval)

@haf
Copy link
Contributor

haf commented Jan 8, 2014

Interesting. I really really need to transfer my e-mail to another provider! I still haven't got it...

@haf
Copy link
Contributor

haf commented Jan 12, 2014

See also Albacore/albacore#81

@haf
Copy link
Contributor

haf commented Jan 19, 2014

See also https://nuget.codeplex.com/workitem/3970 - it's an issue with NuGet it seems.

@ademar
Copy link
Member

ademar commented Jan 29, 2014

I think the problem was that in the file [Content_Types].xml the extension XML was listed twice, in capitals and lower case.

@haf Can you try pushing a nuget now? Is this doable from TC ?

@haf
Copy link
Contributor

haf commented Jan 29, 2014

Yes it's very doable, but is it wanted to push a new nuget every build? I normally don't do that.

@ademar
Copy link
Member

ademar commented Jan 29, 2014

Just to kick it manually.

On Wednesday, January 29, 2014, Henrik Feldt notifications@github.com
wrote:

Yes it's very doable, but is it wanted to push a new nuget every build? I
normally don't do that.

Reply to this email directly or view it on GitHubhttps://github.com//issues/54#issuecomment-33630594
.

Ademar Gonzalez
+1-647-891-3606
http://ademar.name
https://github.com/ademar

@haf
Copy link
Contributor

haf commented Jan 29, 2014

Right, sure. I can set up a build task for it.

@ademar
Copy link
Member

ademar commented Feb 10, 2014

I've updated the nuget, the package is good now.

@ademar ademar closed this as completed Feb 10, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants