Deploying package with dependencies fails

Legacy Uncategorised
1

I know it’s probably not a good idea to have a package with dependencies,
but if you try, this is the exception that is logged in the task output:

2011-06-23 12:28:10 ERROR Deployment on the tentacle failed: System.InvalidOperationException: Unable to resolve dependency ‘log4net (≥ 1.2.10)’.
at NuGet.InstallWalker.OnDependencyResolveError(PackageDependency dependency)
at NuGet.PackageWalker.Walk(IPackage package)
at NuGet.InstallWalker.ResolveOperations(IPackage package)
at NuGet.PackageManager.Execute(IPackage package, IPackageOperationResolver resolver)
at NuGet.PackageManager.InstallPackage(IPackage package, Boolean ignoreDependencies)
at NuGet.PackageManager.InstallPackage(String packageId, Version version, Boolean ignoreDependencies)
at NuGet.PackageManager.InstallPackage(String packageId, Version version)
at Octopus.Tentacle.Packages.UploadedPackageInstaller.Install(PackageMetadata package) in l:\Stovell Australia\Octopus\source\Octopus.Tentacle\Packages\UploadedPackageInstaller.cs:line 22
at Octopus.Tentacle.Jobs.DeployPackageJobExecutor.Execute(DeployPackageJob job) in l:\Stovell Australia\Octopus\source\Octopus.Tentacle\Jobs\DeployPackageJobExecutor.cs:line 30
at Octopus.Tentacle.Jobs.DeployPackageJobExecutor.Execute(Job job) in l:\Stovell Australia\Octopus\source\Octopus.Tentacle\Jobs\DeployPackageJobExecutor.cs:line 25
at Octopus.Tentacle.Jobs.JobQueue.RunDeploymentsOnBackgroundThread(Object state) in l:\Stovell Australia\Octopus\source\Octopus.Tentacle\Jobs\JobQueue.cs:line 73

2

Sorry, this was marked as spam so I didn’t see it until now.

This question explains why dependencies won’t be supported for a while:

http://help.octopusdeploy.com/discussions/suggestions/3-enhancement-be-able-to-interact-with-dependent-packages

The next build will include a change that throws early, with a message along the lines of “NuGet packages with dependencies are not currently supported. The package ‘Acme.Web 1.0’ appears to have dependencies.”

3

Well, my situation was simpeler.

My test was the template ASP.NET MVC 3 application, just created a new project in visual studio. Packaged it up with NuGet (using the .csproj file), which then includes jQuery, EF, … as dependencies.

The exception above shows log4net because I added that dependency as a test.