| Summary: | Update Geo-Ip Database | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | Daniel Lucio <luis.daniel.lucio> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, ouaurelien |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | geoip-1.6.9-2.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Marc Krämer
2018-09-26 11:28:53 CEST
dlucio might be lacking time, last time he pushed a package seems to have been in April (according to my changelog mails). @ dlucio Hope your fine. Do you have time to fix this issue? Assigning to you because you're the registered maintainer. Assignee:
bugsquad =>
luis.daniel.lucio Maxmind is going to drop legacy databases in January 2019 [1], so I wouldn't give much attention to this bug. We could do one final update for databases, but that's all we should do for stable releases. For current Cauldron we should either drop databases from geoip pkg or split them into their own src.rpm. [1] https://support.maxmind.com/geolite-legacy-discontinuation-notice/ Clearly tools from geoip pkg doesn't work without databases, so we can't drop them from Cauldron. If apps are using legacy geoip databases, they should move to newer GeoLite2. For GeoLite2 I could look for pkg'ing upstream tool geoipupdate [1] with a cron or systemd timer support. We have already libs and tools for GeoLite2 dbs. [1] https://github.com/maxmind/geoipupdate If this file is no longer supported or is getting old, WE should drop it. Using old information can lead to severe problems. I assume xtables-geoip is also affected, as /usr/libexec/xtables-addons/xt_geoip_dl uses this database too. 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 |