| View previous topic :: View next topic |
| Author |
Message |
aCOSwt Veteran


Joined: 19 Oct 2007 Posts: 1509 Location: Between the keyboard and the chair
|
Posted: Sun Feb 21, 2010 12:12 pm Post subject: (mysql 5.1 unmasked - upgrading) generalized [Solved] |
|
|
Hello,
I am looking for some kind of general answers (if possible) to questions arising to my mind following the recent unmask of mysql 5.1
1/ In the lastest news (obtained via eselect news read) I understand that mysql 5.1 has been unmasked.
a : Is my understanding that its status passed from hardmasked to unstable correct ?
2/ This news message warns me about specific actions to be taken when upgrading.
As I do not accept unstable for mysql, If my understanding (a) is correct I am not concerned yet.
However, I will be concerned when this package passes from unstable to stable.
b : Will I be rewarned about conditions for upgrading by some equivalent news when 5.1 goes stable ?
3/ Amongst the specific actions to undertake when upgrading, I understand that existing mysql databases might need to be converted.
It is possible that amongst the applications I installed on my system, some make use of mysql databases I am not aware of.
c : How is it possible for me to detect this and if and how I should undertake the conversion for these ?
I ask for some general answer as I believe such questions might arise with other packages.
Last edited by aCOSwt on Mon Feb 22, 2010 11:12 am; edited 1 time in total |
|
| Back to top |
|
 |
desultory Administrator

Joined: 04 Nov 2005 Posts: 7061
|
Posted: Mon Feb 22, 2010 10:30 am Post subject: |
|
|
| aCOSwt wrote: | 1/ In the lastest news (obtained via eselect news read) I understand that mysql 5.1 has been unmasked.
a : Is my understanding that its status passed from hardmasked to unstable correct ? | Indeed.
| aCOSwt wrote: | 2/ This news message warns me about specific actions to be taken when upgrading.
As I do not accept unstable for mysql, If my understanding (a) is correct I am not concerned yet.
However, I will be concerned when this package passes from unstable to stable.
b : Will I be rewarned about conditions for upgrading by some equivalent news when 5.1 goes stable ? | Probably, though it is not guaranteed.
| aCOSwt wrote: | 3/ Amongst the specific actions to undertake when upgrading, I understand that existing mysql databases might need to be converted.
It is possible that amongst the applications I installed on my system, some make use of mysql databases I am not aware of.
c : How is it possible for me to detect this and if and how I should undertake the conversion for these ? |
| Code: | | equery d virtual/mysql |
|
|
| Back to top |
|
 |
aCOSwt Veteran


Joined: 19 Oct 2007 Posts: 1509 Location: Between the keyboard and the chair
|
Posted: Mon Feb 22, 2010 11:11 am Post subject: |
|
|
| Perfect ! Thanks a lot desultory. |
|
| Back to top |
|
 |
dufeu l33t


Joined: 30 Aug 2002 Posts: 675 Location: US-FL-EST
|
Posted: Wed Feb 24, 2010 1:37 pm Post subject: |
|
|
I also have related questions regarding the unmasking of mysql 5.1.
I'm also concerned about applications which use mysql. On my system, I'm primarily concerned about amarok.
The lastest | Code: | emerge --sync
emerge -puNDv @world |
gives me the following messages: | Code: | !!! One or more updates have been skipped due to a dependency conflict:
dev-db/mysql:0
('ebuild', '/', 'dev-db/mysql-5.1.44', 'merge') conflicts with
<dev-db/mysql-5.1[embedded,-minimal] required by ('ebuild', '/', 'media-sound/amarok-2.2.2.90', 'merge')
!!! The following update(s) have been skipped due to unsatisfied dependencies
!!! triggered by backtracking:
virtual/mysql:0 |
Could someone comment and offer guidance? _________________ People whom think M$ is mediocre, don't know the half of it. |
|
| Back to top |
|
 |
aCOSwt Veteran


Joined: 19 Oct 2007 Posts: 1509 Location: Between the keyboard and the chair
|
|
| Back to top |
|
 |
dufeu l33t


