On pią, 2005-01-21 at 09:00 -0600, Marcelo E. Magallon wrote:
> Hi Steve,
>
> On Sat, Jan 08, 2005 at 04:44:22AM -0800, Steve Langasek wrote:
>
> > - First, this bug is not critical: it does not break "unrelated
> > packages or the whole system". It is at most grave (if it makes
> > the package unusable), or serious (if it's your opinion that this
> > bug makes the package unsuitable for release for other reasons).
>
> It depends on how you understand "unrelated packages". It breaks
> existing scripts because the backend is changed from SQLite 2 to 3.
> SQLite 3 can't read files written by SQLite 2 and the error message
> that DBD outputs is rather confusing (much more generic than "can't
> read files in SQLite 2 format").
>
> The package itself is usable, one must only pay attention to what one
> is doing.
>
> It's unsuitable for release with sarge because we don't know what
> upstream's plan is (maybe Krzysztof has already figured out something
> with upstream, but there's no record of that on the BTS). I would very
> much prefer _not_ to release these packages with sarge unless this is
> fixed and an upgrade path is provided. SQLite provides such path, only
> the Perl DBD is a mess.
Upstream author answered that he don't want to change name of package
(to dbd::sqlite3) but will provide "another solution". He didn't tell
what he mind writing this.
I am afraid I am not able to find solution myself so I'll "donate" this
package to Debian Perl Group. I will upload to Alioth this package as
soon as possible.
eloy
--
* Allegro.pl / Aukro.cz / Au-Au.ru
* Krzysztof 'eloy' Krzyżaniak
* <[EMAIL PROTECTED]>
