Discussion:
[rancid] Rancid 3.1.99 Alpha git integration issues.
Thomas Greer
2015-02-07 13:31:54 UTC
Permalink
Hi All

I’ve recently (read today) installed the above alpha in anticipation of the git support. I’ve setup rancid a few times before, but I’m struggling with the git stuff.

When I run rancid-cvs after a fresh install, I get a load of errors.

-bash-4.1$ ./bin/rancid-cvs
error: Malformed value for push.default: simple
error: Must be one of nothing, matching, tracking or current.
fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
error: Malformed value for push.default: simple
error: Must be one of nothing, matching, tracking or current.
fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
error: Malformed value for push.default: simple
error: Must be one of nothing, matching, tracking or current.
fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
error: Malformed value for push.default: simple
error: Must be one of nothing, matching, tracking or current.
fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
error: Malformed value for push.default: simple
error: Must be one of nothing, matching, tracking or current.
fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
error: Malformed value for push.default: simple
error: Must be one of nothing, matching, tracking or current.
fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git

My rancid.conf contains:

# Select which RCS system to use, "cvs" (default), "svn" or "git". Do not
# change this after CVSROOT has been created with rancid-cvs. Changing between
# these requires manual conversions.
RCSSYS=git; export RCSSYS

The README and UPGRADING mention nothing specific to initialising git other than to run rancid-cvs.

Running on Centos 6.6
git version 1.7.1

Any help would be appreciated with this.

Thanks

Thomas
heasley
2015-02-08 04:22:57 UTC
Permalink
Sat, Feb 07, 2015 at 01:31:54PM +0000, Thomas Greer:
> Hi All
>
> I’ve recently (read today) installed the above alpha in anticipation of the git support. I’ve setup rancid a few times before, but I’m struggling with the git stuff.
>
> When I run rancid-cvs after a fresh install, I get a load of errors.
>
> -bash-4.1$ ./bin/rancid-cvs
> error: Malformed value for push.default: simple
> error: Must be one of nothing, matching, tracking or current.
> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
> error: Malformed value for push.default: simple
> error: Must be one of nothing, matching, tracking or current.
> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig

entirely possible that i've screwed-up the git support; i'll have to re-test
it. but, this error is odd. rancid-cvs doesnt create .gitconfig itself.
so, what is the source of that file and thus this error?

> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> error: Malformed value for push.default: simple
> error: Must be one of nothing, matching, tracking or current.
> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
> error: Malformed value for push.default: simple
> error: Must be one of nothing, matching, tracking or current.
> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> error: Malformed value for push.default: simple
> error: Must be one of nothing, matching, tracking or current.
> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
> error: Malformed value for push.default: simple
> error: Must be one of nothing, matching, tracking or current.
> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
>
> My rancid.conf contains:
>
> # Select which RCS system to use, "cvs" (default), "svn" or "git". Do not
> # change this after CVSROOT has been created with rancid-cvs. Changing between
> # these requires manual conversions.
> RCSSYS=git; export RCSSYS
>
> The README and UPGRADING mention nothing specific to initialising git other than to run rancid-cvs.
>
> Running on Centos 6.6
> git version 1.7.1
>
> Any help would be appreciated with this.
>
> Thanks
>
> Thomas



