[Debian-med-packaging] RM: libwww5.808-perl -- RC-buggy, NPOASR

Andreas Tille andreas at an3as.eu
Tue Jan 24 21:39:37 UTC 2012


Hi Jonathan,

I can confirm that I'm working on Ensembl and I'm in contact with
upstream since beginning of this year to work on a strategy to get rid
of this nasty dependency.  Moreover we have a Debian Med sprint this
weekend where issues like this will be explicitely addressed.

I admit that I'm also not very happy about the fact that original
maintainers just pushed a broken package to experimental and take this
distribution as an excuse not to care any more.  I also addressed this
and I will try to actively care about this in the next couple of weeks.
I think this bug could serve as a handle to make them care more for
this package which has quite some importance for them.  So please
stay a bit tuned, we are working on this.

Kind regards

      Andreas.

On Tue, Jan 24, 2012 at 02:36:09PM -0600, Jonathan Nieder wrote:
> reassign 636923 ensembl 63-1
> severity 636923 serious
> quit
> 
> Hi,
> 
> Luca Falavigna wrote:
> 
> > As there's little the FTP Team can do at this point, I'm reassigning
> > this bug to libwww5.808-perl source package, pending a proper fix.
> 
> Since the original report last April, we haven't heard from the
> libwww5.808-perl maintainers at all.  I have run into this same
> problem on multiple machines now, and no one seems to think the
> package's existence is sane, so I'm tempted to suggest just removing
> it, with ensembl as an unfortunate casualty.
> 
> The ensembl package description explains:
> 
>   libwww-perl5.808 will conflict with the latest libwww-perl
>   installation and thus force a downgrade to 5.808, which will disable
>   many other tools on your system. Therefore it is advisable NOT to
>   install this package in parallel with any other software, and/or use
>   a virtual machine or dedicated machine.
> 
> which does not sound like a package that I would expect to find in the
> archive.
> 
> However, maybe the ensembl maintainers can come up with some method
> for avoiding this?  E.g., [1] seems to have some ideas that would not
> require such an invasive package.  Cc-ing them.
> 
> Thanks,
> Jonathan
> 
> [1] http://bugs.debian.org/593568#25
> 
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list