[Debian-med-packaging] Bug#832391: consensuscore2: Any news?

Andreas Tille andreas at an3as.eu
Tue Dec 6 14:48:01 UTC 2016


Hi,

On Tue, Dec 06, 2016 at 11:23:36AM +0000, Ghislain Vaillant wrote:
> > 
> > I should have posted an update. Upstream has moved consensuscore2 into a
> > new source package, unanimity [1]. The packaging issues I was having are
> > due to building the mixed-language code base. I have not found a good
> > solution for this with debhelper, and the upstream build system was also
> > very unconventional in order to handle it (which did not help
> > debhelper's latching onto it). I think what needs to be done is to just
> > package unanimity and have consensuscore2 be one of its binary packages.
> > I'll have to see whether this problem will come up again after that.
> 
> I confirm Afif's reporting. This project is deprecated in favour of a larger
> one.
> 
> We should just request an RM for this package, since we won't be getting any
> support for it from upstream in the future, and focus on the new project. This
> should also clear the current RC bug affecting it.

So I wonder whether we should turn this into an ITP unanimity[1].  The
first stumbling stone is that they do not add release tags but have
somehow switched of reporting this as an issue on Github (at least I
can't find any contact to ask them for tags :-().

I'm personally fine with removing consensuscore2 package from Debian.

Afif, could you push your preliminary work how rudimentary / non-working
it might be?  It just helps to display the current state on the tasks
pages as prospective package in VCS (in case somebody is seeking for an
interesting job ...)

Kind regards

       Andreas.

PS: I'll reassign #832391 to ftp.debian.org and turn it into a ROM request.

[1] https://github.com/PacificBiosciences/unanimity

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list