> _______________________________________________
> Rancid-discuss mailing list
> Rancid-***@shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
Thomas Greer
2015-02-08 07:37:22 UTC
Permalink
> On 8 Feb 2015, at 06:22, heasley <***@shrubbery.net> wrote:
>
> Sat, Feb 07, 2015 at 01:31:54PM +0000, Thomas Greer:
>> Hi All
>>
>> I’ve recently (read today) installed the above alpha in anticipation of the git support. I’ve setup rancid a few times before, but I’m struggling with the git stuff.
>>
>> When I run rancid-cvs after a fresh install, I get a load of errors.
>>
>> -bash-4.1$ ./bin/rancid-cvs
>> error: Malformed value for push.default: simple
>> error: Must be one of nothing, matching, tracking or current.
>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>> error: Malformed value for push.default: simple
>> error: Must be one of nothing, matching, tracking or current.
>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>
> entirely possible that i've screwed-up the git support; i'll have to re-test
> it. but, this error is odd. rancid-cvs doesnt create .gitconfig itself.
> so, what is the source of that file and thus this error?
>
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> error: Malformed value for push.default: simple
>> error: Must be one of nothing, matching, tracking or current.
>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>> error: Malformed value for push.default: simple
>> error: Must be one of nothing, matching, tracking or current.
>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> error: Malformed value for push.default: simple
>> error: Must be one of nothing, matching, tracking or current.
>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>> error: Malformed value for push.default: simple
>> error: Must be one of nothing, matching, tracking or current.
>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>> fatal: Not a git repository (or any of the parent directories): .git
>>
>> My rancid.conf contains:
>>
>> # Select which RCS system to use, "cvs" (default), "svn" or "git". Do not
>> # change this after CVSROOT has been created with rancid-cvs. Changing between
>> # these requires manual conversions.
>> RCSSYS=git; export RCSSYS
>>
>> The README and UPGRADING mention nothing specific to initialising git other than to run rancid-cvs.
>>
>> Running on Centos 6.6
>> git version 1.7.1
>>
>> Any help would be appreciated with this.
>>
>> Thanks
>>
>> Thomas
>
>
>
>> _______________________________________________
>> Rancid-discuss mailing list
>> Rancid-***@shrubbery.net
>> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>


Either make install, or rancid-cvs. I rm’d the /usr/local/rancid directory before running make install
Thomas Greer
2015-02-18 13:01:25 UTC
Permalink
> On 8 Feb 2015, at 07:37, Thomas Greer <***@tsone.net.uk> wrote:
>
>> On 8 Feb 2015, at 06:22, heasley <***@shrubbery.net> wrote:
>>
>> Sat, Feb 07, 2015 at 01:31:54PM +0000, Thomas Greer:
>>> Hi All
>>>
>>> I’ve recently (read today) installed the above alpha in anticipation of the git support. I’ve setup rancid a few times before, but I’m struggling with the git stuff.
>>>
>>> When I run rancid-cvs after a fresh install, I get a load of errors.
>>>
>>> -bash-4.1$ ./bin/rancid-cvs
>>> error: Malformed value for push.default: simple
>>> error: Must be one of nothing, matching, tracking or current.
>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>> error: Malformed value for push.default: simple
>>> error: Must be one of nothing, matching, tracking or current.
>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>
>> entirely possible that i've screwed-up the git support; i'll have to re-test
>> it. but, this error is odd. rancid-cvs doesnt create .gitconfig itself.
>> so, what is the source of that file and thus this error?
>>
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> error: Malformed value for push.default: simple
>>> error: Must be one of nothing, matching, tracking or current.
>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>> error: Malformed value for push.default: simple
>>> error: Must be one of nothing, matching, tracking or current.
>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> error: Malformed value for push.default: simple
>>> error: Must be one of nothing, matching, tracking or current.
>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>> error: Malformed value for push.default: simple
>>> error: Must be one of nothing, matching, tracking or current.
>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>> fatal: Not a git repository (or any of the parent directories): .git
>>>
>>> My rancid.conf contains:
>>>
>>> # Select which RCS system to use, "cvs" (default), "svn" or "git". Do not
>>> # change this after CVSROOT has been created with rancid-cvs. Changing between
>>> # these requires manual conversions.
>>> RCSSYS=git; export RCSSYS
>>>
>>> The README and UPGRADING mention nothing specific to initialising git other than to run rancid-cvs.
>>>
>>> Running on Centos 6.6
>>> git version 1.7.1
>>>
>>> Any help would be appreciated with this.
>>>
>>> Thanks
>>>
>>> Thomas
>>
>>
>>
>>> _______________________________________________
>>> Rancid-discuss mailing list
>>> Rancid-***@shrubbery.net
>>> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>>
>
>
> Either make install, or rancid-cvs. I rm’d the /usr/local/rancid directory before running make install
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-***@shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss

