Version 2.8 of NuGet server now provides a flag in the web.config called allowOverrideExistingPackageOnPush which allows you to decide if you want existing package versions to be overwritten. We decided to set this to false on our internal repository because we didn't want existing packages being accidentally overwritten. However, now when I do a pack and push using the -Symbols flag, the push command will successfully publish the nuget package but when it tries to publish the symbols, it only uses the first part of the package name up to the end of the version number. This means that it fails to publish the symbols package as it believes that the package already exists.
I have yet to find any information or bug reports via googling, and for the package I am writing now I can dispense with symbols, but we need a longer term solution which will allow us to publish symbols and disallow overwriting.
Has anyone encountered this, and if so have you found a way round this (other than not publishing symbols or allowing overwriting)? This has been sapping time which I can't really spare.
Related
I am in the process of migrating to the latest version of ProGet. I'm currently using version 3.8.6, so am quite far behind the stable release.
I decided to start fresh, moving to a brand new Windows Server 2016 box in AWS, and using RDS for the SQL database.
The new setup is working perfectly, I have imported our NuGet packages by creating a feed, entering a Drop Path and dropping all of the packages there. ProGet picked up on this and moved them all to the Feed.
However, I am now trying to import our npm packages. I've created the feed, added a drop location and moved all the npm packges over. On the old server, they're all already in subfolders. ProGet seems to refuse to add them unless they're in the root folder specified as the Drop Path. So I've moved some packages there (inconveniently they're all called package.tgz...) and it picks them up, moves them to /ProgramData/ProGet/Packages/.npm/F5/ puts them in folder too but then does not become visble in the feed on the web interface.
The package number increases, and if I click packages I can see them all, then click into them and download the package, but it doesn't show up on the main Feed 'Page'.
On the other hand, if I manually upload a package via the web interface, it doesn't put the packages in the same location as above, but it is visible on the main feed page... Is this a bug or am I doing something wrong? The NuGet packages work perfectly using the same method, so I'm confused as to why npm isn't working.
I noticed this same behavior when using the bulk upload utilizing the drop path. From what I can tell, you must have at least one version with the "latest" tag on the details for it to show anything in the Feeds view.
I have been trying to use GoClipse (0.8.1v2001409161333 - latest available from the goclipse_feature.feature.group) with Eclipse (4.4.2) on Linux (CentOS6.6) with GO (1.4.2-2.el6) installed via yum from EPEL and have only achieved partial functionality.
Intellisense appears to work fine for the built in packages but GoClipse appears to do something weird with it's directory structure that is different from the normal GO workspace layout. The existing structure under source control looks like:
$GOPATH/bin/...
$GOPATH/pkg/...
$GOPATH/src/externalsite/module/version/*.go
$GOPATH/src/externalsite/module/version/subdir/*.go
$GOPATH/src/me/module/*.go
$GOPATH/src/me/module/feature/*.go
When I try and use GoClipse it always appears to insist that the *.go files must be a peer of the bin|pkg|src directories. This means that I either have my *.go files at $GOPATH or tell GoClipse where main.go is ($GOPATH/src/me/module/main.go) and GoClipse creates the bin|pkg|src directories again:
$GOPATH/src/me/module/bin/
$GOPATH/src/me/module/pkg/
$GOPATH/src/me/module/src/
My GoClipse configuration has $GOPATH set appropriately (I have tried with $GOROOT undefined or set to the yum install location to no effect) and when creating the Go project from existing code specifying the location as $GOPATH/src/me/module/ (manually expanding $GOPATH)
Some resources that I have located do not appear to offer any advice on getting GoClipse to respect the proper go workspace structure and I am hoping someone can tell me how to do this.
The following resources might be of interest but they do not solve this difficulty:
How to run a GO project in eclipse with goclipse installed
https://github.com/GoClipse/goclipse
Indeed, goclipse.github.io/releases is the latest update site URL, so you should use the latest version (the URL did change several times since in the span of the previous year). The way Goclipse handles the Go enviroment has changed significantly since 0.8.0, particularly with 0.9.0, which allows creating an Eclipse project on a folder inside a GOPATH 'src' entry. (and other cases are handled better, especially with the builder).
Note: you will need to recreate your Eclipse Go projects after updating (0.10.0 had some internal, non backward-compatible changes).
You might want to consult the changelog for more details: https://github.com/GoClipse/goclipse/releases
I am trying to install a package (oForms) with a new Orchard 1.8 installation, but receiving the following error:
"Package installation failed: There was an error installing the requested package. This can happen if the server does not have write access to the '~/Modules' or '~/Themes' folder of the web site. If the site is running in shared hosted environement, adding write access to these folders sometimes needs to be done manually through the Hoster control panel. Once Themes and Modules have been installed, it is recommended to remove write access to these folders."
This seemed rather straightforward, however my host has confirmed permissions are fine (and even added Everyone/Full Control to the folder), so I'm lost and appears to be happening with all modules from the Gallery, not just oForms. I changed the Config/log4net.config file to log everything, and I don't see anything specific in there except where it logs the same message above. Nothing outside of that stands out at all.
Is there a way to see why this is failing? Or, if not, is there a way to get the module and install it manually? I tried to download from the gallery, but it's just a NuGet package so I'm not sure how to take that and grab the raw module files.
You can use a program like 7zip to unzip the nuget package, then copy in the module manually yourself.
As for the permissions, when adding a new permission to the folder use:
IIS AppPool\name of your application pool
I also had this exact error message when installing modules from the gallery, and it took me a while to figure out what was happening. I made new installations, copying over files one-by-one, and eventually found the culprit. For my case anyways...
For me, it was all due to a bad formatting in my custom Theme. Specifically the Theme.txt file. The line where is says Version:, I had it formatted without any "."
Good:
Version: 1.0
BAD:
Version: 1
Yes, doing this simple mistake prevented me from installing Modules.
We are using TFS 2012 to build our solution. Once this is done I use the build output to create some NuGet packages which I publish internally. I have just started building these packages with symbols as well so that I can publish these NuGet symbols packages to our internal Symbols Server.
However I am having trouble publishing the symbols packages to the Symbols Server. The reason is that the DLLs and PDBs don't match. I used ChkMatch and indeed the age property is different on the DLLs and PDBs that sit in the TFS Dropfolder Release directory. If I grab the PDB files instead from the obj folder in the actual build directories then they match.
Now I believe that the age property is getting incremented because my Build Process Template has the property "Source and Symbol Server Settings > Index Sources" set to True.
Is it correct to just set this property for false?
Will there be any unforeseen consequences?
If I am using NuGet to publish my symbols can I just ignore an Source and Symbol Server Settings in the build process template?
The age discrepancy raised by chkmatch is misleading. As discussed here (bottom comments section) , it should not prevent Visual Studio from finding the matching Program Database file (PDB) and loading the Symbols.
I have been struggling with this and thought that the age difference was preventing me from stepping through the source code being indexed. There was another issue at hand and it got me on the wrong track. So, a word of caution regarding the age property difference when using chkmatch to debug such issues.
Im building some nuget packages on our build server and have run into a problem.
I have to use nuget pack xxx.csproj to get replacement tokens to work with my nuspec file which is allright.
But when I do the nuget pack on the csproj a lot of "noise" is added to the package in form of folders etc from Open Package Convention.
Due to the fact that im using the packages with Octopus Deploy, i would like to avoid these extra folders.
Is it possible to avoid the extra OPC folders without specifying all the replacement tokens on the command line?
What's the names of these extra folders? Please open a new issue/feature request on http://nuget.codeplex.com and describe your issue in more details.