Uploaded licq 1.0.3-2 (sparc all) to ftp-master
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 14 Mar 2001 17:29:49 -0600
Source: licq
Binary: licq-plugin-rms licq-plugin-qt2 licq-plugin-console licq-plugin-kde licq-plugin-forwarder licq licq-plugin-autoreply licq-dev
Architecture: sparc all
Version: 1.0.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon <buildd@vore.debian.org>
Changed-By: Zed Pobre <zed@debian.org>
Description:
licq - ICQ clone (base files)
licq-dev - LICQ Development and Header Files
licq-plugin-autoreply - LICQ auto-replyer plugin (noninteractive)
licq-plugin-console - Text front-end plugin for LICQ
licq-plugin-forwarder - LICQ message forwarder plugin
licq-plugin-kde - Graphical front-end plugin for LICQ using QT2+KDE
licq-plugin-qt2 - Graphical front-end plugin for LICQ using QT2
licq-plugin-rms - LICQ remote management server for telnet LICQ access
Closes: 88637 89159 89591
Changes:
licq (1.0.3-2) unstable; urgency=low
.
* Fixed Build-Depends (closes: #89591)
* Crash problems in 1.0.2 should have disappeared with 1.0.3-1 (reopen
if this is not the case, they were not reproducible here).
(closes: #88637, #89159)
Files:
d72415088dc39c78789c1faca8f1d6b6 376988 net optional licq_1.0.3-2_sparc.deb
f34b8fb20b3b790fa2b2db544e73ba18 19532 net optional licq-plugin-autoreply_1.0.3-2_sparc.deb
1dd15040051f18913cdae30d0baffcf6 52908 net optional licq-plugin-console_1.0.3-2_sparc.deb
4d37a36fbf9f6fd37b6b604b9c5a2c97 21162 net optional licq-plugin-forwarder_1.0.3-2_sparc.deb
fd2f650ff15c67ba38c585089a923d82 941604 net optional licq-plugin-qt2_1.0.3-2_sparc.deb
f9273873f10c49d673d2dee7138b663c 941482 net optional licq-plugin-kde_1.0.3-2_sparc.deb
b35af783ecf88daa62756de16d8af7a4 24454 net optional licq-plugin-rms_1.0.3-2_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins <bcollins@debian.org>
iD8DBQE6shtGfNc/ZB4E7C0RApm0AKCPqRWzP8dYPnSr9p/zfOOxlhytSQCgr3hM
e3NSsCZmpQHlYNeW2hbG6uM=
=e2hr
-----END PGP SIGNATURE-----
Reply to: