This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 81619 - RFE: Update Licq version 1.2.0a to 1.2.3
RFE: Update Licq version 1.2.0a to 1.2.3
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: licq (Show other bugs)
phoebe
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Thomas Woerner
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-11 05:47 EST by Peter van Egdom
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-16 09:18:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Peter van Egdom 2003-01-11 05:47:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:

According to "http://licq.sourceforge.net/" there's a new stable version of Licq
released. Upgrading this package at this time is low-risk as it contains mostly
upstream bugfixes :

  * Many memory leaks fixed.
  * Improved server side contact list support.
  * Improved v8 compatibility. 



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Check out "http://licq.sourceforge.net/"
2. Checkout Phoebe 8.0.92 / Rawhide
3.
    

Actual Results:  
There's a newer stable version available than the version in  Phoebe 8.0.92 /
Rawhide.

Expected Results:  
As this is a low-risk upgrade with some nice fixes it would be nice to have this
in the next version of Phoebe.

Additional info:

Red Hat Linux release 8.0.92 (Phoebe)

licq-qt-1.2.0a-5
licq-1.2.0a-5
licq-gnome-1.2.0a-5
licq-text-1.2.0a-5
licq-kde-1.2.0a-5
Comment 1 Thomas Woerner 2003-01-16 09:18:40 EST
Fixed in rawhide in rpm licq-1.2.3-2 or newer.

Note You need to log in before you can comment on or make changes to this bug.