Have just emerged MythTV 0.16 up to 0.17. Restarted mythbackend without a problem, but on trying to start mythfrontend I get an error telling me that the database schema upgrade is failing because it's trying to insert a duplicate column. Should likely be checking for the column and/or dropping it before doing an add: mcfletch@raistlin:~$ mythfrontend 2005-02-24 20:21:42.364 Upgrading to schema version 1065 2005-02-24 20:21:59.484 Upgrading to schema version 1066 2005-02-24 20:21:59.484 DB Error (Performing database upgrade): Query was: ALTER TABLE capturecard ADD COLUMN firewire_port INT UNSIGNED NOT NULL DEFAULT 0; Error was: Driver error was [2/1060]: QMYSQL3: Unable to execute query Database error was: Duplicate column name 'firewire_port' new version: 1066 2005-02-24 20:21:59.484 Couldn't upgrade database to new schema, exiting. Reproducible: Always Steps to Reproduce: 1. emerge and configure mythtv 0.16 2. emerge update mythtv 0.17 3. restart mythbackend 4. start mythfrontend Actual Results: Error reported during schema update Expected Results: Start myth front end. Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.3.4, glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r7 x86_64) ================================================================= System uname: 2.6.10-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Feb 18 2005, 01:10:42)] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/mcfletch/portagedev" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aalib acpi alsa arts berkdb bitmap-fonts cdr crypt cups curl dvd esd f77 fam flac font-server fortran gdbmgif gpm gtk imlib ipv6 java jp2 jpeg junit kde ldap lzw lzw-tiff mikmod motif mozilla multilib mysql ncurses nls oggvorbis opengl oss pam perl png postgres python qt readline samba sdl slang ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xml xml2 xmms xpm xrandr xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
This problem only crops up for people who have played with the CVS copies of MythTV, which is not supported. Only the CVS versions after the 0.16 release included any reference to firewire. Now if you insist that you didn't. The only thing I can think of is that you started the backend and frontend pretty much at the sametime... and they hit a race condition updating the DB schema. The backend partly updated the schema and the frontend did too.. now they won't go anywhere... Ah... atomic commits on this stuff would be grand. Granted this guide is completely bare but it does handle this situation... http://dev.gentoo.org/~cardoe/mythtv/
Well, I've never installed a CVS version of Myth, but I did restart the backend and the frontend within a few seconds of one another (issued /etc/init.d/mythbackend restart and as soon as it returned did a mythfrontend). Dropping the columns, re-emerging, starting the backend, pausing, and starting the frontend lets the system start as expected. Thanks.
