Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Overwrite a old version archive does not work #440

Closed
robang74 opened this issue Jun 21, 2023 · 3 comments
Closed

[Bug] Overwrite a old version archive does not work #440

robang74 opened this issue Jun 21, 2023 · 3 comments
Labels
bug something that needs fixing

Comments

@robang74
Copy link

Current 2.0 web interface for developers: https://coderus.openrepos.net/pm2

BUG DESCRIPTION

Trying to overwrite a past version archive file does not work. Everything seems fine but PM2 keeps the old version of the archive. IMHO, it is a feature not a bug - possibly a constrain set pourposely by a specific configuration - in this case, it is a bug because the UI part related to that feature should not even displayed.

STEPS TO REPRODUCE

Try to overwrite the archive of a published version.

ADDITIONAL INFORMATION

Chrome browser for Ubuntu.

@robang74 robang74 added the bug something that needs fixing label Jun 21, 2023
@robang74 robang74 changed the title [Bug] [Bug] Overwrite a old version archive does not work Jun 21, 2023
@Olf0
Copy link
Contributor

Olf0 commented Jun 21, 2023

Thank you for the bug report and using the bug template for it.

Though this issue seems to be addressing the UI of the PM-Webcatalog, which is hosted here: https://github.com/CODeRUS/django-test
If my interpretation is correct (i.e., this is not directly related to Patchmanager proper), please file this bug report there.
But I might misinterpret the bug description, because I am having difficulties to fully comprehend it.

Side note: Mind, that the PM-Webcatalog software is in minimal maintenance mode. Contributions (i.e., PRs) are welcome, but must be well tested and positive testing results demonstrated, before a PR may be accepted.

@robang74
Copy link
Author

robang74 commented Jun 23, 2023

Thanks, reported to the right github project. I close this

UPDATE:

it does not seem that I can close by myself, close for me please.

@Olf0
Copy link
Contributor

Olf0 commented Jun 23, 2023

Sure.

@Olf0 Olf0 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something that needs fixing
Projects
None yet
Development

No branches or pull requests

2 participants