| Summary: | Courier Imap Server - Main Packages Missing in Mageia 6 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Josua Dietze <digidietze> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11, ouaurelien |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | courier-imap | CVE: | |
| Status comment: | |||
|
Description
Josua Dietze
2017-08-06 19:22:33 CEST
Assigning to the registered maintainer of courier-imap. Assignee:
bugsquad =>
shlomif While Shlomi may have been the registered maintainer, keep in mind that he registered to maintain several packages that he doesn't actually maintain. He only made one commit to the package almost 6 years ago, right after it was initially imported by Barry Jackson. The package had gone unmaintained and had not been updated since then. That's why it was dropped. Josua, if you're interested in this package, perhaps you should go through the mentorship process to become a packager yourself so that you can maintain it. None of our existing packagers have shown an interest in this package. Assignee:
shlomif =>
pkg-bugs I will look into the upstream situation of courier-imap. I think it has still a place if you don't need the accumulated power of cyrus-imap and rather want a small and simple local mail storage, for instance. I will think about becoming a packager myself. There are other specific packages I'm missing as well and using regularly with Mageia. I'm also "upstream" myself with the "usb_modeswitch" tool and data, but I suppose there is a brave maintainer at hand already. However, I still consider it a bug (or at least an unfriendly behaviour) that packages retired from the distro are deleted (or probably auto-orphaned) during the upgrade without user confirmation. Also, I find it somewhat confusing that the authentification helper packages for courier-imap are still part of the new distro release. It looks like courier-imap is still maintained upstream. I also managed to build a Mageia 6 RPM by using the SPEC file from the Mageia 5 SRPM, with only few tweaks. Version 4.17.3 builds fine with the prerequisites provided by Mageia 6 (courier-auth, courier-unicode). I would be interested in becoming a maintainer for this package (one SRPM for three packages, including courier-base and courier-pop). Now, how does that mentorship process work? I just saw on the dev list (I'm a few months behind :o) that Jóse offered to mentor you. Were you able to get started with packaging? If not, see the following, and feel free to come on IRC in #mageia-mentoring: https://wiki.mageia.org/en/Becoming_a_Mageia_Packager As far as the package getting removed from your machine, there are arguments on both sides, but you're probably right. task-obsolete effectively removes everything listed in it from users' machines when they upgrade to the next Mageia version, so things should only be left in there if we intend that. Unfortunately, obsoleting things (which we often do there, especially when there isn't somewhere obviously better to do it) also serves the purpose of removing packages from distribution. So, often we intend to do only that, but then those package remain listed in task-obsolete when they really should have been removed from there after the packages got removed. However, for packages that have been dropped and are no longer being maintained, especially ones that could become security concerns, perhaps it is better to remove them from users' machines instead of silently leaving them there even though they're not available in the distro anymore. In most cases one approach is better than the other, but it depends. In this case, since it's server software, removing it was probably appropriate. Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It 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 6'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. 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/ Best regards, Aurélien Bugsquad Team Status:
NEW =>
RESOLVED |