Bootstrapper doesn't work with some Nuget repos

Description

The bootstrapper does not work against our internal Nexus repo which is hosting Nuget instances. Having debugged the bootstrapper, it seems that this is because the Bootstrapper seems to exclusively use the /package-versions/ Nuget v2 API endpoint, which some Nuget repos don't seem to support, including our corporate Nexus installation (v2.13).

I'm unclear on whether it should support this because I can't find a clear documentation for either Nuget or Nexus... but I can see that paket.exe itself falls back to alternative OData query endpoints /FindPackagesById()?... and /Packages?$filter=... which both work fine, so Paket.exe doesn't have this problem - only the bootstrapper.

Repro steps

Difficult to specify beyond the description above as I cannot expose our corporate nexus repo externally.

I'm running

paket.bootstrapper.exe -f --force-nuget --nuget-source=http://my-nuget-repo/the/repo

Expected behavior

Bootstrapper downloads paket.exe

Actual behavior

Error printed to console.
"The remote server turned an error: (404) Not Found. (Nuget)

Known workarounds

None.

Related information

• Operating system = Windows 7 x64
• Branch - v3.16.3.0

Start with the bootstrapper's NuGet download path and compare its /package-versions/ request with Paket.exe's fallback OData endpoints, /FindPackagesById() and /Packages?$filter=.... Reproduce the reported command against a compatible Nexus-style repository; done means paket.bootstrapper.exe downloads paket.exe when /package-versions/ is unavailable.