--- Begin Message ---
- To: Thomas Schiex <thomas.schiex@inra.fr>
- Subject: Re: toulbar2: What will happen if testing migration takes longer than removal from testing
- From: Andreas Tille <andreas@an3as.eu>
- Date: Tue, 19 Feb 2019 11:39:40 +0100
- Message-id: <20190219103940.ma2xf7iaifc4swvo@an3as.eu>
- In-reply-to: <cd57252d-2434-23f1-c6a5-afc963133b05@inra.fr>
- References: <[🔎] 20190219074610.l2qb447uxfqqa6ak@an3as.eu> <cd57252d-2434-23f1-c6a5-afc963133b05@inra.fr>
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 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 (another bug popped up, that was
> apparently already met by other people using doxygen using the same
> TexLive update but I found no workaround).
I think doxygen is severly broken and just skipping refman.pdf (finally
users can read other format) the only safe solution to keep the package
in. I added several FIXMEs to get it back for Buster+1.
> If there is anything I can do, please do not hesitate to ask for
> support. I'm not sure I'll be able to quickly allocate time, but I at
> least I would be happy to try.
I do not think that there is anything to do now but hoping that the
package will be kicked for no good reason.
Kind regards
Andreas.
PS: Its better to write in public - at least CCing the bug would
have made sense. Feel free to quote me.
> Le 19/02/2019 à 08:46, Andreas Tille a écrit :
> > 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 <bunk@debian.org> Fri, 11 Jan 2019 13:47:51 +0200
> >
> >
> > The problem is that the package did not migrated due to #920459 (doxygen
> > currently breaks lots of packages and I wonder in general what will
> > happen with those packages). I now uploaded
> >
> >
> > toulbar2 (1.0.0+dfsg3-2) unstable; urgency=medium
> > ...
> > * Prevent generation of PDF documentation since otherwise toulbar2 does
> > not build (see bug #920459). This means should be reverted once doxygen
> > is fixed.
> > ...
> > -- Andreas Tille <tille@debian.org> Mon, 18 Feb 2019 22:17:10 +0100
> >
> >
> > Which enabled the build on all release architectures.
> >
> > I'm simply wondering what will happen with toulbar2 (and other packages
> > - I'm actually not that much involved in this, it is just a random
> > Debian Science package) once it was removed from testing. As far as I
> > understood there will be no migrations from unstable to testing any more
> > if there is no version of that package in testing. Does that mean that
> > the doxygen issues will kick several packages out of Buster or is there
> > any way to prevent this?
> >
> > Kind regards
> >
> > Andreas.
> >
>
--
http://fam-tille.de
--- End Message ---