| Summary: | mysql-workbench is not available on Mageia 8 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Peter Potrowl <peter017> |
| Component: | New RPM package request | Assignee: | Jani Välimaa <jani.valimaa> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | jani.valimaa, lewyssmith |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://madb.mageia.org/package/show/name/mysql-workbench/release/7/arch/x86_64 | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Peter Potrowl
2021-08-16 13:08:54 CEST
It was dropped because of needing python2. I'll see if I can revive the pkg in Cauldron first. Assignee:
bugsquad =>
jani.valimaa It was also unmaintained and affected by security issues that weren't getting fixed (such as Bug 26080 and Bug 26521, and there've been others in more recent Oracle CPU's). It's up to Jani whether he does re-instate the pkg (if that is indeed possible). If you succeed, I think it might go in Backports; and it would be up to Peter to test it. If that happens OK, Jani will you close the bug FIXED? OTOH If you cannot re-instate it successfully, or in the light of DavidW's comment above decide not to try, the bug should be closed INVALID. I do not think, as a pkg dropped for a good reason, it should go through QA. Component:
RPM Packages =>
New RPM package request Thanks for your answers. I'm ok to test it if re-instated. If not, please suggest alternate SQL clients. Thanks! mysql-workbench is not available. Closing as OLD. Resolution:
(none) =>
OLD |