GPG signing is bent on WIndows

Several weeks ago I updated to the latest Git for Windows (when prompted by the version check). At the time I noticed: $ git commit -S -am "Fix unset MAKE variable in test scripts" gpg: signing failed: No pinentry gpg: signing failed: No pinentry error: gpg failed to sign the data fatal: failed

Re: How to push using SSH and pull using HTTPS for all repos on GitHub?

On Sat, Aug 4, 2018 at 9:26 PM, Jonathan Nieder wrote: > Hi, > > Jeffrey Walton wrote: > >> I'm having trouble setting up my ~/.gitconfig to push using SSH and >> pull using HTTPS for all repos on GitHub. The idea is, no passwords on >> pulls and only use the pas

How to push using SSH and pull using HTTPS for all repos on GitHub?

I'm having trouble setting up my ~/.gitconfig to push using SSH and pull using HTTPS for all repos on GitHub. The idea is, no passwords on pulls and only use the password for push. I've got the first part of the equation using the following in my ~/.gitconfig (the ellipses are user info): $

Re: No rule to make target `git-daemon'

On Fri, Jul 20, 2018 at 5:04 PM, brian m. carlson wrote: > On Thu, Jul 19, 2018 at 09:37:08PM -0400, Jeffrey Walton wrote: >> Hi Everyone, >> >> I'm working from the 2.18 tarball on Solaris 11.3 x86_64. I'm catching >> the following when building from sources. This a

No rule to make target `git-daemon'

Hi Everyone, I'm working from the 2.18 tarball on Solaris 11.3 x86_64. I'm catching the following when building from sources. This appears to be a new issue. It was not present in 2.17.1. gmake: *** No rule to make target `git-daemon'. Stop. gmake: *** Waiting for unfinished jobs

Re: sed: command garbled: rGIT-PERL-HEADER

On Wed, Jul 18, 2018 at 2:47 PM, Jeffrey Walton wrote: > On Wed, Jul 18, 2018 at 1:49 PM, Junio C Hamano wrote: >> Jeffrey Walton writes: >> ... >> diff --git a/Makefile b/Makefile >> index 2ba24035f5..50138e85eb 100644 >> --- a/Makefile >&g

Re: sed: command garbled: rGIT-PERL-HEADER

On Wed, Jul 18, 2018 at 1:49 PM, Junio C Hamano wrote: > Jeffrey Walton writes: > ... > diff --git a/Makefile b/Makefile > index 2ba24035f5..50138e85eb 100644 > --- a/Makefile > +++ b/Makefile > @@ -2086,7 +2086,7 @@ $(SCRIPT_PERL_GEN): % : %.perl GIT-PERL-DEFINES > GIT

sed: command garbled: rGIT-PERL-HEADER

I'm trying to build Git 2.18 on Solaris 11.3 x86_64. $ gmake V=1 rm -f git-add--interactive git-add--interactive+ && \ sed -e '1{' \ -e 's|#!.*perl|#!/usr/bin/perl|' \ -e 'rGIT-PERL-HEADER' \ -e 'G' \ -e '}' \ -e 's/@@GIT_VERSION@@/2.18.0/g' \

Re: Crash when clone includes magic filenames on Windows

On Sat, Feb 10, 2018 at 4:31 AM, Torsten Bögershausen <tbo...@web.de> wrote: > On Sat, Feb 10, 2018 at 03:55:58AM -0500, Jeffrey Walton wrote: >> Hi Everyone, >> >> I'm seeing this issue on Windows: https://pastebin.com/YfB25E4T . It >> seems the filename AUX

Crash when clone includes magic filenames on Windows

Hi Everyone, I'm seeing this issue on Windows: https://pastebin.com/YfB25E4T . It seems the filename AUX is the culprit. Also see https://blogs.msdn.microsoft.com/oldnewthing/20031022-00/?p=42073 . (Thanks to Milleneumbug on Stack Overflow). I did not name the file, someone else did. I doubt the

Does Git build things during 'make install"?

My script to build Git dies during cleanup. Cleanup removes the downloaded tarball and the unpacked directory: ** Cleanup ** rm: cannot remove 'git-2.14.2/perl/blib/lib/.exists': Permission denied rm: cannot remove 'git-2.14.2/perl/blib/lib/Git/SVN/Fetcher.pm': Permission denied

Re: undefined reference to `pcre_jit_exec'

