Pushing older package version to octopus

Hello,

I’m working on a project with a Trunk (v2.4.x.x) and a Branch (v2.3.x.x). Our TeamCity is configured to push packages to octopus nuget repo whenever a new deployment is required. I’ve successfully pushed the trunk versions of the packages.
However, when trying to push the branch package, I get a “(400) Bad Request” response:

Cmd> NuGet.exe push “Package.2.3.2.11.nupkg” [apiKey] -s https://[octopus url]/nuget/packages -Verbosity detailed
Pushing Package 2.3.2.11 to ‘https://[octopus url]/nuget/packages’…
PUT https://[octopus url]/nuget/packages/
System.InvalidOperationException: Failed to process request. ‘Bad Request’. The remote server returned an error: (400) Bad Request… —> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at NuGet.RequestHelper.GetResponse()
at NuGet.HttpClient.GetResponse()
at NuGet.PackageServer.EnsureSuccessfulResponse(HttpClient client, Nullable1 expectedStatusCode) --- End of inner exception stack trace --- at NuGet.PackageServer.EnsureSuccessfulResponse(HttpClient client, Nullable1 expectedStatusCode)
at NuGet.PackageServer.PushPackageToServer(String apiKey, Func`1 packageStreamFactory, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at NuGet.PackageServer.PushPackage(String apiKey, IPackage package, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at NuGet.Commands.PushCommand.PushPackageCore(String source, String apiKey, PackageServer packageServer, String packageToPush, TimeSpan timeout)
at NuGet.Commands.PushCommand.PushPackage(String packagePath, String source, String apiKey, TimeSpan timeout)
at NuGet.Commands.PushCommand.ExecuteCommand()
at NuGet.Commands.Command.Execute()
at NuGet.Program.Main(String[] args)

I’m thinking that it won’t let me because it’s an older version. But I’m a bit worried about this, as we need to be able to work on both the branch and the trunk, in parallel.
Is this something I could get your help with?
Thanks!

Regards,
Diana

Oops… my mistake. The error occurred because a package with the same version number was already there. My TeamCity build configuration was publishing the same version twice!
Sorry!