Am Sonntag, den 20.09.2009, 16:32 +0200 schrieb Gaudenz Steinlin:
> I'll write to the upstream author about the nameing conflict.
Thanks for taking care of this!
> The best way to go would be to rename the upstream package. What's the
> purpose of the sinfo binary in the slurm-llnl package? If it
Hi
On Sat, Sep 19, 2009 at 11:26:04PM +0200, oliv...@na.icar.cnr.it wrote:
> Hi,
> I do agree with Manuel objections.
> Maybe you can call it ant-sinfo, from the name of the laboratory where
> the tool is developed.
> Best Regards
> --
> Gennaro
>
> On Sat, Sep 19, 2009 at 04:07:36PM +0200, Man
Hi,
I do agree with Manuel objections.
Maybe you can call it ant-sinfo, from the name of the laboratory where
the tool is developed.
Best Regards
--
Gennaro
On Sat, Sep 19, 2009 at 04:07:36PM +0200, Manuel Prinz wrote:
> Hi Gaudenz!
>
> As it seems, the executable is named "sinfo", which is alre
Hi Gaudenz!
As it seems, the executable is named "sinfo", which is already supplied
in the SLURM batch system package (slurm-llnl). Because both packages
are useful on clusters, a Conflicts does not make sense, so renaming
seems to be the best option. I CC'ed Gennaro (slurm-llnl maintainer) so
he
Package: wnpp
Severity: wishlist
Owner: Gaudenz Steinlin
* Package name: sinfo
Version : 0.0.33
Upstream Author : Jürgen Rinas
* URL : http://www.ant.uni-bremen.de/whomes/rinas/sinfo/
* License : GPL
Programming Lang: C++
Description : Monitoring tool
5 matches
Mail list logo
