In a testdir of the 'lchmod' module, I get this error:
gcc -g -O2 -o test-lchmod test-lchmod.o libtests.a ../gllib/libgnu.a
libtests.a ../gllib/libgnu.a libtests.a @LIBINTL@
gcc: error: @LIBINTL@: No such file or directory
make[4]: *** [Makefile:2563: test-lchmod] Error 1
This patch fixes it
() Florian Weimer
() Mon, 09 Nov 2020 10:14:00 +0100
Would you be able to share details of the file system used
(XFS or something else?) and the kernel version (uname -a,
rpm -q kernel)?
Do you use virtualization or containers?
I would like to see if I can reproduce it internall
On 1/10/21 5:14 PM, Bruno Haible wrote:
> "https://git.savannah.gnu.org/git/myproject.git -
>encrypted read-only anonymous smart http access"
Nice, then https:// seems indeed to be better than git://.
Have a nice day,
Berny
Bernhard Voelker wrote:
> For HTTP/HTTPS, the question is if the server is configured for
> "smart HTTP" or if the client has to fall back to "dumb HTTP".
Does https://savannah.gnu.org/maintenance/UsingGit/ answer this question?
It says:
"https://git.savannah.gnu.org/git/myproject.git -
encry
On 1/10/21 1:20 PM, Simon Josefsson via Gnulib discussion list wrote:
> Using https:// instead of git:// makes this slightly better.
Both https:// and git:// URLs are configured to be read-only on the
Savannah server, and only the ssh:// variant allows pushing.
https://git-scm.com/book/en/v2/Git-
I had a walk and realized it might be better to think of the problem
like this. Consider if someone wants to volunteer to do a new gettext
release, they would go to
https://savannah.gnu.org/git/?group=gettext
which properly suggest to checkout over https or SSH. After reading
HACKING the pers
Bruno Haible writes:
> Hi Simon,
>
> Can you briefly say, why, please? Is the 'git' protocol unsecure?
> Is it a problem specifically with Savannah? Or what else?
Sorry I should have included this -- I thought it was well-known.
The man page for git-clone https://git-scm.com/docs/git-clone says
