On Fri, Aug 05, 2005 at 06:49:51AM -0600, Barak Pearlmutter wrote:
> Could I trouble you to recompile and dupload evince against
> libdjvulibre1 (>= 3.5.14-6) to deal with soname change? Evince is the
> only package that uses the lib, so that will clear the issue.
No, libdjvulibre1 was included i
Yes, all true.
I will upload a rev which generates libdjvulibre15. When that comes
down the pike, please recompile evince against it.
--Barak.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT
Le vendredi 05 août 2005 à 07:16 -0600, Barak Pearlmutter a écrit :
> Problem is what does "fix djvulibre" mean here?
>
> Fix it to generate the old soname, thus losing soname compatibility
> with upstream?
>
> Fix it to generate a different library name, perhaps libdjvulibre15?
>
> Fix it by as
Problem is what does "fix djvulibre" mean here?
Fix it to generate the old soname, thus losing soname compatibility
with upstream?
Fix it to generate a different library name, perhaps libdjvulibre15?
Fix it by asking upstream to stop changing the soname for no reason?
Fix it by convincing anyon
Le vendredi 05 août 2005 à 06:49 -0600, Barak Pearlmutter a écrit :
> Sebastien,
>
> Could I trouble you to recompile and dupload evince against
> libdjvulibre1 (>= 3.5.14-6) to deal with soname change? Evince is the
> only package that uses the lib, so that will clear the issue.
Hi,
What about
Sebastien,
Could I trouble you to recompile and dupload evince against
libdjvulibre1 (>= 3.5.14-6) to deal with soname change? Evince is the
only package that uses the lib, so that will clear the issue.
I'm not sure if the API has changed in a fashion that justifies a
chance in soname. Upstream
6 matches
Mail list logo
