logs archiveIRC Archive / Freenode / #centos / 2015 / July / 22 / 1
imriz
LzrdKing, It is compatible I think
TrevorH
LzrdKing: rpmforge and EPEL used to conflict but...
LzrdKing
s/aren;t/weren't/
TrevorH
@rpmforge
centbot
rpmforge/repoforge can no longer be considered a trusted resource. Updates are few and far between which can, has and will continue to put people at risk. Please find alternative package sources such as EPEL.
imriz
you have the mysql compat RPM for that
LzrdKing
TrevorH: yes, those two are what i was thinking of
imriz
LzrdKing, use mysql.com's if you need a newer version
TrevorH
imriz: I disagree, IUS is better
         

OneM_Industries
Just tested with another computer, no response.
imriz
TrevorH, you can't say that without knowing what exactly he needs :)
I would say Percona is better for me
TrevorH
IUS targets _only_ enterprise linux versions so they know what they are doing
LzrdKing
imriz: what i need is a package :)
OneM_Industries
Odd, dmesg shows it, imriz.
imriz
I disagree - databases are best handled by the experts of databases
hence using Percona :)
LzrdKing
epel, ius, percona, mysql, whatever, as long as the correct version is installed, one rpm maintainter is pretty much the same to me as any other
Nahual
If that's true I have an RPM I'd like to sell you.
imriz
LzrdKing, mysql.com provides yum repos
and again, I run dozens of TBs of MySQL with Percona, with great success
LzrdKing
the repo is going to get synced to our katello server anyway
imriz
but what is "best" for you, only you can know at this point :)
LzrdKing
which is a mess unto itself anyway
imriz
pulp is indeed fun :)
LzrdKing
i don;t see mysql-server listed at https://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/letter_m.group.html; am in the wrong place?
carlgeorge
imriz: an expert in databases in not necessarily an expert on RPM packaging
TrevorH
LzrdKing: you will not find mysql in EPEL, it's in IUS
LzrdKing
TrevorH: ok, one less choice to be concerned about
imriz
carlgeorge, RPM is a relatively easy job comparing to maintaining a good production ready database
carlgeorge
IUS mysql packages ship a my.cnf with some adjustments from Rackspace DBAs https://github.com/iuscommunity-pkg/mysql56u/blob/master/SOURCES/my-56-verbose.cnf
LzrdKing
imriz: right, "yum install mysql-server" is where the rpm's job begins and ends
         

carlgeorge
imriz: Apples and oranges. Being proficient in one does not automatically mean you know how to do the other properly.
LzrdKing
we have a mysql puppet module thats going to do the configuration, including writing a my.cnf; i just need to update the repos
imriz
carlgeorge, I maintain my share of RPMs
TrevorH
yes, and then when it says you need to remove postfix and everything else that depends on mysql, what do you do next?
imriz
carlgeorge, not rocket science
LzrdKing
TrevorH: rebuild with puppet :)
imriz
use the compat package
again, not hard
they test their stuff with the major distros
TrevorH
imriz: you are entitled to your opinion
imriz
that is not opinion, that is first hand experience from managing mysql at scale :)
LzrdKing
i see ius has 5.5 and 5.6; maybe the dba will make it easy and say we need 5.7
bharper
is 5.7 stable yet? last I checked it was not
imriz
I don't think so
carlgeorge
LzrdKing: I surely hope not, 5.7 is not stable yet
http://dev.mysql.com/doc/relnotes/mysql/5.7/en/
TrevorH
imriz: so what, I run multiple mysql databases too. In addition, I'm in this channel just about every day helping people clean up after the messes that various third aprty repos cause
LzrdKing
i guess thats why its not in ius
carlgeorge
exactly
Inline with Upstream Stable
LzrdKing
the advantage of using the mysql.com repo is that there will only be mysql packages in it; if we use ius, there will be other, unrelated packages as well
imriz
TrevorH, the CentOS 6 support is stable
TrevorH
LzrdKing: but they are all deliberately named differently than the ones in base so they do not overwrite by accident
imriz
you use their yum repo, and it is fine
carlgeorge
LzrdKing: That's the beauty of IUS; all packages have alternative names from stock. Nothing is upgraded unless you explicitly swap it out with the stock version.
LzrdKing
TrevorH: yes, i do see that
imriz
if you will try to force it to install without dependencies, than you will get into a mess :)
LzrdKing
imriz: won;t be so bad, i'll just fix the problem and rerun puppet, blowing away the messed up VM and creating a new one as needed
imriz: i mean, puppet doesn't force installs, not that i can see
imriz
LzrdKing, you shouldn't get there, just read the instructions of whatever repo you decide to do
LzrdKing, you can make it force :)
LzrdKing
forcing anything is usually wrong though
imriz
but anyway
choose your poison - all of these will work
LzrdKing
imriz: no, i'm more concerned about modifying the module so new manifests can specify the version to use in such a way that existing machines will be unaffected
i am not sure if IUS naming the packages differently makes this easier or harder
easier, i think
TrevorH
easier
OneM_Industries
So, any ideas about the keyboard? It shows up in dmesg.
imriz
btw
LzrdKing
the mysql repo calls everything mysql-community(-*) but it look slike 5.5 and 5.6 are named the same except for the version
imriz
if you talk about errors
than IUS creates conflicts
carlgeorge
LzrdKing: If you want to chat more about the IUS repo you can hit us up directly in #iuscommunity.
imriz
*then
carlgeorge
imriz: IUS explictly conflicts with stock packages, by design.
LzrdKing
carlgeorge: probably better than discussing it in here
imriz
that is what I am saying :)
carlgeorge
you can't use stock mysql and IUS mysql at the same time.
imriz: A conflict is not an error necessarily.
imriz
there was complaint of 3rd repos creating errors that sends users over here :)
LzrdKing
even though IUS packages are called mysql55 and mysql56u?
imriz
a conflict is an error :)
the exit code says that
LzrdKing
and centos repo is just mysql?
TrevorH
no, a conflict means it needs a human to decide which should be used
carlgeorge
No, it isn't. Non-zero exit codes are used for many things.
TrevorH
LzrdKing: IUS called their 5.5 packages mysql55* but then SCL re-used mysql55 for their packages so when 5.6 came out, IUS added the 'u' to make sure they were different again
carlgeorge
LzrdKing: IUS packages use the stock file locations, i.e. /usr/bin/mysql. So to avoid actual errors for conflicting files, the package conflicts.
TrevorH
which also stops you from installing it by accident
imriz
guys
carlgeorge
Use yum shell to swap them out. We also have a mysqlclient16 package to prevent that postfix error.
imriz
it says error in the message :)
Error: php55u-common conflicts with php-common-5.3.3-46.el6_6.x86_64
heh
anyway
this is pointless
TrevorH
yes
« prev 1 2 3 4 5 6 7 8 9 10 next »