=== mycosys1 is now known as mycosys === mycosys1 is now known as mycosys [08:35] superm1: FYI when I run build-debs.sh against master I have to manually git stash the mythweb checkout after failed builds [10:22] hi! my fresh mythbuntu installation does not boot, all i get is blank screen with blinking cursor [10:24] i already tried editing /etc/default/grub, removing "quiet splash" to try "xforcevesa", "nomodeset" or "text". always running update-grub within chroot. no success [10:28] there's some syslinux thing in the mbr of the sole hd. first partition is a fat32 efi ... i would think this is how it should be [10:44] thorwil try ctrl alt and f1 when you see the cursor [10:44] thorwil: are you thre [10:45] rileyp: the only key.combo that works at that stage ist ctrl-alt-del for reset [10:45] so it boots to flashing cursor? [10:46] yes. i guess it fails before even loading all of grub, because holding down shift does nothing [10:46] do you get the grub emnu [10:47] did you use a usb stick to install or cd [10:47] no, it's straight motherboard boot screen -> blinking cursor [10:47] usb stick [10:48] ah ok and then it says no boot disk? or just hangs at cursar [10:48] cursor sorry [10:49] was it a clean install on a new disk did you select partitions and did you install grub to sda during setup? [10:50] or is a windows dual boot which is fine so long as you chose sda to install grub [10:50] and windows is on teh first partition [10:50] 3rd attempt installing on a fresh disc. allowed mythbuntu to partition as it likes [10:52] I personally have had a lot of trouble with disk parttioner on the ubuntu cd's in the last few years and always use gparted prior [10:52] (3rd attempt because i had to find out that mythbuntu only succeeds in installing grub-efi, if it can install updates thanks to a network connection!) [10:53] you can install without network but its a painfull process [10:54] thanks for your attention. lunch, bbiab [14:43] dekarl: oh really? are you modifying stuff on mythweb then for your build? [15:53] superm1, there's been some different bugs on mythweb being broken in 0.25. We need to do some testing on that [18:44] tgm4883: on fresh installs? [18:44] or upgrades [18:44] really need to figure out who and how these are breaking [18:44] because i haven't experienced it at all onn my stuff [19:05] Hi. How do I do a database schema upgrade? My frontend desktop (Precise) won't connect to my backend (Lucid). The backend machine has the mythbuntu-repos installed and is upto date (well, apt-get says it is) on 0.24. [19:06] The frontend says the database schema is quite a few versions out of date. [19:09] DarthFrog: precise comes with 0.25 [19:16] Oh. I didn't realise that 0.25 has been released. [19:16] not yet [19:16] soonish, should be right around precise release [19:16] Nuisance. Can it be downgraded to 0.24? [19:17] tgm4883: does mythbuntu-repos have old version for precise ^ [19:17] rhpot1991, nope [19:17] it shouldn't anyway [19:17] DarthFrog: I don't imagine you have a ppa? [19:17] My own? No. [19:18] I'd just push the latest 0.24 to my ppa and build for precise and run that for the time being [19:18] rhpot1991, https://launchpad.net/~mythbuntu/+archive/0.24?field.series_filter=precise [19:18] [launchpad.net] 0.24 : “Mythbuntu Developers” team [19:18] it's there, but the builds are from Feb 13th [19:18] and there won't be any newer builds for precise for the 0.24 branch [19:19] or use that [19:19] or upgrade everything [19:19] tgm4883: Tnx. I'll upgrade both backend machines to Precise once it's released. I dare not now; my wife knows where I sleep! :-) [19:20] DarthFrog: I recommend upgrading on weekends too :) [19:20] If she loses access to her "Mythbusters" collection, I'm doomed! :-) [19:35] Hmm. I install libmyth-0.24-0 from that ppa; it rips out the current MythTV stuff. I then try to install mythtv and it wants to rip out libmyth-0.24.0 and replace it with 0.25. AFAICT, libmyth-0.24-0 is the only package in that ppa. [19:36] you have to tell it to install particular versions of stuff [19:36] using the = and a version number if you want to go that route [19:36] and then use apt pinning to keep it in place [19:36] 0.25 just hit RC, so it's super close to release right now anyway [19:37] i would say backup your DB, bite the bullet and upgrade this weekend [19:37] superm1: Don't want 0.25. Want 0.24 [19:37] if it works, great, if you hit a snag, report it, revert etc [19:37] yeah i'm saying it's going to be super hard to do 0.24 in precise unless you do that apt pinning and tell apt to install specific versions of all the packages [19:38] DarthFrog: that or install 11.10 on that frontend [19:38] if you really don't want 0.25 that is prob easier [19:39] I have 11.10 also installed but it's eating itself. :-( Not impressed with Oneiric, not at all. [19:39] Guess I'll install Oneiric in a virtualbox VM and run 0.24 there. [19:43] Mythbuntu switching to LTS only releases is a smart move, IMHO. [20:03] OK, got it working in a Lucid VM. :-) [20:04] Thanks for your help, folks. It's greatly appreciated. [22:08] i've updated to 0.25 and works fine so far except tv-guide-data [22:08] till now i ran /usr/bin/mythfilldatabase --file 1 /home/ubuntu/xmltv-data/data.xml [22:09] but now i get [22:09] Boolean type options do not accept values: [22:09] --file [22:09] Received '1' but unassociated arguments have not been enabled [22:12] any idea what's wrong? [22:12] probably syntax changed? [22:13] i think you additionally an --xmlfile after the 1 [22:17] hmm getting the same error [22:27] check in #mythtv-users then, hopefully you'll find someone who know's it's syntax better [22:38] superm1: thanx [23:10] superm1: nope, I'm only modifying the main mythtv source code [23:13] hpeter: your command line is 0.24 syntax but you are running 0.25 :) [23:13] i suspect that ;) [23:14] do you know the correct 0.25 syntax? [23:15] something like mfdb --file --xmlfile --sourceid 1>