Posts made by parthu.reddy

A small question, can we upgrade proget but continue using classic maven for some time

@dean-houston Thanks

@dean-houston

https://repo1.maven.org/maven2/com/sun/activation/jakarta.activation/2.0.0-RC2/jakarta.activation-2.0.0-RC2.pom

Getting error for jakarta.activation-2.0.0 versions

Looks like there's some problem in orginal repo itself

Another example:
https://repo1.maven.org/maven2/com/sun/xml/bind/mvn/jaxb-parent/3.0.0/jaxb-parent-3.0.0.pom

I'm getting few of these errors.

An empty feed is getting this error

Getting this error while moving from classic maven to new maven on 2024.22

We've 3 proget servers in cluster, during upgrade do we have to stop all 3 servers and then do upgrade or can we do upgrade one server after another without stopping other servers.

Thanks

@dean-houston Thanks

Steps to reproduce:

1. Upgrade from 2024.13 to 2024.22
2. Upgrade classic maven feed to new maven feed
3. Revert back to classic maven feed
4. Downgrade from 2024.22 to 2024.13
5. Try accessing connectors page
   You'll get above error.

Could you pls look into it. If we've some problems and if we want to downgrade it's better if such issues doesn't occur.

Thanks

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.

Any reason why whole database is locked?

Looks like it's starting with this.

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.

https://repo1.maven.org/maven2/org/scala-sbt/jline/jline/2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493/jline-2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493.pom - maven pom url

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.

@atripp Ohh, sorry my mistake, changed it to proget, same problem actually. Will check at our end.

@atripp Thanks

Actually it's just postman to trigger APIs, pls check the versions. I triggered multiple versions, All of them got immediate response except for the 1.3.1 and 1.3.0. These two versions are failing sometimes. Will check with wireshark, pls check at your end as well.(there might be possibilities of missing headers that helps in closing socket or something like that.)

Actually this has nothing to do with npm client I guess. As I'm directly downloading the tgz from proget, which was causing error in npm client.

Getting this error for only 1.3.1 and 1.3.0 versions. others are working fine. Any idea why?

This is happening randomly.

Got this error. Could you check this.

Version 2024.3 (Build 4) - this is the version

getting
This artifact cannot be downloaded because it is Noncompliant: Artifact does not have an associated .pom.
error for a lot of maven repositories.

https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-project/3.1.2/hadoop-project-3.1.2.pom

I understand that there is some parsing problem with POM file but it can be downloaded I guess, as SHA1 and MD5 are valid.

Let us know your thoughts.