git repo version clarificaiton

git repo version clarificaiton

[Daniel Hawthorne]

[-- Attachment #1: Type: text/plain, Size: 185 bytes --]

Hi,
   As stated by the variable "org-version," the git repo version is 7.8.03.
The stable release is 7.8.11. Is the version number for the repo not
meaningful?

Best,
Daniel Hawthorne

[-- Attachment #2: Type: text/html, Size: 242 bytes --]

Re: git repo version clarificaiton

[Nick Dokos]

Daniel Hawthorne <djthorne@stanford.edu> wrote:

>    As stated by the variable "org-version," the git repo version is 7.8.03.
> The stable release is 7.8.11. Is the version number for the repo not
> meaningful?
> 

You probably have an out-of-date org-version.el[c].  You need to ``make
autoloads'' after pulling. That will remake org-version.el and
org-install.el to reflect reality.

Nick

Re: git repo version clarificaiton

[Tassilo Horn]

Nick Dokos <nicholas.dokos@hp.com> writes:

Hi Nick,

>>    As stated by the variable "org-version," the git repo version is
>> 7.8.03.  The stable release is 7.8.11. Is the version number for the
>> repo not meaningful?
>
> You probably have an out-of-date org-version.el[c].  You need to
> ``make autoloads'' after pulling. That will remake org-version.el and
> org-install.el to reflect reality.

I think, it's still wrong.  I can see that in commit
60587ea91cb42ae8618666c7dae5b029f751b913 Basien bumped the defconst
org-version to 7.8.11, but that doesn't exist anymore.  And making clean
and recompiling everything still says

Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ /home/horn/Repos/el/org-mode/lisp/)

instead of 7.8.11.

Bye,
Tassilo

Re: git repo version clarificaiton

[Samuel Wales]

Confirmed.

Jun 28 08:58 ./lisp/org-version.el

Version 7.8.10.

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

Re: git repo version clarificaiton

[Nick Dokos]

Tassilo Horn <tassilo@member.fsf.org> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> Hi Nick,
> 
> >>    As stated by the variable "org-version," the git repo version is
> >> 7.8.03.  The stable release is 7.8.11. Is the version number for the
> >> repo not meaningful?
> >
> > You probably have an out-of-date org-version.el[c].  You need to
> > ``make autoloads'' after pulling. That will remake org-version.el and
> > org-install.el to reflect reality.
> 
> I think, it's still wrong.  I can see that in commit
> 60587ea91cb42ae8618666c7dae5b029f751b913 Basien bumped the defconst
> org-version to 7.8.11, but that doesn't exist anymore.  And making clean
> and recompiling everything still says
> 
> Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ /home/horn/Repos/el/org-mode/lisp/)
> 
> instead of 7.8.11.
> 

Is this master or maint? On maint, I get

release_7.8.10-11-g5968047

On master, I get

release_7.8.11-89-gcf8d979

Nick

Re: git repo version clarificaiton

[Nick Dokos]

Tassilo Horn <tassilo@member.fsf.org> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> Hi Nick,
> 
> >>    As stated by the variable "org-version," the git repo version is
> >> 7.8.03.  The stable release is 7.8.11. Is the version number for the
> >> repo not meaningful?
> >
> > You probably have an out-of-date org-version.el[c].  You need to
> > ``make autoloads'' after pulling. That will remake org-version.el and
> > org-install.el to reflect reality.
> 
> I think, it's still wrong.  I can see that in commit
> 60587ea91cb42ae8618666c7dae5b029f751b913 Basien bumped the defconst
> org-version to 7.8.11, but that doesn't exist anymore.  And making clean
> and recompiling everything still says
> 
> Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ /home/horn/Repos/el/org-mode/lisp/)
> 
> instead of 7.8.11.
> 

Oh, and as Achim pointed out, you probably need to do

  git fetch --tags origin

Nick

Re: git repo version clarificaiton

[Tassilo Horn]

Nick Dokos <nicholas.dokos@hp.com> writes:

Hi Nick,

> Is this master or maint?

master

>> Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @
>> /home/horn/Repos/el/org-mode/lisp/)
>> 
>> instead of 7.8.11.
>
> Oh, and as Achim pointed out, you probably need to do
>
>   git fetch --tags origin

Oh, yes, that does the trick.  So the org version is constructed from
the latest tag in git?

Bye,
Tassilo

Re: git repo version clarificaiton

[Nick Dokos]

Tassilo Horn <tassilo@member.fsf.org> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> Hi Nick,
> 
> > Is this master or maint?
> 
> master
> 
> >> Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @
> >> /home/horn/Repos/el/org-mode/lisp/)
> >> 
> >> instead of 7.8.11.
> >
> > Oh, and as Achim pointed out, you probably need to do
> >
> >   git fetch --tags origin
> 
> Oh, yes, that does the trick.  So the org version is constructed from
> the latest tag in git?
> 

When you ``make autoloads'', it runs ``git describe --abbrev=6 HEAD''
and uses the resulting string to create a new org-version.el file. That
file is then used from that point on. And yes, ``git describe''
calculates the name by counting how many commits past the latest
available tag there are (on the appropriate branch).

Nick

Re: git repo version clarificaiton

[Achim Gratz]

Daniel Hawthorne writes:
>    As stated by the variable "org-version," the git repo version is
> 7.8.03.

Each checkout you make from the repo has it's own version.  Now, if you
are shown version 7.8.03, it can mean several things: you really have
that version checked out (forgot to pull?  on a different branch?) or
you may have a mixed install.

> The stable release is 7.8.11. Is the version number for the
> repo not meaningful?

It is.  The above tells us that something is amiss with your org-mode
from Git.  We just can't tell what exactly since you didn't give enough
information.

git remote update
git fetch --tags
git checkout master
git describe


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html