Receiving a message after upgrade?

[PNWDrew]

I've been seeing a message about a changes in git after I upgrade recently.  I've tried to figure out what it is telling me but it is way over my head.  I'm not seeing a problem anywhere; I just wanted to understand what I am seeing and what if any action I should take.

Thanks,
Drew

Code Select Expand

 
git (1:1.8.4~rc0-1) experimental; urgency=low

  Starting with this version, gitweb and "git daemon" on Debian are
  configured to look for repositories under /var/lib/git by default
  instead of /var/cache/git.  You may want to adjust your inetd,
  rsyncd, and web server configuration to use the new base path.

  See /usr/share/doc/git/README.Debian for details.

  Symlinks are installed during the upgrade to ensure existing
  repositories remain accessible.  If no local scripts or
  configuration depend on /var/cache/git then it is safe to remove
  the old directory after replacing these symlinks with their
  targets:

    mv --backup /var/cache/git/* /var/lib/git/
    rmdir /var/cache/git
    rm /var/lib/git/*~

-- Jonathan Nieder <jrnieder@gmail.com>  Sun, 28 Jul 2013 17:46:05 -0700

git (1:1.8.2~rc0-1) experimental; urgency=low

The default behavior of "git push" when run without specifying any
  ref names will change in the upcoming Git 2.0 release.

  The previous default behavior was to use "matching" semantics: push
  all branches for which there is already a branch of the same name on
  the remote end.  The new default is "simple" semantics: push the
  current branch to a branch of the same name, provided that "git
  pull" is configured to integrate with that branch.  You can get a
  glimpse of the future with

        echo '[push] default = simple' >>~/.gitconfig

  See Documentation/RelNotes/1.8.2.txt and the entry on push.default
  in git-config(1) for details.

-- Jonathan Nieder <jrnieder@gmail.com>  Mon, 18 Feb 2013 16:48:53 -0800

git (1:1.8.0-1) experimental; urgency=low

Git's bash completion script is now loaded on the fly when tab
  completion is attempted for the 'git' or 'gitk' command.  This
  change involved moving the completion script.  If your ~/.bashrc
  previously contained

    . /etc/bash_completion.d/git

  then it should be corrected to

    if [ -e /usr/share/bash-completion/completions/git ]; then
      . /usr/share/bash-completion/completions/git
    elif [ -e /etc/bash_completion.d/git ]; then
      . /etc/bash_completion.d/git
    fi

  or, better,

    . /etc/bash_completion

  See /usr/share/doc/bash-completion/README.Debian for details.

-- Jonathan Nieder <jrnieder@gmail.com>  Sun, 13 Jan 2013 08:59:42 -0800


[MoroS]

Ignore it, if you're not using Git. By default this package shouldn't be installed. Git and Subversion packages are used by us to synchronize Sparky's code with a remote repository on SourceForge. I guess we forgot to clean it up. :P

[pavroo]

No, we haven't.
Git is not preinstalled in Sparky.

[MoroS]

No, we haven't.
Git is not preinstalled in Sparky.

Subversion is present, so I thought that it's the same with Git. Then I wonder where did it come from... :P

[PNWDrew]

So this is meant to alert you guys to changes if you were using git? The change in push behavior makes some sense to me, the rest is beyond my current knowledge.  Time to start googling I guess. 

Let me know if I can do anything to provide any further info.  It doesn't seem to affect me so no worries here.

Sparky has been great for me, so thanks for your work. I'm a Linux convert now!

Drew

[MoroS]

No, that's a standard package upgrade message, that needs users attention. Sooner or later you'll get another for a different package. The git push behaviour change was announced a few months back, but Debian sometimes has late package updates and I guess that now the version that forces the use of simple pushing is getting prepared.

[PNWDrew]

No, that's a standard package upgrade message, that needs users attention. Sooner or later you'll get another for a different package. The git push behaviour change was announced a few months back, but Debian sometimes has late package updates and I guess that now the version that forces the use of simple pushing is getting prepared.

Thanks for your help on this and other questions I've had. I guess all I really need to know at this moment is if there is action that I need to take?

I've been reading the Debian FAQ to try to learn something but I think I will need to back up to a more basic level as I frequently am just reading it with no comprehension.  There are lots of online learning options. Any advice on a good beginner (as in I know nothing) knowledge source? 

Drew

[MoroS]

I guess all I really need to know at this moment is if there is action that I need to take?

If you're doing some code development and using Git as a repository, then yes. If not, then just ignore it. :)

[PNWDrew]

Great... now you've forced me to satisfy my curiousity ;).  So I found I didn't know what I thought I knew about git, and reading about git also clarified a few of the terms I hear around Android ROM development.   

Thanks!