Re: Should I go ahead with the full-upgrade
On Mon, Nov 09, 2009 at 11:12:02PM +0100, Raven ra...@vp44.net was heard to say: What I wanted to know is if aptitude, when removing mysql-server-5.0, keeps the data files and makes them available in v5.1. I can't tell you the answer to that because aptitude does not make that decision; the mysql package does. In my past experience, database servers leave the database on the system (some of them ask and default to keeping it). But I'm not a database expert and I know particularly little about mysql. If you're really worried, I'd suggest taking a test machine, installing mysql 5.0 and storing some data in it, then upgrading to 5.1 and seeing whether the data is kept. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Should I go ahead with the full-upgrade
Hi all.
This is a production server running debian testing. It's been a while and
I wanted to update the system. Unfortunately it seems that some packages
are BROKEN:
The following packages are BROKEN:
mysql-client-5.1 php5-geoip php5-imagick php5-suhosin php5-xcache
The following NEW packages will be installed:
javascript-common{a} libjs-mootools{a} libreadline6{a}
mysql-server-5.1{a} tcl8.5{a} wwwconfig-common{a}
The following packages will be REMOVED:
ghostscript{u} gs-common{u} libcupsimage2{u} libdjvulibre-text{u}
libdjvulibre21{u} libgraphviz4{u} libgs8{u} liblqr-1-0{u}
libmagickcore2{u}
libmagickwand2{u} psfontmgr{u}
The following packages will be upgraded:
binutils bsd-mailx bsdutils courier-base courier-imap courier-imap-ssl
courier-pop courier-pop-ssl courier-ssl cpp debconf debconf-i18n dpkg
dpkg-dev
dselect eject expect fakeroot file g++ gcc geoip-database lftp
libbit-vector-perl libblkid1 libc-bin libc-dev-bin libc6 libc6-dev
libc6-i686
libcap-ng0 libcap2 libcarp-clan-perl libdate-calc-perl
libdevmapper1.02.1 libdirectfb-1.2-0 libdrm-intel1 libdrm2 libfreetype6
libfreetype6-dev
libgdbm3 libgeoip1 libglib2.0-0 libglib2.0-data libgnutls26 libgsf-1-114
libgsf-1-common libgtk2.0-0 libgtk2.0-bin libgtk2.0-common
libhtml-parser-perl libidn11 libkeyutils1 liblua5.1-0 libmagic-dev
libmagic1 libmysqlclient16 libnet-snmp-perl libopenexr6 libpci3 libpcre3
libperl5.10 libpng12-0 libpng12-dev libpopt0 libselinux1 libsensors4
libsepol1 libsqlite3-0 libtimedate-perl libuuid1 libwww-perl libxml2
lm-sensors
locales modconf module-init-tools mount munin-node munin-plugins-extra
mysql-client mysql-client-5.0 mysql-common mysql-server mysql-server-5.0
nomarch openssh-client openssh-server openvpn os-prober pciutils perl
perl-base perl-modules pflogsumm phpmyadmin procps proftpd-basic
proftpd-mod-mysql python-support sed sensord smartmontools spamassassin
spamc squirrelmail-viewashtml ssh traceroute tzdata ucf udev util-linux
vim-scripts wget xml-core xterm
The following packages are RECOMMENDED but will NOT be installed:
uuid-runtime vim-addon-manager
120 packages upgraded, 7 newly installed, 11 to remove and 0 not upgraded.
Need to get 128MB of archives. After unpacking 35.3MB will be used.
The following packages have unmet dependencies:
mysql-client-5.1: Conflicts: mysql-client-5.0 but 5.0.51a-24+lenny2 is
to be installed.
php5-geoip: Depends: php5-common (= 5.2.11-0.dotdeb.1) but
5.2.11.dfsg.1-1 is installed.
php5-xcache: Depends: php5-common (= 5.2.11-0.dotdeb.1) but
5.2.11.dfsg.1-1 is installed.
php5-imagick: Depends: libmagick10 but it is not installable
Depends: php5-common (= 5.2.11-0.dotdeb.1) but
5.2.11.dfsg.1-1 is installed.
php5-suhosin: Depends: php5-common (= 5.2.11-0.dotdeb.1) but
5.2.11.dfsg.1-1 is installed.
The following actions will resolve these dependencies:
Remove the following packages:
mysql-client
mysql-server
php5-imagick
Keep the following packages at their current version:
mysql-client-5.1 [Not Installed]
mysql-server-5.1 [Not Installed]
php5-geoip [1.0.7-1 (testing, now)]
php5-suhosin [0.9.29-1 (testing, now)]
php5-xcache [1.3.0-1 (testing, now)]
Score is 425
If I try manually to install mysql-server-5.1 this is what aptitude
suggests:
The following packages are BROKEN:
mysql-client mysql-client-5.1 mysql-server-5.0 mysql-server-5.1
The following packages will be REMOVED:
mysql-client-5.0{a}
The following packages will be upgraded:
libmysqlclient16 mysql-common
2 packages upgraded, 2 newly installed, 1 to remove and 119 not upgraded.
Need to get 21.9MB of archives. After unpacking 28.2MB will be used.
The following packages have unmet dependencies:
mysql-client: Depends: mysql-client-5.0 but it is not installable
mysql-server-5.0: Depends: mysql-client-5.0 (= 5.0.51a-24+lenny1) but
it is not installable
mysql-server-5.1: Conflicts: mysql-server ( 5.1.40-0.dotdeb.1) but
5.0.51a-24+lenny1 is installed and it is kept back.
mysql-client-5.1: Conflicts: mysql-client ( 5.1.40-0.dotdeb.1) but
5.0.51a-24+lenny1 is installed and it is kept back.
The following actions will resolve these dependencies:
Remove the following packages:
mysql-server-5.0
Upgrade the following packages:
mysql-client [5.0.51a-24+lenny1 (now) - 5.1.40-0.dotdeb.1 (NULL)]
mysql-server [5.0.51a-24+lenny1 (now) - 5.1.40-0.dotdeb.1 (NULL)]
Score is 259
The db server is way too important to risk losing data and even though I
have a backup it would be a real pain in the ass to restore it.
What I wanted to know is if aptitude, when removing mysql-server-5.0,
keeps the data files and makes them available in v5.1.
Thanks
-rv
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Should I go ahead with the full-upgrade
Raven wrote: Hi all. This is a production server running debian testing. It's been a while and I wanted to update the system. Unfortunately it seems that some packages are BROKEN: your braver than i am. thats the reason why noone should *ever* use testing on a production machine. does it work now? why do you want to update? if it was me, id be backing up the db, installing stable, and restoring the db to that, then let it ride. -- Steve Reilly http://reillyblog.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Should I go ahead with the full-upgrade
Raven wrote: Hi all. This is a production server running debian testing. It's been a while and I wanted to update the system. Unfortunately it seems that some packages are BROKEN: What happens if you just do safe-upgrade instead of full-upgrade? -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Should I go ahead with the full-upgrade
I like a constant upgrade, but still enjoy a stable system. On testing you may have to wait for the new stuff, but eventually, you'll get it, and with some serious bugs already fixed. It's not like waiting in stable for a new release to happen, so if I were you, I'll stick with testing, and keep with it when it gets stable. I use testing, and I'm just on a laptop. Tried once to upgrade to sid and it ended up in a unbootable system. And if you want a new program/feature so bad, why not build it? On Mon, Nov 09, 2009 at 07:28:07PM -0500, H.S. wrote: Raven wrote: Hi all. This is a production server running debian testing. It's been a while and I wanted to update the system. Unfortunately it seems that some packages are BROKEN: What happens if you just do safe-upgrade instead of full-upgrade? -- Why stop now just when I'm hating it? -- Marvin The Paranoid Android -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
