Hi Carnë,

On Mon, Feb 11, 2019 at 12:59:45PM +0000, Carnë Draug wrote:
> On Wed, 6 Feb 2019 at 14:06, Andreas Tille <ti...@debian.org> wrote:
> > This is what I've though about: Removing the files from bioperl-run
> > (which would be 1.7.2-5 then)
> Upstream has released BioPerl-Run 1.7.3 which fixes this conflict
> issue.  If someone could prepare that release that would be nice.

Thanks a lot for this hint.
> Like BioPerl 1.7.3, this new release of BioPerl-Run removed multiple
> modules and so, probably not suitable for migration to Buster during
> this transition freeze period.

This is demonstrated very well here:


Lots of packages (not only bioperl-run) are broken by the new version.
Thus I admit I see no real profit in upgrading bioperl-run at this
release stage.  We could upload to experimental (Carnë, I'm explicitly
encouraging you to do so if you have some interest in it).  I for
myself have currently more important things on my desk since this
becomes important for my only after Buster release.

For sure everybody is invited to fix all those packages in experimental
that are currently broken by bioperl 1.7.4.  This would enable a smooth
transition after testing is open for Buster+1.

Kind regards



Reply via email to