Re: Restore from backup

On May 16, 2012, at 01:13, Adam Dershowitz wrote: > Thanks. Sounds simple enough, although one question. I had 2.0.?. It > crashed before I upgraded to 2.1.0. So I assume that I should instead us an > older installer, then once all is working do the upgrade to 2.1.0. Or will > the 2.1.0 in

Re: Restore from backup

Thanks. Sounds simple enough, although one question. I had 2.0.?. It crashed before I upgraded to 2.1.0. So I assume that I should instead us an older installer, then once all is working do the upgrade to 2.1.0. Or will the 2.1.0 installer be fine now and it will upgrade fine? --Adam Ryan

Re: Restore from backup

On May 16, 2012, at 00:28, Adam Dershowitz wrote: > I have macports, with many ports installed. > I had my harddrive fail, but have a recent timemachine backup. > But, when I tried to restore, after a fresh OS install, at first when I > clicked transfer, nothing would happen. I finally opened

Restore from backup

I have macports, with many ports installed. I had my harddrive fail, but have a recent timemachine backup. But, when I tried to restore, after a fresh OS install, at first when I clicked transfer, nothing would happen. I finally opened the users that timemachine had selected to restore. Sever

Re: MacPorts 2.1.0 has been released - problems with the progress lines

Removing macports-dev since this isn't a development issue. On May 16, 2012, at 12:59 a.m., Bjarne D Mathiesen wrote: > Is there something I can do to switch this progess thingy off ??? I'm not sure if there's a way to disable the output. You can do upgrades without rev-upgrade with the --no-r

Re: MacPorts 2.1.0 has been released - problems with the progress lines

I've noticed these two new lines in my output: ---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 100.0% My problem is with the progress of the percentages in combination with updating ports automatically using a script in periodic daily logging to syslog. That

Re: Update fails at iso-codes

Invalid entry, eh? Looks like something else for 2.1.1. Be in touch with the dev list to debug it, this will help squish the bug :-) Jasper Frumau wrote: >jaspersmbp:~ jasper$ sudo port uninstall iso-codes @3.34_0 >Password: >an invalid entry was passed >while executing >"$dependent name"

Re: Python27 update error

Thanks. Managed to get beyond this error now. On Wed, May 16, 2012 at 9:59 AM, Ryan Schmidt wrote: > > On May 15, 2012, at 19:01, Jasper Frumau wrote: > > > :info:destroot > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_xmlplus/parsers/pyexpat.so: >

Re: Update fails at iso-codes

jaspersmbp:~ jasper$ sudo port uninstall iso-codes @3.34_0 Password: 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"

Re: Python27 update error

On May 15, 2012, at 19:01, Jasper Frumau wrote: > :info:destroot > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_xmlplus/parsers/pyexpat.so: > mach-o, but wrong architecture > https://trac.macports.org/ticket/34060 _

Re: Update fails at iso-codes

> It mentioned it could not be installed because a port depend on it, but the > port was not mentioned... Perhaps trying to uninstall it manually would trigger the proper message (or at least deactivating)? smime.p7s Description: S/MIME cryptographic signature

Python27 update error

While I was doing a general update of MacPorts on my Lion - newly upgraded - with the latest XCode I ran into this error: -- :info:destroot from pyexpat import * :info:destroot ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_x

Macports xorg-server as default X11

Hi all, On a fresh system: Mac OS X 10.7.4 Xcode 4.3.2 Macports 2.1.0 I installed Macports and installed xorg-server-devel and rebooted. $ port installed xorg-server* xinit The following ports are currently installed: xinit @1.3.2_3 (active) xorg-server-devel @1.12.99.0_2 (active) When I r

Re: git-core fails to upgrade

Bjarne D Mathiesen wrote: > Bjarne D Mathiesen wrote: >> argggh ... found the error :-( >> >> It's still trying to reference Perl5.12 even though I've upgraded to >> Perl5.14 & removed Perl5.12 completely from my computers ... >> >> now to find out exactly where it goes wrong ... >> >> :-) > > OK

Re: git-core fails to upgrade

Bjarne D Mathiesen wrote: > argggh ... found the error :-( > > It's still trying to reference Perl5.12 even though I've upgraded to > Perl5.14 & removed Perl5.12 completely from my computers ... > > now to find out exactly where it goes wrong ... > > :-) OK - Perl5.12 is hardcoded into the Port

Re: git-core fails to upgrade

On May 15, 2012, at 4:52 p.m., Bjarne D Mathiesen wrote: > It's still trying to reference Perl5.12 even though I've upgraded to > Perl5.14 & removed Perl5.12 completely from my computers ... You do know that git-core depends on perl5.12, right? vq __

Re: git-core fails to upgrade

argggh ... found the error :-( It's still trying to reference Perl5.12 even though I've upgraded to Perl5.14 & removed Perl5.12 completely from my computers ... now to find out exactly where it goes wrong ... :-) -- Bjarne D Mathiesen København N ; Danmark ; Europa -

Re: git-core fails to upgrade

OK - I'm also getting this exact same error on a clean install on another computer: sh-3.2# port install git-core ---> Computing dependencies for git-core ---> Fetching archive for git-core ---> Fetching git-core ---> Verifying checksum(s) for git-core ---> Extracting git-core ---> Applying

Re: archive_site_local [was: MacPorts 2.1.0 has been released]

On 2012-5-16 06:09 , Joshua Root wrote: > On 2012-5-16 06:01 , Arno Hautala wrote: >> On 5/15/12, C D wrote: >>> >>> Then there might be a bug: following the procedure in >>> https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local >>> archive repository, which I access through

Re: archive_site_local

> So, is there a way to work around this? Maybe a way to escape the colon? You could host it on the port 80, or you can create a tunnel from localhost:80 to the correct port otherhost:. > Can you point me to why this is broken? What is it that MacPorts > doesn't like about the :port conventi

Re: archive_site_local

On May 15, 2012, at 15:07, Arno Hautala wrote: > On 5/15/12, Ryan Schmidt wrote: >> >> Sounds like: https://trac.macports.org/ticket/32018 > > So, is there a way to work around this? Maybe a way to escape the colon? > > Can you point me to why this is broken? What is it that MacPorts > doesn

Re: archive_site_local [was: MacPorts 2.1.0 has been released]

On 2012-5-16 06:01 , Arno Hautala wrote: > On 5/15/12, C D wrote: >> >> Then there might be a bug: following the procedure in >> https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local >> archive repository, which I access through the URL http://localhost:6227/ . >> When this U

Re: archive_site_local

On 5/15/12, Ryan Schmidt wrote: > > Sounds like: https://trac.macports.org/ticket/32018 So, is there a way to work around this? Maybe a way to escape the colon? Can you point me to why this is broken? What is it that MacPorts doesn't like about the :port convention? -- arno s hautala/-|

Re: archive_site_local [was: MacPorts 2.1.0 has been released]

On 5/15/12, C D wrote: > > Then there might be a bug: following the procedure in > https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local > archive repository, which I access through the URL http://localhost:6227/ . > When this URL is put into ${prefix}/etc/archive_sites.conf,

Re: archive_site_local

On May 15, 2012, at 14:49, C D wrote: > Then there might be a bug: following the procedure in > https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local > archive repository, which I access through the URL http://localhost:6227/ . > When this URL is put into ${prefix}/etc/ar

Re: MacPorts 2.1.0 has been released

At 4:17 AM +1000 5/16/12, Joshua Root wrote: On 2012-5-16 03:55 , Craig Treleaven wrote: Thanks to the devs for all their work. In the NEWS, I noticed a couple of points: == Overview of changes from MacPorts 2.0.4 to 2.1.0 == *) The pkg and mpkg targets will create flat packages on 10.6

archive_site_local [was: MacPorts 2.1.0 has been released]

> The MacPorts Project is happy to announce that the 2.1.0 version has now > been released.   Thanks to all for the work!  It seems that 'archive_site_local' in macports.conf is now ignored (at least it stopped working for me after the upgrade to MacPorts 2.1.0). I understand that it has been r

Re: MacPorts 2.1.0 has been released

On May 15, 2012, at 12:55, Craig Treleaven wrote: > In the NEWS, I noticed a couple of points: > >> == Overview of changes from MacPorts 2.0.4 to 2.1.0 == >> >> *) The pkg and mpkg targets will create flat packages on 10.6+. >> >> >> *) Multiple ports can now be defined in one Portfile using

Re: MacPorts 2.1.0 has been released

On 2012-5-16 03:55 , Craig Treleaven wrote: > Thanks to the devs for all their work. > > In the NEWS, I noticed a couple of points: > >> == Overview of changes from MacPorts 2.0.4 to 2.1.0 == >> >> *) The pkg and mpkg targets will create flat packages on 10.6+. >> >> >> *) Multiple ports can no

Re: MacPorts 2.1.0 has been released

At 1:29 AM +1000 5/16/12, Joshua Root wrote: The list of what's new in 2.1.0 is quite extensive (so I won't list it here), the details can be found in the NEWS [7] file or the somewhat more exhaustive ChangeLog [8]. [7]

Re: MacPorts 2.1.0 has been released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/05/2012 18:07, Jeremy Lavergne wrote: >> Makes sense (& the fact the whole of /Library is set executable). >> I just wondered why it was pointed it out in the message & Tcl >> was mentioned explicitly. > > It's just letting you know what it's d

