The "homepage" quoted in http://packages.ubuntu.com/raring/cpulimit is not correct

I suggest using the github link as homepage, as the cpulimit.sourceforge.net address mentions that cpulimit has moved to github.

On Fri, 03 May 2013 12:18:10 -0000, Ganton wrote:

> This is easy to fix: the "homepage" quoted in
> "http://packages.ubuntu.com/raring/cpulimit" is not correct. There it
> says "limitcpu.sourceforge.net" but it should be
> "cpulimit.sourceforge.net" (or "https://github.com/opsengine/cpulimit").

No, the cpulimit in Debian (and Ubuntu) is the version from
http://limitcpu.sourceforge.net/. This was chosen since the original
one was dormant for quite some time.

Cheers,
gregor (cpulimit maintainer in Debian)

--
 .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
 `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-

Hi!

> On Fri, 03 May 2013 12:18:10 -0000, Ganton wrote:
> > This is easy to fix: the "homepage" quoted in
> > "http://packages.ubuntu.com/raring/cpulimit" is not correct. There it
> > says "limitcpu.sourceforge.net" but it should be
> > "cpulimit.sourceforge.net" (or "https://github.com/opsengine/cpulimit").
>
> No, the cpulimit in Debian (and Ubuntu) is the version from
> http://limitcpu.sourceforge.net/. This was chosen since the original
> one was dormant for quite some time.

Mmm... when there are differences between LimitCPU and Cpulimit, between
limitcpu.sourceforge.net and cpulimit.sourceforge.net, I wonder if the package
has to be called cpulimit or limitcpu (as its author names its software), to
avoid confusions.

I mean, if I make a debian-based distribution called Genian, if someone
officially calls it Debian, there are going to be errors :-(

> Cheers,
> gregor (cpulimit maintainer in Debian)

Cheers! And thanks for all the maintaining and all!

On Sat, 04 May 2013 12:49:55 -0000, Ganton wrote:

> > > This is easy to fix: the "homepage" quoted in
> > > "http://packages.ubuntu.com/raring/cpulimit" is not correct. There it
> > > says "limitcpu.sourceforge.net" but it should be
> > > "cpulimit.sourceforge.net" (or "https://github.com/opsengine/cpulimit").
> > No, the cpulimit in Debian (and Ubuntu) is the version from
> > http://limitcpu.sourceforge.net/. This was chosen since the original
> > one was dormant for quite some time.
> Mmm... when there are differences between LimitCPU and Cpulimit, between
> limitcpu.sourceforge.net and cpulimit.sourceforge.net, I wonder if the package
> has to be called cpulimit or limitcpu (as its author names its software), to
> avoid confusions.

That's a good question ... When Jesse took Angelo's cpulimit code and
improved it, I decided to go with the original package name; and the
"limitcpu" upstream source also still produces a "cpulimit" binary.

Since then Angelo has shown some signs of activity, and Jesse and
Angelo are in contact. Not sure about the future, since the last
"cpulimit" commits are 10 months old ...

As I understand it Jesse's work is meant as a continuation of the
original cpulimit, he just picked a different project name on SF ...

So yes, that's a bit confusing, but I think sticking with the package
name is the lesser problem.

Cheers,
gregor

--
 .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
 `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `- NP: Cat Power: Empty Shell

So since the Debian maintainer has confirmed the url is valid since were are getting our source from the old link and not merging from the new project I think it might be good to consider marking this invalid at this time.

[Expired for cpulimit (Ubuntu) because there has been no activity for 60 days.]

So finally this bug was "expired". Because of the explanations that Gregor Herrmann and others wrote there, I guess that a different bug report will have to be made to call this package "limitcpu" instead of "cpulimit". Just to be loyal to truth, to the author of limitcpu (who calls its software... limitcpu not cpulimit), to avoid what are trademark violations, and to avoid confusions (*).

(*) Like people installing the cpulimit package and seeing that some things don't work as they expected... because they installed the limitcpu software instead.

I understand that not everyone has enough time to do what he thinks it's correct... but, who knows, after reporting a situation, maybe someone with enough time and resources will mend it in the future. At least, the door is open.