Joined: 30 Aug 2002 Posts: 675 Location: US-FL-EST
|
Posted: Fri Feb 26, 2010 4:23 pm Post subject: |
|
|
Actually ... nope!
I had missed that one when I had searched the forums previously.
I did the mysql upgrade and it went fairly smoothly after unmerging amarok as per your suggested link. I have not yet re-emerged amarok yet.
I did run into two problems which could not be resolved by revdep-rebuild and I feel that perhaps they should have been at least seen by revdep-rebuild.
The steps were: | Code: | emerge --sync
emerge -1uND @world |
"devicekit-power" and "gutenprint" were both marked for upgrading. Both failed with similar failure messages. The messages were on the order of " /usr/lib64/perl5/{more levels}/{some name}.pm does not exist". The failure messages then told me what was in $INC.
It turns out that for reasons I don't understand, the directory "/usr/lib64/perl5/5.8.8/{more}" was left intact. The missing files were in the 5.8.8 sub directory structure. $INC included only "/usr/lib64/perl5/5.10.1{more}" and friends.
An equery on the DBD.pm showed it belonged to DBD-mysql. revdep-rebuild showed nothing missing while DBD-mysql would not re-compile. Working further up the dependency chain, I found I needed to: | Code: | emerge DBI foomatic-db-engine
emerge DBD-mysql
emerge devicekit-power gutenprint |
My system is now fine and I didn't save any previous states so I don't know what to report to gentoo bugzilla. _________________ People whom think M$ is mediocre, don't know the half of it. |
|
| Back to top |
|
 |
desultory Administrator

Joined: 04 Nov 2005 Posts: 7061
|
Posted: Sat Feb 27, 2010 4:12 am Post subject: |
|
|
| dufeu wrote: | | My system is now fine and I didn't save any previous states so I don't know what to report to gentoo bugzilla. | Perhaps you should investigate the use of perl-cleaner before you investigate the use of bugzilla. |
|
| Back to top |
|
 |
dufeu l33t


Joined: 30 Aug 2002 Posts: 675 Location: US-FL-EST
|
Posted: Sat Feb 27, 2010 10:03 pm Post subject: |
|
|
| desultory wrote: | | Perhaps you should investigate the use of perl-cleaner ... |
Thank you for the tip.  _________________ People whom think M$ is mediocre, don't know the half of it. |
|
| Back to top |
|
 |
depontius Veteran

Joined: 05 May 2004 Posts: 1925
|
Posted: Sat Feb 27, 2010 10:26 pm Post subject: |
|
|
It's worth mentioning that mythtv-0.22 is on the verge of going stable. Probably the greatest snag in the mythtv upgrade is the change to the database schema - there are several potential levels of complication to the upgrade. Mine was pretty bad - called "partial corruption", which is worse than "uniform corruption".
I would strongly suggest keeping the mythtv and mysql upgrades well separated. _________________ .sigs waste space and bandwidth |
|
| Back to top |
|
 |
aCOSwt Veteran


Joined: 19 Oct 2007 Posts: 1509 Location: Between the keyboard and the chair
|
Posted: Sat Feb 27, 2010 10:39 pm Post subject: |
|
|
| depontius wrote: | | ...Mine was pretty bad - called "partial corruption", which is worse than "uniform corruption".... |
This is a truly authentic philosophical statement.
Highly interesting because of some kind of obvious paradox.
though one could legitimately wonder if it was perceived worse because of its partiality or...
because it was...
yours...
 |
|
| Back to top |
|
 |
depontius Veteran

Joined: 05 May 2004 Posts: 1925
|
Posted: Sat Feb 27, 2010 11:18 pm Post subject: |
|
|
The mythtv people said that partial corruption was worse. In order to fix it, I ended up throwing out a bunch of my data, and only restoring the stuff that could be safely restored. I had to reconfigure afterward. A "uniformly corrupted" database could have a simple character-set fix applied, then reloaded - complete.
The corruption was because of character sets, latin1 vs utf8. Mythtv assumes latin1. "Uniform corruption" meant that you had utf8, and all of your tables were written with utf8. "Partial corruption" meant that by hook or by crook, some of your data had been written using utf8, and some written using latin1. That also means duplicate table rows and other messy stuff. _________________ .sigs waste space and bandwidth |
|
| Back to top |
|
 |
|