Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.14.6, 3.8.0, 2.14.8, 3.10.0, 2.14.10, 3.14.0
-
Fix Version/s: 3.15.0
-
Labels:
-
Epic Link:
Description
I just upgraded from 2.14.8 to 3.10.0 and used the upgrade capability. One of my repositories holds hosted ruby gems. The actual migration mostly worked - the gems were in the new version of Nexus, but bundler and gem could not find them. I would get errors like "Could not find a valid gem"
I tried using both the group repo (which proxied rubygems.org and held my hosted) as well as my hosted repo. While using the group, I was able to pull gems from rubygems.org.
The Nexus API listed all gems correctly. I was able to work around this by using the API to loop through all gems, download them, delete them from Nexus, and then I re-submitted them to nexus using the nexus gem. Once I did that, bundler and gem were able to find the gems succesfully.
It appears as though metadata was lost during the transfer. Not sure exactly what.
Sonatype added Acceptance Criteria
- Verify this works with an uncompressed index as well as the compressed solution
Attachments
Issue Links
- relates
-
NEXUS-14885 Remove support for the non-gzipped specs 4.8 from Rubygems
-
- Closed
-