[Pkg-firebird-general] Issues firebird 1.5.2

Remco Seesink raseesink@hotpop.com
Tue, 25 Jan 2005 16:26:53 +0100


--Signature=_Tue__25_Jan_2005_16_26_53_+0100_RYDXkhS3+g9Sh21I
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Hi Damyan,

I have found some more issues, some may have existed before your
version.

>From the changelog:

>firebird2 (1.5.2-0mentors1) unstable; urgency=low
>.
>  * New upstream release
>  * Upload to mentors.debian.net

This is fine on mentors, but don't forget to remove this entry and
mentor versions if you prepare the final version so the changelog is
clean and complete.

>  * Fixed short description to please lintian
I couldn't make out what you changed exactly here.

>  * libfoo.so->libfoo.so.1.5.2 moved to -dev to please lintian
I didn't find it in the -dev package. Also, ibaccess (which is not
packaged in debian) uses the old library symlink libgds.so.0 and stopped
working when I installed the classic version of the library. Super still
works.

I think a library (symlink) should not be in a -dev package, but in the
lib package. It would be unexpected that you would need to install a
-dev package for a library instead of lib package. But I don't
understand why lintian would disagree, so I might be completly wrong
here.

>  * Add mysenf in Uploaders
Small type and welcome in the team.

One other thing I noticed today is that the classic server is started
through inetd. Is this new behaviour? I am not so sure this is a good
idea. It also gave me several problems when trying to deinstall te
classic server. It complained the process was still running and hence
couldn't deinstall.

And another issue which we should work out is the setting of the sysdba
password. According to policy this should be done through debconf. It
also shouldn't echo the actual password. I think the easiest solution is
to take the password question out of the installer and into the
documentation. After that I could look into this to produce a debconf
patch.

This is what I additionally discovered so far.

Cheers,
Remco.


--Signature=_Tue__25_Jan_2005_16_26_53_+0100_RYDXkhS3+g9Sh21I
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB9mVBVYMI95VPXscRAvocAJ9y5aDar4anUOYCcktdUxKnDqI3egCeJA5N
7lkFNrhssFpvKGjAmgXsE2g=
=vQMP
-----END PGP SIGNATURE-----

--Signature=_Tue__25_Jan_2005_16_26_53_+0100_RYDXkhS3+g9Sh21I--