When I tried to install mythtv in a chroot running Debian testing the
first problem was
Preconfiguring packages ...
/tmp/mythtv-common.config.320363: 21: /tmp/mythtv-common.config.320363: pwgen: not found
mythtv-common failed to preconfigure, with exit status 127
I had requested that only dependencies, not recommends, be installed.
This suggests that mythtv-common is missing a pre-dependency on the
pwgen package. pwgen was installed by the end.
Then there were other problems, most of which seemed to stem from a
failure to setup mysql properly, which may have had something to do with
the chroot (I did not bind mount /dev). And then I ran out of space!
If anyone has any tips for getting myth working in a chroot, I'd love to
hear them. The host system is Debian Lenny; I'm probably about to go up
to the backported 2.6.32 kernel for unrelated reasons. Yes, I know it's
time to go to squeeze :)
I shutdown the host's mysql server; contention for the port should not
have been an issue.
Thanks.
Ross Boylan
P.S. If you're intersted, here are highlights of the problems with
installation via aptitude:
/tmp/mythtv-common.config.320363: 21: /tmp/mythtv-common.config.320363: pwgen: not found
mythtv-common failed to preconfigure, with exit status 127
Unpacking mysql-server-5.1 (from .../mysql-server-5.1_5.1.58-1_i386.deb) ...
df: Warning: cannot read table of mounted file systems: No such file or directory
# the solution is to create a fake /etc/mtab, I think.
Setting up mysql-server-5.1 (5.1.58-1) ...
Stopping MySQL database server: mysqld.
120214 23:50:05 [Note] Plugin 'FEDERATED' is disabled.
120214 23:50:05 InnoDB: Initializing buffer pool, size = 8.0M
120214 23:50:05 InnoDB: Completed initialization of buffer pool
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
120214 23:50:05 [ERROR] Plugin 'InnoDB' init function returned error.
120214 23:50:05 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
ERROR: 1146 Table 'mysql.user' doesn't exist
120214 23:50:05 [ERROR] Aborting
120214 23:50:05 [Note] /usr/sbin/mysqld: Shutdown complete
df: Warning: cannot read table of mounted file systems: No such file or directory
/etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.1 (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
mysql-server-5.1
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up mysql-server-5.1 (5.1.58-1) ...
Stopping MySQL database server: mysqld.
df: Warning: cannot read table of mounted file systems: No such file or directory
/etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.1 (--configure):
subprocess installed post-installation script returned error exit status 1
mythtv-database says
Setting up mythtv-database (0.24.2-0.0) ...
Failed to connect to database: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at -e line 5, <> line 1.