Re: MacPorts 2.1.0 has been released

> Makes sense (& the fact the whole of /Library is set executable). I > just wondered why it was pointed it out in the message & Tcl was > mentioned explicitly. It's just letting you know what it's doing and where. It probably reflects any change you might have made if you were compiling it outsi

Re: MacPorts 2.1.0 has been released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/05/2012 17:54, Jeremy Lavergne wrote: >> I've just upgraded via selfupdate on 10.6.8 & got a message about >> Tcl's executable bit being set: >> >> `MacPorts base is outdated, installing new version 2.1.0 >> Installing new MacPorts release in

Re: MacPorts 2.1.0 has been released

> I've just upgraded via selfupdate on 10.6.8 & got a message about Tcl's > executable bit being set: > > `MacPorts base is outdated, installing new version 2.1.0 > Installing new MacPorts release in /opt/local as root:admin; permissions > 0755; Tcl-Package in /Library/Tcl` > > upon doing a `ls -

Re: MacPorts 2.1.0 has been released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/05/2012 16:29, Joshua Root wrote: > The MacPorts Project is happy to announce that the 2.1.0 version has now > been released. It is available via the usual methods: [snip] I've just upgraded via selfupdate on 10.6.8 & got a message about Tcl's

MacPorts 2.1.0 has been released

