Mailing List Archive

2010/12/9 E. Westbrook <mythtv-users@westbrook.com>:
> On Wed, Dec 8, 2010 at 20:11, Nick Rout <nick.rout@gmail.com> wrote:
>>
>> > But won't a variable length commit number cause havoc with things like
>> > rpm version comparisons. I guess there's a need to ensure that the
>> > version string components used allow for a previous component that is
>> > always increasing.
>>
>> mythbuntu is now numbering by date yyyymmdd then a hash number, eg:
>>
>> mythtv-common-0.24.0+fixes.20101208.3e9463e-0ubuntu0mythbuntu1
>
> Just as another way:  To keep it numeric, increasing, and consistent, I'm
> currently numbering my Gentoo ebuilds using the unix integer commit
> timestamp of the commit at the point in question, which I can capture when
> checked out to the right HEAD using:
>
> $ echo 0.24.$(git log -n1 --pretty="format:%ct")
> 0.24.1291777173
>
> In reverse, I obtain the commit hash from that point in time on that branch
> with:
>
> $ echo $(git log -n1 --pretty="format:%H" --since=1291777173
> --until=1291777173)
> hash = ee57332927393d071d7b3f1788476f07c77f7e82
>
> which is great for direct checkout or use with github's tarball URL feature.
>
> Git is fun, isn't it!
>
> $0.02,
> EW

If you have a working solution for ebuilds on Gentoo - could you
please share your findings here:
http://bugs.gentoo.org/show_bug.cgi?id=347750
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On Wed, Dec 8, 2010 at 23:09, Glenn Sommer <glemsom@gmail.com> wrote:

> If you have a working solution for ebuilds on Gentoo - could you
> please share your findings here:
> http://bugs.gentoo.org/show_bug.cgi?id=347750
>

It's almost ready. Will do.

Eric

On Wed, Dec 8, 2010 at 7:32 PM, E. Westbrook <mythtv-users@westbrook.com> wrote:
> Just as another way:  To keep it numeric, increasing, and consistent, I'm
> currently numbering my Gentoo ebuilds using the unix integer commit
> timestamp of the commit at the point in question, which I can capture when
> checked out to the right HEAD using:
>
> $ echo 0.24.$(git log -n1 --pretty="format:%ct")
> 0.24.1291777173
>
> In reverse, I obtain the commit hash from that point in time on that branch
> with:
>
> $ echo $(git log -n1 --pretty="format:%H" --since=1291777173
> --until=1291777173)
> hash = ee57332927393d071d7b3f1788476f07c77f7e82

This is a bad plan. The reason for that is, there can be more than on
simultaneous commit at any second on a single branch. It won't happen
often, but it can, and therefore eventually will, happen. Which one
the fancy git log pulls out may or may not be indeterminate. How can
this happen? Easily. Two developers independently commit to their
local trees at that same moment in time.

If you use a methodology like this, first, be very careful at what
timestamps you capture. Do so when there's no concurrent work (which
you may not know in advance if the other branch is not pushed yet).
Secondly, you might as well use human readable dates if you're going
to do that. :)

Just my thoughts.