On Thu, Oct 12, 2017 at 4:38 PM, Jeff King <p...@peff.net> wrote: > On Thu, Oct 12, 2017 at 04:34:38PM -0400, Jeffrey Walton wrote: > >> > It looks like autoconf turns on USE_LIBPCRE1, but isn't smart enough to >> > test NO_LIBPCRE1_JIT. >> >> If Git wants

Re: undefined reference to `pcre_jit_exec'

On Thu, Oct 12, 2017 at 4:10 PM, Jeff King <p...@peff.net> wrote: > On Thu, Oct 12, 2017 at 04:06:11PM -0400, Jeffrey Walton wrote: > >> I have a script to build Git on some old platforms to ease testing. >> Old platforms include CentOS 5. The script is available at >&g

undefined reference to `pcre_jit_exec'

Hi Everyone, I have a script to build Git on some old platforms to ease testing. Old platforms include CentOS 5. The script is available at https://github.com/noloader/Build-Scripts/blob/master/build-ssh.sh. It looks like something got knocked loose recently. I'm seeing several of these when

Re: How to force a push to succeed?

Commit seems to be the wrong command as Git appears to be trying to do something I don't want. How do I force the push to succeed? Thanks in advance. >>> >>> Checkout the --force[-with-lease] argument. > > Thanks again Stefan, > > From another testing machine, it

Re: How to force a push to succeed?

On Tue, Aug 22, 2017 at 6:03 PM, Jeffrey Walton <noloa...@gmail.com> wrote: > On Tue, Aug 22, 2017 at 5:57 PM, Stefan Beller <sbel...@google.com> wrote: >> On Tue, Aug 22, 2017 at 2:55 PM, Jeffrey Walton <noloa...@gmail.com> wrote: >>> I tested some changes

Re: How to force a push to succeed?

On Tue, Aug 22, 2017 at 5:57 PM, Stefan Beller <sbel...@google.com> wrote: > On Tue, Aug 22, 2017 at 2:55 PM, Jeffrey Walton <noloa...@gmail.com> wrote: >> I tested some changes that lead to a dead end. The changes need to be >> removed. The changes were added in 7

How to force a push to succeed?

