Your message dated Mon, 24 Oct 2011 16:26:12 +0200
with message-id <[email protected]>
and subject line aclock.app: homepage in description
has caused the Debian Bug report #615181,
regarding aclock.app: please use Homepage field to point to upstream homepage
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
615181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615181
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aclock.app
Severity: minor
User: [email protected]
Usertags: homepage-field
[ This is an automated bug report, part of the mass bug filing discussed
at <http://lists.debian.org/debian-devel/2011/02/msg00367.html>. The
submitter is Stefano Zacchiroli, reachable at <[email protected]>. ]
According to lintian, aclock.app uses its long description
to point to upstream homepage, following an old Developer's Reference
recommendation. That practice has various drawbacks, including the
inability to automatically process homepage information from
package-related services such as packages.d.o, the PTS, etc. Starting
from version 1.14.6, dpkg supports Homepage: as a regular field in
debian/control. You can check Debian Policy § 5.6.23 for more information
<http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Homepage>
Please remove the deprecated pseudo header from the long description of
aclock.app and turn it into a regular debian/control field.
In case of multiple binary packages, doing so would also allow to factor
out homepage information into the source stanza of debian/control,
instead of repeating it in each binary stanza.
Cheers.
--- End Message ---
--- Begin Message ---
This problem has been fixed with the experimental upload 0.2.3-4.
Yours,
Gurkan
--- End Message ---
