[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Broken/Obsolete packages - I think we can do better.



On Wed, 18 Aug 2010 13:56:44 -0500, Timothy Legg wrote:

> I wish to bring up something that bothers me.
> 
> I just installed a stable Debian package that advertises to perform so
> many wonderful tasks, but in reality, it does little more than provide
> an attractive graphical interface for a segmentation fault.
> 
> I searched google and indeed found others that had this problem with
> this package.  I also found out that this problem was solved a couple
> years ago in a newer version.  Unfortunately, Debian is still delivering
> a broken-out-of-the-box version of this package.

I agree what others have already commented out: just report it.

Should you find any error or estimate there is something it can be 
improved, just contact the developer by means of the standard path, i.e., 
Debian BTS or just by dropping a few lines by e-mail. 

> I feel that this issue reflects a need for the Debian team to enforce a
> higher standard on functionality and reliability of the packages that
> are available in the family of stable packages.

I agree there must be mechanisms to prevent such things to happen but 
those mechanisms involve "us" (you, me...) mostly due to the own nature 
of the FLOSS projects, which usually lack of resources to constantly keep 
an eye on this. So we (users) have to, at least, help on things to 
improve this. People who can't code a patch or upload a new package, can 
collaborate in many other tasks, like informing the developer about this.

> I believe there should be a stronger system where broken, non-functional
> or obsolete package are weeded out as they make Debian appear broken and
> unstable.  At minimum, a voting system where users can rate up or down
> packages at packages.debian.org or some other feedback to warn or
> encourage prospective users.

It happens in all (small, big, extra-big) places/projects. 

Recently, Mozilla found an extension that was used for sniffing user's 
data, and had to remove it from their add-ons site.

You find it, you report it :-)

Greetings,

-- 
Camaleón


Reply to: