After renaming the feed the API keys are pointing to maven old feed. Should this be done manually. If so I think it's better if it's mentioned in documentation as well.
https://docs.inedo.com/docs/proget/feeds/maven#maven-classic-feed-types
Pls let us know your thoughts. If there are any such cases, pls let us know.
Every time I run dotnet tool run paket restore --verbose I'm getting error with different packages. It's not the same every time I run it. Could you let us know why this is happening.
We came across this while trying to upgrade from 2024.6 to 2024.13. So we again downgraded it to 2024.6 and checked there. Looks like it's happening in both the versions.
Getting lot of these errors, could you suggest on this.
Thanks, we're planning to upgrade tomorrow. Will keep you updated.
Yes @stevedennis , that would be helpful. Pls ship it early.
Thanks
And our team suggested that increasing VARCHAR(50) to a larger number for versions in Maven tables could help. Could you check it.
If it's not possible, could you let us know an eta on fixing this.
@stevedennis said in File not found org.scala-sbt.jline/jline:
2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493
In the above screenshot, there is a version without 3 in it, is it created by proget? When I clicked that version, the files inside it are same as the one with 3
Versions that are on maven doesn't match the versions that are on proget.
Getting 2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c096450749 extra version on proget.
http://proget.sand.wtg.zone/maven2/Maven-Sbt/org/scala-sbt/jline/jline/2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c096450749/jline-2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493.pom - proget pom url, looks like 3 is missing.
This is happening in version 2024.5, after upgrading from 2024.3.
Deleted the artifact, now not able to find any packages in versions.
