Re: Install older subversion version

[Jasper Frumau]

Installed Easy SVN and added that repository. Still getting:
This client is too old to work with working copy '/opt/local/www/site'.
You need
to get a newer Subversion client, or to downgrade this working copy.
See http://subversion.tigris.org/faq.html#working-copy-format-change
for details.
The tool /usr/local/bin/change-svn-wc-format.py
may be used to convert this working copy to match this SCPlugin (see
'About'),
but you will loose any features of the newer Subversion you may be using.

The tool cannot be used I understood as the latest MacPorts version is
1.7.7 ..




On Mon, Oct 22, 2012 at 1:22 PM, Jasper Frumau wrote:

> Thanks. Checking out Easy SVN now.
>
>
> On Mon, Oct 22, 2012 at 1:02 PM,  wrote:
>
>> Am 22.10.2012 um 07:46 schrieb Jasper Frumau:
>> >
>> > Hi veryone,
>> >
>> > I am working on a site usinf SVN , making changes locally and uploading
>> them. Doing this mainly from the command line, but wanted to use SCPlugin
>> to do commits from a finder window. I got this warning:
>> > This client is too old to work with working copy '/opt/local/www/site'.
>>  You need
>> > to get a newer Subversion client, or to downgrade this working copy.
>>
>> See the thread
>>
>> http://scplugin.tigris.org/ds/viewMessage.do?dsForumId=1525&dsMessageId=2870525
>> and
>>
>> http://scplugin.tigris.org/ds/viewMessage.do?dsForumId=1525&dsMessageId=2972465
>> and this:
>> http://svn-ref.assembla.com/easysvn.html
>
>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Install older subversion version

[Jasper Frumau]

Thanks. Checking out Easy SVN now.

On Mon, Oct 22, 2012 at 1:02 PM,  wrote:

> Am 22.10.2012 um 07:46 schrieb Jasper Frumau:
> >
> > Hi veryone,
> >
> > I am working on a site usinf SVN , making changes locally and uploading
> them. Doing this mainly from the command line, but wanted to use SCPlugin
> to do commits from a finder window. I got this warning:
> > This client is too old to work with working copy '/opt/local/www/site'.
>  You need
> > to get a newer Subversion client, or to downgrade this working copy.
>
> See the thread
>
> http://scplugin.tigris.org/ds/viewMessage.do?dsForumId=1525&dsMessageId=2870525
> and
>
> http://scplugin.tigris.org/ds/viewMessage.do?dsForumId=1525&dsMessageId=2972465
> and this:
> http://svn-ref.assembla.com/easysvn.html
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Install older subversion version

[sierkb]

Am 22.10.2012 um 07:46 schrieb Jasper Frumau:
> 
> Hi veryone,
> 
> I am working on a site usinf SVN , making changes locally and uploading them. 
> Doing this mainly from the command line, but wanted to use SCPlugin to do 
> commits from a finder window. I got this warning:
> This client is too old to work with working copy '/opt/local/www/site'.  You 
> need
> to get a newer Subversion client, or to downgrade this working copy.

See the thread
http://scplugin.tigris.org/ds/viewMessage.do?dsForumId=1525&dsMessageId=2870525
and
http://scplugin.tigris.org/ds/viewMessage.do?dsForumId=1525&dsMessageId=2972465
and this:
http://svn-ref.assembla.com/easysvn.html
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: shell command failed

[Ryan Schmidt]

On Oct 21, 2012, at 23:06, Felix Drud wrote:

> Ryan Schmidt wrote:

> 
>> On Oct 20, 2012, at 17:52, Felix Emil Drud wrote:
>> 
>>> sudo port -f uninstall db46
>>> sudo port clean --all db46
>>> sudo port install db46
>>> 
>>> I did this but received the following error, when executing the last 
>>> command:
>>> http://pastebin.com/i4ZN6w1S
>> 
>> This log says:
>> 
>> :info:configure configure: error: C compiler cannot create executables
>> :info:configure See `config.log' for more details.
>> 
>> Seeing that config.log file might tell us more about why it failed.
> 
> Any idea where I can find the config.log file?

Yes, it is in the directory identified by the command:

port work db46



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: shell command failed

[Felix Drud]

> On Oct 20, 2012, at 17:52, Felix Emil Drud wrote:
>
>> I was trying to install pkgconfig libao, by doing this:
>>
>> sudo port install pkgconfig libao
>> Password:
>> --->  Computing dependencies for pkgconfig
>> --->  Dependencies to be installed: libiconv gperf
>> --->  Configuring gperf
>> Error: Target org.macports.configure returned: configure failure: shell 
>> command failed (see log for details)
>> Error: Failed to install gperf
>> Log for gperf is at: 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/main.log
>> Error: The following dependencies were not installed: libiconv gperf
>> Error: Status 1 encountered during processing.
>> To report a bug, see 
>>
>> I keep getting the "shell command failed" error whenever i try to install 
>> anything, using macports.
>
> "shell command failed" tells us almost nothing other than that "something" 
> went wrong. MacPorts runs shell commands all the time. To learn anything, we 
> must know *what* shell command failed, and with *what* error message. The 
> aforementioned main.log file might tell us more.
>
>> I tried searching for the error and found a mailing list archive where it 
>> said that i should try reinstalling db46:
>
> That's probably not relevant to your issue.
>
>> sudo port -f uninstall db46
>> sudo port clean --all db46
>> sudo port install db46
>>
>> I did this but received the following error, when executing the last command:
>> http://pastebin.com/i4ZN6w1S
>
> This log says:
>
> :info:configure configure: error: C compiler cannot create executables
> :info:configure See `config.log' for more details.
>
> Seeing that config.log file might tell us more about why it failed.
Any idea where I can find the config.log file?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: MariaDB vs MySQL for Wordpress CMS

[Phil Dobbin]

Markus Neuenschwander wrote:

> Hi
> 
> MacPorts includes both MariaDB and MySQL. For a new web project with
> WordPress blog (1000 visitors / day) I need to decide between MySQL and
> MariaDB. I don't need official support. I googled and found old articles
> (weeks after buyout from Oracle) and biased info from AskMonty
> KnowledgeBase.
> 
> What do you think? Did MySQL loose popularity in web projects (after new
> owner Oracle)? Do you know numbers about installation base?

I've never used MariaDB but if you're used to MySQL, I'd be tempted to
stick to MySQL 5.5.

MariaDB isn't in the repos for Fedora 17 or Ubuntu 12.10 (didn't bother
checking CentOS or Debian: if they ain't in Fedora or Ubuntu, I doubt
it's in CentOS or Debian) so it's can't be that prevalent yet so while
MariaDB may be the upstream of MySQL nowadays, it'll be a while before
the pure volume of help available for it gets anywhere near matching
what's on offer freely for MySQL.

And besides, if it's a straight drop-in replacement™, you can always
cross that bridge when you come to it.

Just my two bob.

Cheers,

  Phil...

-- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing




signature.asc
Description: OpenPGP digital signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Newb

[Jeremy Lavergne]

> I believe my computer then shut down for no reason, it didn't lose power.

Sounds like your computer may have overheated.

> Error: Unable to execute port: sqlite error: database disk image is malformed 
> (11) while executing query: SELECT state FROM registry.ports WHERE id=105

I suspect your best result will be to dump out the database to a text file and 
then read it back in. The database is powered by sqlite3, so it's something 
along the following lines (Google probably will get you far as well).

Dump the db:
sqlite3 /opt/local/var/macports/registry/registry.db
sqlite> .mode insert
sqlite> .output dump_all.sql
sqlite> .dump

Create a new db:
sqlite3 registry.db
sqlite> .read dump_all.sql

Replace the old db:
sudo cp registry.db /opt/local/var/macports/registry/registry.db

