> Hi Thomas,
>> Dear Andreas,
>>
>> Thanks for taking care of toulbar2. I did spend some time to try to go
>> around this #920459 bug but even a postprocessing of the LaTeX output of
>> doxygen (removing inclusion of the xcolor package that generates the
>> LaTeX compilation issue) did not work (an
Sorry, missed the Reply-All as Andreas pointed out. See attached mail.
Thomas
--- Begin Message ---
Hi Thomas,
On Tue, Feb 19, 2019 at 11:15:13AM +0100, Thomas Schiex wrote:
> Dear Andreas,
>
> Thanks for taking care of toulbar2. I did spend some time to try to go
> around this #920459 bug bu
On Tue, Feb 19, 2019 at 11:13:29AM +0100, Andreas Tille wrote:
> On Tue, Feb 19, 2019 at 09:07:24AM +0100, Ondřej Surý wrote:
> > I believe that it was the case before that if the autoremoval was due a
> > specific RC bug, any activity on that specific bug would reset the timer
> > for autoremova
On Tue, Feb 19, 2019 at 09:07:24AM +0100, Ondřej Surý wrote:
> I believe that it was the case before that if the autoremoval was due a
> specific RC bug, any activity on that specific bug would reset the timer for
> autoremoval.
I've thought the same but despite the activity it is not reset (at
Hi,
I believe that it was the case before that if the autoremoval was due a
specific RC bug, any activity on that specific bug would reset the timer for
autoremoval.
But it might have changed since… or my memory is failing me.
Cheers,
Ondrej
> On 19 Feb 2019, at 08:46, Andreas Tille wrote:
>
Hi,
toulbar2 is
Marked for autoremoval on 22 February: #916715
However, this bug was closed in
toulbar2 (1.0.0+dfsg3-1.1) unstable; urgency=medium
* Non-maintainer upload.
* Add the missing build dependency on zlib1g-dev. (Closes: #916715)
-- Adrian Bunk Fri, 11 Jan 2019 13:47:51 +
6 matches
Mail list logo
