Re: No module named back_ for sqlite backend

Dear John,

I figured out the root cause.

I was choosing responsive template, and for some reason my roundup(version 1.6.0) generated one outdated config.ini without the backend entry.
One issue was raised here:
http://issues.roundup-tracker.org/issue2550997 <http://issues.roundup-tracker.org/issue2550997>

BR,Austin

> On Sep 3, 2018, at 4:48 AM, John P. Rouillard <[email protected]> wrote:
> 
> Hi Austin:
> 
> In message <[email protected]>,
> Austin Wang writes:
>> I just try to use the sqlite backend, and when I finish configuration
>> and start roundup-admin initialise, It complains that 
>> 
>> No module named back_
>> 
> 
> The module that is being imported should be something like back_sqlite
> or back_anydb. The lack of a db name after back_ indicates that init
> can't figure out what the db should be.
> 
> What is the value of the:
> 
>  # Database backend.
>  # Default:
>  backend = anydbm
> 
> entry in config.ini? Actually you may not have that key in the config
> file.  If it's empty/missing this could cause the error you see.
> 
> Also IIRC you mentioned something in a previous email about a
> config.ini file in the responsive template directory. I wonder if that
> somehow prevents the install from configuring it properly. I think
> it's an error that config.ini's are shipped with the templates, but
> they should be overwritten with a correct current one after running
> install. I have to admit that classic template is the one that used in
> testing. The others get less attention. Also I think there was a
> recent addition to the responsive template to add a search form.
> 
> In any case, after running install, your tracker directory should have
> a newly generated config.ini for you to edit.
> 
> If the config.ini is broken without a backend setting, try moving the
> config.ini file in the *template* directory aside and rerun your
> roundup-admin install. This should generated a new config.ini with a
> valid backend setting.
> 
>> [austin@support roundup]$ roundup-admin install
>> Enter tracker home: /opt/roundup/ticket
>> Templates:: responsive-ticket, jinja2, classic, responsive, minimal, devel
>> Select template [classic]: classic
>> Back ends:: anydbm, sqlite
>> Select backend [anydbm]: sqlite
> 
> This shows that python has support for the sqlite database. Otherwise
> it would not be listed.
> 
> [...]
>> You MUST run the "roundup-admin initialise" command once you've performed
>> the above steps.
>> [...]
>> [austin@support ticket]$ cp ~/roundup_config.ini config.ini
> 
> You shouldn't need to do this. You should edit the config.ini in the
> tracker directory created by install.
> 
> What is the source of roundup_config.ini? Did you see directions
> that said you should copy some roundup_config.ini over the one
> generated by install? If so where, we need to fix that.
> 
> Have a great day.
> 
> --
> 				-- rouilj
> John Rouillard
> ===========================================================================
> My employers don't acknowledge my existence much less my opinions.
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users