View previous topic :: View next topic |
Author |
Message |
BonesToo Apprentice
Joined: 19 Aug 2003 Posts: 153
|
Posted: Thu Feb 28, 2013 9:45 pm Post subject: mythtv / mythplugins 0.25.3 version mismatch |
|
|
Just noticed MythTV went to 0.25.3_p20130131 but mythplugins did not get bumped and since mythplugins depends on the exact version number you can't upgrade to this new 31st version.
Is there a better place to report ebuild issues?
PS - I know I can fix this myself in a local overlay, just wanted to report back to community. |
|
Back to top |
|
|
eyoung100 Veteran
Joined: 23 Jan 2004 Posts: 1428
|
|
Back to top |
|
|
BonesToo Apprentice
Joined: 19 Aug 2003 Posts: 153
|
Posted: Thu Feb 28, 2013 11:44 pm Post subject: |
|
|
No, its not. I was confused at first too. One ends 01, and the new one ends 31.
0.25.3_p20130101 vs 0.25.3_p20130131 |
|
Back to top |
|
|
eyoung100 Veteran
Joined: 23 Jan 2004 Posts: 1428
|
Posted: Thu Feb 28, 2013 11:47 pm Post subject: |
|
|
BonesToo wrote: | No, its not. I was confused at first too. One ends 01, and the new one ends 31.
0.25.3_p20130101 vs 0.25.3_p20130131 |
I apologize, looks like we both misread, would you like to file a bug or would you like me to? _________________ The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper |
|
Back to top |
|
|
BonesToo Apprentice
Joined: 19 Aug 2003 Posts: 153
|
Posted: Thu Feb 28, 2013 11:48 pm Post subject: |
|
|
Go for it, if you don't mind. I'm moving on to 0.26 now |
|
Back to top |
|
|
eyoung100 Veteran
Joined: 23 Jan 2004 Posts: 1428
|
|
Back to top |
|
|
BonesToo Apprentice
Joined: 19 Aug 2003 Posts: 153
|
Posted: Fri Mar 01, 2013 5:31 pm Post subject: |
|
|
awesome |
|
Back to top |
|
|
gkmac Guru
Joined: 19 Jan 2003 Posts: 333 Location: West Sussex, UK
|
Posted: Tue Mar 05, 2013 8:02 pm Post subject: |
|
|
For me it's essential that this gets fixed for version 0.25.3_p20130131. Some would say "give v0.26" a try, except with that version its impossible to make DVDs of recordings thanks to this bug. _________________ If ~amd64 ebuilds are cutting edge, then git-9999 ebuilds are chainsaws.
"Not everyone can ride a unicycle, does that mean we should put another wheel on it?" - Lokheed |
|
Back to top |
|
|
BonesToo Apprentice
Joined: 19 Aug 2003 Posts: 153
|
Posted: Tue Mar 05, 2013 8:07 pm Post subject: |
|
|
gkmac wrote: | For me it's essential that this gets fixed for version 0.25.3_p20130131. Some would say "give v0.26" a try, except with that version its impossible to make DVDs of recordings thanks to this bug. |
You don't have to wait for it to be fixed. You can copy the mythplugins ebuild to a local portage overlay and just modified the version number on it. Re-digest it and add the local portage path to your make.conf env var and it will work. There are many howtos out there on doing this. |
|
Back to top |
|
|
gkmac Guru
Joined: 19 Jan 2003 Posts: 333 Location: West Sussex, UK
|
Posted: Wed Mar 06, 2013 9:08 pm Post subject: |
|
|
BonesToo wrote: | gkmac wrote: | For me it's essential that this gets fixed for version 0.25.3_p20130131. Some would say "give v0.26" a try, except with that version its impossible to make DVDs of recordings thanks to this bug. | You don't have to wait for it to be fixed. You can copy the mythplugins ebuild to a local portage overlay and just modified the version number on it... | ...except that mythtranscode (the bit that fails) is part of mythtv itself. Code: | $ equery belongs /usr/bin/mythtranscode
* Searching for /usr/bin/mythtranscode ...
media-tv/mythtv-0.25.3_p20130101 (/usr/bin/mythtranscode) |
_________________ If ~amd64 ebuilds are cutting edge, then git-9999 ebuilds are chainsaws.
"Not everyone can ride a unicycle, does that mean we should put another wheel on it?" - Lokheed |
|
Back to top |
|
|
BonesToo Apprentice
Joined: 19 Aug 2003 Posts: 153
|
Posted: Wed Mar 06, 2013 9:14 pm Post subject: |
|
|
Huh? But that transcode bug is related to 0.26. I thought we were talking about how you could stay using 0.25? You can't upgrade to the newest 0.25.3_*31 because of the mythplugins mismatch. I was saying you can copy the mythplugins ebuild for 0.25.3_01 into a local portage overlay, rename it 0.25.3_31, and then you can build the newer mythtv_0.25.3_31 by also building the newly created local overlay of mythplugins for the same matching version. Then you'll have the latest 0.25.3 build without having to wait for the version mismatch to be fixed by portage maintainers. |
|
Back to top |
|
|
gkmac Guru
Joined: 19 Jan 2003 Posts: 333 Location: West Sussex, UK
|
Posted: Wed Mar 06, 2013 9:23 pm Post subject: |
|
|
Oh, sorry. When you said "you don't have to wait for it to be fixed", I thought you meant that 0.26 mythtranscode bug... _________________ If ~amd64 ebuilds are cutting edge, then git-9999 ebuilds are chainsaws.
"Not everyone can ride a unicycle, does that mean we should put another wheel on it?" - Lokheed |
|
Back to top |
|
|
BonesToo Apprentice
Joined: 19 Aug 2003 Posts: 153
|
Posted: Wed Mar 06, 2013 9:35 pm Post subject: |
|
|
hehe, no worries |
|
Back to top |
|
|
tld Veteran
Joined: 09 Dec 2003 Posts: 1816
|
Posted: Sat Mar 16, 2013 7:45 pm Post subject: |
|
|
Thanks for this post...I was going to upgrading to 0.25.3 soon and would have run into this one.
BonesToo wrote: |
You don't have to wait for it to be fixed. You can copy the mythplugins ebuild to a local portage overlay and just modified the version number on it. Re-digest it and add the local portage path to your make.conf env var and it will work. There are many howtos out there on doing this. |
Are you sure this will work with the current ebuilds? The mythplugins ebuild uses this:
Code: | SRC_URI="ftp://ftp.osuosl.org/pub/mythtv/${MY_P}.tar.bz2
${BACKPORTS:+http://dev.gentoo.org/~cardoe/distfiles/${MY_P}-${BACKPORTS}.tar.xz}"
|
...where $BACKPORTS is set as:
Code: | BACKPORTS="ff8c4960" |
I can see that SRC_URI working with just a rename of the ebuild, but I'm unclear on that BACKPORTS. Am I missing something there?
EDIT: I just noticed that the urls in the mythtv (mythtv-0.25.3_p20130131.ebuild) are the same and use the same BACKPORTS. Maybe this would work. Can anyone confirm?
Thanks
Tom
Tom |
|
Back to top |
|
|
tld Veteran
Joined: 09 Dec 2003 Posts: 1816
|
Posted: Sun Mar 17, 2013 1:55 pm Post subject: |
|
|
Ah....never mind. I was forgetting that, because mythvideo is no longer a separate plugin as of 0.25 this doesn't affect me.
Tom |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Mon Mar 18, 2013 12:49 pm Post subject: |
|
|
tld wrote: | Can anyone confirm?
Thanks
Tom
Tom |
I can. Last weekend I upgraded to 0.25.3, after finding exactly what you did, as well as the same advice. I created a mythplugins-0.25.3_pre20130131.ebuild in a local overlay, did a digest, and everything was happy, then installed as well.
The odd thing was that when I went to the URI site, it looked like a snapshot from last October or so - not the end of January, 2013. _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
tld Veteran
Joined: 09 Dec 2003 Posts: 1816
|
Posted: Mon Mar 18, 2013 1:41 pm Post subject: |
|
|
depontius wrote: | The odd thing was that when I went to the URI site, it looked like a snapshot from last October or so - not the end of January, 2013. |
I believe that's what the backports uri is all about. It's a tar file with backport patch files.
Tom |
|
Back to top |
|
|
|