| Summary: | Knode says it can't save config | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Doug Laidlaw <laidlaws> |
| Component: | RPM Packages | Assignee: | Nicolas Lécureuil <mageia> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | balcaen.john, lmenut |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Doug Laidlaw
2014-06-21 18:19:52 CEST
Do you have a reference to an upstream bug? Hopefully there's a fix somewhere and our maintainers can find it. AFAIK, Knode is essentially dead upstream unfortunately and is planned to be dropped for KDE Frameworks 5 and Plasma 2 :o( CC:
(none) =>
balcaen.john, lmenut Not really, David. I hunted around the Web. In a 2008 forum, somebody mentioned this bug. A reply said that it was known, it was upstream, and any fix had to wait for that. I found one dated 2008 here: http://lists.kde.org/?l=knode-devel&m=121619843315908 I have Claws-Mail, which will take newsgroups, and I understand that Thunderbird will, as well. (In reply to David Walser from comment #1) > Do you have a reference to an upstream bug? > > Hopefully there's a fix somewhere and our maintainers can find it. AFAIK, > Knode is essentially dead upstream unfortunately and is planned to be > dropped for KDE Frameworks 5 and Plasma 2 :o( I said this on alt.support.mageia and was told that development of knode is continuing. Aragorn advises: "KNode is not listed as a separate package but instead as part of the kde-pim package, as it is a kpart to Kontact." Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Seems to have gone away - most of the time. Looks like a "Won't Fix." As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED Seems to be a "won't fix" and I haven't noticed it recently on Mga 5 Official. |