You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What problem are you trying to solve?
We have a nuget proxy repo that connects to jfrog artifactory. When a package of specific version is being removed from jfrog artifactory our nexus repo does not show that package version in Browse index(html view) but when I simply use search bar and search for the package the deleted version appears in the result and the last update date is set 1/1/1970 with the file size mentioned as 0 bytes.
this cause issue in our builds that nuget cli resolves the dependencies to one of these deleted assets and our dotnet nuget restore and build fails with a message package with the version not found in feed.
Do you have a workaround you are using at present?
Temporarily to make our build/restore work with latest nuget client (6.12.1) we had to recursively delete (manually) the faulty assets with date (1/1/1970) and size 0 bytes from the search in nexus.
What feature or behavior is this required for?
dotnet nuget restore/build
How could we solve this issue? (Not knowing is okay!)
my expectations is that if we delete a package version or if a package is removed from the remote repo(ex jfrog artificatory) nuget search should not display it
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
I tried the 2 versions of Nexus i.e. 3.69.0-02 and 3.72.0-04 and the search displaying deleted packages with last updated date on 1/1/1970 behavior is seen in both.
OS -Windows 10
Database 3.69.0-02 uses Orient DB and 3.72.0-04 is H2, so issue is seen in both DBs
In this proxy repo we have set Maximum Component age and maximum metadata age to just 5 minutes. Nuget protocol is set to Nuget v2
Anything else?
one interesting observation is that when using latest nuget.exe client 6.12.1 this issue is seen and when downgrading the nuget client to 6.11 or 6.10 this issue of picking the deleted versions of packages for resolution does not happen.
VishnuJin
changed the title
Nexus search displays deleted package version with last updated date as 1/1/970 and file sizes as 0 bytes
Nexus search displays deleted package version with last updated date as 1/1/1970 and file sizes as 0 bytes
Nov 29, 2024
What problem are you trying to solve?
We have a nuget proxy repo that connects to jfrog artifactory. When a package of specific version is being removed from jfrog artifactory our nexus repo does not show that package version in Browse index(html view) but when I simply use search bar and search for the package the deleted version appears in the result and the last update date is set 1/1/1970 with the file size mentioned as 0 bytes.
this cause issue in our builds that nuget cli resolves the dependencies to one of these deleted assets and our dotnet nuget restore and build fails with a message package with the version not found in feed.
Do you have a workaround you are using at present?
Temporarily to make our build/restore work with latest nuget client (6.12.1) we had to recursively delete (manually) the faulty assets with date (1/1/1970) and size 0 bytes from the search in nexus.
What feature or behavior is this required for?
dotnet nuget restore/build
How could we solve this issue? (Not knowing is okay!)
my expectations is that if we delete a package version or if a package is removed from the remote repo(ex jfrog artificatory) nuget search should not display it
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
I tried the 2 versions of Nexus i.e. 3.69.0-02 and 3.72.0-04 and the search displaying deleted packages with last updated date on 1/1/1970 behavior is seen in both.
OS -Windows 10
Database 3.69.0-02 uses Orient DB and 3.72.0-04 is H2, so issue is seen in both DBs
In this proxy repo we have set Maximum Component age and maximum metadata age to just 5 minutes. Nuget protocol is set to Nuget v2
Anything else?
one interesting observation is that when using latest nuget.exe client 6.12.1 this issue is seen and when downgrading the nuget client to 6.11 or 6.10 this issue of picking the deleted versions of packages for resolution does not happen.
I also posted this topic in Nexus Community and attaching the link for reference - https://community.sonatype.com/t/nexus-repository-nuget-proxy-repo-deleted-assets-appears-in-search/13925
The text was updated successfully, but these errors were encountered: