MariaDB won't start
I can't get online with the machine I'm trying to use MariaDB on, so I won't quote the full text of the messages. But if you need me to I can transfer them on a stick. $ port info mariadb mariadb @5.5.34_1 Mac OS X 10.8.4 on a Retina Display MacBook Pro, Early 2013, Model Identifier MacBookPro10,1. mysqld_safe indicates a successful startup, but ps -ef | grep doesn't find any processes with mysql or maria in their names. There is only one zero-length file in /opt/local/var/log/mariadb, rather curiously named something like .turd_mariadb_server. No actual log text. I found a post advising the check the ownership and groups on the log and some other directories were both _mysql. They are. If I have to put my MariaDB Mac back on the line, it will need to wait until tomorrow when I can go to a wifi spot. But I'm in no real hurry. I just want to learn SQL out of a book, and need MariaDB to do the exercises. Thanks for any help you can give me. Mike -- Michael David Crawford mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Mobile Development in the Portland, Oregon Metropolitan Area. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9
On Tuesday February 18 2014 22:10:53 Ryan Schmidt wrote: Things started out fine, but somehow I found myself with a 64bit-only libiconv (despite the fact that the database told me I had the universal variant, as requested), which of course gave problems. Couldn't figure out how to force-reinstall the port, For future reference: sudo port -ns upgrade --force libiconv Thanks. I tried with -f and possibly even with -n, but that resulted just in the usual post-install scan of the database. MacPorts does not have the capability to re-install older versions of ports; if you want that you have to follow the instructions in the howto/InstallingOlderPort wiki page. So no, the instructions will only leave you with the latest version of each port, because that’s all that MacPorts knows how to install. Good to know, also as a reminder not to uninstall older versions immediately after each upgrade as apparently there's no (easy) way back! R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
So I uninstalled and cleaned my MacPorts installation as instructed and the called restore.tcl . Now builds are failing with :debug:extract Executing command line: cd /Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_devel_bsdmake/bsdmake/work /usr/bin/gzip -dc '/Volumes/Debian/MacPorts/var/macports/distfiles/bsdmake/bsdmake-24.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - :info:extract sh: /usr/bin/gnutar: No such file or directory Indeed I have no /usr/bin/gnutar, and I don't see where in the MacPorts conf files this parameters is set? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 8:27 AM, René J.V. Bertin rjvber...@gmail.com wrote: So I uninstalled and cleaned my MacPorts installation as instructed and the called restore.tcl . Now builds are failing with :debug:extract Executing command line: cd /Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_devel_bsdmake/bsdmake/work /usr/bin/gzip -dc '/Volumes/Debian/MacPorts/var/macports/distfiles/bsdmake/bsdmake-24.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - :info:extract sh: /usr/bin/gnutar: No such file or directory Indeed I have no /usr/bin/gnutar, and I don't see where in the MacPorts conf files this parameters is set? you didn't follow the Migration instructions correctly, specifically you missed https://trac.macports.org/wiki/Migration#ReinstallMacPorts [MacPorts picks up which tar/gnutar to use at install time] -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Wed, Feb 19, 2014 at 8:27 AM, René J.V. Bertin rjvber...@gmail.comwrote: So I uninstalled and cleaned my MacPorts installation as instructed and the called restore.tcl . Now builds are failing with :debug:extract Executing command line: cd /Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_devel_bsdmake/bsdmake/work /usr/bin/gzip -dc '/Volumes/Debian/MacPorts/var/macports/distfiles/bsdmake/bsdmake-24.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - :info:extract sh: /usr/bin/gnutar: No such file or directory Indeed I have no /usr/bin/gnutar, and I don't see where in the MacPorts conf files this parameters is set? Did you reinstall or upgrade the MacPorts base? Installing the latest MacPorts for Mavericks will fix this; upgrading the existing base (`sudo port selfupdate`) should detect it during configure and deal with it (but if you did that and it didn't, please file a bug on trac.macports.org). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
Hi, Did you reinstall or upgrade the MacPorts base? Installing the latest MacPorts for Mavericks will fix this; upgrading the existing base (`sudo port selfupdate`) should detect it during configure and deal with it (but if you did that and it didn't, please file a bug on trac.macports.org ). `sudo port selfupdate` will only fix this, if the current version of base is actually outdated, i.e. if you had 2.2.0 installed before upgrading to Mavericks. If you already had 2.2.1 installed before the OS upgrade, selfupdate will not reconfigure/rebuild and this will not work. That's why I suggested using `sudo port -f selfupdate`, which skips the version check and forces the rebuild, but I now realize this might not have triggered a re-configure either. I guess the selfupdate action should check whether current base has been built on an older OS and trigger the rebuild if it was. I know we recently added a field for the OS version when base was built, but I'm not sure we already trigger selfupdate on OS version mismatch. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MariaDB won't start
On Wed, Feb 19, 2014 at 3:08 AM, Michael Crawford mdcrawf...@gmail.comwrote: I can't get online with the machine I'm trying to use MariaDB on, so I won't quote the full text of the messages. But if you need me to I can transfer them on a stick. $ port info mariadb mariadb @5.5.34_1 Have you installed mariadb-server? Without it, you get the server components but not the configuration or the glue to start them properly. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 15:37, Clemens Lang wrote: this will not work. That's why I suggested using `sudo port -f selfupdate`, which skips the version check and forces the rebuild, but I now realize this might not have triggered a re-configure either. I guess the selfupdate action should check whether current base has been built on an older OS and trigger the rebuild if it was. I know we recently added a field for the OS version when base was built, but I'm not sure we already trigger selfupdate on OS version mismatch. In the end it must have come through. I've configured MacPorts to run install as a normal user (meaning I did the selfupdate without sudo, clearly that wasn't the best idea), and I also had to move a couple of older gnutar variants out of the path. Things are building now, I suppose using the system tar command. We'll see how far the process goes! Thanks for the suggestions in any case! R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 08:37, Clemens Lang wrote: `sudo port selfupdate` will only fix this, if the current version of base is actually outdated, i.e. if you had 2.2.0 installed before upgrading to Mavericks. If you already had 2.2.1 installed before the OS upgrade, selfupdate will not reconfigure/rebuild and this will not work. That's why I suggested using `sudo port -f selfupdate`, which skips the version check and forces the rebuild, but I now realize this might not have triggered a re-configure either. Why wouldn’t “sudo port -f selfupdate have triggered a re-configure and re-build? I thought that’s exactly what it would do. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MariaDB won't start
On Feb 19, 2014, at 02:08, Michael Crawford wrote: $ port info mariadb mariadb @5.5.34_1 FYI, “port info” tells you what’s available, not what’s installed. “port installed” tells you what you actually have installed. There is only one zero-length file in /opt/local/var/log/mariadb, rather curiously named something like .turd_mariadb_server. No actual log text. This is not curious. MacPorts uses empty .turd files to mark directories that should not be deleted. (During installs, MacPorts deletes directories that are empty; by putting a .turd file (or any file) in a directory, this makes it non-empty so MacPorts doesn’t delete it.) The command used in Portfiles to create .turd files is destroot.keepdirs. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
Hi, Why wouldn’t “sudo port -f selfupdate have triggered a re-configure and re-build? I thought that’s exactly what it would do. It would certainly trigger a rebuild, I'm just not sure it would trigger a re-configure. If the files generated by configure were still in place and newer than the configure script, a re-configure might not happen unless you run make distclean first. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
Just saw --- Fetching distfiles for libstdcxx --- Verifying checksums for libstdcxx --- Extracting libstdcxx --- Configuring libstdcxx Error: libstdcxx has been made obsolete by the port libgcc. Please install libgcc instead. Error: org.macports.configure for port libstdcxx returned: obsolete port Please see the log file for port libstdcxx for details: /Volumes/Debian/MacPorts/var/macports/logs/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_lang_libstdcxx/libstdcxx/main.log popping up. The script is continuing, can I presume that libgcc will get installed automatically? R ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 12:05, René J.V. Bertin rjvber...@gmail.com wrote: Just saw --- Fetching distfiles for libstdcxx --- Verifying checksums for libstdcxx --- Extracting libstdcxx --- Configuring libstdcxx Error: libstdcxx has been made obsolete by the port libgcc. Please install libgcc instead. Error: org.macports.configure for port libstdcxx returned: obsolete port Please see the log file for port libstdcxx for details: /Volumes/Debian/MacPorts/var/macports/logs/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_lang_libstdcxx/libstdcxx/main.log popping up. The script is continuing, can I presume that libgcc will get installed automatically? Sure, if libgcc is required by another port you’re installing (i.e. any of the gcc4x ports). ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
imagemagick with pdf
Does anybody get the following failure with using imagemagick on pdf's? (install ghostscript first) $ convert Children.pdf[0] yo.jpg convert: unable to load module `/opt/rdp_project_local/lib/ImageMagick-6.8.0/modules-Q16/coders/pdf.la': file not found @ error/module.c/OpenModule/1278. convert: no decode delegate for this image format `Children.pdf' @ error/constitute.c/ReadImage/550. Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: imagemagick with pdf
Roger, I have ghostscript installed, but port contents ghostscript | grep convert yields nothing. What do which convert and type convert yield for you? -Sterling On Feb 19, 2014, at 5:00PM, Roger Pack wrote: Does anybody get the following failure with using imagemagick on pdf's? (install ghostscript first) $ convert Children.pdf[0] yo.jpg convert: unable to load module `/opt/rdp_project_local/lib/ImageMagick-6.8.0/modules-Q16/coders/pdf.la': file not found @ error/module.c/OpenModule/1278. convert: no decode delegate for this image format `Children.pdf' @ error/constitute.c/ReadImage/550. Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