The MacPorts Project is happy to announce that the 2.1.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers for 10.5 [1], 10.6 [2], and 10.7 [3] (all universal builds, the first i386/ppc and the latter

Re: Xquartz 2.5.0

man bash then read carefully the section INVOCATION to understand how (and which) dot-files are processed. willy-nilly shuffling of files and contents is usually a poor strategy for troubleshooting. --WD On Tue, May 15, 2012 at 7:51 AM, Jasper Frumau wrote: > .bash_profile is empty, but .bash_

Re: Xquartz 2.5.0

.bash_profile is empty, but .bash_login has: [[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm" # Load RVM into a shell session *as a function* Will check out and clean up .profile .bashrckilled // former .bashrc has also an RVM piece: PATH=$PATH:$HOME/.rvm/bin # Add RVM to PA

Re: Xquartz 2.5.0

Hey we are getting somewhere. I renamed .bash_login and .bash_profile to the same filenames + killed, opened a new terminal and now I have: Last login: Tue May 15 20:22:37 on ttys000 You have new mail. /opt/subversion/bin:/opt/local/bin:opt/local/sbin:/opt/local/lib/python2.4/site-packages/django/

Re: Xquartz 2.5.0

On Tue, May 15, 2012 at 8:17 PM, Jeremy Lavergne wrote: > > now when you open a new terminal does it print out the path? > Nope: Last login: Tue May 15 20:06:52 on ttys000 You have new mail. jaspersmbp:~ jasper$ cat .profile # MacPorts Installer addition on 2009-10-20_at_13:11:20: adding an ap

Re: Xquartz 2.5.0

On Tue, May 15, 2012 at 8:00 PM, Jeremy Lavergne wrote: > > As in > > .profile: > > > > # MacPorts Installer addition on 2009-10-20_at_13:11:20: adding an > appropriate PATH variable for use with MacPorts. > > export PATH=/opt/local/bin:/opt/local/sbin:$PATH > > # Finished adapting your PATH envi

Re: Xquartz 2.5.0

As in .profile: # MacPorts Installer addition on 2009-10-20_at_13:11:20: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. #Django path export PATH=/opt/local/bin:opt

Re: fail to compile pcre 8.30 +universal

On Tue, May 15, 2012 at 9:34 AM, Jeremy Lavergne wrote: > > I trying to install the pcre with universal and I having this problem: > > > > http://pastebin.com/3tr2MyDU > > > > :info:build ld: warning: ignoring file /opt/local/lib/libreadline.dylib, > file was built for unsupported file format whi

Re: Xquartz 2.5.0

I closed the terminal and did the following: Last login: Tue May 15 19:44:41 on ttys000 You have new mail. jaspersmbp:~ jasper$ gedit -bash: gedit: command not found jaspersmbp:~ jasper$ rails Rails is not currently installed on this system. To get the latest version, simply type: $ sudo gem

Re: fail to compile pcre 8.30 +universal

> I trying to install the pcre with universal and I having this problem: > > http://pastebin.com/3tr2MyDU > > :info:build ld: warning: ignoring file /opt/local/lib/libreadline.dylib, file > was built for unsupported file format which is not the architecture being > linked (i386) > :info:build U

fail to compile pcre 8.30 +universal

I trying to install the pcre with universal and I having this problem: http://pastebin.com/3tr2MyDU :info:build ld: warning: ignoring file /opt/local/lib/libreadline.dylib, file was built for unsupported file format which is not the architecture being linked (i386) :info:build Undefined symbols f

Re: XCode command line tools enough for MacPorts?

At 11:41 AM +0200 5/15/12, Harry van der Wolf wrote: We now have the "XCode command line tools" since March 2012. An initiative you probably have heard of and started by Kenneth Reitz (0,1) and now fully supported by Apple. They can be downloaded from within XCode 4.3.x or directly as a command

Re: Xquartz 2.5.0

On 15/05/12 13:00, Jasper Frumau wrote: Thanks for all the help so far. Appreciate it! jaspersmbp:~ jasper$ sudo mv .bashrc .bashrckilled no need for sudo there. You own the file ! Password: jaspersmbp:~ jasper$ ls -a | grep bash .bash_history .bash_login .bash_profile .bashrckilled .bashrc~

Re: Xquartz 2.5.0

Thanks for all the help so far. Appreciate it! jaspersmbp:~ jasper$ sudo mv .bashrc .bashrckilled Password: jaspersmbp:~ jasper$ ls -a | grep bash .bash_history .bash_login .bash_profile .bashrckilled .bashrc~ jaspersmbp:~ jasper$ echo $PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bi

Re: Xquartz 2.5.0

> /Users/jasper/.bashrc:PATH=$PATH:$HOME/.rvm/bin # Add RVM to PATH for > scripting My guess is the presence of .bashrc. Temporarily rename that, open a new terminal and echo $PATH. If that fixed it, you now know the culprit. smime.p7s Description: S/MIME cryptographic signature

Re: Xquartz 2.5.0

On Tue, May 15, 2012 at 6:43 PM, Chris Jones wrote: > On 15/05/12 12:39, Jasper Frumau wrote: > >> In .profile I already have >> >> >> # MacPorts Installer addition on 2009-10-20_at_13:11:20: adding an >> appropriate PATH variable for use with MacPorts. >> export PATH=/opt/local/bin:/opt/**local/s

Re: Xquartz 2.5.0

On 15/05/12 12:39, Jasper Frumau wrote: In .profile I already have # MacPorts Installer addition on 2009-10-20_at_13:11:20: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with

Re: Xquartz 2.5.0

In .profile I already have # MacPorts Installer addition on 2009-10-20_at_13:11:20: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. #Django path export PATH=/opt/l

Re: Xquartz 2.5.0

> Should I just do > > export PATH=/opt/local/bin:/opt/local/sbin:$PATH > > to fix the issue? Depends. That will only work in the current shell unless you put it in a dot file that is sourced when you open a new terminal. smime.p7s Description: S/MIME cryptographic signature ___

Re: Xquartz 2.5.0

Should I just do export PATH=/opt/local/bin:/opt/local/sbin:$PATH to fix the issue? On Tue, May 15, 2012 at 6:28 PM, Jasper Frumau wrote: > > > On Tue, May 15, 2012 at 6:25 PM, Jeremy Lavergne < > jer...@lavergne.gotdns.org> wrote: > >> > MacPorts is no longer working since I added Xquartz 2.5

Re: Xquartz 2.5.0

> Here is my $PATH: > > jaspersmbp:~ jasper$ echo $PATH > /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Looks like installing XQuartz clobbered your PATH--possibly other things in your bash dot files. Append to whichever dot file you prefer and know is being used (I personally use

Re: Xquartz 2.5.0

On Tue, May 15, 2012 at 6:25 PM, Jeremy Lavergne wrote: > > MacPorts is no longer working since I added Xquartz 2.5.0 I need help > fixing this asap. I also upgraded to Lion + latest XCode. > > > > Last login: Tue May 15 16:44:59 on console > > You have new mail. > > jaspersmbp:~ jasper$ gedit >

Re: Xquartz 2.5.0

> MacPorts is no longer working since I added Xquartz 2.5.0 I need help fixing > this asap. I also upgraded to Lion + latest XCode. > > Last login: Tue May 15 16:44:59 on console > You have new mail. > jaspersmbp:~ jasper$ gedit > -bash: gedit: command not found > jaspersmbp:~ jasper$ port -qv i

Re: Xquartz 2.5.0

MacPorts is no longer working since I added Xquartz 2.5.0 I need help fixing this asap. I also upgraded to Lion + latest XCode. Last login: Tue May 15 16:44:59 on console You have new mail. jaspersmbp:~ jasper$ gedit -bash: gedit: command not found jaspersmbp:~ jasper$ port -qv installed > myports

XCode command line tools enough for MacPorts?

Hi, We now have the "XCode command line tools" since March 2012. An initiative you probably have heard of and started by Kenneth Reitz (0,1) and now fully supported by Apple. They can be downloaded from within XCode 4.3.x or directly as a command line tool set. This last is of course the preferred