Description of problem: Geo-rep started using sqlite3 for storing temporary details. Regression is failing because of sqlite3 not exists in NetBSD machine. Please do the needful ftp://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/databases/py-sqlite3/README.html 05:13:54 Traceback (most recent call last): 05:13:54 File "/build/install/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 33, in <module> 05:13:54 import resource 05:13:54 File "/data/build/install/libexec/glusterfs/python/syncdaemon/resource.py", line 34, in <module> 05:13:54 from master import gmaster_builder 05:13:54 File "/data/build/install/libexec/glusterfs/python/syncdaemon/master.py", line 29, in <module> 05:13:54 from changelogsdb import db_init, db_record_data, db_record_meta 05:13:54 File "/data/build/install/libexec/glusterfs/python/syncdaemon/changelogsdb.py", line 12, in <module> 05:13:54 import sqlite3 05:13:54 File "/usr/pkg/lib/python2.7/sqlite3/__init__.py", line 24, in <module> 05:13:54 from dbapi2 import * 05:13:54 File "/usr/pkg/lib/python2.7/sqlite3/dbapi2.py", line 28, in <module> 05:13:54 from _sqlite3 import * 05:13:54 ImportError: No module named _sqlite3
Geo-rep tests are disabled in NetBSD. Import error is coming when `gsyncd.py --version` is run from other parts of Gluster code. Doing Lazy import in code when required. Closing this bug, since not required now.
Heh, just when I fixed :D
(In reply to Nigel Babu from comment #2) > Heh, just when I fixed :D Thanks. It will be useful when we work on to support Geo-rep on BSD. Sorry about the inconvenience.