View previous topic :: View next topic |
Author |
Message |
col l33t
Joined: 08 May 2002 Posts: 820 Location: Melbourne - Australia
|
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
|
Back to top |
|
|
PraetorZero Apprentice
Joined: 11 Dec 2004 Posts: 239 Location: /home
|
Posted: Wed Apr 11, 2012 4:37 am Post subject: |
|
|
OR, clone their additions to your local overlay and either manually update the ebuilds for the current commit OR use the provided tool to update the ebuilds.
https://github.com/MythTV/packaging/tree/master/Gentoo/scripts _________________ What's the worst that can happen? |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3522
|
Posted: Wed Apr 11, 2012 1:11 pm Post subject: |
|
|
I have the github "overlay" on my systems, and did an "emerge --sync" this morning, to see if the released 0.25 would show up. Obviously it was still at the RC, as mentioned earlier in this thread. Does anyone have any idea when github will make the release standard? As for "OR use the provided tool to update the ebuilds" I would think that that would merely update my local tree, the same as is automatically done as part of "emerge --sync". _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
PraetorZero Apprentice
Joined: 11 Dec 2004 Posts: 239 Location: /home
|
Posted: Wed Apr 11, 2012 3:53 pm Post subject: |
|
|
depontius wrote: | I have the github "overlay" on my systems, and did an "emerge --sync" this morning, to see if the released 0.25 would show up. Obviously it was still at the RC, as mentioned earlier in this thread. Does anyone have any idea when github will make the release standard? As for "OR use the provided tool to update the ebuilds" I would think that that would merely update my local tree, the same as is automatically done as part of "emerge --sync". |
Not true. It compares the most recent hash in your local overlay to what the most recent commit is and creates new rebuilds in your local overlay. You just have to sync against the github overlay once then you can update on your own, independent of whatever is present in the github overlay.
I've been using that script weekly to keep my boxes current against the master branch for a long while now. It sure beats the bash script I had put together. _________________ What's the worst that can happen? |
|
Back to top |
|
|
col l33t
Joined: 08 May 2002 Posts: 820 Location: Melbourne - Australia
|
Posted: Tue Apr 17, 2012 10:51 pm Post subject: |
|
|
how do you use the mythtv-buildebuild tool to get the latest version ?
All I get is this:
./mythtv-buildebuild.py
File "./mythtv-buildebuild.py", line 75
if self.opts.verbose: print 'Updating '+self.package
^
SyntaxError: invalid syntax |
|
Back to top |
|
|
PraetorZero Apprentice
Joined: 11 Dec 2004 Posts: 239 Location: /home
|
Posted: Wed Apr 18, 2012 12:00 am Post subject: |
|
|
There is a bug in the script, but it's an easy work-around. You have to execute the script while you are in your local overlay's root folder.
First, change to your overlay. In my case, it's /usr/local/portage.
Second, run the script from where it is located. Assuming yours is under your homedir, ${HOME}/mythtv-buildebuild.py. I moved it to /usr/local/bin, but it shouldn't matter. _________________ What's the worst that can happen? |
|
Back to top |
|
|
flysideways Guru
Joined: 29 Jan 2005 Posts: 491
|
Posted: Mon Apr 23, 2012 6:43 pm Post subject: |
|
|
Which method are you using to get the stable v0.25? |
|
Back to top |
|
|
flysideways Guru
Joined: 29 Jan 2005 Posts: 491
|
Posted: Wed Apr 25, 2012 4:01 am Post subject: |
|
|
Everything needed to get a Gentoo box with the current v0.25 mythtv is found here.
https://github.com/MythTV/packaging/tree/master/Gentoo
Follow the Gentoo/README instructions to setup your environment.
Once that is done make note of the previously mentioned mythtv-buildebuild.py found in scripts.
If you setup as per the readme, #cd /usr/local/mythtv_portage/Gentoo will get you in the proper directory for updating.
NB, WITH NO OPTIONS IT WILL UPDATE TO 0.26pre. The options are found near the end of the script, it can be easily viewed from the github website.
Now you can run scripts/mythtv-buildebuild.py --version=0.25 --branch=fixes/0.25 and get a functional v0.25 ebuild. emerge how you see fit.
There are various discussions on the web about the inadequacies of this script, as of yesterday and today it worked just fine. The naming of the ebuild is consistent with the date of the last commit used. I used it both with and without the options, building working versions of both v0.25 and v0.26-pre.
Enjoy. |
|
Back to top |
|
|
flysideways Guru
Joined: 29 Jan 2005 Posts: 491
|
Posted: Wed Apr 25, 2012 4:12 am Post subject: |
|
|
I also did a git clone of the stable tree, per http://code.mythtv.org/trac, to a different directory in order to checkout both the master and fixes/v0.25 branches' logs to make sure that the mythtv-buildebuild.py script was behaving as expected. |
|
Back to top |
|
|
col l33t
Joined: 08 May 2002 Posts: 820 Location: Melbourne - Australia
|
Posted: Tue May 01, 2012 10:11 pm Post subject: |
|
|
I still get an error:
scripts/mythtv-buildebuild.py --version=0.25 --branch=fixes/0.25
File "scripts/mythtv-buildebuild.py", line 75
if self.opts.verbose: print 'Updating '+self.package
^
SyntaxError: invalid synonetax
anyone know how to get this working ?
EDIT
finally got it working:
eselect python set python2.7
cd /usr/local/mythtv-portage/Gentoo
scripts/mythtv-buildebuild.py --version=0.25 --branch=fixes/0.25
eselect python set python3.2
media-tv/mythtv [ Masked ]
Latest version available: 0.25_rc20120501 |
|
Back to top |
|
|
fuzzybee Apprentice
Joined: 09 May 2005 Posts: 159
|
Posted: Tue Jun 12, 2012 7:54 pm Post subject: |
|
|
I tried the directions listed, but get this:
Code: | scripts/mythtv-buildebuild.py --version=0.25 --branch=fixes/0.25
Traceback (most recent call last):
File "scripts/mythtv-buildebuild.py", line 312, in <module>
Ebuild(package).update()
File "scripts/mythtv-buildebuild.py", line 79, in update
self.get_cur()
File "scripts/mythtv-buildebuild.py", line 190, in get_cur
commits = json.load(urllib.urlopen("http://github.com/api/v2/json/commits/list/mythtv/MythTV/"+self.branch))
File "/usr/lib64/python2.7/json/__init__.py", line 278, in load
**kw)
File "/usr/lib64/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded |
Any suggestions? |
|
Back to top |
|
|
trilexx Apprentice
Joined: 19 Jul 2004 Posts: 217 Location: Austria
|
Posted: Sat Jun 23, 2012 7:19 pm Post subject: |
|
|
fuzzybee wrote: | I tried the directions listed, but get this:
Code: | scripts/mythtv-buildebuild.py --version=0.25 --branch=fixes/0.25
Traceback (most recent call last):
File "scripts/mythtv-buildebuild.py", line 312, in <module>
Ebuild(package).update()
File "scripts/mythtv-buildebuild.py", line 79, in update
self.get_cur()
File "scripts/mythtv-buildebuild.py", line 190, in get_cur
commits = json.load(urllib.urlopen("http://github.com/api/v2/json/commits/list/mythtv/MythTV/"+self.branch))
File "/usr/lib64/python2.7/json/__init__.py", line 278, in load
**kw)
File "/usr/lib64/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded |
Any suggestions? |
Github removed support for the v2 API. You will have to wait until the script has been updated. See: http://code.mythtv.org/trac/ticket/10792 _________________ if it lives, compile it |
|
Back to top |
|
|
Etal Veteran
Joined: 15 Jul 2005 Posts: 1932
|
Posted: Sat Jun 23, 2012 8:57 pm Post subject: |
|
|
Or try out the new masked highly-experimental official ebuild and report issues
https://bugs.gentoo.org/show_bug.cgi?id=411547#c11 _________________ “And even in authoritarian countries, information networks are helping people discover new facts and making governments more accountable.”– Hillary Clinton, Jan. 21, 2010 |
|
Back to top |
|
|
trilexx Apprentice
Joined: 19 Jul 2004 Posts: 217 Location: Austria
|
Posted: Sun Jun 24, 2012 7:28 am Post subject: |
|
|
Challenge accepted. _________________ if it lives, compile it |
|
Back to top |
|
|
fuzzybee Apprentice
Joined: 09 May 2005 Posts: 159
|
Posted: Fri Jul 13, 2012 2:32 am Post subject: |
|
|
Hmm - I've tried to use the official ebuilds for .25.1-fixes, but portage keeps trying to pull in the .26 tree. I feel dumb for asking this, but how can I direct portage to only download the .25.1 line? |
|
Back to top |
|
|
fuzzybee Apprentice
Joined: 09 May 2005 Posts: 159
|
Posted: Wed Jul 18, 2012 12:55 am Post subject: |
|
|
fuzzybee wrote: | Hmm - I've tried to use the official ebuilds for .25.1-fixes, but portage keeps trying to pull in the .26 tree. I feel dumb for asking this, but how can I direct portage to only download the .25.1 line? |
Anyone? |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
Posted: Wed Jul 18, 2012 1:04 am Post subject: |
|
|
No disrespect ... but in five days you refrained from reading man portage? Here's the spoonfeeding:
Code: |
package.mask
A list of package atoms to mask. Useful if specific versions of packages do
not work well for you. For example, you swear by the Nvidia drivers, but only
versions earlier than 1.0.4496. No problem!
Format:
- comment lines begin with # (no inline comments)
- one DEPEND atom per line
Example:
# mask out versions 1.0.4496 of the nvidia
# drivers and later
>=media-video/nvidia-kernel-1.0.4496
>=media-video/nvidia-glx-1.0.4496
|
_________________ My Gentoo installation notes.
Please learn how to denote units correctly! |
|
Back to top |
|
|
|