On my system, the registry.db is owned by root:admin with permissions 0644.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Newb

[jake pasner]

Hello,
First off I should say I could be incorrectly using this list so please tell me 
to shut up and go somewhere else if that is what I should do.
My problem is I was attempting to have Macports get wine for me and had an 
error.  Info follows:
System:Mac OS 10.8.22.66 GHz Intell Core 2 Duo2 gigs of memory(can supply more 
info if needed)
What I did:Having already installed latests Xcode package from apple I 
installed Macports and use the following command:
$ sudo port install wine
It ran fine and was going well until it was attempting to install the wine 
dependency cairo.  I believe my computer then shut down for no reason, it 
didn't lose power.Not knowing how to deal with this, I attempted to run the 
same command $ sudo port install wine.  It reevaluated dependencies and then 
started cleaning already present dependencies.
--
--->  Dependencies to be installed: apple-gcc42 cctools cctools-headers 
llvm-3.1 libffi llvm_select gcc_select ld64 bison gettext expat libiconv 
ncurses m4 flex fontconfig freetype bzip2 zlib gst-plugins-base gnome-vfs 
desktop-file-utils glib2 perl5 perl5.12 gdbm popt gconf dbus-glib dbus gtk2 atk 
gobject-introspection cairo libpixman libpng xorg-xcb-util xorg-libxcb python27 
db46 libedit openssl python_select sqlite3 xorg-libXau xorg-xproto 
xorg-libXdmcp xorg-libpthread-stubs xorg-xcb-proto libxml2 xz xrender 
xorg-libX11 xorg-kbproto xorg-renderproto gdk-pixbuf2 jasper jpeg tiff 
hicolor-icon-theme pango Xft2 pkgconfig shared-mime-info xorg-libXcomposite 
xorg-compositeproto xorg-libXext xorg-xextproto xorg-libXfixes xorg-fixesproto 
xorg-libXcursor xorg-libXdamage xorg-damageproto xorg-libXi xorg-inputproto 
xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto intltool 
p5.12-getopt-long p5.12-pathtools p5.12-scalar-list-utils p5.12-xml-parser 
orbit2 gtk-doc docbook-xml docbook-xml-4.1.2 docbook-xml-4.2 xmlcatmgr 
docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl 
py27-libxml2 rarian libxslt libidl policykit eggdbus gnome-doc-utils iso-codes 
gnome-mime-data autoconf help2man p5.12-locale-gettext automake libtool 
gstreamer gzip texinfo libtheora libvorbis libogg orc xorg-libice xorg-xtrans 
xorg-libsm lcms mesa makedepend xorg-dri2proto xorg-glproto xorg-libXmu 
xorg-libXt xorg-libXxf86vm xorg-xf86vidmodeproto--->  Cleaning cctools-headers  
   {clip}--->  Cleaning xorg-libXfixes--->  Cleaning xorg-libXcomposite--->  
Cleaning xorg-libXcursor--->  Cleaning xorg-damageprotoError: Failed to install 
xorg-libXdamagePlease see the log file for port xorg-libXdamage for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_xorg-libXdamage/xorg-libXdamage/main.logError:
 The following dependencies were not installed: gst-plugins-base gnome-vfs 
