RPM Bulk Edit Delete does not work

aristo_4359

Hello not sure whether this has been reported, using 2025.9 (Build 16) version, I have 2 RPM feeds and when I check bulk edit for deleting multiple packages, it does not seems to work on both feeds. I can see the API call sent correctly (POST and payload are sent) and returned 200 but there is nothing done on rpm packages. I checked npm feed and it seems to work in npm so likely rpm feed specific issue (though I do not check other feed types)

Also a suggestion, when user delete package the page ideally stay on same page, instead redirecting to main feed on deleting single package and redirecting to first page when deleting using bulk edit

rhessinger

Hi @aristo_4359,

Is this all rpm packages or just specific versions of a package? Can you share package names and version on the ones that will not delete?

@aristo_4359 said in RPM Bulk Edit Delete does not work:

Also a suggestion, when user delete package the page ideally stay on same page, instead redirecting to main feed on deleting single package and redirecting to first page when deleting using bulk edit

Thanks for the suggestion. The reason we redirect to the feed page after deleting a single package is because we don't know if the package will still exist (has other versions and/or is a remote package) in that feed. Although it is not trivial to check before we redirect, it could be added. I am going to add this to the list to discuss for ProGet 2026.

Thanks,
Rich

aristo_4359

Thank you, I only have one type of rpm package
The name and versioning are like the following

ssdh:0.5.0.177-1.el.7.centos
ssdh:0.5.0.179-1.el.7.centos

The API will call like this

POST https://artifacttest02.dev.petrolink.net/packages/bulk-delete
AHAntiCsrfToken=Tps3B1Cx9nbQARqwWTHx6rE0NqoFG4N8Ujyn6fPvO%2FTQXJRFIHFbkuNblk7ds7E862rGTM9eRWP%2BSXgvnC70Pw%3D%3D&ids=7%3A%3Assdh%3A0.5.0.177-1.el.7.centos%2C7%3A%3Assdh%3A0.5.0.179-1.el.7.centos

Response Status code is 200

rhessinger

Hi @aristo_4359,

Thank you for sending that over. I have recreated the issue and created PG-3116 to track the fix. We should have this resolved within the next two maintenance releases of ProGet.

Thanks,
Rich