From: James Ausmus <james.ausmus@gmail.com>
To: gentoo-user@lists.gentoo.org, Mark Knecht <markknecht@gmail.com>
Subject: Re: [gentoo-user] mysql update questions
Date: Mon, 21 Nov 2005 10:28:37 -0800 [thread overview]
Message-ID: <b79f23070511211028r6c905d8dt93f65ebb2f6e989@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0511181622p14077fc3i1bb2cc2799832968@mail.gmail.com>
If you want painless, then don't upgrade to MySQL 5.X when using
MythTV - the DB schema that MythTV uses has a table with a column
named repeat (I believe, I'm not sitting in front of my Myth box),
which, as of MySQL 5.X, is a reserved word, so the Myth back-end setup
won't be able to create that table, which leads to all sorts of
unpleasant Myth-not-working-ness. You can work around this by
modifying the column name that the table creates/uses (haven't done
this myself, don't know how many Myth places you would need to touch,
so not sure how pain{full,less} that would be, but I have seen reports
of others doing it), or you can just not upgrade to 5.X.
Out of curiousity, why are you looking to upgrade MySQL?
-James
On 11/18/05, Mark Knecht <markknecht@gmail.com> wrote:
> Hi,
> What are my options? This mysql thing has been hanging out for a
> long time. I was scared off by two things:
>
> 1) I run MythTV which uses mysql. I have a database on my server (this
> machine) that I'm worried about losing or messing up.
>
> 2) I *think* that if I update this server then I have to update all of
> my MythTV frontend boxes also as I've heard that Myth required both
> the frontend and the backend to run the same versions.
>
> Does anyone have direct experience with this? I'm sort of worried
> about creating problems that take days (or longer) to fix.
>
> Thanks,
> Mark
>
> dragonfly ~ # cat /etc/portage/package.mask
> >x11-drivers/ati-drivers-8.12.10
> #>media-tv/ivtv-0.2.0_rc3-r4
> <=dev-db/mysql-4.1.14
> dragonfly ~ #
>
> dragonfly ~ # emerge -pv --deep --update mplayer
>
> These are the packages that I would merge, in order:
>
> Calculating dependencies /
> !!! All ebuilds that could satisfy "dev-db/mysql" have been masked.
> !!! One of the following masked packages is required to complete your request:
> - dev-db/mysql-4.1.15 (masked by: ~x86 keyword)
> - dev-db/mysql-4.1.14 (masked by: package.mask)
> - dev-db/mysql-5.0.13_rc (masked by: ~x86 keyword)
> - dev-db/mysql-4.1.15-r30 (masked by: -* keyword)
> - dev-db/mysql-3.23.58-r1 (masked by: package.mask)
> - dev-db/mysql-5.0.15-r30 (masked by: -* keyword)
> - dev-db/mysql-4.0.26 (masked by: package.mask, ~x86 keyword)
> - dev-db/mysql-4.0.26-r30 (masked by: package.mask, -* keyword)
> - dev-db/mysql-5.0.15 (masked by: ~x86 keyword)
> - dev-db/mysql-4.0.25-r2 (masked by: package.mask)
>
> For more information, see MASKED PACKAGES section in the emerge man page or
> section 2.2 "Software Availability" in the Gentoo Handbook.
> !!! (dependency required by "net-fs/samba-3.0.14a-r2" [ebuild])
>
> dragonfly ~ #
>
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-11-21 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 0:22 [gentoo-user] mysql update questions Mark Knecht
2005-11-19 5:52 ` Francesco R.
2005-11-21 18:28 ` James Ausmus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b79f23070511211028r6c905d8dt93f65ebb2f6e989@mail.gmail.com \
--to=james.ausmus@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=markknecht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox