Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #7692

Closed (moved)
(moved)
Open
Created Dec 10, 2012 by Karsten Loesing@karsten

Backport A1-less GeoIP database

We should backport the new A1-less GeoIP database file that got recently merged into master (#6266 (moved)) to previous maintained branches. Two questions:

  • Should we only backport changes to the geoip file (35d09dd, c718921), or should we also include the deanonymind.py script, manual assignment overrides in geoip-manual, and README.geoip (2bf195d) explaining how we created that new geoip file?

  • Should we backport geoip updates to all previous maintained branches (including 0.2.2.x), or will that make package maintainers sad?

Once I know what to backport, I can prepare a branch.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking