[Pkg-sympa-devel] Bug#631162: sympa: Package will not configure if dbconfig-common is not used

[Paul Menzel]

Dear Emmanuel,


Am Freitag, den 26.10.2012, 21:41 +0200 schrieb Emmanuel Bouthenot:

> On Fri, Oct 26, 2012 at 04:56:28PM +0200, Paul Menzel wrote:
> [...]
> 
> > I hit the same problem when upgrading from 5.3.4-6.1 in Lenny to
> > Squeeze. Unfortunately neither the NEWS.Debian.gz nor the commits in the
> > Git packaging repository mention what to do in such a case and if it is
> > mandatory and how to work with dbconfig-common at all.
> > 
> > It is not clear at all if dbconfig-common *has* to be used or if it is
> > optional.
> This is an annoying bug but actually sympa is not ready to be installed
> without dbconfig.

I was just hit by this bug again, when migrating already existing Sympa
files and databases and the DebConf question told me to not configure
the database in this case.

> It is planned to fix this bug in Debian Jessie by rewriting the whole
> installation process for each backend.

That is not helpful to Debian Wheezy users. Keep in mind that Debian
Wheezy is probably going to be the recommended release for the next
three to four years.

> Anyway, I'm lowering the severity to important. I think that severity
> 'important' is more suitable in this case.

Sorry, I disagree after seeing how I was hit by this again. The DebConf
message should clearly state, that installation is going to fail when
not selecting dbconfig and point to a `README.Debian` with instructions
how to manually fix it. I’d assume a gracefully failing postinst would
be even better.


Thanks,

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-sympa-devel/attachments/20130430/dbe6aaff/attachment.pgp>