Now, all you individual gentoo ebuild creators... you are wasting lots
of time (thankfully it's your time) by duplicating efforts. I know of
at *least* 4 different ebuilds being worked on at the same time.
Wouldn't it be wiser to pool your brainpower and time and do it
*once*? Again, your time to waste, but...
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

>>
>> $ echo $(git log -n1 --pretty="format:%H" --since=1291777173
>> --until=1291777173)
>> hash = ee57332927393d071d7b3f1788476f07c77f7e82
>
> This is a bad plan.  The reason for that is, there can be more than on
> simultaneous commit at any second on a single branch.  It won't happen
> often, but it can, and therefore eventually will, happen.  Which one
> the fancy git log pulls out may or may not be indeterminate.  How can
> this happen?  Easily.  Two developers independently commit to their
> local trees at that same moment in time.
>
> If you use a methodology like this, first, be very careful at what
> timestamps you capture.  Do so when there's no concurrent work (which
> you may not know in advance if the other branch is not pushed yet).
> Secondly, you might as well use human readable dates if you're going
> to do that. :)
>
> Just my thoughts.
>
> Now, all you individual gentoo ebuild creators... you are wasting lots
> of time (thankfully it's your time) by duplicating efforts.  I know of
> at *least* 4 different ebuilds being worked on at the same time.
> Wouldn't it be wiser to pool your brainpower and time and do it
> *once*?  Again, your time to waste, but...

yeah they should collaborate via git :)
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 12/07/2010 11:33 AM, Jean-Yves Avenard wrote:
> On 7 December 2010 21:54, Udo van den Heuvel<udovdh@xs4all.nl> wrote:
>> Hello,
>>
>> Where on the wiki is the info as per what date and/or svn the developers
>> switched to git?
>>
>> Where on the wiki is the info so we can check out from git and switch to
>> the right branch/tag/whatever to build 0.24-fixes?
>>
>> Please let us know.
>
> www.mythtv.org
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

More specifically, I think the question should have stated:

at http://www.mythtv.org/download it says:

"If you would like to grab the current development version or just want
to keep up with the latest fixes to the stable branch, you will find git
checkout instructions at https://github.com/MythTV"

However, the "checkout instructions" do not exist on
"https://github.com/MythTV" - at least I cannot see them, furthermore if
you follow every link on that page you will still not find the
instructions because they are not there.

As a user (and not a developer of MythTV), I don't mind what repository
is used as long as I get checkout the latest version and also I don't
think I should be forced to read the Git Guide to the Galaxy either.

I do think it's an unnecessary barrier to not include the following
basic instructions (or similar) at http://www.mythtv.org/download:-

git clone git://github.com/MythTV/myththemes
git clone git://github.com/MythTV/packaging
git clone git://github.com/MythTV/mythtv


Best regards.

Albert.

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 12/14/2010 03:05 PM, agraham wrote:
> More specifically, I think the question should have stated:
>
> at http://www.mythtv.org/download it says:
>
> "If you would like to grab the current development version or just
> want to keep up with the latest fixes to the stable branch, you will
> find git checkout instructions at https://github.com/MythTV"
>
> However, the "checkout instructions" do not exist on
> "https://github.com/MythTV" - at least I cannot see them, furthermore
> if you follow every link on that page you will still not find the
> instructions because they are not there.
>
> As a user (and not a developer of MythTV), I don't mind what
> repository is used as long as I get checkout the latest version and
> also I don't think I should be forced to read the Git Guide to the
> Galaxy either.
>
> I do think it's an unnecessary barrier to not include the following
> basic instructions (or similar) at http://www.mythtv.org/download:-
>
> git clone git://github.com/MythTV/myththemes
> git clone git://github.com/MythTV/packaging
> git clone git://github.com/MythTV/mythtv

See http://code.mythtv.org/trac , which explains how to get the stable
version, so you don't accidentally upgrade to the non-compatible
development version--as you would with the commands above.

Also, there's really no reason to get (and install) myththemes,
now--since the theme downloader will allow you to download just the
theme(s) you want.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On Wed, Dec 15, 2010 at 9:22 AM, Michael T. Dean
<mtdean@thirdcontact.com> wrote:
> Also, there's really no reason to get (and install) myththemes, now--since
> the theme downloader will allow you to download just the theme(s) you want.

Using the theme downloader, how do you know if a theme has been
updated? On mythbuntu repos i just assume that any theme updates are
included in the daily builds.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 12/14/2010 03:49 PM, Nick Rout wrote:
> On Wed, Dec 15, 2010 at 9:22 AM, Michael T. Dean wrote:
>> Also, there's really no reason to get (and install) myththemes, now--since
>> the theme downloader will allow you to download just the theme(s) you want.
> Using the theme downloader, how do you know if a theme has been
> updated? On mythbuntu repos i just assume that any theme updates are
> included in the daily builds.

