On 11 December 2012 18:20, Kevin Kofler wrote:
> Eric H. Christensen wrote:
>> This is a good point. Unfortunately this would lead to the only option
>> being to remove fop and Publican from EPEL5 because fop is broken...
>> badly.
>>
>> If no one needs it then I'll just retire it.
>
> Uh, I don'
Eric H. Christensen wrote:
> This is a good point. Unfortunately this would lead to the only option
> being to remove fop and Publican from EPEL5 because fop is broken...
> badly.
>
> If no one needs it then I'll just retire it.
Uh, I don't think it's possible to retire shipped packages. (At leas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 11, 2012 at 01:38:43PM +0100, Stanislav Ochotnicky wrote:
> Quoting Eric H. Christensen (2012-12-10 22:51:11)
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > The last week or so has seen a couple of patches going into fop in
Quoting Eric H. Christensen (2012-12-10 22:51:11)
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The last week or so has seen a couple of patches going into fop in the Fedora
> repositories. I recently became a co-maintainer of fop in EPEL5 and was
> trying to bring fop into current ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The last week or so has seen a couple of patches going into fop in the Fedora
repositories. I recently became a co-maintainer of fop in EPEL5 and was trying
to bring fop into current there. Unfortunately there are many dependency
failures there th