gconf gtk2 xorg-libXdamage xorg-libXi xorg-inputproto xorg-libXinerama 
xorg-xineramaproto xorg-libXrandr xorg-randrproto intltool p5.12-getopt-long 
p5.12-pathtools p5.12-scalar-list-utils p5.12-xml-parser orbit2 gtk-doc 
docbook-xml docbook-xml-4.1.2 docbook-xml-4.2 xmlcatmgr docbook-xml-4.3 
docbook-xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl py27-libxml2 rarian 
libxslt libidl policykit eggdbus gnome-doc-utils iso-codes gnome-mime-data 
autoconf help2man p5.12-locale-gettext automake libtool gstreamer gzip texinfo 
libtheora libvorbis libogg orc xorg-libice xorg-xtrans xorg-libsm lcms mesa 
makedepend xorg-dri2proto xorg-glproto xorg-libXmu xorg-libXt xorg-libXxf86vm 
xorg-xf86vidmodeprotoTo report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.ticketsError: Processing of port wine failed
--
I looked around online for a while and found stuff that said to update my 
ports.  So I ran $ sudo port selfupdate.  It replied that MacPorts base was 
already the latest version.
I then tried to install xorg-libXdamage by itself with the following 
result:--
users-iMac:~ user$ sudo port install xorg-libXdamage--->  Computing 
dependencies for xorg-libXdamage--->  Dependencies to be installed: 
xorg-damageproto xorg-libXfixes xorg-fixesproto xorg-libX11 xorg-kbproto 
xorg-libXau xorg-xproto xorg-libXdmcp xorg-libxcb python27 bzip2 db46 gettext 
expat libiconv ncurses libedit openssl zlib python_select sqlite3 
xorg-libpthread-stubs xorg-xcb-proto libxml2 xz--->  Cleaning 
xorg-damageproto--->  Cleaning xorg-fixesproto--->  Cleaning xorg-kbproto--->  
Cleaning xorg-xproto--->  Cleaning xorg-libXau--->  Cleaning xorg-libXdmcp--->  
Cleaning bzip2--->  Cleani

Re: MariaDB vs MySQL for Wordpress CMS

[Randal L. Schwartz]

> "Markus" == Markus Neuenschwander  writes:

Markus> What do you think? Did MySQL loose popularity in web projects
Markus> (after new owner Oracle)? Do you know numbers about installation
Markus> base?

Listen to my interview with Monty himself: http://twit.tv/show/floss-weekly/194

In short, *stop* using MySQL.  Use MariaDB.  It's now the *upstream* of
MySQL, and is 99.9% compatible in its default install.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
 http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: MariaDB vs MySQL for Wordpress CMS

[Bradley Giesbrecht]

On Oct 21, 2012, at 12:19 PM, Markus Neuenschwander wrote:

> Hi
> 
> MacPorts includes both MariaDB and MySQL. For a new web project with 
> WordPress blog (1000 visitors / day) I need to decide between MySQL and 
> MariaDB. I don't need official support. I googled and found old articles 
> (weeks after buyout from Oracle) and biased info from AskMonty KnowledgeBase.
> 
> What do you think? Did MySQL loose popularity in web projects (after new 
> owner Oracle)? Do you know numbers about installation base?

For your questions I have nothing useful.

However, I suggest you choose either mysql55, mariadb or percona rather then 
the older mysql ports like mysql4, mysql5 and mysql51.

If there are other ports you need that have not been updated to use either 
mysql55, mariadb or percona let me know or file a trac ticket asking for the 
port to be updated to use mysql55, mariadb or percona.


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/macports-users

MariaDB vs MySQL for Wordpress CMS

[Markus Neuenschwander]

Hi

MacPorts includes both MariaDB and MySQL. For a new web project with 
WordPress blog (1000 visitors / day) I need to decide between MySQL and 
MariaDB. I don't need official support. I googled and found old articles 
(weeks after buyout from Oracle) and biased info from AskMonty 
KnowledgeBase.


What do you think? Did MySQL loose popularity in web projects (after new 
owner Oracle)? Do you know numbers about installation base?


Markus

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate incredibly slow

[Clemens Lang]

Hello,

On Sun, Oct 21, 2012 at 11:06:42AM -0700, cowwoc wrote:
> I implemented the timestamp approach in my build script (as a
> workaround) and it works great. Total I/O time: 10ms.

I don't think this is a very common usage of selfupdate. Most users only
run selfupdate once in a while given the current rate of commits in
MacPorts _will_ see at least one change.

Consider writing a patch if you want this. I don't see myself doing
this, because the benefit to the average user is probably zero and the
developers are all using subversion anyway.

