After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 653215 - Outdated FSF Address in code files
Outdated FSF Address in code files
Status: RESOLVED DUPLICATE of bug 721515
Product: metacity
Classification: Other
Component: general
2.34.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks: 721455
 
 
Reported: 2011-06-23 07:37 UTC by Dominique Leuenberger
Modified: 2014-01-08 21:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Leuenberger 2011-06-23 07:37:36 UTC 
metacity-devel.x86_64: W: incorrect-fsf-address /usr/include/metacity-1/metacity-private/util.h
metacity-devel.x86_64: W: incorrect-fsf-address /usr/include/metacity-1/metacity-private/common.h
metacity-devel.x86_64: W: incorrect-fsf-address /usr/include/metacity-1/metacity-private/theme-parser.h
metacity-devel.x86_64: W: incorrect-fsf-address /usr/include/metacity-1/metacity-private/theme.h
metacity-devel.x86_64: W: incorrect-fsf-address /usr/include/metacity-1/metacity-private/preview-widget.h
metacity-devel.x86_64: W: incorrect-fsf-address /usr/include/metacity-1/metacity-private/gradient.h
metacity-devel.x86_64: W: incorrect-fsf-address /usr/include/metacity-1/metacity-private/boxes.h
metacity.x86_64: W: incorrect-fsf-address /usr/share/doc/packages/metacity/COPYING
The Free Software Foundation address in this file seems to be outdated or
misspelled.  Ask upstream to update the address, or if this is a license file,
possibly the entire file with a new copy available from the FSF.
Comment 1 Dominique Leuenberger 2014-01-08 21:06:14 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 721515 ***