Need a better validation for repo relative path
traceback during publish when repo relative path is an absolute path
If a user specifies relative path as an absolute path, we don't actually append it to publish directories (and maybe some other places), resulting in errors during publish (see attachment).
We need to either do a better validation of relative path specified by the user and make sure that it is not an absolute path or convert it internally to a relative path.
+ This bug was cloned from Bugzilla Bug #1100010 +
#2 Updated by bmbouter over 2 years ago
- Severity set to 1. Low
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Please register to edit this issue