On Tue, Nov 28, 2006 at 11:35:47PM -0200, Otavio Salvador wrote: > John Goerzen <[EMAIL PROTECTED]> writes: > > > No, please reread more carefully. > > > > The bug is that if you swap out libpython-sqlite and > > libpython-pysqlite2 -- both of which satisfy the trac deps -- you > > break trac. > > > > The bug is also that you get nondeterministic behavior depending on > > whether you have libpython-pysqlite2 installed. If you do, you get a > > sqlite2 db, and if not, you get sqlite3. These have completely > > different commands for use in system backup scripts, etc. > > > > TracDarcs is how I *noticed* it. > > But as far as I know with "official" trac there's no problem with > both, right?
Either one, taken on its own, works. The problem is that there is no way to tell trac which one to use. And worse, unrelated system changes can instantly break trac. Let's say you have some other package that conflicts with libpython-sqlite, so apt automatically switches to libpython-pysqlite2 instead. It's still fulfilling the dependency, but breaking trac. Also, sysadmins can't write scripts against trac because they don't know which sqlite any given system will use at any given time. Debian should do one of the following: a) Drop the dependency on libpython-sqlite b) Set the sqlite version in a config file rather than autodetect at runtime c) Depend on both and prefer one I repeat, the problem here is that unrelated changes can instantly break trac. This is a dependency bug, plain and simple. -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