-- 
Clemens Lang

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate incredibly slow

[cowwoc]

 I implemented the timestamp approach in my build script (as a 
workaround) and it works great. Total I/O time: 10ms.

 Again, please consider folding this into "port selfupdate".

Thanks,
Gili

On 21/10/2012 4:56 AM, Ryan Schmidt-24 [via Mac OS Forge] wrote:
>
> On Oct 19, 2012, at 21:58, Davor Cubranic <[hidden email] 
> > wrote:
>
> > What he means is that you can use Subversion as an alternative 
> distribution system to downloading the ports.tar file. That way you 
> get roughly the behaviour you asked for, since "svn update" will do 
> nothing if you locally have the most recent version of the master.
>
> Well, it won't do "nothing"... it will scan the local ports working 
> copy and compare it with what's available on the server. The end 
> result is that no files will be changed and nothing significant will 
> have to be downloaded, but it will still take up to several minutes of 
> disk I/O to determine that, depending on the speed of your disk. Using 
> Subversion 1.7 or later should decrease the amount of I/O needed and 
> thus decrease the time needed.
>
>
> ___
> macports-users mailing list
> [hidden email] 
> http://lists.macosforge.org/mailman/listinfo/macports-users
>
>
> 
> If you reply to this email, your message will be added to the 
> discussion below:
> http://mac-os-forge.2317878.n4.nabble.com/port-selfupdate-incredibly-slow-tp117503p197473.html
>  
>
> To unsubscribe from port selfupdate incredibly slow, click here 
> .
> NAML 
> 
>  
>





--
View this message in context: 
http://mac-os-forge.2317878.n4.nabble.com/port-selfupdate-incredibly-slow-tp117503p197500.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate incredibly slow

[Ryan Schmidt]

On Oct 19, 2012, at 21:58, Davor Cubranic  wrote:

> What he means is that you can use Subversion as an alternative distribution 
> system to downloading the ports.tar file. That way you get roughly the 
> behaviour you asked for, since "svn update" will do nothing if you locally 
> have the most recent version of the master.

Well, it won't do "nothing"... it will scan the local ports working copy and 
compare it with what's available on the server. The end result is that no files 
will be changed and nothing significant will have to be downloaded, but it will 
still take up to several minutes of disk I/O to determine that, depending on 
the speed of your disk. Using Subversion 1.7 or later should decrease the 
amount of I/O needed and thus decrease the time needed.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: shell command failed

[Ryan Schmidt]

On Oct 20, 2012, at 17:52, Felix Emil Drud wrote:

> I was trying to install pkgconfig libao, by doing this:
> 
> sudo port install pkgconfig libao
> Password:
> --->  Computing dependencies for pkgconfig
> --->  Dependencies to be installed: libiconv gperf
> --->  Configuring gperf
> Error: Target org.macports.configure returned: configure failure: shell 
> command failed (see log for details)
> Error: Failed to install gperf
> Log for gperf is at: 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/main.log
> Error: The following dependencies were not installed: libiconv gperf
> Error: Status 1 encountered during processing.
> To report a bug, see 
> 
> I keep getting the "shell command failed" error whenever i try to install 
> anything, using macports.

"shell command failed" tells us almost nothing other than that "something" went 
wrong. MacPorts runs shell commands all the time. To learn anything, we must 
know *what* shell command failed, and with *what* error message. The 
aforementioned main.log file might tell us more.

> I tried searching for the error and found a mailing list archive where it 
> said that i should try reinstalling db46:

That's probably not relevant to your issue.

> sudo port -f uninstall db46
> sudo port clean --all db46
> sudo port install db46
> 
> I did this but received the following error, when executing the last command:
> http://pastebin.com/i4ZN6w1S

This log says:

:info:configure configure: error: C compiler cannot create executables
:info:configure See `config.log' for more details.

Seeing that config.log file might tell us more about why it failed.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users