Any further info or progress on this? :)
heasley
2015-03-11 21:42:04 UTC
Permalink
Wed, Feb 18, 2015 at 01:01:25PM +0000, Thomas Greer:
> >>> I’ve recently (read today) installed the above alpha in anticipation of the git support. I’ve setup rancid a few times before, but I’m struggling with the git stuff.
> >>>
> >>> When I run rancid-cvs after a fresh install, I get a load of errors.
> >>>
> >>> -bash-4.1$ ./bin/rancid-cvs
> >>> error: Malformed value for push.default: simple
> >>> error: Must be one of nothing, matching, tracking or current.
> >>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
> >>> error: Malformed value for push.default: simple
> >>> error: Must be one of nothing, matching, tracking or current.
> >>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
> >>
> >> entirely possible that i've screwed-up the git support; i'll have to re-test
> >> it. but, this error is odd. rancid-cvs doesnt create .gitconfig itself.
> >> so, what is the source of that file and thus this error?
> >>
> >>> fatal: Not a git repository (or any of the parent directories): .git

...

> >>> fatal: Not a git repository (or any of the parent directories): .git
> >>>
> >>> My rancid.conf contains:
> >>>
> >>> # Select which RCS system to use, "cvs" (default), "svn" or "git". Do not
> >>> # change this after CVSROOT has been created with rancid-cvs. Changing between
> >>> # these requires manual conversions.
> >>> RCSSYS=git; export RCSSYS
> >>>
> >>> The README and UPGRADING mention nothing specific to initialising git other than to run rancid-cvs.
> >>>
> >>> Running on Centos 6.6
> >>> git version 1.7.1

I'm not certain why this error occurs; it occurs with git 1.7, but not git
2.3. Is it reasonable to just upgrade your installation of git?
Thomas Greer
2015-03-11 21:45:16 UTC
Permalink
That's the highest available is centos standard. I can have a look and see



> On 11 Mar 2015, at 21:42, heasley <***@shrubbery.net> wrote:
>
> Wed, Feb 18, 2015 at 01:01:25PM +0000, Thomas Greer:
>>>>> I’ve recently (read today) installed the above alpha in anticipation of the git support. I’ve setup rancid a few times before, but I’m struggling with the git stuff.
>>>>>
>>>>> When I run rancid-cvs after a fresh install, I get a load of errors.
>>>>>
>>>>> -bash-4.1$ ./bin/rancid-cvs
>>>>> error: Malformed value for push.default: simple
>>>>> error: Must be one of nothing, matching, tracking or current.
>>>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>>>> error: Malformed value for push.default: simple
>>>>> error: Must be one of nothing, matching, tracking or current.
>>>>> fatal: bad config file line 6 in /usr/local/rancid//.gitconfig
>>>>
>>>> entirely possible that i've screwed-up the git support; i'll have to re-test
>>>> it. but, this error is odd. rancid-cvs doesnt create .gitconfig itself.
>>>> so, what is the source of that file and thus this error?
>>>>
>>>>> fatal: Not a git repository (or any of the parent directories): .git
>
> ...
>
>>>>> fatal: Not a git repository (or any of the parent directories): .git
>>>>>
>>>>> My rancid.conf contains:
>>>>>
>>>>> # Select which RCS system to use, "cvs" (default), "svn" or "git". Do not
>>>>> # change this after CVSROOT has been created with rancid-cvs. Changing between
>>>>> # these requires manual conversions.
>>>>> RCSSYS=git; export RCSSYS
>>>>>
>>>>> The README and UPGRADING mention nothing specific to initialising git other than to run rancid-cvs.
>>>>>
>>>>> Running on Centos 6.6
>>>>> git version 1.7.1
>
> I'm not certain why this error occurs; it occurs with git 1.7, but not git
> 2.3. Is it reasonable to just upgrade your installation of git?
Per Carlson
2015-03-11 22:30:54 UTC
Permalink
Hi.

On 11 March 2015 at 22:42, heasley <***@shrubbery.net> wrote:

>
> I'm not certain why this error occurs; it occurs with git 1.7, but not git
> 2.3.
>