http://mythtv.org/pipermail/mythtv-theming/2010-December/000475.html

For stable releases, there aren't often changes to the themes, so for
users with 0.24-fixes installed, they would need to just re-download it
"when appropriate." When appropriate, in this context, would mean if
they notice any problems that may be theme related or when they hear the
theme they're using has been updated or before reporting any bugs. :)

Also, unless I'm mistaken, the existing Theme Downloader, itself, will
show you if a newer version of the theme you're using is available (even
in 0.24-fixes). The patch just gives you an "in your face" popup so you
have to notice.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 2010-12-08 20:20, Jarod Wilson wrote:
>> [root@recorder mythweb.git]# pwd
>> /usr/src/mythweb.git
>> [root@recorder mythweb.git]# git describe | cut -d- -f 3
>> fatal: No names found, cannot describe anything.
>> [root@recorder mythweb.git]# git show HEAD | head -1 | awk '{print $2}'
>> 52cb8fb98f1aa209cfd2befa92a9cdd0b7841070
>>
>> How come?
>
> Not sure how you managed that, I've never had it not work. Are
> you running that in a local branch and/or with a detached HEAD?

root@recorder mythtv.git]# cd -
/usr/src/mythweb.git
[root@recorder mythweb.git]# git branch
* 0.24-fixes
master

Just a full checkout where I changed the branch to 0.24-fixes.
Similar as the description I gave a short while back:

# git clone https://github.com/MythTV/mythtv.git mythtv.git
# cd mythtv.git
# git branch -r
origin/HEAD -> origin/master
origin/dkristjansson/mythtv-rec
origin/fixes/0.18
origin/fixes/0.19
origin/fixes/0.20
origin/fixes/0.21
origin/fixes/0.22
origin/fixes/0.23
origin/fixes/0.24
origin/master
origin/mythsystem-rewrite
origin/temp/newaudiosetup
# git checkout -b 0.24-fixes origin/fixes/0.24
# git branch
* 0.24-fixes
master
# git pull
Already up-to-date.
#

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

First off: if you are not using git 1.7.x, you should be.

git --version

Second... do:

git tag

If it's not showing any tags, there's your problem. A simple

git pull --tags

should fix that issue.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 2010-12-27 00:17, Gavin Hurlbut wrote:
> First off: if you are not using git 1.7.x, you should be.
>
> git --version
>
> Second... do:
>
> git tag

[root@recorder mythtv.git]# git version
git version 1.7.2.3
[root@recorder mythtv.git]# git tag
b0.24
v0.10
v0.11
v0.12
v0.13
v0.14
v0.15
(etc)

Good or bad?

Kind regards,
Udo


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 12/27/2010 09:15 AM, Udo van den Heuvel wrote:
> On 2010-12-27 00:17, Gavin Hurlbut wrote:
>> First off: if you are not using git 1.7.x, you should be.
>>
>> git --version
>>
>> Second... do:
>>
>> git tag
> [root@recorder mythtv.git]# git version
> git version 1.7.2.3
> [root@recorder mythtv.git]# git tag
> b0.24
> v0.10
> v0.11
> v0.12
> v0.13
> v0.14
> v0.15
> (etc)
>
> Good or bad?

http://www.gossamer-threads.com/lists/mythtv/users/463947#463947

(from this same thread)

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

On 2010-12-27 21:40, Michael T. Dean wrote:
>> Good or bad?
>
> http://www.gossamer-threads.com/lists/mythtv/users/463947#463947

Thanks.
I solved it, while converting the auto svn checkout spec file, using
%define _git_rev %(cd '%_git_root' ; git log -n1 --pretty="format:%t" )

Kind regards,
Udo
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users