Page 11 of 36 FirstFirst ... 91011121321 ... LastLast
Results 101 to 110 of 353

Thread: mythbuntu-repos, mythtv-updates, mythbuntu-updates - Questions or Issues

  1. #101
    Join Date
    Apr 2005
    Beans
    79

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Quote Originally Posted by lionsnob View Post
    Thanks for your help! We'll see how it goes on Friday.
    Looks like its fixed now - version 20830 is listed for all of the modules. Thanks for clearing this up!

  2. #102
    Join Date
    Nov 2008
    Beans
    4

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Quote Originally Posted by pigah View Post
    I just tried upgrading to trunk and having problems like Nikas with database password. I dpkg-reconfigured both mysql-server-5.0 and mythtv-database to have the same password.

    dpkg-reconfigure mysql-server-5.0 seems to work but gives the following warning:
    "090514 11:54:37 [Warning] option 'net_buffer_length': unsigned value 8388608 adjusted to 1048576"

    dpkg-reconfigure mythtv-database exits with:

    "Failed to create or modify database (incorrect admin username/password?)"

    When I look at the mythbackend logs there is this nugget:

    Code:
    2009-05-14 11:50:55.300 mythbackend version: trunk [Unknown] www.mythtv.org
    2009-05-14 11:50:55.317 Using runtime prefix = /usr
    2009-05-14 11:50:55.320 Empty LocalHostName.
    2009-05-14 11:50:55.321 Using localhost value of mythtv
    2009-05-14 11:50:55.374 New DB connection, total: 1
    2009-05-14 11:50:55.408 Connected to database 'mythconverg' at host: localhost
    2009-05-14 11:50:55.411 Closing DB connection named 'DBManager0'
    2009-05-14 11:50:55.414 Connected to database 'mythconverg' at host: localhost
    2009-05-14 11:50:55.441 Current Schema Version: 1224
    2009-05-14 11:50:55.442 Database schema is old. Waiting to see if DB is being upgraded.
    2009-05-14 11:50:56.444 New DB connection, total: 2
    2009-05-14 11:50:56.447 Connected to database 'mythconverg' at host: localhost
    2009-05-14 11:50:56.458 Current Schema Version: 1224
    2009-05-14 11:50:57.470 Current Schema Version: 1224
    2009-05-14 11:50:58.482 Current Schema Version: 1224
    2009-05-14 11:50:59.492 Current Schema Version: 1224
    2009-05-14 11:51:00.501 Current Schema Version: 1224
    2009-05-14 11:51:00.504 Timed out waiting.
    2009-05-14 11:51:00.544 Database backup script does not exist: /usr/share/mythtv/mythconverg_backup.pl
    2009-05-14 11:51:00.561 Backing up database to file: '/var/lib/mythtv/recordings/mythconverg-1224-20090514115100.sql'
    2009-05-14 11:51:00.613 DBUtil Error: Error backing up database: 'mysqldump --defaults-extra-file='/tmp/mythtv_db_backup_conf_RApObJ' --host='localhost' --user='root' --add-drop-table --add-locks --allow-keywords --complete-insert --extended-insert --lock-tables --no-create-db --quick 'mythconverg' > '/var/lib/mythtv/recordings/mythconverg-1224-20090514115100.sql' 2>/dev/null' (512)
    2009-05-14 11:51:00.705 Console is non-interactive, can't prompt user...
    2009-05-14 11:51:00.708 Upgrading.
    2009-05-14 11:51:00.710 Newest Schema Version : 1232
    2009-05-14 11:51:00.724 Upgrading to schema version 1225
    2009-05-14 11:51:00.726 DB Error (Performing database upgrade): 
    Query was: CREATE TABLE bad_people AS SELECT * FROM people; 
    Error was: Driver error was [2/1050]:
    QMYSQL3: Unable to execute statement
    Database error was:
    Table 'bad_people' already exists
     
    new version: 1225
    2009-05-14 11:51:00.728 Database Schema upgrade FAILED, unlocking.
    2009-05-14 11:51:00.732 Couldn't upgrade database to new schema

    I have this identical problem. Is there a solution?

  3. #103
    Join Date
    Jul 2009
    Beans
    4

    Question Re: Weekly Builds for Hardy, Intrepid, Jaunty

    I use the weekly builds packages for 0.21-fixes under Intrepid. Could the following patch please be integrated into these builds?

    http://cvs.mythtv.org/trac/changeset/17172

    It fixes a problem with input groups where one input shares a card with another input which is not in the same group. For example, using firewire capture with s-video/composite capture to a PVR-150. In this setup, the analog tuner is not part of that input group, but if the analog tuner is busy, then the firewire tuner is marked busy as well.

    -Ray

  4. #104
    Join Date
    Nov 2006
    Location
    Oregon
    Beans
    4,434
    Distro
    Ubuntu Development Release

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Quote Originally Posted by Observer64 View Post
    I use the weekly builds packages for 0.21-fixes under Intrepid. Could the following patch please be integrated into these builds?

    http://cvs.mythtv.org/trac/changeset/17172

    It fixes a problem with input groups where one input shares a card with another input which is not in the same group. For example, using firewire capture with s-video/composite capture to a PVR-150. In this setup, the analog tuner is not part of that input group, but if the analog tuner is busy, then the firewire tuner is marked busy as well.

    -Ray
    You should ask upstream first. We try to keep as close to the official tree as we can.
    *Don't PM me directly for support, open a new thread
    *Looking for a MythTV quick start guide?

  5. #105
    Join Date
    Jul 2009
    Beans
    4

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Quote Originally Posted by tgm4883 View Post
    You should ask upstream first. We try to keep as close to the official tree as we can.
    I have made posts to the mythtv-users and mythtv-dev mailing lists with almost no response. I have tried contacting Daniel K using the email address he uses on the list -- at the suggestion of the community -- also with no response.

    I would really like to keep one source from clobbering recordings on the other, and input groups is supposed to be the way to do it.

    If someone here has the ear of one of the source managers, your help is greatly appreciated.

    If it wasn't so darn convenient to use the weekly build packages, I'd just roll it myself and be done with it. But it shouldn't have to be that way.

    -Ray

  6. #106
    Join Date
    Nov 2006
    Location
    Oregon
    Beans
    4,434
    Distro
    Ubuntu Development Release

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Quote Originally Posted by Observer64 View Post
    I have made posts to the mythtv-users and mythtv-dev mailing lists with almost no response. I have tried contacting Daniel K using the email address he uses on the list -- at the suggestion of the community -- also with no response.

    I would really like to keep one source from clobbering recordings on the other, and input groups is supposed to be the way to do it.

    If someone here has the ear of one of the source managers, your help is greatly appreciated.

    If it wasn't so darn convenient to use the weekly build packages, I'd just roll it myself and be done with it. But it shouldn't have to be that way.

    -Ray
    I'll have our lead dev take a look at it, but usually we try not to stray from upstream unless it's pretty important.
    *Don't PM me directly for support, open a new thread
    *Looking for a MythTV quick start guide?

  7. #107
    Join Date
    Jul 2009
    Beans
    4

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Thank you. And as I mentioned before, if someone here could convince someone in charge of the upstream to integrate that patch, it would be appreciated.

    -Ray

  8. #108
    Join Date
    Nov 2006
    Location
    Oregon
    Beans
    4,434
    Distro
    Ubuntu Development Release

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Quote Originally Posted by Observer64 View Post
    Thank you. And as I mentioned before, if someone here could convince someone in charge of the upstream to integrate that patch, it would be appreciated.

    -Ray
    Ok, we aren't going to apply that patch here. My suggestion would be to go to #mythtv-users on freenode and ask there about the patch. You may have to wait around for someone in charge to see it and comment on it.
    *Don't PM me directly for support, open a new thread
    *Looking for a MythTV quick start guide?

  9. #109
    Join Date
    Oct 2006
    Location
    North of Kali-Fornia
    Beans
    97
    Distro
    Ubuntu 7.04 Feisty Fawn

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    I just skimmed thru these - lots of info here. I would suggest a simple simple build status indicator be added to the very first post (or somewhere). Just something that give a very terse status for Hardy, Intrepid, Jaunty ... I know these things can take on a life of their own but even if updated twice a month would great.

    Hardy - Very stable. Current issues: Backend:zzz xxx, Install:yyy
    Mythbuntu Build: 11111111 MythTV Ver: 0.xx Last Build:07-22-09

    where zzz xxx yyy are just terms you could use in a search to find more info
    Its not the years, its the mileage ...

  10. #110
    Join Date
    Apr 2006
    Location
    Belleville, MI, USA
    Beans
    117
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Weekly Builds for Hardy, Intrepid, Jaunty

    Current weekly build broken?

    I just updated my weekly build, hoping an intermittent lockup would go away....and it appears to have broken Myth entirely.

    I'm getting:
    Protocol version mismatch (frontend=46,backend=45)

    Now, that's pretty self-explanatory, I see the problem. I just don't know how to fix it. Is there a workaround?

    I checked to make sure that all myth packages, including frontend and backend, are at the same version. According to synaptic, all things Myth are at 0.21.0-trunk21261. And, it seems that's the latest. Doing sudo apt-get update && sudo apt-get dist-upgrade tells me there are 0 packages to be updated.

    So, is mythbuntu weekly broken till next week? Anyone know of a workaround?

    Thanks,

    -Mark

Page 11 of 36 FirstFirst ... 91011121321 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •