On Wed, 6 Feb 2019 at 14:06, Andreas Tille <ti...@debian.org> wrote: > On Wed, Feb 06, 2019 at 01:18:26PM +0000, Carnė Draug wrote: > > I guess the fix for this is to have in bioperl's d/control: > > > > Breaks: libbio-perl-run-perl (<< 1.7.3) > > > > It would be nice if upstream did a new release of bioperl-run soon > > without those modules. I have prepared the upstream repository and > > have requested them to make a release but I don't know when it will > > happen. > > > > Alternatively, you could remove those files in Debian and have a > > bioperl-run version 1.7.2-4. > > 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. 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.