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

Bug#368130: marked as done (grep "59 Temple St" /usr/bin/*)



Your message dated Mon, 19 Jun 2006 15:09:45 -0500
with message-id <87wtbcc3g6.fsf@glaurung.internal.golden-gryphon.com>
and subject line This is not appropriate for policy
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: debian-policy
Severity: wishlist

Many programs in /usr/bin have GNU's _old_ address hardwired in:
$ cd /usr/bin
$ fgrep --files-with-matches '59 Temple Place' *|wc -l
179
$ fgrep --files-with-matches Temple *|wc -l
187
And that's just on my machine.
$ fgrep --files-with-matches Mass *|wc -l
40 #An even older address, Mass Ave.

It must be because policy doesn't say anything about sticking
copyright notices in the /usr/[s]bin/file, only about
/usr/share/doc/<package>/copyright .

Therefore policy should say not to put copyright notices in
/usr/[s]bin/* or at least not office addresses that will get stale.
Instead when one does
$ some_program --view-copyright
the output should say to see /usr/share/common-licenses/...


--- End Message ---
--- Begin Message ---
Hi,

        An old, or wrong, address in the script is a bug, or at least a
 wishlist for updating. The bugs should be fixed, and should not need
 policy to say "do not have bugs in your packages".

        manoj
-- 
I think we're all Bozos on this bus.
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

--- End Message ---

Reply to: