| Summary: | Backport updated Evolution | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | aguador <waterbearer54> |
| Component: | Backports | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | olav |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | evolution-3.32.2-1.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
aguador
2020-05-16 09:55:39 CEST
Thank you for these observations. Evolution is as old as the hills, so it surprises me that it still produces so many problems. We already have 3.36.2 in Cauldron. It has no registered maintainer, so assigning this globally. CC'ing Olav who has done the recent new version commits. CC:
(none) =>
olav Old as the hills, but constantly, er, evolving! I don't know what the compose problem is as I have never seen it reported on the evo mailing list. The colours are a problem precipitated by a change in Webkit2-gtk. If upstream tests turn out well, there will be a major change in the editor for Evo in 3.38. Thanks for the quick response. I hate to add to Olav's list and only reported after seeing the "unknowns" about when we might have a target date for Mga 8. Best, Roy Hi, Thanks for requesting a backport to Mageia 7 for packages updated in Cauldron. According to our current backports policy: https://wiki.mageia.org/en/Backports_policy - Package maintainers are under no obligation to provide backports for the packages they maintain (whereas a maintainer should provide updates to the stable releases for packages he/she maintains). - Another packager can step in and provide backports provided he contacts maintainer about this. He must then keep the maintainer informed when working on it. - The maintainer can refuse that some packages be backported. If hard conflicts arise (eg. the maintainer vs all other packagers), we can refer to the council. - Packager (maintainer or not) who will submit backport will also have to provide security and bug updates if necessary. Packager/Maintainer: If you are working on this backport request, please change status to "Assigned". Feel free to Close this if you think it is against current Backports policy. Reporter: Your request is under investigations. In the meantime, we suggest look for Appimage or Flatpak version of this. Thank you for the suggestion, but as a follower of the Evo mailing list who has seen repeated issues raised as a result of the limitations of the Flatpak version, there is absolutely no way I would consider it even as an interim solution. Furthermore, even given the issue of maintainers being spread thinly, I find it odd that an Appimage or Flatpak version would be recommended to resolve a problem with a supported package. One of the true strong points of Mageia is that everything supported is built from source, never from a pre-packaged rpm. At the moment I can live with the problem, especially knowing that the intention is to release Mageia 8 "when ready". If I needed to change, it would be to move to Cauldron (which, with care, has given me fewer problems in my main machine than the stable version in my small laptop). With Mageia 8 due out soon, it is silly to hold this open, closing. Resolution:
(none) =>
WONTFIX |