On 28/11/17 20:43, Antoine Beaupré wrote:
> On 2017-11-27 20:38:20, Roberto C. Sánchez wrote:
>> On Thu, Nov 23, 2017 at 02:51:56PM -0500, Antoine Beaupré wrote:
>>>
>>> So I ended up adding it to the debian/rules file, but that wasn't enough
>>> either - I had to add "export" to every line so it s
On 2017-11-27 20:38:20, Roberto C. Sánchez wrote:
> On Thu, Nov 23, 2017 at 02:51:56PM -0500, Antoine Beaupré wrote:
>>
>> So I ended up adding it to the debian/rules file, but that wasn't enough
>> either - I had to add "export" to every line so it shows up in the
>> environment.
>
> I think that
On Thu, 23 Nov 2017, Antoine Beaupré wrote:
> Fun times. So I'm stuck now - I reported the CVE issues upstream so
> they're at least aware of the issue:
>
> https://github.com/Exiv2/exiv2/issues/174
>
> ... but I am not sure what to do with the package in Wheezy. I'm tempted
> to mark this as no-
On 2017-11-23 15:10:17, Roberto C. Sánchez wrote:
> On Thu, Nov 23, 2017 at 02:51:56PM -0500, Antoine Beaupré wrote:
>>
>> Fun times. So I'm stuck now - I reported the CVE issues upstream so
>> they're at least aware of the issue:
>>
>> https://github.com/Exiv2/exiv2/issues/174
>>
>> ... but I a
On Thu, Nov 23, 2017 at 02:51:56PM -0500, Antoine Beaupré wrote:
>
> Fun times. So I'm stuck now - I reported the CVE issues upstream so
> they're at least aware of the issue:
>
> https://github.com/Exiv2/exiv2/issues/174
>
> ... but I am not sure what to do with the package in Wheezy. I'm tempt
On 2017-11-14 08:58:33, Roberto C. Sánchez wrote:
> All,
>
> Some of the last few updates I have done have required building the
> package with ASAN in order to reproduce the bug and/or confirm the fix.
>
> After some searches did not come up with anything that captured the
> issues I have encounte
