On Sat, 2011-06-04 at 15:21 +0200, Sebastian Krämer wrote:
> On 06/03/2011 12:14 PM, Jindrich Novy wrote:
> >> Does this make sense to you? What can I do about it?
> >
> > Yes. It is caused by the fact that Fedora evince is linked against old
> > kpathsea library. The new and old kpathsea librari
On 06/04/2011 05:55 PM, Matthew Saltzman wrote:
> On Sat, 2011-06-04 at 15:21 +0200, Sebastian Krämer wrote:
>> On 06/03/2011 12:14 PM, Jindrich Novy wrote:
Does this make sense to you? What can I do about it?
>>>
>>> Yes. It is caused by the fact that Fedora evince is linked against old
>>>
On 06/03/2011 12:14 PM, Jindrich Novy wrote:
>> Does this make sense to you? What can I do about it?
>
> Yes. It is caused by the fact that Fedora evince is linked against old
> kpathsea library. The new and old kpathsea libraries can not actually
> coexist so the only solution is to remove evince
Hi Sebastian,
On Thu, May 26, 2011 at 10:34:20PM +0200, Sebastian Krämer wrote:
> Hello there,
>
> I'm following the mailing list (and the original bug report) for a while
> now and just today considered upgrading texlive (after I upgraded to
> Fedora 15 yesterday).
>
> I did a 'yum clean all',
Hello there,
I'm following the mailing list (and the original bug report) for a while
now and just today considered upgrading texlive (after I upgraded to
Fedora 15 yesterday).
I did a 'yum clean all', then 'yum upgrade' with the texlive-release
repo enabled. After a long list of packages that ar
