1.4 on git

[Larry Martell]

Last month I set up a system and when I cloned django from git I got
version 1.4. Now I an setting up another system, and when I clone
django from git I get 1.5, and my app is failing. How I can get 1.4? I
see a django-nonrel / django-1.4 but it says "Work in progress 1.4
port, DON'T USE"

[Ramiro Morales]

The github.com/django/django repository is now the official Django
development repository, we migrated from SVN a week ago.

Problem is that we've only migrated the development mainline. We are
working to also migrate the release tags (1.4, 1.3, ...) and the
post-release maintenance branches. The plan is to have it ready in a
couple of days.

The repository that previously was at github.com/django/django is called
now github.com/django/django-old and it has the 1.4 tag. You can clone
from it if you can't wait.

Regards,

--
Ramiro Morales

[Rivsen]

Simply, you can see what git index in your first system, run "git log" and remember the first row of commit( need only remember the first six or eight like this 'commit 42198ad13560c46070223e095f787dff5bd8a918'  ).

Then checkout this commit in your second system, run 'git checkout 42198ad1' and you will get the same code status between two system.

ps. 42198ad1 is a example, not real

Best regards,

Rivsen

2012/5/6 Ramiro Morales <cra...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

[Rivsen]

If you want save this git index in a new branch, you can run 'git checkout -b <branch-name> -f 42198ad1', then you will get a new branch with 42198ad1 index.

Best regards,

Rivsen

2012/5/6 Rivsen <rivse...@gmail.com>

[Larry Martell]

On Sat, May 5, 2012 at 9:30 PM, Rivsen <rivse...@gmail.com> wrote:
> Simply, you can see what git index in your first system, run "git log" and
> remember the first row of commit( need only remember the first six or eight
> like this 'commit 42198ad13560c46070223e095f787dff5bd8a918'  ).
>
> Then checkout this commit in your second system, run 'git checkout 42198ad1'
> and you will get the same code status between two system.
>
> ps. 42198ad1 is a example, not real

On system 1 (the one with 1.4):

# git log
commit 6fbf282ac2b467bd71f807cad45e12a86aa371bd
Author: claudep <claudep@bcc190cf-cafb-0310-a4f2-bffc1f526a37>
Date: Fri Mar 23 19:44:52 2012 +0000

On system 2 (which has 1.5 installed):

# git checkout 6fbf282
error: pathspec '6fbf282' did not match any file(s) known to git

Also tried it with the entire commit string:

# git checkout 6fbf282ac2b467bd71f807cad45e12a86aa371bd
fatal: reference is not a tree: 6fbf282ac2b467bd71f807cad45e12a86aa371bd

[Larry Martell]

i cloned from django-old, and I get 1.5 alpha (which does not work for me):

>>> django.VERSION
(1, 5, 0, 'alpha', 0)

My working system has:

>>> django.VERSION
(1, 4, 0, 'final', 0)

[Ramiro Morales]

You will need to read the Git documentation because we are in Git territory now.

)ou got the latest development code by default but remember that when
you clone you get (most of) the development history and it is
available locally.

You need to get a checkout of the commit pointed to by the '1.4' tag.
IIRC you can achieve that with::

git checkout 1.4

> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

--

Sent from my mobile device

Ramiro Morales

[Larry Martell]

On Sun, May 6, 2012 at 12:54 PM, Ramiro Morales <cra...@gmail.com> wrote:
> You will need to read the Git documentation because we are in Git territory now.
>
> )ou got the latest development code by default but remember that when
> you clone you get (most of) the development history and it is
> available locally.
>
> You need to get a checkout of the commit pointed to by the '1.4' tag.
> IIRC you can achieve that with::
>
>  git checkout 1.4

Ok, Thanks. I'll try that next time. I ended up just scp-ing the
django dir from my working system.

[Rivsen]

Hi Larry, 

I cloned django and django-old from github, and I found the git index of yours.

It's in django-old repo, not in django.

So you need clone django-old not django.

git clone git://github.com/django/django-old.git

cd django-old

git checkout -b test -f 6fbf282ac2

git log

commit 6fbf282ac2b467bd71f807cad45e12a86aa371bd

Author: claudep <claudep@bcc190cf-cafb-0310-a4f2-bffc1f526a37>

Date:   Fri Mar 23 19:44:52 2012 +0000

Now, The 'test' branch is the same to your system 1.

Best regards,

Rivsen

2012/5/7 Larry Martell <larry....@gmail.com>

[Andre Terra]

add "django==1.4" to a requirements.txt file (no quotes!)

$ pip install -R requirements.txt