#30522 closed enhancement (implemented)
Update to May GeoIP2 database
Reported by: | karsten | Owned by: | |
---|---|---|---|
Priority: | Medium | Milestone: | Tor: 0.2.9.x-final |
Component: | Core Tor/Tor | Version: | |
Severity: | Normal | Keywords: | tor-client, tor-relay, tor-dirauth, 029-backport, 034-backport, 035-backport, 040-backport |
Cc: | Actual Points: | ||
Parent ID: | Points: | ||
Reviewer: | Sponsor: |
Description
My geoip-2019-05-13 branch contains the updated geoip
and geoip6
files with IPv4 and IPv6 ranges and is supposed to be merged into maint-0.2.9 and other branches that are still maintained.
Child Tickets
Change History (6)
comment:1 Changed 7 months ago by
Status: | new → needs_review |
---|
comment:2 Changed 7 months ago by
Status: | needs_review → needs_revision |
---|
comment:3 Changed 7 months ago by
Status: | needs_revision → needs_review |
---|
Oops. Looks like I forgot to update my maint-0.2.9 branch before making the patch. There, I just pushed a new geoip-2019-05-13 branch (forced update). Please try again. Sorry!
comment:4 Changed 7 months ago by
Resolution: | → implemented |
---|---|
Status: | needs_review → closed |
Thanks again; this one merged fine. Merged to 0.2.9 and forward.
comment:5 follow-up: 6 Changed 7 months ago by
Keywords: | tor-dirauth 040-backport added; 032-backport 033-backport 035-must 035-rc-must removed |
---|
Fix backport tags.
Karsten, I can put the right release tags on future GeoIP update tickets. Just assign me as the reviewer.
Nick, can we put these tickets through the same merge and backport process as other tickets?
They're low-risk, but a bad GeoIP config could break the build (I think we have GeoIP tests?) or break a release.
comment:6 Changed 7 months ago by
Replying to teor:
Fix backport tags.
Karsten, I can put the right release tags on future GeoIP update tickets. Just assign me as the reviewer.
Sure, I can assign you as reviewer and leave the keywords empty, if that helps.
I get a merge conflict when I try to merge this into maint-0.2.9.