Thomas Reitelbach wrote:
> On Wednesday 08 January 2003 18:33, Roman Stepanov wrote:
> > Jon Keating wrote:
> > > On Wednesday 08 January 2003 06:19 am, Roman Stepanov wrote:
> > > > After new stable release of Licq has been announced I decided to
> > > > upgrade from licq-2002 to a licq-200301
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 08 January 2003 18:33, Roman Stepanov wrote:
> Jon Keating wrote:
> > On Wednesday 08 January 2003 06:19 am, Roman Stepanov wrote:
> > > After new stable release of Licq has been announced I decided to
> > > upgrade from licq-2002 to a
Jon Keating wrote:
> On Wednesday 08 January 2003 06:19 am, Roman Stepanov wrote:
> > After new stable release of Licq has been announced I decided to upgrade
> > from licq-2002 to a licq-20030108 snapshot. I've built a new package,
> > installed it and finally got a segfault:
>
> Try doing thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 08 January 2003 06:19 am, Roman Stepanov wrote:
> After new stable release of Licq has been announced I decided to upgrade
> from licq-2002 to a licq-20030108 snapshot. I've built a new package,
> installed it and finally got a segfaul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 08 January 2003 13:45, wwp wrote:
> Hi Roman Stepanov,
>
> On Wed, 8 Jan 2003 15:19:00 +0300 Roman Stepanov <[EMAIL PROTECTED]> wrote:
> > Hi, All!
> >
> > After new stable release of Licq has been announced I decided to upgrade
> > from l
Hi Roman Stepanov,
On Wed, 8 Jan 2003 15:19:00 +0300 Roman Stepanov <[EMAIL PROTECTED]> wrote:
> Hi, All!
>
> After new stable release of Licq has been announced I decided to upgrade
> from licq-2002 to a licq-20030108 snapshot. I've built a new package,
> installed it and finally got a se
