Re: FTP and WordPress in mac ports environment
On 6/14/12 1:28 PM, Rainer Müller wrote: On 2012-06-14 19:54, Érico wrote: And my environment is the following : apache2 @2.2.22_2+preforkmpm (active) php5 @5.3.12_0+apache2 (active) wordpress @3.2.1_0 (active) Do I need to set something for SSH on it ? As I said nothing works with FTP ... I mean , plugin install, plugin updates, themes install, wordpress upgrade , etc ... I don't think you are running a FTP server, are you? At least you did not mention which FTP server you would be using or how you configured it... However, I guess you don't want to operate a FTP server at all and rather should set the FS_METHOD in your wp-config.php to 'direct'. This selects a mode in which files are manipulated directly without relying on a FTP connection. Doesn't the FS_METHOD = direct setting open you up to huge security holes? So says the codex... I would love to be able to have one-click updating on all of my 50+ wordpress installs, but I'm not willing to chance the security problems. If someone has a better way, I'd love to hear it. The only thing I've ever gotten out of the WordPress forums is it's a server thing. Despite my already having stated that I'm running the dang server. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: FTP and WordPress in mac ports environment
Bill Christensen wrote: I would love to be able to have one-click updating on all of my 50+ wordpress installs, but I'm not willing to chance the security problems. If someone has a better way, I'd love to hear it. The only thing I've ever gotten out of the WordPress forums is it's a server thing. Despite my already having stated that I'm running the dang server. Let me get this straight : + you are running your very own dang Apache2 server + you've got 50 individual installs of WordPress + you'ld like to upgrade all instances of WP in one go Some scripting ought to be able to fix that problem. Qs : + do you have a logical/similiar file structure for where the WPs are installed like eg Sites/gTLD/domain/server/wp/ for all the WP installs ? A pseudo alogrithm for this could look like this: for each WPsite do remove old WPfiles copy new WPfiles done -or- for each WPsite do overwrite with new WPfiles done -- Bjarne D Mathiesen København N ; Danmark ; Europa -- denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.7.4 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: FTP and WordPress in mac ports environment
On Jun 14, 2012, at 11:29 AM, Érico wrote: Hello I am using the mac os 10.6.8 default FTP : You may want to try pure-ftpd with virtual users. $ port info pure-ftpd Regards, Bradley Giesbrecht (pixilla) smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: FTP and WordPress in mac ports environment
On Jun 25, 2012, at 11:11 PM, Bill Christensen wrote: On 6/14/12 1:28 PM, Rainer Müller wrote: On 2012-06-14 19:54, Érico wrote: And my environment is the following : apache2 @2.2.22_2+preforkmpm (active) php5 @5.3.12_0+apache2 (active) wordpress @3.2.1_0 (active) Do I need to set something for SSH on it ? As I said nothing works with FTP ... I mean , plugin install, plugin updates, themes install, wordpress upgrade , etc ... I don't think you are running a FTP server, are you? At least you did not mention which FTP server you would be using or how you configured it... However, I guess you don't want to operate a FTP server at all and rather should set the FS_METHOD in your wp-config.php to 'direct'. This selects a mode in which files are manipulated directly without relying on a FTP connection. Doesn't the FS_METHOD = direct setting open you up to huge security holes? So says the codex... I would love to be able to have one-click updating on all of my 50+ wordpress installs, but I'm not willing to chance the security problems. If someone has a better way, I'd love to hear it. The only thing I've ever gotten out of the WordPress forums is it's a server thing. Despite my already having stated that I'm running the dang server. http://lmgtfy.com/?q=upgrade+multiple+wordpress+installs I clicked this link from above google query: http://wordpress.org/support/topic/how-to-upgrade-multiple-wordpress-blogs Toward the bottom of the page above svn is suggested and another person posted a link to his svn script. Regards, Bradley Giesbrecht (pixilla) smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
How to clean registry
How
to clean this up? I started to uninstall inactive ports, but interrupted that,
and got an error message (I did not pick that up), some SQLite error, IIRC.
Now, with some ports (some behave beautifully) I get the following:
an invalid entry was passed
while executing
$dependent name
(procedure receipt_sqlite::list_dependents line 18)
invoked from within
${macports::registry.format}::list_dependents $name $version $revision
$variants
(procedure registry::list_dependents line 3)
invoked from within
registry::list_dependents $pvals(name)
(procedure portlist_sortdependents line 7)
invoked from within
portlist_sortdependents $portlist
(procedure action_uninstall line 17)
invoked from within
$action_proc $action $portlist [array get global_options]
(procedure process_cmd line 95)
invoked from within
process_cmd $remaining_args
invoked from within
if { [llength $remaining_args] 0 } {
# If there are remaining arguments, process those as a command
set exit_status [process_cmd $remaining...
(file /opt/local/bin/port line 4784)
So, do I have to clean registry.db or receipts.db manually, or is there some
cleaning operation already that I do not know of?
!
! Jyrki Wahlstedt
! http://www.wahlstedt.fi/jyrki/
!
! Our life is no dream; but it ought to become one and perhaps will.
! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9
139C C386
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to clean registry
On Jun 26, 2012, at 11:24, Wahlstedt Jyrki wrote:
How
to clean this up? I started to uninstall inactive ports, but interrupted
that, and got an error message (I did not pick that up), some SQLite error,
IIRC. Now, with some ports (some behave beautifully) I get the following:
an invalid entry was passed
while executing
$dependent name
(procedure receipt_sqlite::list_dependents line 18)
invoked from within
${macports::registry.format}::list_dependents $name $version $revision
$variants
(procedure registry::list_dependents line 3)
invoked from within
registry::list_dependents $pvals(name)
(procedure portlist_sortdependents line 7)
invoked from within
portlist_sortdependents $portlist
(procedure action_uninstall line 17)
invoked from within
$action_proc $action $portlist [array get global_options]
(procedure process_cmd line 95)
invoked from within
process_cmd $remaining_args
invoked from within
if { [llength $remaining_args] 0 } {
# If there are remaining arguments, process those as a command
set exit_status [process_cmd $remaining...
(file /opt/local/bin/port line 4784)
So, do I have to clean registry.db or receipts.db manually, or is there some
cleaning operation already that I do not know of?
I don't know how to clean or fix the registry. What command(s) lead to the
error message you showed above? Some registry problems get cleaned up
automatically next time you use any port command, but only if MacPorts has
write access to the repository, meaning try using sudo port info zlib or
something and see if that helps.
To avoid problems in the future, don't interrupt MacPorts when it's
uninstalling ports. Or when it's activating or deactivating.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to clean registry
On Jun 26, 2012, at 16:53, Ryan Schmidt wrote: but only if MacPorts has write access to the repository *registry, not repository ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
perl5* and p5* ports updated; ignore the warnings when you upgrade
Joshua committed a big update to all of the perl ports and modules in MacPorts today in r94655. (Thanks, Joshua!) As a result when you run sudo port selfupdate and port outdated, you'll find all perl and p5 ports need to be upgraded. When you upgrade the p5 ports, you may see warning messages like these: --- Computing dependencies for p5.12-locale-gettext --- Fetching distfiles for p5.12-locale-gettext --- Verifying checksum(s) for p5.12-locale-gettext --- Extracting p5.12-locale-gettext --- Applying patches to p5.12-locale-gettext --- Configuring p5.12-locale-gettext --- Building p5.12-locale-gettext --- Staging p5.12-locale-gettext into destroot --- Installing p5.12-locale-gettext @1.50.0_7 --- Cleaning p5.12-locale-gettext --- Computing dependencies for p5.12-locale-gettext Warning: Failed to open Portfile from registry for p5.12-locale-gettext @1.50.0_6 --- Deactivating p5.12-locale-gettext @1.50.0_6 --- Activating p5.12-locale-gettext @1.50.0_7 --- Cleaning p5.12-locale-gettext Warning: Failed to open Portfile from registry for p5.12-locale-gettext @1.50.0_6 --- Uninstalling p5.12-locale-gettext @1.50.0_6 Ignore the warnings; they are harmless. When you originally installed these ports (or any port), a copy of the portfile was placed in the registry. And when you upgrade or uninstall a port, MacPorts tries to use that old copy of the portfile to perform any custom deactivation instructions. But the old p5 portfiles are not compatible with the changes that have just occurred in the perl5 portgroup; therefore MacPorts prints the warnings. You can ignore the warnings because none of the p5 ports contain any custom deactivation instructions. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
valgrind configure error on Lion
Hi, Please see the following: version:1 :msg:clean --- Computing dependencies for valgrind:info:clean .:debug:clean Checking for conflicts against valgrind :debug:clean Searching for dependency: valgrind-devel :debug:clean Didn't find receipt, going to depspec regex for: valgrind-devel :debug:clean Searching for dependency: perl5 :debug:clean Found Dependency: receipt exists for perl5 :msg:clean :debug:main Executing org.macports.main (valgrind) :debug:main changing euid/egid - current euid: 0 - current egid: 0 :debug:main egid changed to: 501 :debug:main euid changed to: 502 :debug:main Skipping completed org.macports.archivefetch (valgrind) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.fetch (valgrind) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.checksum (valgrind) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.extract (valgrind) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.patch (valgrind) :debug:main Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Wed Jun 27 10:55:15 HKT 2012 :notice:configure --- Configuring valgrind :debug:configure Using compiler 'Mac OS X clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Executing org.macports.configure (valgrind) :debug:configure Environment: CPATH='/opt/local/include' CFLAGS='-pipe -O2' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2 -arch x86_64' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.7' CXX='/usr/bin/clang++' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_valgrind/valgrind/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2 -m64' LDFLAGS='-L/opt/local/lib' OBJC='/usr/bin/clang' FCFLAGS='-pipe -O2 -m64' INSTALL='/usr/bin/install -c' OBJCFLAGS='-pipe -O2 -arch x86_64' FFLAGS='-pipe -O2 -m64' CC_PRINT_OPTIONS='YES' CC='/usr/bin/clang' :debug:configure Assembled command: 'cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_valgrind/valgrind/work/valgrind-3.7.0 ./configure --prefix=/opt/local --mandir=/opt/local/share/man --without-mpicc --enable-only64bit' :debug:configure Executing command line: cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_valgrind/valgrind/work/valgrind-3.7.0 ./configure --prefix=/opt/local --mandir=/opt/local/share/man --without-mpicc --enable-only64bit :info:configure checking for a BSD-compatible install... /usr/bin/install -c :info:configure checking whether build environment is sane... yes :info:configure checking for a thread-safe mkdir -p... ./install-sh -c -d :info:configure checking for gawk... gawk :info:configure checking whether make sets $(MAKE)... yes :info:configure checking whether to enable maintainer-specific portions of Makefiles... no :info:configure checking whether ln -s works... yes :info:configure checking for gcc... /usr/bin/clang :info:configure checking whether the C compiler works... yes :info:configure checking for C compiler default output file name... a.out :info:configure checking for suffix of executables... :info:configure checking whether we are cross compiling... no :info:configure checking for suffix of object files... o :info:configure checking whether we are using the GNU C compiler... yes :info:configure checking whether /usr/bin/clang accepts -g... yes :info:configure checking for /usr/bin/clang option to accept ISO C89... none needed :info:configure checking for style of include used by make... GNU :info:configure checking dependency style of /usr/bin/clang... gcc3 :info:configure checking whether /usr/bin/clang and cc understand -c and -o together... yes :info:configure checking how to run the C preprocessor... /usr/bin/clang -E :info:configure checking whether we are using the GNU C++ compiler... yes :info:configure checking whether /usr/bin/clang++ accepts -g... yes :info:configure checking dependency style of /usr/bin/clang++... gcc3 :info:configure checking for ranlib... ranlib :info:configure checking for a sed that does not truncate output... /opt/local/bin/gsed :info:configure checking for ar... /opt/local/bin/ar :info:configure checking for perl... /opt/local/bin/perl :info:configure checking for gdb... /usr/bin/gdb :info:configure checking dependency style of /usr/bin/clang... gcc3 :info:configure checking for diff -u... yes :info:configure checking for a supported version of gcc... no (2.1) :info:configure configure: error: please use gcc = 3.0 or clang = 2.9 :info:configure Command failed: cd
Re: valgrind configure error on Lion
On Jun 26, 2012, at 22:30, Wu Degang wrote: :info:configure checking for a supported version of gcc... no (2.1) :info:configure configure: error: please use gcc = 3.0 or clang = 2.9 This looks similar to this ticket: https://trac.macports.org/ticket/32994 Valgrind's compiler version detection seems to be rather brittle. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