​The default push mode did change in git 2.0.0 (
https://github.com/git/git/blob/master/Documentation/RelNotes/2.0.0.txt#L7-L23).
Before 2.0.0 it was "matching" but from 2.0.0 it's "simple". The error
occurs when using a git version less than 1.7.11 (when "simple" where
introduced, see
https://github.com/git/git/blob/master/Documentation/RelNotes/1.7.11.txt#L9-L14).
​

To fix that a compatible mode must be used, like "current" (or "matching").
This can be set by running "git config push.default <mode>" or manually
editing the repository git config file (please don't set this globally).

For more information of the available modes (and what they do), search for
"push.default" in http://git-scm.com/docs/git-config.

--
Pelle

Research is what I'm doing when I don't know what I'm doing.
- Wernher von Braun
Thomas Greer
2015-03-12 11:09:00 UTC
Permalink
?I tried changing the line in rancid-cvs to say matching instead of simple... still many errors, suspect it's not just a simple swap out a keyword fix.

________________________________
From: Per Carlson <***@hemmop.com>
Sent: 11 March 2015 22:30
To: heasley
Cc: Thomas Greer; rancid-***@shrubbery.net
Subject: Re: [rancid] Rancid 3.1.99 Alpha git integration issues.

Hi.

On 11 March 2015 at 22:42, heasley <***@shrubbery.net<mailto:***@shrubbery.net>> wrote:

I'm not certain why this error occurs; it occurs with git 1.7, but not git
2.3.

?The default push mode did change in git 2.0.0 (https://github.com/git/git/blob/master/Documentation/RelNotes/2.0.0.txt#L7-L23). Before 2.0.0 it was "matching" but from 2.0.0 it's "simple". The error occurs when using a git version less than 1.7.11 (when "simple" where introduced, see https://github.com/git/git/blob/master/Documentation/RelNotes/1.7.11.txt#L9-L14).?

To fix that a compatible mode must be used, like "current" (or "matching"). This can be set by running "git config push.default <mode>" or manually editing the repository git config file (please don't set this globally).

For more information of the available modes (and what they do), search for "push.default" in http://git-scm.com/docs/git-config.

--
Pelle

Research is what I'm doing when I don't know what I'm doing.
- Wernher von Braun
heasley
2015-03-12 18:23:07 UTC
Permalink
Thu, Mar 12, 2015 at 11:09:00AM +0000, Thomas Greer:
> ?I tried changing the line in rancid-cvs to say matching instead of simple... still many errors, suspect it's not just a simple swap out a keyword fix.

It does work for me; git 1.7.10.4. make sure that you start with a clean
slate, including ~/.gitconfig.

Thanks Per Carlson.

> ________________________________
> From: Per Carlson <***@hemmop.com>
> Sent: 11 March 2015 22:30
> To: heasley
> Cc: Thomas Greer; rancid-***@shrubbery.net
> Subject: Re: [rancid] Rancid 3.1.99 Alpha git integration issues.
>
> Hi.
>
> On 11 March 2015 at 22:42, heasley <***@shrubbery.net<mailto:***@shrubbery.net>> wrote:
>
> I'm not certain why this error occurs; it occurs with git 1.7, but not git
> 2.3.
>
> ?The default push mode did change in git 2.0.0 (https://github.com/git/git/blob/master/Documentation/RelNotes/2.0.0.txt#L7-L23). Before 2.0.0 it was "matching" but from 2.0.0 it's "simple". The error occurs when using a git version less than 1.7.11 (when "simple" where introduced, see https://github.com/git/git/blob/master/Documentation/RelNotes/1.7.11.txt#L9-L14).?
>
> To fix that a compatible mode must be used, like "current" (or "matching"). This can be set by running "git config push.default <mode>" or manually editing the repository git config file (please don't set this globally).
>
> For more information of the available modes (and what they do), search for "push.default" in http://git-scm.com/docs/git-config.
>
> --
> Pelle
>
> Research is what I'm doing when I don't know what I'm doing.
> - Wernher von Braun
Thomas Greer
2015-03-12 18:42:59 UTC
Permalink
Is the following output expected then?

./bin/rancid-cvs
Initialized empty Git repository in /usr/local/rancid/var/CVS/lon/
Initialized empty Git repository in /usr/local/rancid/var/lon/.git/
warning: You appear to have cloned an empty repository.
[master (root-commit) 523f48d] new
1 files changed, 2 insertions(+), 0 deletions(-)
create mode 100644 configs/.gitignore
No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to '/usr/local/rancid/var/CVS/lon'
[master 2638f0b] new
0 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 router.db
No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to '/usr/local/rancid/var/CVS/lon'
Initialized empty Git repository in /usr/local/rancid/var/CVS/gs1/
Initialized empty Git repository in /usr/local/rancid/var/gs1/.git/
warning: You appear to have cloned an empty repository.
[master (root-commit) 523f48d] new
1 files changed, 2 insertions(+), 0 deletions(-)
create mode 100644 configs/.gitignore
No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to '/usr/local/rancid/var/CVS/gs1'
[master 2638f0b] new
0 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 router.db
No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to '/usr/local/rancid/var/CVS/gs1'
Initialized empty Git repository in /usr/local/rancid/var/CVS/tal/
Initialized empty Git repository in /usr/local/rancid/var/tal/.git/
warning: You appear to have cloned an empty repository.
[master (root-commit) 523f48d] new
1 files changed, 2 insertions(+), 0 deletions(-)
create mode 100644 configs/.gitignore
No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to '/usr/local/rancid/var/CVS/tal'
[master 2638f0b] new
0 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 router.db
No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to '/usr/local/rancid/var/CVS/tal'

> On 12 Mar 2015, at 18:23, heasley <***@shrubbery.net> wrote:
>
> Thu, Mar 12, 2015 at 11:09:00AM +0000, Thomas Greer:
>> ?I tried changing the line in rancid-cvs to say matching instead of simple... still many errors, suspect it's not just a simple swap out a keyword fix.
>
> It does work for me; git 1.7.10.4. make sure that you start with a clean
> slate, including ~/.gitconfig.
>
> Thanks Per Carlson.
>
>> ________________________________
>> From: Per Carlson <***@hemmop.com>
>> Sent: 11 March 2015 22:30
>> To: heasley
>> Cc: Thomas Greer; rancid-***@shrubbery.net
>> Subject: Re: [rancid] Rancid 3.1.99 Alpha git integration issues.
>>
>> Hi.
>>
>> On 11 March 2015 at 22:42, heasley <***@shrubbery.net<mailto:***@shrubbery.net>> wrote:
>>
>> I'm not certain why this error occurs; it occurs with git 1.7, but not git
>> 2.3.
>>
>> ?The default push mode did change in git 2.0.0 (https://github.com/git/git/blob/master/Documentation/RelNotes/2.0.0.txt#L7-L23). Before 2.0.0 it was "matching" but from 2.0.0 it's "simple". The error occurs when using a git version less than 1.7.11 (when "simple" where introduced, see https://github.com/git/git/blob/master/Documentation/RelNotes/1.7.11.txt#L9-L14).?
>>
>> To fix that a compatible mode must be used, like "current" (or "matching"). This can be set by running "git config push.default <mode>" or manually editing the repository git config file (please don't set this globally).
>>
>> For more information of the available modes (and what they do), search for "push.default" in http://git-scm.com/docs/git-config.
>>
>> --
>> Pelle
>>
>> Research is what I'm doing when I don't know what I'm doing.
>> - Wernher von Braun
heasley
2015-03-12 21:57:57 UTC
Permalink
Thu, Mar 12, 2015 at 06:42:59PM +0000, Thomas Greer:
> Is the following output expected then?

no; i receive no such errors. if you started with a totally clean env,
there is a variance between even 1.7.1 and 1.7.11.4. i'm not a git user;
you apparently are, so whats wrong with this:

git init --bare $CVSROOT/$GROUP
git clone $CVSROOT/$GROUP .
git config --global user.name RANCiD
git config --global user.email $USER$MAILDOMAIN
git config --global push.default current

its clones it fine, commits fine, why wouldnt it push w/o specifying a
branch? i dont want to specify a branch; i expect a user may clone sth.
specific and pushes should just go to that branch - which is what
"current" seems like its intended to do and seems to work in the previously
mentioned versions.

can't you just install sth. more recent and move on? 1.7.1 doesnt even
appear to be available anymore. even the debian pkg is more than 2 years
old.
Thomas Greer
2015-03-12 21:59:58 UTC
Permalink
If I fancy compiling git from scratch, sure, but that’s the latest debian has. Let me try again.

> On 12 Mar 2015, at 21:57, heasley <***@shrubbery.net> wrote:
>
> Thu, Mar 12, 2015 at 06:42:59PM +0000, Thomas Greer:
>> Is the following output expected then?
>
> no; i receive no such errors. if you started with a totally clean env,
> there is a variance between even 1.7.1 and 1.7.11.4. i'm not a git user;
> you apparently are, so whats wrong with this:
>
> git init --bare $CVSROOT/$GROUP
> git clone $CVSROOT/$GROUP .
> git config --global user.name RANCiD
> git config --global user.email $USER$MAILDOMAIN
> git config --global push.default current
>
> its clones it fine, commits fine, why wouldnt it push w/o specifying a
> branch? i dont want to specify a branch; i expect a user may clone sth.
> specific and pushes should just go to that branch - which is what
> "current" seems like its intended to do and seems to work in the previously
> mentioned versions.
>
> can't you just install sth. more recent and move on? 1.7.1 doesnt even
> appear to be available anymore. even the debian pkg is more than 2 years
> old.
heasley
2015-03-12 22:18:09 UTC
Permalink
Thu, Mar 12, 2015 at 09:59:58PM +0000, Thomas Greer:
> If I fancy compiling git from scratch, sure, but that’s the latest debian has. Let me try again.

the process seems layed-out here:
http://tecadmin.net/install-git-2-0-on-centos-rhel-fedora/

maybe one of these other rpm repos has a newer git?
http://wiki.centos.org/AdditionalResources/Repositories?action=show&redirect=Repositories

> > On 12 Mar 2015, at 21:57, heasley <***@shrubbery.net> wrote:
> >
> > Thu, Mar 12, 2015 at 06:42:59PM +0000, Thomas Greer:
> >> Is the following output expected then?
> >
> > no; i receive no such errors. if you started with a totally clean env,
> > there is a variance between even 1.7.1 and 1.7.11.4. i'm not a git user;
> > you apparently are, so whats wrong with this:
> >
> > git init --bare $CVSROOT/$GROUP
> > git clone $CVSROOT/$GROUP .
> > git config --global user.name RANCiD
> > git config --global user.email $USER$MAILDOMAIN
> > git config --global push.default current
> >
> > its clones it fine, commits fine, why wouldnt it push w/o specifying a
> > branch? i dont want to specify a branch; i expect a user may clone sth.
> > specific and pushes should just go to that branch - which is what

or what command provides the branch name of the clone, which can then be
passed to push?

> > "current" seems like its intended to do and seems to work in the previously
> > mentioned versions.
> >
> > can't you just install sth. more recent and move on? 1.7.1 doesnt even
> > appear to be available anymore. even the debian pkg is more than 2 years
> > old.
>
Thomas Greer
2015-03-12 22:03:38 UTC
Permalink
It appears, that i has matching, which doesn’t play ball, however, current works fine.

I’ll soldier on.

Many thanks

Thomas

> On 12 Mar 2015, at 21:59, Thomas Greer <***@tsone.net.uk> wrote:
>
> If I fancy compiling git from scratch, sure, but that’s the latest debian has. Let me try again.
>
>> On 12 Mar 2015, at 21:57, heasley <***@shrubbery.net> wrote:
>>
>> Thu, Mar 12, 2015 at 06:42:59PM +0000, Thomas Greer:
>>> Is the following output expected then?
>>
>> no; i receive no such errors. if you started with a totally clean env,
>> there is a variance between even 1.7.1 and 1.7.11.4. i'm not a git user;
>> you apparently are, so whats wrong with this:
>>
>> git init --bare $CVSROOT/$GROUP
>> git clone $CVSROOT/$GROUP .
>> git config --global user.name RANCiD
>> git config --global user.email $USER$MAILDOMAIN
>> git config --global push.default current
>>
>> its clones it fine, commits fine, why wouldnt it push w/o specifying a
>> branch? i dont want to specify a branch; i expect a user may clone sth.
>> specific and pushes should just go to that branch - which is what
>> "current" seems like its intended to do and seems to work in the previously
>> mentioned versions.
>>
>> can't you just install sth. more recent and move on? 1.7.1 doesnt even
>> appear to be available anymore. even the debian pkg is more than 2 years
>> old.
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-***@shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
Loading...