Incidencia #34859

incorrect-fsf-address

Abrir Fecha: 2015-02-01 15:38 Última actualización: 2015-02-02 13:21

Informador:
Propietario:
Tipo:
Estado:
Cerrado
Componente:
Prioridad:
8
Gravedad:
8
Resolución:
Accepted
Fichero:
Ninguno

Details

RPMlint found FSF addresses in the sources are incorrect.

[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/jiskana.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/pinyin.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/zenkaku.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/quanjiao.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/egg/wnn.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/doc/packages/tamago/COPYING
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/hangul.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/ascii.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/egg/sj3rpc.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/egg-edep.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/zhuyin.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/hira.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/egg/canna.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its-keydef.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/menudiag.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/bixing.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/eggrc
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/hankata.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/thai.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/egg.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/erpin.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/leim-list.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/aynu.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/egg/cannarpc.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/its/jeonkak.el
[   31s] tamago.noarch: W: incorrect-fsf-address /usr/share/emacs/site-lisp/egg/egg/sj3.el
[   31s] The Free Software Foundation address in this file seems to be outdated or
[   31s] misspelled.  Ask upstream to update the address, or if this is a license file,
[   31s] possibly the entire file with a new copy available from the FSF.

Ticket History (3/5 Histories)

2015-02-01 15:38 Updated by: itisango
  • New Ticket "incorrect-fsf-address" created
2015-02-01 17:40 Updated by: itisango
2015-02-02 08:58 Updated by: itisango
Comentario

I found more bad addresses.

egrep -R -i '02111-1307' .
./docomp.el:;; Boston, MA 02111-1307, USA.
./egg-cnv.el:;; Boston, MA 02111-1307, USA.
./egg-com.el:;; Boston, MA 02111-1307, USA.
./egg-mlh.el:;; Boston, MA 02111-1307, USA.
./egg-sim.el:;; Boston, MA 02111-1307, USA.
./egg-x0213.el:;; Boston, MA 02111-1307, USA.
./egg/anthy.el:;; Boston, MA 02111-1307, USA.
./egg/anthyipc.el:;; Boston, MA 02111-1307, USA.
./egg/wnnrpc.el:;; Boston, MA 02111-1307, USA.
./its/kata.el:;; Boston, MA 02111-1307, USA.
./jisx0213.el:;; Boston, MA 02111-1307, USA.
2015-02-02 13:21 Updated by: itisango
  • Estado Update from Open to Cerrado
  • Ticket Close date is changed to 2015-02-02 13:21
Comentario

fixed in tsunagi-5.0.6.0.

Attachment File List

No attachments

Editar

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Entrar