Bug 977150
| Summary: | Licq not works in F18 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eugene A. Pivnev <ti.eugene> |
| Component: | licq | Assignee: | Christopher Meng <i> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | contribs, yaneti |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | licq-1.7.1-4.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-16 23:03:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eugene A. Pivnev
2013-06-23 19:26:47 UTC
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Hi Eugene, Can you reproduce on 1.7.1 version now? If not I'll close it. (In reply to Christopher Meng from comment #2) > Hi Eugene, > > Can you reproduce on 1.7.1 version now? > > If not I'll close it. bash-4.2$ LC_ALL=C licq 12:58:38.241 [ERR] licq: Unable to load plugin (/usr/lib/licq/protocol_jabber.so): /usr/lib/licq/protocol_jabber.so: cannot open shared object file: No such file or directory bash-4.2$ rpm -q licq licq-1.7.1-1.fc19.i686 http://koji.fedoraproject.org/koji/taskinfo?taskID=5682946 --- licq.spec.orig 2013-07-31 12:58:22.402695914 +0400 +++ licq.spec 2013-07-31 13:13:04.255953191 +0400 @@ -1,6 +1,6 @@ Name: licq Version: 1.7.1 -Release: 1%{?dist} +Release: 2%{?dist} License: GPLv2+ Source0: http://downloads.sourceforge.net/%{name}/%{name}-%{version}.tar.bz2 @@ -15,6 +15,7 @@ BuildRequires: gettext, cmake BuildRequires: xosd-devel BuildRequires: cdk-devel ncurses-devel +BuildRequires: gloox-devel # fcami - licq calls "play" directly Requires: sox @@ -83,6 +84,13 @@ make %{?_smp_mflags} popd +pushd plugins/jabber +mkdir build +cd build +%cmake $cmakeopts .. +make %{?_smp_mflags} +popd + pushd plugins/msn mkdir build cd build @@ -138,6 +146,10 @@ make DESTDIR=$RPM_BUILD_ROOT install popd +pushd plugins/jabber/build +make DESTDIR=$RPM_BUILD_ROOT install +popd + pushd plugins/msn/build make DESTDIR=$RPM_BUILD_ROOT install popd @@ -173,6 +185,7 @@ %{_libdir}/licq/licq_autoreply.so %{_libdir}/licq/licq_forwarder.so %{_libdir}/licq/licq_rms.so +%{_libdir}/licq/protocol_jabber.so %{_datadir}/licq %{_datadir}/applications/*licq.desktop %doc doc/ upgrade/ README* LICENSE @@ -189,6 +202,9 @@ %doc plugins/console/{README,licq_console.conf} %changelog +* Wed Jul 31 2013 TI_Eugene <fcami> - 1.7.1-2 +- Jabber protocol added. + * Sun Jun 02 2013 François Cami <fcami> - 1.7.1-1 - New upstream release. Thanks. This package needs some big work, I may rewrite the spec. Please wait a moment or few days. Thanks. licq-1.7.1-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/licq-1.7.1-4.fc18 licq-1.7.1-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/licq-1.7.1-4.fc19 Package licq-1.7.1-4.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing licq-1.7.1-4.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-14547/licq-1.7.1-4.fc18 then log in and leave karma (feedback). Works for me (In reply to Eugene A. Pivnev from comment #9) > Works for me Please leave karma. Thanks. licq-1.7.1-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. licq-1.7.1-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |