Re: Signature for a released source code package

2017-12-08 Thread Federico Mena Quintero
On Sat, 2017-10-14 at 22:08 +0200, Uwe Scholz wrote: > Now after I thought about it I was wondering how a user can be sure > that he gets the same source code which I uploaded to the Gnome > servers. The thing is, when I do a release with "make distcheck" as > described in the gnome wiki(*), a tar.

Re: Signature for a released source code package

2017-10-15 Thread Uwe Scholz
Okay, in this case I will have a look in our config files and change the output of make distcheck. This should be enough then. Best Uwe Am 15. Oktober 2017 00:19:53 MESZ schrieb Christian Hergert : >On 10/14/2017 01:08 PM, Uwe Scholz wrote: >> >> I have been asked by a user why I don't put a s

Re: Signature for a released source code package

2017-10-14 Thread Christian Hergert
On 10/14/2017 01:08 PM, Uwe Scholz wrote: I have been asked by a user why I don't put a signature for the software package on my projects homepage. Actually, I just put a link to the *.tar.xz file on it, pointing to the these file(s) on the gnome server: https://download.gnome.org/sources/gno

Signature for a released source code package

2017-10-14 Thread Uwe Scholz
Hi, I am the maintainer of Gnome-Commander which is hosted and distributed on the gnome servers. I have been asked by a user why I don't put a signature for the software package on my projects homepage. Actually, I just put a link to the *.tar.xz file on it, pointing to the these file(s) on th