I tested some changes that lead to a dead end. The changes need to be removed. The changes were added in 7 commits. I went back in time to the point before the changes: $ git reset --hard HEAD~7 HEAD is now at 559fc3b Fix benchmark selection code (GH #464) When I attempted to push:

Re: Please fix the useless email prompts

On Sat, Aug 19, 2017 at 12:36 PM, Junio C Hamano <gits...@pobox.com> wrote: > Jeffrey Walton <noloa...@gmail.com> writes: > >> Is it possible to fix the issue shown below? >> >> I'm on a test machine. All I do is update to the latest code, build &

Please fix the useless email prompts

Is it possible to fix the issue shown below? I'm on a test machine. All I do is update to the latest code, build the library and run the self tests. The test user account does not have a name and does not have an email address. There's nothing to provide. There's no reason to break my workflows

Re: How to avoid "Please tell me who you are..."?

On Fri, Jun 2, 2017 at 3:00 AM, Konstantin Khomoutov <kostix+...@007spb.ru> wrote: > On Fri, Jun 02, 2017 at 02:02:22AM -0400, Jeffrey Walton wrote: > >> I'm working on a test machine. It mostly needs to be a clone of >> upstream. On occasion it needs to test a particu

Re: How to avoid "Please tell me who you are..."?

with test@. As a matter of policy, no check-ins occur on it. Other than the password database and authroized_keys file, there is no information on it to be lost or stolen. Jeff > On June 2, 2017 7:02:22 AM GMT+01:00, Jeffrey Walton <noloa...@gmail.com> > wrote: >> >> I'm working o

How to avoid "Please tell me who you are..."?

I'm working on a test machine. It mostly needs to be a clone of upstream. On occasion it needs to test a particular commit. When I attempt to test a commit it produces: $ git cherry-pick eb3b27a6a543 *** Please tell me who you are. Run git config --global user.email

Re: How to force a pull to succeed?

On Mon, May 15, 2017 at 11:42 PM, Junio C Hamano <gits...@pobox.com> wrote: > Jeffrey Walton <noloa...@gmail.com> writes: > >> On Mon, May 15, 2017 at 11:27 PM, Junio C Hamano <gits...@pobox.com> wrote: >>> Jeffrey Walton <noloa...@gmail.com> write

Re: How to force a pull to succeed?

On Mon, May 15, 2017 at 11:27 PM, Junio C Hamano <gits...@pobox.com> wrote: > Jeffrey Walton <noloa...@gmail.com> writes: > >> I scp'd a file to another machine for testing. The change tested OK, >> so I checked it in on the original machine. >> ... >> H

How to force a pull to succeed?

I scp'd a file to another machine for testing. The change tested OK, so I checked it in on the original machine. I'm now on the remote machine, and I'm trying to pull the same exact file that exists on both local and remote. Git won't allow me to do it, even with -f. I'd really like -f (or

chmod: changing permissions of `blib/arch/auto/Git': Operation not permitted

This is kind of unusual. I'm seeing it under Debian 7 on a ci20 mipsel dev-board when building/installing Git 2.12.2: ... 317 translated messages. GEN gitk-wish 307 translated messages. SUBDIR perl chmod: changing permissions of `blib/lib': Operation not permitted chmod: changing

Re: Very promising results with libpcre2

> Just to make sure that we are on the same page. While I do not see > the need to link with both variants and allow users to choose > between them at runtime, I do not know if the whole world is ready > to drop pcre1 and use pcre2 (the latter of which has only been > around for a bit over two

Preparing for the Upcoming Removal of UCB Utilities from the Next Version of Solaris

Preparing for the Upcoming Removal of UCB Utilities from the Next Version of Solaris, https://blogs.oracle.com/partnertech/entry/preparing_for_the_upcoming_removal . Sorry to keep beating the Solaris horse. Oracle charges forks for simple updates, like security bug fixes, and updates to cURL and

/bin/bash: /usr/ucb/install: No such file or directory

I think this is the last of the issues for Git 2.12.2 on Solaris 11.3. It looks like 'install' is located in a few places, but not in '/usr/ucb'. I believe /usr/ucb is Solaris 9 or Solaris 10. I think the equivalent place to look on Solaris 11 is /usr/gnu (but I only have limited experience on

Re: Git and PCRE2 vs PCRE?

On Thu, Mar 30, 2017 at 5:23 PM, Junio C Hamano <gits...@pobox.com> wrote: > Jeffrey Walton <noloa...@gmail.com> writes: > >> Is it possible to use PCRE2 with Git? If so, how do I tell Git to use PCRE2? > > Given that pcre2's symbols are all prefixed with

Git and PCRE2 vs PCRE?

Some more 2.12.2 testing on Solaris 11.3 x86_64: ... CC ident.o CC kwset.o CC line-log.o CC levenshtein.o CC line-range.o CC list-objects.o In file included from revision.h:5:0, from line-log.c:10: grep.h:5:18: fatal error: pcre.h: No such file or

Re: git-compat-util.h:735:13: error: conflicting types for 'inet_ntop'

On Thu, Mar 30, 2017 at 4:30 PM, Junio C Hamano <gits...@pobox.com> wrote: > Jeffrey Walton <noloa...@gmail.com> writes: > >> On Wed, Mar 29, 2017 at 1:11 PM, Junio C Hamano <gits...@pobox.com> wrote: >>> Jeffrey Walton <noloa...@gmail.com> writes: >

Re: git-compat-util.h:735:13: error: conflicting types for 'inet_ntop'

On Thu, Mar 30, 2017 at 4:06 PM, Jeffrey Walton <noloa...@gmail.com> wrote: > On Wed, Mar 29, 2017 at 1:11 PM, Junio C Hamano <gits...@pobox.com> wrote: >> Jeffrey Walton <noloa...@gmail.com> writes: >> >>> Some more 2.12.2 testing on Solaris 11.3 x86_64

Re: git-compat-util.h:735:13: error: conflicting types for 'inet_ntop'

On Wed, Mar 29, 2017 at 1:11 PM, Junio C Hamano <gits...@pobox.com> wrote: > Jeffrey Walton <noloa...@gmail.com> writes: > >> Some more 2.12.2 testing on Solaris 11.3 x86_64: >> >> $ make V=1 >> gcc -o credential-store.o -c -MF ./.depend/credential-store

Re: [PATCH v3] perl: regenerate perl.mak if perl -V changes

>>> Now the logic added in commit ee9be06770 ("perl: detect new files in >>> MakeMaker builds", 2012-07-27) is extended to regenerate >>> perl/perl.mak if there's any change to "perl -V". >> >> Nice. This fix is way simpler than I feared. >> >>> This will in some cases redundantly trigger

git-compat-util.h:735:13: error: conflicting types for 'inet_ntop'

Some more 2.12.2 testing on Solaris 11.3 x86_64: $ make V=1 gcc -o credential-store.o -c -MF ./.depend/credential-store.o.d -MQ credential-store.o -MMD -MP -I/usr/local/include -m64 -m64 -I. -D__EXTENSIONS__ -D__sun__ -DUSE_LIBPCRE -I/usr/local/include -DHAVE_ALLOCA_H -I/usr/local/include

Can't locate ExtUtils/MakeMaker.pm in @INC

This looks like the last issue with Git 2.12.2. This time the machine is Fedora 25. I configured with PERL_PATH=/usr/local/bin/perl. The local Perl was built specifically for this error, and it includes ExtUtils/MakeMaker.pm: $ find /usr/local -name MakeMaker.pm

Git fails to build on Ubuntu Server 16.04

I configured with --enable-pthreads, and LIBS included -lpthread. $ make V=1 gcc -I/usr/local/include -g -O2 -I. -DHAVE_ALLOCA_H -I/usr/local/include -DUSE_CURL_FOR_IMAP_SEND -I/usr/local/include -I/usr/local/include -DHAVE_PATHS_H -DHAVE_STRINGS_H -DHAVE_DEV_TTY -DHAVE_CLOCK_GETTIME

Re: Git configure/make does not honor ARFLAGS

On Mon, Sep 14, 2015 at 12:59 AM, Jeff King wrote: > On Sun, Sep 13, 2015 at 09:57:08PM -0700, Junio C Hamano wrote: > >> On Sun, Sep 13, 2015 at 9:30 PM, Jeff King wrote: >> > >> > Ah, OK. Today I learned something. :) >> > >> > Jeffrey, can you produce a tested

Re: Git configure/make does not honor ARFLAGS

On Sun, Sep 13, 2015 at 1:11 PM, Eric Sunshine <sunsh...@sunshineco.com> wrote: > On Sun, Sep 13, 2015 at 6:17 AM, Jeff King <p...@peff.net> wrote: >> On Sun, Aug 30, 2015 at 05:34:59PM -0400, Jeffrey Walton wrote: >>> I'm working on an old OS X machine. I needed to

Git configure/make does not honor ARFLAGS

I'm working on an old OS X machine. I needed to perform: AR=libtool ARFLAGS=-static -o ... make configure ./configure ... make However, it appears the Makefile does not respect ARFLAGS: $ grep -IR '$(AR)' * Makefile:$(QUIET_AR)$(RM) $@ $(AR) rcs $@ $^ Makefile: