Mail Archives: geda-user/2012/02/18/06:19:27
--bcaec52be7b9d995cb04b93b3a3f
Content-Type: text/plain; charset=ISO-8859-1
Hi Juergen
Thanks for the pointer and don't worry about the list - now that I know
what I'm looking for, I'll get a ticket opened and build a cleanup patch
for this over the next few days (I'm out of town til Tuesday).
Cheers
Gareth
On Saturday, 18 February 2012, Juergen Harms wrote:
> Hi Gareth - thanks for picking up this (un-amusing) issue - I do not know
> why somebody invested time to make rpmlint more complicated than it is
> already - probably this is "lawyers-feed".
>
> And sorry that I did not explore things further. I now generated a list of
> all the modules that trigger this error. Many of them turned out to be
> auto-generated by one of the makes and I could skip them
>
> Result:
>
> There are both modules with correct and with incorrect addresses in the
> geda package - the example you gave is correct: gschem/src/x_rc.c with
> Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
> MA 02111-1301 USA
>
> Here is an example of an incorrect one: gnetlist/src/vams-misc.c with
> Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
>
> Doing the sorting and going back from the messages generated by rpmlint to
> the source modules in the tarball is somewhat painful - I ended up with a
> list of 92 modules but, given the manual filterering, I may have committed
> some mistakes. Where can I send that list without annoying people on this
> list who might have a slow connection?
>
> Anyhow, it is probably better to do a global search for Cambridge to find
> the faulty packages by context.
>
> Regards, Juergen
>
--bcaec52be7b9d995cb04b93b3a3f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi Juergen<div><br></div><div>Thanks for the pointer and don't worry ab=
out the list - now that I know what I'm looking for, I'll get a tic=
ket opened and build a cleanup patch for this over the next few days (I'=
;m out of town til Tuesday).</div>
<div><br></div><div>Cheers</div><div>Gareth<br><br>On Saturday, 18 February=
2012, Juergen Harms wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Gareth - =
thanks for picking up this (un-amusing) issue - I do not know why somebody =
invested time to make rpmlint more complicated than it is already - probabl=
y this is "lawyers-feed".<br>
<br>
And sorry that I did not explore things further. I now generated a list of =
all the modules that trigger this error. Many of them turned out to be auto=
-generated by one of the makes and I could skip them<br>
<br>
Result:<br>
<br>
There are both modules with correct and with incorrect addresses in the ged=
a package - the example you gave is correct: gschem/src/x_rc.c with<br>
Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA=
02111-1301 USA<br>
<br>
Here is an example of an incorrect one: gnetlist/src/vams-misc.c with<br>
Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.<br>
<br>
Doing the sorting and going back from the messages generated by rpmlint to =
the source modules in the tarball is somewhat painful - I ended up with a l=
ist of 92 modules but, given the manual filterering, I may have committed s=
ome mistakes. Where can I send that list without annoying people on this li=
st who might have a slow connection?<br>
<br>
Anyhow, it is probably better to do a global search for Cambridge to find t=
he faulty packages by context.<br>
<br>
Regards, Juergen<br>
</blockquote></div>
--bcaec52be7b9d995cb04b93b3a3f--
- Raw text -