Bug 768585

Summary: pkg-config file missing in libecap-devel
Product: [Fedora] Fedora Reporter: AMM <anon.amish>
Component: libecapAssignee: Spike <SpikeFedora>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: anon.amish, SpikeFedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: libecap-0.2.0-2.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-21 17:03:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description AMM 2011-12-17 08:19:14 UTC
Description of problem:

pkg-config file missing in libecap-devel (atleast in Fedora 16)

Due to this squid (with --enable-ecap) does not compile. Also unable to compile other packages (clamav-ecap-adapter) as well.

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


How reproducible:
Everytime

Steps to Reproduce:
1. Compile squid with eCap support
2. Compile clamav-ecap-adaptor
  
Actual results:
Fails at ./configure stage

Expected results:
Compilation should happen without error

Additional info:
Manually adding libecap.pc file is workaround.

Comment 1 Spike 2011-12-17 16:12:19 UTC
Well, there is an updated build in koji. Does that work for you?

Comment 2 Fedora Update System 2011-12-17 16:13:23 UTC
libecap-0.2.0-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/libecap-0.2.0-2.fc16

Comment 3 AMM 2011-12-17 17:30:16 UTC
Ok..i havent tried it...but issue is minor. Will try in a day or two. Actually I am waiting for squid maintainer as well to update F16 squid to enable support for ecap.(which they disable for unknown reason)

But I see you have added libecap.pc so it should work.

Thanks for updating so fast.

Comment 4 Fedora Update System 2011-12-17 20:53:14 UTC
Package libecap-0.2.0-2.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libecap-0.2.0-2.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-17213/libecap-0.2.0-2.fc16
then log in and leave karma (feedback).

Comment 5 Spike 2011-12-17 22:54:26 UTC
(In reply to comment #3)
> Ok..i havent tried it...but issue is minor. Will try in a day or two. Actually
> I am waiting for squid maintainer as well to update F16 squid to enable support
> for ecap.(which they disable for unknown reason)

I already dropped Jiri an email concerning this. Didn't hear from him yet, but rebuilding the squid spec file with --enable-ecap works fine for me. Unfortunately I don't have commit access to squid, so maybe you can catch him (or one of the co-maintainers) on IRC to bug them :)


> But I see you have added libecap.pc so it should work.
> 
> Thanks for updating so fast.

Sure, you're welcome.

Comment 6 AMM 2011-12-18 05:45:21 UTC
Yes I have already filed a ticket here:
https://bugzilla.redhat.com/show_bug.cgi?id=768586

Also I had rebuilt squid with e-cap before filing this ticket.(By manually adding pkgconfig file)

However there was/is issue with clamav-ecap-adapter and squid was segfaulting.
(2011/12/18 11:06:52 kid1| Loading Squid module from '/usr/local/ecap/lib/ecap_clamav_adapter.so'
FATAL: Received Segment Violation...dying.)

No idea if bug resides in ecap, squid or adapter but I wonder if that was the reason ecap was disabled in squid?

Will file a bug report in squid once ecap is enabled on squid for F16.


----

As far as this ticket is concerned, I installed the update and it works fine. ./configure scripts work fine.

Thank you

Comment 7 Fedora Update System 2011-12-21 17:03:06 UTC
libecap-0.2.0-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.