Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BridgeDB BridgeDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • BridgeDBBridgeDB
  • Issues
  • #10446
Closed
Open
Issue created Dec 20, 2013 by Isis Lovecruft@isis

BridgeDB is/was using a GeoIP module which is incompatible with virtualenvs

04:07 [ (isis) ) sysrqb: i realised yesterday that we're actually using the wrong GeoIP module in bridgedb's requirements.txt
04:08 [ (isis) ) although the one we're using, pygeoip.GeoIP, is compatible (at least it has all the same functions we're using from the the GeoIP one)
04:09 [ (isis) ) i am thinking that perhaps we should keep using the "wrong" one, since it is compatible
04:10 [ (isis) ) because the "wrong" one (the pygeoip one) installs cleanly in a virtualenv, while the other one does not
04:10 [ (isis) ) i think they both require the same underlying deps, libgeoip-dev and geoip-database in Debian
04:11 [ (isis) ) which means that my README instructions which said that bridgedb requires tor-geoipdb were also wrong
Assignee
Assign to
Time tracking