On Mon, Feb 11, 2019 at 03:32:47PM +0000, Carnë Draug wrote:
> Well, all those regressions are because they can't install bioperl
> which is their dependency.  There is no issue on themselves or in
> upstream bioperl.  The issue is that Debian's bioperl claims to have
> recommend dependency on bioperl-run which does not actually exist in
> upstream anymore.

> > 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.
> I'm not interested on bioperl-run either.  But can you remove the
> current bioperl from sid which is causing all those issues on the
> other packages?

There is no easy way to remove a package from sid.  The only way would
be to upload version 1.7.2 with an epoch (1:1.7.2).  Since epochs are
ugly I would like to avoid this.  If it hurds anybody to much we might
consider uploading bioperl-run as well.  Since it probably needs a
versioned depends ob bioperl 1.7.4 it should not migrate to testing as
well.  But since all these regressions are only in sid I see no real
harm (except Ubuntu might fetch from unstable and will end up with
broken bioperl stuff.

What do you think?

Kind regards



Reply via email to