[pkg-firebird-general] Bug#470238: Bug#470238: firebird2.0 super on debian stable using backports

[marius popa]

On Mon, Mar 10, 2008 at 7:33 AM, Damyan Ivanov <dmn at debian.org> wrote:

> Package: firebird2.0-super
> Version: 2.0.3.12981.ds1-2
> Severity: grave
>
> -=| marius popa, Wed, Mar 05, 2008 at 04:32:42PM +0200 |=-
> > On Wed, Mar 5, 2008 at 1:22 PM, Damyan Ivanov <dmn at debian.org> wrote:
> >
> > > -=| marius popa, Wed, Mar 05, 2008 at 11:52:58AM +0200 |=-
> > > > Setting up firebird2.0-super (2.0.3.12981.ds1-5~bpo40+1) ...
> > > > adduser: Warning: that home directory does not belong to the user
> you
> > > are
> > > > currently creating.
> > > > Created default security.fdb
> > > > Unable to complete network request to host "localhost".
> > > > Failed to establish a connection.
> > > > Connection refused
> > > > unable to open database
> > > > dpkg: error processing firebird2.0-super (--configure):
> > > >  subprocess post-installation script returned error exit status 1
> > > > Errors were encountered while processing:
> > > >  firebird2.0-super
> > > > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > > >
> > > >
> > > >  sudo /etc/init.d/firebird2.0-super start
> > > > * Not starting Firebird 2.0 server manager
> > > > * Use `dpkg-reconfigure firebird2.0-super' to enable.
> > >
> > > Thanks for testing.
> > >
> > > I guess what you'd expect is:
> > >
> > > 1) be asked whether to enable firebird server at startup
> > > 2) do no try to set sysdba password (or even ask for it) when firebird
> > > server is not enabled
> > >
> > > Does this look satisfactory?
> >
> >
> > ok it asked me when i installed but it failed to start see the first
> error
>
> I traced the source of the error. It exisits, it is grave. I am very
> surprised that no one found it almost three months.
>
> The reason for the failure is an excessive cleanup after abandoning the
> idea of supportingmultiple firebird vesions being installed at the same
> time. the postinst script never asks if you want to enable the server,
> but tries to change sysdba's password. As the server is not started, it
> fails.
>
> The fix is to ask for, and attempt to change the password only the
> server is enabled and only after it has been started.
>
> I'll produce fixed packages soon and present them for testing.
> Meanwhile, I a filing a bug to the BTS so that others are aware.
>
> --
> dam            JabberID: dam at jabber.minus273.org
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFH1MhEHqjlqpcl9jsRAtuOAJ46wHf1HarBiEcFpvdOtXutz09iFwCgyE7E
> HvOrlL94pscq69cMhZNS/rY=
> =xJ9U
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> pkg-firebird-general mailing list
> pkg-firebird-general at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-firebird-general
>

the same bug seems to be present in ubuntu hardy too (postinstall script is
the same)
i tested and then i did an diff
dget
http://archive.ubuntu.com/ubuntu/pool/universe/f/firebird2.0/firebird2.0_2.0.3.12981.ds1-5ubuntu1.dsc
dget  dget
http://ftp.de.debian.org/debian/pool/main/f/firebird2.0/firebird2.0_2.0.3.12981.ds1-5.dsc

debdiff firebird2.0_2.0.3.12981.ds1-5.dsc
firebird2.0_2.0.3.12981.ds1-5ubuntu1.dsc

the only  differences are about the hppa-patch and ia64 patches

-- 
developer flamerobin.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-firebird-general/attachments/20080311/14c7c3a9/attachment-0001.htm