About mass bug filling: Bug#X: The package description does not follow Debian policy
Le mar 09/09/2003 à 16:21, Javier Fernández-Sanguino Peña a écrit :
> Your package does not comply with the policy as it does not provide
> a proper extended descrition. Policy section 2.3.3 states:
>
> The description should be written so that it gives the system
> administrator enough information to decide whether to install the
> package.
...
> This report has been automatically generated and the main reason is that
> the package has an extended description which is only one line long.
This mass bug filing has been discussed in June (more than two months
ago). Personally I don't archive of debian-* ml for that long. Archives
are available on the web but reading long threads on a web interface
sucks. Anyway even if the consensus was on ok-ing the bug filling, I
don't think it gives you an authorization to do it 10 years later.
Now for my package, I don't think it's package's
name/description/long_description/content is THE best but it is MY best.
If you want it to be improved at least make a suggestion. I would be
happy to improve the long description but I don't see what would be
missing in the current one.
Package: netmon-applet
Description: GNOME2 Network Load Applet
A simple textual network load monitor for the GNOME panel.
Personally I believe this is a false positive of your script and I am
wondering how many you filled. Also note that lintian is already doing
this kind of test and IMHO do it better.
Christophe
Le mar 09/09/2003 à 16:21, Javier Fernández-Sanguino Peña a écrit :
> Package: netmon-applet
> Version: 0.4-5
> Severity: important
> Justification: section 2.3.3
>
> Your package does not comply with the policy as it does not provide
> a proper extended descrition. Policy section 2.3.3 states:
>
> The description should be written so that it gives the system
> administrator enough information to decide whether to install the
> package.
>
> Take in account that package descriptions are very important to administrators
> to determine wether a package is (or isn't) useful for them and are
> used by package frontends in order to implement keyword-based searchs
> (samples include command line tools such as 'apt-cache search X'
> or 'grep-dctrl -F Description X' or even fancier interfaces such as
> 'dpkg-iasearch').
>
> If you need help to provide a proper description for your package you
> are advised to digest the README/manpages/HTML files provided by the package
> or, as a last resort, request help at the debian-devel mailing list.
>
> If this package is being generated from a single source package and
> you already provide a full description in your control file for the
> main package, you might want to use it automatically in sub-packages. If this
> is the case consider using ${description}, and debian/substvars.
>
> This report has been automatically generated and the main reason is that
> the package has an extended description which is only one line long.
>
> Regards
>
> Javier Fernandez-Sanguino
>
> PS: For more information please read the Debian Policy or the thread
> at debian-devel started by
> Message-ID: <20030620155309.GA7065@dat.etsit.upm.es>
> which is available at
> http://lists.debian.org/debian-devel/2003/debian-devel-200306/msg01257.html
--
Christophe Barbe <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
Reply to: