Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-11-28 Thread Andreas Beckmann
On 28/11/2019 11.05, Michael Crusoe wrote: > Would breaks+replaces libbio-perl-run-perl (<<1.7.3) make sense? Exactly. Andreas

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-11-28 Thread Michael Crusoe
Thanks Andreas Beckmann! Would breaks+replaces libbio-perl-run-perl (<<1.7.3) make sense? On Thu, Nov 28, 2019 at 12:00 AM Andreas Beckmann wrote: > Followup-For: Bug #921495 > Control: found -1 1.7.6-1 > > libbio-perl-perl is missing proper > Breaks+Replaces: libbio-perl-run-perl (<< 1.7.3)

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-11-27 Thread Andreas Beckmann
Followup-For: Bug #921495 Control: found -1 1.7.6-1 libbio-perl-perl is missing proper Breaks+Replaces: libbio-perl-run-perl (<< 1.7.3) There is a typoed (lib?io-perl-run-perl) and wrongly versioned Breaks: libio-perl-run-perl (<= 1.7.3-1), roary (<= 3.12.0+dfsg-2) without corresponding

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-07-30 Thread Andreas Beckmann
Followup-For: Bug #921495 Control: found -1 1.7.5-1 There is a file overwrite issue upgrading from buster: Preparing to unpack .../libbio-perl-perl_1.7.5-1_all.deb ... Unpacking libbio-perl-perl (1.7.5-1) over (1.7.2-3) ... dpkg: error processing archive

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-02-12 Thread Andreas Tille
On Mon, Feb 11, 2019 at 04:15:21PM +, Carnë Draug wrote: > > What do you think? > > All packages that depend on bioperl are being affected by this. The > current situation is a bit awkward because packaging and testing in > sid fails even though it would be fine in testing. This will cause

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-02-11 Thread Carnë Draug
On Mon, 11 Feb 2019 at 15:47, Andreas Tille wrote: > > On Mon, Feb 11, 2019 at 03:32:47PM +, 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

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-02-11 Thread Andreas Tille
On Mon, Feb 11, 2019 at 03:32:47PM +, 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

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-02-11 Thread Carnë Draug
On Mon, 11 Feb 2019 at 14:06, Andreas Tille wrote: > > Hi Carnė, > > On Mon, Feb 11, 2019 at 12:59:45PM +, Carnė Draug wrote: > > On Wed, 6 Feb 2019 at 14:06, Andreas Tille wrote: > > > This is what I've though about: Removing the files from bioperl-run > > > (which would be 1.7.2-5 then) >

Bug#921495: Bioperl 1.7.4 should not migrate to Buster

2019-02-11 Thread Andreas Tille
Hi Carnë, On Mon, Feb 11, 2019 at 12:59:45PM +, Carnë Draug wrote: > On Wed, 6 Feb 2019 at 14:06, Andreas Tille 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