On 13/10/2018 12:58, Mattia Rizzolo wrote:
> On Sat, Oct 13, 2018 at 12:45:04PM +0200, Emilio Pozuelo Monfort wrote:
>> For the next ones do you mean in case poppler breaks the API again for
>> buster?
>> I.e. can you easily fix this bug?
>
> Yes, this one bug is already done locally, pending
On Sat, Oct 13, 2018 at 12:45:04PM +0200, Emilio Pozuelo Monfort wrote:
> For the next ones do you mean in case poppler breaks the API again for buster?
> I.e. can you easily fix this bug?
Yes, this one bug is already done locally, pending one last build…
I meant for further API breaks before the
On 13/10/2018 12:01, Mattia Rizzolo wrote:
> On Fri, Oct 12, 2018 at 06:26:18PM +0200, Mattia Rizzolo wrote:
>>> I intend to update our poppler soon as there are some security fixes
>>> in the newer versions. I'd appreciate if you can take a look at this
>>> and apply any necessary fixes.
>>
>>
On Fri, Oct 12, 2018 at 06:26:18PM +0200, Mattia Rizzolo wrote:
> > I intend to update our poppler soon as there are some security fixes
> > in the newer versions. I'd appreciate if you can take a look at this
> > and apply any necessary fixes.
>
> I'm guessing this upstream commit might help:
>
> Your package fails to build against poppler 0.69, currently in experimental.
> In some cases there are patches in Ubuntu, the PTS has links.
Hardly in ubuntu, they are using poppler 0.68, and they are in very deep
freeze with the looming release :)
> I intend to update our poppler soon as
5 matches
Mail list logo
