Re: Get package license with ProGetClient
the pgutils packages metadata + API end point to be used in Inedo.Proget lib is what I need :)
Do you have a timeline for the implementation ?
Best Regards,
Pedro
Re: Get package license with ProGetClient
the pgutils packages metadata + API end point to be used in Inedo.Proget lib is what I need :)
Do you have a timeline for the implementation ?
Best Regards,
Pedro
Re: Get package license with ProGetClient
Sorry to recover an old topic, but what I want is to be able to read the package metadata including the license (LicenseUrl, LicenseType, or LicenseExpression) assigned in ProGet, which is MIT (the license assigned to the package in ProGet).
The PackageVersionInfo (https://docs.inedo.com/docs/proget/api/packages#package-version) does not contain the license information.
Best Regards,
Pedro
Hello,
the version 25.0.9 of proget is not present in the inedo feed, and the hub is not able to find: https://proget.inedo.com/feeds/Products/InedoReleases/ProGet/versions/all
Best Regards,
Pedro
Hi @atripp ,
thank you for the update. I reverted to 2025.07 and I will wait for the next maintenance release.
@power_pille thank you too, for your findings and suggestions.
I'm having the same problem, and I can see in the database the duplicated entries.
Hello,
Is it possible to get the Package Policies with ProGetClient? I'm interested in the License Rules.
Best Regards,
Pedro
Hello,
I was trying to use ProGetClient to get the license information from a NuGet package present on a feed, but I didn't find any method to get that information.
I know I can use the NuGet CLI to get that information, but if the license is set on ProGet GUI, the returned license is not what we have on ProGet, but what is present in the package metadata.
As an example, the System.Memory 4.5.5 has a URL license, and on ProGet, it was set to MIT.
Best Regards,
Pedro
Hello @atripp ,
Thank you for your help.
We have an intermediate certificate (proxy), which I think, as you point out, can be the problem. I will clarify with our IT department. Anyway, after reading a little bit more, there is a variable to force Kaniko to use HTTP/1.1.
variables:
GODEBUG: "http2client=0"
After adding that, everything works :)
Thank you!
Best Regards,
Pedro
Hello,
I'm trying to publish a Docker image from Gitlab pipeline using Kaniko to Proget.
With HTTP, everything goes smoothly, but with HTTPS, an error occurs: stream error: stream ID 47; HTTP_1_1_REQUIRED; received from peer
I checked all certificates, and they are valid.
Do you have any advice on continuing the troubleshooting?
The full error:
Pushing image to xxx.lokal:8625/dev-images/image-name:latest
error pushing image: failed to push to destination xxx.lokal:8625/dev-images/image-name:latest: Head "https://xxx.lokal:8625/v2/dev-images/image-name/blobs/sha256:944cb9daf72b35ac4c2a49b5ad6d66fd45e201e5fd2a67b47cb5d4b4c838f19e": stream error: stream ID 47; HTTP_1_1_REQUIRED; received from peer
Best Regards,
Pedro