Re: A portupgrade question
On Tue, Apr 25, 2006 at 09:42:44AM +0930, Ian Moore wrote: > So to sum up, it's a problem with the way the ports system detects wether the > mysql-client port is installed that caused the problem (I thought it just > used the ports database), and/or it's a problem with the mysql-client port > not registering libmysqlclient.so ? Using the ports database to determine if a particular piece of software is installed is not terribly robust - what if you installed mysql manually? The ports system would know nothing about it, but you certainly wouldn't want your manually built package to get clobbered because of an apparently failed dependency. Well, that's my take on it, any way. I could be well off the mark. ;-) Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpRmwiKJwCrm.pgp Description: PGP signature
Re: A portupgrade question
On Monday 24 April 2006 23:56, Matthew Seaman wrote: > Ian Moore wrote: > > Hi, I've got a question about portupgrade and something that's happened > > with it a couple of times now. The last 2 times libgda has been upgraded, > > I've run portupgrade -a to upgrade a bunch of ports, including libgda. > > > > The libgda upgrade has caused a re-install of mysql-client-4, but when > > portupgrade has tried to install mysql-client, it's failed because > > mysql-client is already installed. > > > > The workaround for this is simple enough, delete mysql-client and then > > run portupgrade again, but I'm wondering why this situation occurs - > > portupgrade should see that mysql-client is already installed and not try > > to install it again (or if it needs upgrading, it should deinstall the > > old version and build & install the new version). > > > > /etc/ports/UPDATING doesn't seem to help, there's no mention of either > > port in it. > > The reason the ports system can't detect that you've already got > mysql-client software installed is because you haven't got > libmysqlclient.so in your loader cache. Try this command -- you should get > similar output: > > lack-of-gravitas:~:% ldconfig -r | grep mysqlclient > 441:-lmysqlclient_r.14 => > /usr/local/lib/mysql/libmysqlclient_r.so.14 442:-lmysqlclient.14 => > /usr/local/lib/mysql/libmysqlclient.so.14 Nope, I get no output at all! > > ldconfig(8) needs to be told to scan /usr/local/lib/mysql for shared > libraries, as that's not one of the default directories. This is generally > handled through the ldconfig_compat port which installs precisely one file: > > sisyphus:~:% pkg_info -L ldconfig_compat-1.0_7 > Information for ldconfig_compat-1.0_7: > > Files: > //etc/rc.d/ldconfig_compat > Yes, that's what my system shows. > although you can also add /usr/local/lib/mysql to the set of stuff scanned > by ldconfig by modifying variables in /etc/rc.conf (but that's the old and > unfashionable way of doing this...). Re-installing that port and running > > /etc/rc.d/ldconfig_compat start > > should sort out the problem you're seeing. Yes, that sorted things out - libgda installed without trying to re-install mysql40-client this time. > > Note that mergemaster(1) will ask you to delete that file because it's in > /etc/rc.d and it's not one of the one installed by the system. You should > resist the suggestion to do that, or put up with various MySQL (and certain > other port) related things not working in the way you might expect. I'll remember that one. > > Note too: this is system version number dependant -- recent 6.1-STABLE or > above will have the ldconfig_compat script installed in /usr/local/etc/rc.d So to sum up, it's a problem with the way the ports system detects wether the mysql-client port is installed that caused the problem (I thought it just used the ports database), and/or it's a problem with the mysql-client port not registering libmysqlclient.so ? Thanks for your help in sorting that out, I knew it was something more than just not using the recursion switches with portupgrade. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpu7JjmqUBDX.pgp Description: PGP signature
Re: A portupgrade question
On Monday 24 April 2006 21:29, Garrett Cooper wrote: > RW wrote: > >On Monday 24 April 2006 12:50, Richard Collyer wrote: > >>On Mon, April 24, 2006 12:16 pm, Ian Moore wrote: > >>>On Monday 24 April 2006 20:43, Ian Moore wrote: > Hi, I've got a question about portupgrade and something that's happened > with it a couple of times now. The last 2 times libgda has been > upgraded, > I've run portupgrade -a to upgrade a bunch of ports, including libgda. > > > >> > >>I always use portupgrade -aR to make sure dependencies are done. However > >>with mysql I find that portupgrade is not the best. > > > > -a, -ra, -Ra and -RrA all do *exactly* the same thing > > Not true. -a is for all, -r is recursive, -R is upper recursive, and -A > is not even valid given the syntax above... Obviously -RrA was a typo for -Rra, but the rest is correct. If you omit -F and include -a, then the -r and -R options are ignored. Hence -a, -ra, -Ra and -Rra are all equivalent. > All I can say is, "RTFM": portupgrade(1). All I can say is "RTFS": /usr/local/sbin/portupgrade. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A portupgrade question
Ian Moore wrote: On Monday 24 April 2006 22:38, Kevin Kinsey wrote: Ian Moore wrote: Yes, that would fix the problem, but I'm just curious about what causes the problem in the first place, given that portupgrade rarely seems to have these kind of problems. Cheers, ls -l /var/db/pkg/mysql-client*?? total 28 -rw-r--r-- 1 root wheel36B Feb 26 09:08 +COMMENT -rw-r--r-- 1 root wheel 4.0K Apr 23 09:39 +CONTENTS -rw-r--r-- 1 root wheel 167B Feb 26 09:08 +DESC -r--r--r-- 1 root wheel15K Feb 26 09:08 +MTREE_DIRS -rw-r--r-- 1 root wheel57B Apr 23 23:50 +REQUIRED_BY I used to always have trouble compiling packages with -ar or -aR exclusively, but running it like -aRr works like a charm every time (unless the thing gets into a deadlock from dependencies being removed, ie php, apache, and mysql >_<). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A portupgrade question
RW wrote: On Monday 24 April 2006 12:50, Richard Collyer wrote: On Mon, April 24, 2006 12:16 pm, Ian Moore wrote: On Monday 24 April 2006 20:43, Ian Moore wrote: Hi, I've got a question about portupgrade and something that's happened with it a couple of times now. The last 2 times libgda has been upgraded, I've run portupgrade -a to upgrade a bunch of ports, including libgda. I always use portupgrade -aR to make sure dependencies are done. However with mysql I find that portupgrade is not the best. -a, -ra, -Ra and -RrA all do *exactly* the same thing Not true. -a is for all, -r is recursive, -R is upper recursive, and -A is not even valid given the syntax above... All I can say is, "RTFM": portupgrade(1). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A portupgrade question
On Monday 24 April 2006 12:50, Richard Collyer wrote: > On Mon, April 24, 2006 12:16 pm, Ian Moore wrote: > > On Monday 24 April 2006 20:43, Ian Moore wrote: > >> Hi, I've got a question about portupgrade and something that's happened > >> with it a couple of times now. The last 2 times libgda has been > >> upgraded, > >> I've run portupgrade -a to upgrade a bunch of ports, including libgda. > >> > >> > > I always use portupgrade -aR to make sure dependencies are done. However > with mysql I find that portupgrade is not the best. > -a, -ra, -Ra and -RrA all do *exactly* the same thing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A portupgrade question
Ian Moore wrote: > Hi, I've got a question about portupgrade and something that's happened with > it a couple of times now. The last 2 times libgda has been upgraded, I've run > portupgrade -a to upgrade a bunch of ports, including libgda. > > The libgda upgrade has caused a re-install of mysql-client-4, but when > portupgrade has tried to install mysql-client, it's failed because > mysql-client is already installed. > > The workaround for this is simple enough, delete mysql-client and then run > portupgrade again, but I'm wondering why this situation occurs - portupgrade > should see that mysql-client is already installed and not try to install it > again (or if it needs upgrading, it should deinstall the old version and > build & install the new version). > > /etc/ports/UPDATING doesn't seem to help, there's no mention of either port > in > it. The reason the ports system can't detect that you've already got mysql-client software installed is because you haven't got libmysqlclient.so in your loader cache. Try this command -- you should get similar output: lack-of-gravitas:~:% ldconfig -r | grep mysqlclient 441:-lmysqlclient_r.14 => /usr/local/lib/mysql/libmysqlclient_r.so.14 442:-lmysqlclient.14 => /usr/local/lib/mysql/libmysqlclient.so.14 ldconfig(8) needs to be told to scan /usr/local/lib/mysql for shared libraries, as that's not one of the default directories. This is generally handled through the ldconfig_compat port which installs precisely one file: sisyphus:~:% pkg_info -L ldconfig_compat-1.0_7 Information for ldconfig_compat-1.0_7: Files: //etc/rc.d/ldconfig_compat although you can also add /usr/local/lib/mysql to the set of stuff scanned by ldconfig by modifying variables in /etc/rc.conf (but that's the old and unfashionable way of doing this...). Re-installing that port and running /etc/rc.d/ldconfig_compat start should sort out the problem you're seeing. Note that mergemaster(1) will ask you to delete that file because it's in /etc/rc.d and it's not one of the one installed by the system. You should resist the suggestion to do that, or put up with various MySQL (and certain other port) related things not working in the way you might expect. Note too: this is system version number dependant -- recent 6.1-STABLE or above will have the ldconfig_compat script installed in /usr/local/etc/rc.d Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
Re: A portupgrade question
On Monday 24 April 2006 22:38, Kevin Kinsey wrote: > Ian Moore wrote: > >Yes, that would fix the problem, but I'm just curious about what causes > > the problem in the first place, given that portupgrade rarely seems to > > have these kind of problems. > > > >Cheers, > > ls -l /var/db/pkg/mysql-client*?? total 28 -rw-r--r-- 1 root wheel36B Feb 26 09:08 +COMMENT -rw-r--r-- 1 root wheel 4.0K Apr 23 09:39 +CONTENTS -rw-r--r-- 1 root wheel 167B Feb 26 09:08 +DESC -r--r--r-- 1 root wheel15K Feb 26 09:08 +MTREE_DIRS -rw-r--r-- 1 root wheel57B Apr 23 23:50 +REQUIRED_BY -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpggKDD0WYNd.pgp Description: PGP signature
Re: A portupgrade question
Ian Moore wrote: Yes, that would fix the problem, but I'm just curious about what causes the problem in the first place, given that portupgrade rarely seems to have these kind of problems. Cheers, ls -l /var/db/pkg/mysql-client*?? Kevin Kinsey -- A method of solution is perfect if we can forsee from the start, and even prove, that following that method we shall attain our aim. -- Leibnitz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A portupgrade question
I have: FORCE_PKG_REGISTER=YES in /etc/make.conf for portupgrade or if I need to re-install a port manually. -Derek At 06:16 AM 4/24/2006, Ian Moore wrote: On Monday 24 April 2006 20:43, Ian Moore wrote: > Hi, I've got a question about portupgrade and something that's happened > with it a couple of times now. The last 2 times libgda has been upgraded, > I've run portupgrade -a to upgrade a bunch of ports, including libgda. > Sorry, I forgot to add the output of the portupgrade sessions: The first time it happened: ---> Upgrading 'libgda2-1.9.100_2' to 'libgda3-1.9.102' (databases/libgda3) ---> Building '/usr/ports/databases/libgda3' ===> Cleaning for gmake-3.80_2 ===> Cleaning for intltool-0.34.2 ===> Cleaning for pkgconfig-0.20 ===> Cleaning for popt-1.7_1 ===> Cleaning for gettext-0.14.5_2 ===> Cleaning for mysql-client-4.0.26_1 ===> Cleaning for glib-2.8.6_1 ===> Cleaning for libxml2-2.6.23_1 ===> Cleaning for libxslt-1.1.15_1 ===> Cleaning for xorg-libraries-6.9.0 ===> Cleaning for gnomehier-2.0_7 ===> Cleaning for perl-5.8.8 ===> Cleaning for p5-XML-Parser-2.34_2 ===> Cleaning for libiconv-1.9.2_2 ===> Cleaning for libtool-1.5.22_2 ===> Cleaning for ldconfig_compat-1.0_6 ===> Cleaning for libgcrypt-1.2.2 ===> Cleaning for imake-6.9.0 ===> Cleaning for libdrm-2.0_1 ===> Cleaning for freetype2-2.1.10_3 ===> Cleaning for fontconfig-2.3.2_3,1 ===> Cleaning for expat-2.0.0_1 ===> Cleaning for libgpg-error-1.1 ===> Cleaning for libgda3-1.9.102 You can enable support for LDAP databases by defining WITH_LDAP. You can enable support for TDS databases by defining WITH_FREETDS. You can enable support for Sybase databases by defining WITH_SYBASE. You can enable support for MDB databases by defining WITH_MDB. You can enable support for ODBC databases by defining WITH_ODBC. You can enable support for SQLITE databases by defining WITH_SQLITE. ===> Extracting for libgda3-1.9.102 => MD5 Checksum OK for gnome2/libgda-1.9.102.tar.bz2. ===> Patching for libgda3-1.9.102 ===> Applying FreeBSD patches for libgda3-1.9.102 ===> libgda3-1.9.102 depends on executable: gmake - found ===> libgda3-1.9.102 depends on file: /usr/local/bin/intltool-extract - found ===> libgda3-1.9.102 depends on executable: pkg-config - found ===> libgda3-1.9.102 depends on shared library: popt.0 - found ===> libgda3-1.9.102 depends on shared library: intl - found ===> libgda3-1.9.102 depends on shared library: mysqlclient.12 - not found ===>Verifying install for mysqlclient.12 in /usr/ports/databases/mysql40-client ===> Extracting for mysql-client-4.0.26_1 => MD5 Checksum OK for mysql-4.0.26.tar.gz. ===> Patching for mysql-client-4.0.26_1 ===> Applying FreeBSD patches for mysql-client-4.0.26_1 ===> mysql-client-4.0.26_1 depends on file: /usr/local/bin/libtool - found ===> Configuring for mysql-client-4.0.26_1 checking build system type... i386-portbld-freebsd5.4 checking host system type... i386-portbld-freebsd5.4 /bin/mv mysqlshow.1-t mysqlshow.1 ===> Installing for mysql-client-4.0.26_1 ===> mysql-client-4.0.26_1 depends on file: /usr/local/libdata/ldconfig - found ===> Generating temporary packing list ===> Checking if databases/mysql40-client already installed ===> mysql-client-4.0.26_1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of databases/mysql40-client without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 And the second time (sorry, I only have the last part) /bin/mv mysqlshow.1-t mysqlshow.1 ===> Installing for mysql-client-4.0.26_1 ===> mysql-client-4.0.26_1 depends on file: /usr/local/libdata/ldconfig - foun d ===> Generating temporary packing list ===> Checking if databases/mysql40-client already installed ===> mysql-client-4.0.26_1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of databases/mysql40-client without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A portupgrade question
On Monday 24 April 2006 21:20, Richard Collyer wrote: > On Mon, April 24, 2006 12:16 pm, Ian Moore wrote: > >> Hi, I've got a question about portupgrade and something that's happened > >> with it a couple of times now. The last 2 times libgda has been > >> upgraded, > >> I've run portupgrade -a to upgrade a bunch of ports, including libgda. > >> > >> > > I always use portupgrade -aR to make sure dependencies are done. However > with mysql I find that portupgrade is not the best. > > Personally I would update ports tree (cvsup), cd to mysql ports directory, > make clean && make && make deinstall && make reinstall > > Never had a problem doing it that way. Yes, that would fix the problem, but I'm just curious about what causes the problem in the first place, given that portupgrade rarely seems to have these kind of problems. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpxZwzPaKJ9q.pgp Description: PGP signature
Re: A portupgrade question
On Mon, April 24, 2006 12:16 pm, Ian Moore wrote: > On Monday 24 April 2006 20:43, Ian Moore wrote: >> Hi, I've got a question about portupgrade and something that's happened >> with it a couple of times now. The last 2 times libgda has been >> upgraded, >> I've run portupgrade -a to upgrade a bunch of ports, including libgda. >> >> I always use portupgrade -aR to make sure dependencies are done. However with mysql I find that portupgrade is not the best. Personally I would update ports tree (cvsup), cd to mysql ports directory, make clean && make && make deinstall && make reinstall Never had a problem doing it that way. -- Richard Collyer [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A portupgrade question
On Monday 24 April 2006 20:43, Ian Moore wrote: > Hi, I've got a question about portupgrade and something that's happened > with it a couple of times now. The last 2 times libgda has been upgraded, > I've run portupgrade -a to upgrade a bunch of ports, including libgda. > Sorry, I forgot to add the output of the portupgrade sessions: The first time it happened: ---> Upgrading 'libgda2-1.9.100_2' to 'libgda3-1.9.102' (databases/libgda3) ---> Building '/usr/ports/databases/libgda3' ===> Cleaning for gmake-3.80_2 ===> Cleaning for intltool-0.34.2 ===> Cleaning for pkgconfig-0.20 ===> Cleaning for popt-1.7_1 ===> Cleaning for gettext-0.14.5_2 ===> Cleaning for mysql-client-4.0.26_1 ===> Cleaning for glib-2.8.6_1 ===> Cleaning for libxml2-2.6.23_1 ===> Cleaning for libxslt-1.1.15_1 ===> Cleaning for xorg-libraries-6.9.0 ===> Cleaning for gnomehier-2.0_7 ===> Cleaning for perl-5.8.8 ===> Cleaning for p5-XML-Parser-2.34_2 ===> Cleaning for libiconv-1.9.2_2 ===> Cleaning for libtool-1.5.22_2 ===> Cleaning for ldconfig_compat-1.0_6 ===> Cleaning for libgcrypt-1.2.2 ===> Cleaning for imake-6.9.0 ===> Cleaning for libdrm-2.0_1 ===> Cleaning for freetype2-2.1.10_3 ===> Cleaning for fontconfig-2.3.2_3,1 ===> Cleaning for expat-2.0.0_1 ===> Cleaning for libgpg-error-1.1 ===> Cleaning for libgda3-1.9.102 You can enable support for LDAP databases by defining WITH_LDAP. You can enable support for TDS databases by defining WITH_FREETDS. You can enable support for Sybase databases by defining WITH_SYBASE. You can enable support for MDB databases by defining WITH_MDB. You can enable support for ODBC databases by defining WITH_ODBC. You can enable support for SQLITE databases by defining WITH_SQLITE. ===> Extracting for libgda3-1.9.102 => MD5 Checksum OK for gnome2/libgda-1.9.102.tar.bz2. ===> Patching for libgda3-1.9.102 ===> Applying FreeBSD patches for libgda3-1.9.102 ===> libgda3-1.9.102 depends on executable: gmake - found ===> libgda3-1.9.102 depends on file: /usr/local/bin/intltool-extract - found ===> libgda3-1.9.102 depends on executable: pkg-config - found ===> libgda3-1.9.102 depends on shared library: popt.0 - found ===> libgda3-1.9.102 depends on shared library: intl - found ===> libgda3-1.9.102 depends on shared library: mysqlclient.12 - not found ===>Verifying install for mysqlclient.12 in /usr/ports/databases/mysql40-client ===> Extracting for mysql-client-4.0.26_1 => MD5 Checksum OK for mysql-4.0.26.tar.gz. ===> Patching for mysql-client-4.0.26_1 ===> Applying FreeBSD patches for mysql-client-4.0.26_1 ===> mysql-client-4.0.26_1 depends on file: /usr/local/bin/libtool - found ===> Configuring for mysql-client-4.0.26_1 checking build system type... i386-portbld-freebsd5.4 checking host system type... i386-portbld-freebsd5.4 /bin/mv mysqlshow.1-t mysqlshow.1 ===> Installing for mysql-client-4.0.26_1 ===> mysql-client-4.0.26_1 depends on file: /usr/local/libdata/ldconfig - found ===> Generating temporary packing list ===> Checking if databases/mysql40-client already installed ===> mysql-client-4.0.26_1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of databases/mysql40-client without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 And the second time (sorry, I only have the last part) /bin/mv mysqlshow.1-t mysqlshow.1 ===> Installing for mysql-client-4.0.26_1 ===> mysql-client-4.0.26_1 depends on file: /usr/local/libdata/ldconfig - foun d ===> Generating temporary packing list ===> Checking if databases/mysql40-client already installed ===> mysql-client-4.0.26_1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of databases/mysql40-client without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgp8fdpUwrPMz.pgp Description: PGP signature
A portupgrade question
Hi, I've got a question about portupgrade and something that's happened with it a couple of times now. The last 2 times libgda has been upgraded, I've run portupgrade -a to upgrade a bunch of ports, including libgda. The libgda upgrade has caused a re-install of mysql-client-4, but when portupgrade has tried to install mysql-client, it's failed because mysql-client is already installed. The workaround for this is simple enough, delete mysql-client and then run portupgrade again, but I'm wondering why this situation occurs - portupgrade should see that mysql-client is already installed and not try to install it again (or if it needs upgrading, it should deinstall the old version and build & install the new version). /etc/ports/UPDATING doesn't seem to help, there's no mention of either port in it. Perhaps my ports db is screwed up? Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpw2ttWn06DJ.pgp Description: PGP signature
