Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Bachsau wrote: Am 02.11.2016 um 23:48 schrieb Murray Eisenberg: After upgrading from OS X El Capitan to macOS Sierra (10.12.1), I’m following the migration steps at https://trac.macports.org/wiki/Migration. Against the recommendations in that article, I discovered the easiest way to migrate is

Re: Trac & Subversion available again

On 2016-10-23 14:48 , Jeremy Huddleston Sequoia wrote: On Oct 21, 2016, at 18:16, Clemens Lang wrote: Hello MacPorts users and developers, On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote: Due to the current SVN and Trac downtime, we are also discussing to make the move of Trac

Re: Moving to GitHub: Status Update, Action Required

On 2016-10-22 23:31 , Marko Käning wrote: Hi Clemens, great to see the GitHub conversion progressing this rapidly! Thumbs up from me!!! When reading the WorkingWithGit wiki page [1] I saw how port contributors can post their suggestions to MacPorts via "Pull Requests”, yet it does not get cl

Imagick version?

Bjarne D Mathiesen wrote: You'll just have to re-compile php55-imagick : This will take care of all of your php\d{2}-imagick versions port -q installed name:imagic \ | while read -a port do port -n upgrade --force ${port[0]} done but more explicitly for just php55-imagick : port -n upgr

Getting rid of port binaries in /software

Eric A. Borisch wrote: If you are just looking to save some space at the expense of time, you could set: portarchivetype txz in macports.conf; on some of the big clang/llvm archives this is ~2x improvement... Nobody has yet mentioned the very important fact that you can't just change th

Re: How add variant when upgrading octave

Murray Eisenberg wrote: Currently installed and active is: octave @3.8.2_18+atlas+gcc48+glgui This is flagged as having available upgrade to 4.0.2_0, so I executed... sudo port upgrade octave …which generated the error: Error: org.macports.fetch for port octave returned: mu

Re: About mozjs24 being built

On 2016-4-4 01:46 , Clemens Lang wrote: Hi Josh, On Mon, Apr 04, 2016 at 01:06:50AM +1000, Joshua Root wrote: MPL 2.0 is GPL compatible only by way of an optional clause that allows relicensing under the GPL. Some software is under MPL-2 but has an "Incompatible With Secondary Licenses&qu

Re: About mozjs24 being built

On 2016-4-4 00:45 , Clemens Lang wrote: Hi, On Sun, Apr 03, 2016 at 04:05:02PM +0200, Clemens Lang wrote: Doesn't seem like it will: $ port_binary_distributable.tcl -v mozjs24 "mozjs24" is not distributable because its license "mpl" conflicts with license "GPL-3+" of dependency "gdbm" Actua

Re: python_select

ou to set those default versions if you need both? On Mar 28, 2016, at 5:46 AM, Joshua Root wrote: Mark Brethen wrote: Why are there a python_select, python2_select and python3_select? When is one vs the others used? They allow creating links 'python&#x

python_select

Mark Brethen wrote: Why are there a python_select, python2_select and python3_select? When is one vs the others used? They allow creating links 'python', 'python2' and 'python3' respectively. - Josh ___ macports-users mailing list macports-users@lis

py-pip usage

Mark Brethen wrote: How is the py-pip port used to install python packages and where are they installed? Is this advisable? You use it just as described in the pip documentation[1]. By default the packages go to the same place as a normal distutils install, which is not a good idea since tha

Sending logs to the list (was: Guile is broken, again...)

Dave Horsfall wrote: > On Wed, 10 Feb 2016, Chris Jones wrote: > >> Just compress the log file before posting it. It will be a fraction of >> its original size then... > > Yet another hoop through which to jump, in other words... Should it be > ZIP, Compress, or what? Sigh, so many standards

py33-scipy problem

David Strubbe wrote: > As the message says, you need to select a Fortran variant. You have not. > You can see this from the fact that the file trying to be fetched is > py33-scipy-0.16.1_0.darwin_13.x86_64.tbz2 not > py33-scipy-0.16.1_0+gcc48.darwin_13.x86_64.tbz2. Yes, you had py33-scipy > +gcc48

Usefulness of boost-jam and boost-build

Are people using boost-jam and/or boost-build? They have no dependents in the ports tree, haven't been updated upstream in years, and apparently boost-jam is somewhat broken: Just wondering if it's worth patching or if we should just delete them. - Josh __

Cannot connect to X server

Brandon Allbery wrote: > On Thu, Dec 17, 2015 at 4:23 PM, Eneko Gotzon > wrote: > >> As being just an humble user, do you think advisable to also install the >> xinit port? (Responsible for configuring the initial environment when X11 >> starts up) > > > xinit also has the launchd configurati

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"?

On 2015-11-11 01:26 , Daniel J. Luke wrote: > On Nov 10, 2015, at 5:42 AM, Ryan Schmidt wrote: >> I think interest in PowerPC systems is truly very low at this time. > > These machines no longer run a version of Mac OS X that receives security > updates from Apple - and don’t run one of the 2 ma

Re_ graphite2 build error

rmgls wrote: > On Mon, 26 Oct 2>15 16:13:24 -0500 Ryan Schmidt > wrote: > >> Yes. Not having /usr/include would be a problem. /usr/include is = >> provided by the Xcode command line tools, so install that. > > Hello Ryan, > > then i do not understand, please look: > xcode-select --install

Re: libgmp

+1 I would suggest looking at how the binary distros build their gmp. We should do the same thing in our port for the default no-variants case, and have a variant that forces a local build and gives better runtime performance. Personally I don't need gfactor from coreutils to run at peak efficien

Re: Darwin Version

Jeremy Huddleston Sequoia wrote: >> On Oct 2, 2015, at 08:01, Clemens Lang wrote: >> There are changes that can be done by Apple with OS upgrades that will render >> your currently installed libraries useless. Examples for changes that are of >> this nature are: >> - Apple changing CPU architect

MacPorts 2.3.4 has been released

The MacPorts Project is pleased to announce the release of version 2.3.4. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs,

Re: Problem upgrading `tiff`

> On 08.08.2015 11:43 AM, Kurt Pfeifle wrote: >> But I have every package installed which has /jpeg/ in its name: >> >> |$> port installed *jpeg* jpeg @9a_1+universal (active) jpeg2ps @1.9_0 >> (active) >> jpegoptim @1.2.4_1 (active) libjpeg-turbo @1.3.1_0 libjpeg-turbo @1.4.0_0 >> libjpeg-turbo

port-search: is --glob option really the default?

> Hello list, > > The man page of port-search says --glob is the default, but the result > was different when I added this option manually, for example: > $ port search --name guile > found 6 ports > > $ port search --name --glob guile > found 1 ports > > Did I misunderstand anything here? > >

Re: selfupdate doesn't work

(Re-adding the list.) OK. You need to mention what exactly you have tried, or we'll probably just re-suggest all of it. :) The gist of the FAQ is very relevant though. The rsync server is working (I just tried it), so there has to be something about your computer or internet connection that is bl

Re: selfupdate doesn't work

> Hello... I'm running OS X 10.6.8 on a dual-core Macbook Pro... > > I've got Xcode 3.2 loaded from the snow leopard CD. Software Update did not > find an update for it. > > Using the pkg file, I loaded Macports 2.3.3 > > Selfupdate doesn't work; any advice? ... > > Last login: Sun Mar 1 23

Re: updating a very old Macports install

On 2015-2-14 15:01 , Ryan Schmidt wrote: > > On Feb 13, 2015, at 9:21 PM, Joshua Root wrote: > >>> See below: >>> expected integer but got "-exclusive" obtaining lock on >>> /opt/local/var/macports/registry/.registry.lock >>>while exe

updating a very old Macports install

> See below: > expected integer but got "-exclusive" obtaining lock on > /opt/local/var/macports/registry/.registry.lock > while executing > "registry::exclusive_lock" > (procedure "mportexec" line 32) You appear to be running trunk. You could take this opportunity to go back to a released

Re: Not really MacPorts problem, I don't think.

On 2015-1-24 14:40 , William H. Magill wrote: > >> On Jan 23, 2015, at 2:36 AM, Joshua Root wrote: >> >>> At 8:42 PM -0600 1/22/15, Ryan Schmidt wrote: >>>> So launchd is launching apache too early. I believe there are some >>>> keys one can use i

Not really MacPorts problem, I don't think.

> At 8:42 PM -0600 1/22/15, Ryan Schmidt wrote: >>So launchd is launching apache too early. I believe there are some >>keys one can use in a launchd plist that would affect when launchd >>tries to launch a service. If you can find a launchd plist key/value >>that fixes this issue, MacPorts could

/opt/local/macports/software

Daniel J. Luke wrote: >> On Jan 19, 2015, at 6:34 AM, René J.V. Bertin wrote: >> What could be an option: >> - use xz instead of bzip2 to compact things a bit more > > this would probably be a small change (I think there's support for gzip and > zip already) - but changing your local archive typ

Re: Multiple MacPort prefixes

On 2014-12-18 01:53 , Tres Finocchiaro wrote: > I'll fire up a Lion VM for this, thank you. NP. That's probably the best approach. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/m

Multiple MacPort prefixes

> Hi, > > I'm recently trying to bundling some backwards compat software packages > using a Lion version of XCode (3.x) on Mavericks and MacPorts. Xcode 3.x is not the right version to use with Lion, 4.x is. 3.1 is for Leopard and 3.2 is for Snow Leopard. IIRC, 3.2.6 didn't even work right on Li

Identifying newly available ports

> Howdy all. > > I’ve been using macports for a number of years, but have never figured out > how to readily identify NEW ports (newly available ports, not updates of > existing packages). I am forced to root around in the ports list or the > categories among thousands of files, like a pig aft

Friendly reminder: we have another list :)

Not to be the OT police, but all the recent portfile development discussion on this list would be much more at home on macports-dev. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/

Re: [KDE/Mac] MacPorts usage statistics

On 2014-12-8 07:45 , Marko Käning wrote: > Hi René, > > On 07 Dec 2014, at 21:32 , René J.V. Bertin wrote: >> That calls for a bit of lobbying -- or maybe a survey how many MacPorts >> users were aware of the port's existence. >> >> Not me in any case… > > well, the original thread started off

MacPorts 2.3.3 has been released

The MacPorts Project is pleased to announce the release of version 2.3.3. This is a bugfix release which addresses performance issues when using the SQLite version included with Yosemite. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate

Logging bug (was: Port update outdated problem.)

> I don't truly understand how base works and fits together, and my feeling is > few people do, or someone would have figured out the solution to weird bugs > like https://trac.macports.org/ticket/37093 by now. I assure you the logging code is not that hard to understand compared with some other

controlling Macports version of Apache2 -- part 2

>> On Oct 23, 2014, at 9:42 PM, Brandon Allbery wrote: >> >> On Thu, Oct 23, 2014 at 9:37 PM, William H. Magill wrote: >> What is the equivalent today? MacPorts does not contain a Lynx port which >> the search command can find. >> >> links or elinks, probably. Ports exist for both. There's als

Cyrus-IMapd fails to build on 10.10

> On Oct 21, 2014, at 8:45 PM, Horst Simon wrote: > >> OS/X 10.10, Xcode 6.1 and Command Line tools 6.1. >> >> cyrus_imapd fails again to build, but this time it appears to be a different >> error: > > Ok, the log says: > >> :info:build Can't locate Digest/SHA1.pm in @INC (@INC contains: >> /

MacPorts 2.3.2 has been released

The MacPorts Project is pleased to announce the release of version 2.3.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs,

libgcc update ... to 4.9?

> On Aug 21, 2014, at 12:17, Clemens Lang wrote: > >> I couldn't see anything that would prevent the use of binary archives. Can >> you >> attach the main.log of an attempt to install a package that should use binary >> archives, but didn't? > > I still had the log from the attempt to install li

Re: Undo universal?

On 2014-8-21 03:54 , Brandon Allbery wrote: > On Wed, Aug 20, 2014 at 1:31 PM, Joshua Root <mailto:j...@macports.org>> wrote: > > >> What about: > >> > >> sudo port upgrade --enforce-variants OpenSceneGraph -universal > >> >

Re: Undo universal?

On 2014-8-21 03:28 , Adam Dershowitz Ph.D., P.E. wrote: > > > On Aug 20, 2014, at 1:22 PM, Joshua Root wrote: > >>> I had OpenSceneGraph installed, but, for another application I was testing, >>> I needed a universal version. So, I did >>> sudo

Use proxy only on one network

> I'm experimenting with running a proxy server on my network, which I would > like MacPorts to use while on that network, while not interfering with my > ability to use MacPorts while connected to other networks. What's the best > way to do this in an automated way? Editing macports.conf proxy

Undo universal?

> I had OpenSceneGraph installed, but, for another application I was testing, I > needed a universal version. So, I did > sudo port install OpenSceneGraph +universal > It then proceeded to upgrade MANY things to universal. I hadn’t realized how > many dependencies there were. > My question i

Re: gnupg12, gnupg users, please reply.

On 2014-7-7 10:00 , Mihai Moldovan wrote: > Hi gpg users, > > We currently have three unmaintained ports for gnupg: gnupg (ver 1.4), gnupg12 > (ver 1.2) and gnupg2 (ver 2.x). > > In order to implement proper launchd integration in gpg-agent, I will likely > have to slightly patch gnupg as well. >

Re: Troubles installing ports with Macports 2.3.1

On 2014-7-3 04:38 , Ryan Schmidt wrote: > > On Jul 2, 2014, at 2:25 AM, Joshua Root wrote: > >>> On Jul 1, 2014, at 4:58 AM, Joël Brogniart wrote: >>> >>>> I suppose that, during the "Computing dependencies for >>>> auto-multiple-

Troubles installing ports with Macports 2.3.1

> On Jul 1, 2014, at 4:58 AM, Joël Brogniart wrote: > >> I suppose that, during the "Computing dependencies for auto-multiple-choice" >> phase, a lot of http requests are made to obtain port information and that >> these requests are not fully closed either by Macports or by the proxy. As >> th

MacPorts 2.3.1 has been released

The MacPorts Project is pleased to announce the release of version 2.3.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs,

Problem compiling gnome-libs

> 1) I assume that this or another error must be occurring on the bulk build > server as there is no pre-built package. It's because of the same error. Open a ticket and attach your config.log. > 2) On my old PB G4 running Leopard, I can get past Configure, but the build > dies later on with some

Idle (Python) on OS X Mavericks

> Ok, I’ve got python2.7 and 3.4 from Macports installed. I’m trying to use > idle but the error printed is: > > ** IDLE can’t import Tkinter. Your Python may not be configured for tk ** > > I also installed the py34-tkinter port as I believe this port contains the > required libraries for Idle

Re: 'port build' is getting EPERM from access(2) on "/var/tmp"

On 2014-5-25 09:21 , Quentin Barnes wrote: > On Sat, May 24, 2014 at 10:18:12AM +1000, Joshua Root wrote: >> I'm not sure what exact syscalls test -w uses, > > That was covered in my base note, access("/var/tmp", W_OK). > >> but possibly allowing >>

MacPorts 2.3.0 has been released

The MacPorts Project is happy to announce that the 2.3.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers for 10.4 [1], 10.5 [2], 10.6 [3], 10.7 [4], 10.8 [5] and 10.9 [6] (all universal builds, i386/pp

Re: 'port build' is getting EPERM from access(2) on "/var/tmp"

On 2014-5-24 03:19 , Quentin Barnes wrote: > On Tue, May 13, 2014 at 05:34:31AM +1000, Joshua Root wrote: >> We do exclude /var/tmp itself with the regex we use. We certainly don't >> want to allow file-write* on it, but possibly one of the subsets could >> be added safe

MacPorts 2.3.0-rc2 now available for testing

Source code and pkg/dmgs for MacPorts 2.3.0-rc2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no

Re: 'port build' is getting EPERM from access(2) on "/var/tmp"

On 2014-5-13 05:01 , Clemens Lang wrote: > Hi, > > Please keep the conversation on the list so others with the same problem > can follow. > >> Yes! The `sandbox_enable no' hack worked around the problem. >> >> Can you reproduce the problem by creating a fake package and trying the >> "test -w /v

Re: Migration question and binary question

On 2014-5-10 00:03 , Brandon Allbery wrote: > On Fri, May 9, 2014 at 1:39 AM, Joshua Root <mailto:j...@macports.org>> wrote: > > Handling variants of dependencies correctly is precisely why > restore_ports.tcl exists. The lack of automatic preservation of the >

MacPorts 2.3.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.3.0-rc1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no sho

Re: Migration question and binary question

Jerry wrote: > I am considering using the "Automatically reinstall ports" suggestion whereby > a script is downloaded which script then works with a previously saved > myports.txt. If I do this, will the script install old versions of ports > which had not been active? I'm thinking that this mig

MacPorts 2.3.0-beta2 now available for testing

Source code and pkgs for MacPorts 2.3.0-beta2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There a

Problem pyton PIL

> On Tue, Apr 15, 2014 at 9:00 AM, Spinxer wrote: > >> $ python >> Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) >> [GCC 4.0.1 (Apple Inc. build 5493)] on darwin >> > > You're getting /usr/bin/python (Apple's build). No idea what's up with its > PIL. > > You probably want `sudo port select --se

OpenSSL

Niels Dettenbach wrote: > On 8. April 2014 05:34:28 MESZ, Ludwig wrote: >>What else do I need to do about the addressed vulnerability besides >>updating >>the port — generate new keys or what? > > ...as far as i informed about the current security notice / patch in OpenSSH > (!) it makes no sens

MacPorts 2.3.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.3.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There a

py27-gst-python, targeting gstreamer1 vs gstreamer010

> Is there a port which is like py27-gst-python, but for gstreamer1 instead? Apparently there's no need for a specific installation of gstreamer python bindings any more with the new version; everything can be done via gobject-introspection and pygobject. I don't know much more about it than that

Re: Swarm on OS X 10.9

> On Feb 6, 2014, at 00:48, Degang Wu wrote: > >> Is there any progress in "porting" swarm to OS X 10.9? What prevents it to >> build on 10.9? I tried to build it from the source, but have encountered >> errors after errors. > > I don’t know why the port is disabled on Mavericks. I would guess

Re: cutting the tree: is there a way to remove leaves recursivelly?

sudo port uninstall --follow-dependencies leaves - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Scheduled downtime on Jan 28, 15-19 UTC

On 2014-1-24 05:44 , Rainer Müller wrote: > Hello, > > there will be a scheduled downtime for all MacPorts services due to > maintenance at our hosting provider MacOSforge. The servers will be > available with new IP addresses after the downtime, which will take up > to an hour until the change pr

Re: Troubles installing rc

> destroot fails for rc: > > /usr/bin/install -c history /opt/local/bin/- ;\ > rm -f /opt/local/bin/--; ln /opt/local/bin/- /opt/local/bin/-- ;\ > rm -f /opt/local/bin/-p; ln /opt/local/bin/- /opt/local/bin/-p ;\ > rm -f /opt/local/bin/--p; ln /opt/local/bin/- /opt/local/

Re: Trouble updating gnucash to current version with quartz

> On Dec 29, 2013, at 05:19, Olaf Föllinger wrote: > >> Error: org.macports.build for port gnome-desktop returned: command >> execution failed >> Please see the log file for port gnome-desktop for details: >> >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_relea

Re: gcc48/gcc49: isalnum/isgraph: Undefined symbols for architecture x86_64

On 2013-11-7 10:44 , Brian D. McGrew wrote: >>> >> Shouldn't that be '#include ' since you're compiling as C++? > > Yeah, probably so. It¹s compiled like this for over a year in MacOS 7 and > 8Š It¹s just now that I¹ve gone to 9 it¹s a problem. And, changing it to > #include didn¹t change anyt

gcc48/gcc49: isalnum/isgraph: Undefined symbols for architecture x86_64

> Hello all, > > I’m getting an undefined symbol for isalnum and isgraph using g++-mp-4.8. > > I found this article here: > http://stackoverflow.com/questions/19649421/something-odd-happened-to-c-11-in-mavericks > which mentions the issue in Mavericks and the Xcode command line tools. > Howev

MacPorts 2.2.1 has been released

The MacPorts Project is pleased to announce the release of version 2.2.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs,

Downgrading squid3

It's pretty garbled because of overlapping output from multiple make jobs (append 'build.jobs=1' to the command to avoid this BTW), but it looks like the failure is due to a compiler warning about a tautological comparison, which is escalated to an error because -Werror is used. The current squid3

MacPorts 2.2.0 has been released

The MacPorts Project is happy to announce that the 2.2.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], 10.7 [3], and 10.8 [4] (all universal builds, i386/ppc for 10.5 and t

MacPorts 2.2.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.2.0-rc1 are now available [1]. Testing of either of these install methods is helpful. While there are no known regressions from 2.1.3 at this point, be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you f

MacPorts 2.2.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.2.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There a

qt4-mac using wrong g++

> On Feb 11, 2013, at 15:21, Frank J. R. Hanstick wrote: > >> I thought that MacPorts defaulted to the system gcc default setting(s) >> (limited to Apple certified versions of course) rather than a hard coded >> default setting. > > The hardcoded default compiler in MacPorts, which varies by Xc

How to get a full list of dependents?

> Apparently commands such as "port dependents xxx" or "port echo > dependentof:xxx" > will only list *installed* dependents --- and "xxx" must itself be installed. > > How can I get a full list of ports that are dependents of "xxx", whether or > not > they or "xxx" are installed? > > ATM I wou

MacPorts 2.1.3 has been released

The MacPorts Project is pleased to announce the release of version 2.1.3. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs,

mongodb-2.2.2_0 binaries for ML 10.8 missing from MacPorts

Lawrence Velázquez wrote: > On Dec 9, 2012, at 11:08 PM, Behrang Saeedzadeh > wrote: > >> Is this intentional or are the binaries eventually going to be added to >> MacPorts? > > We cannot distribute a binary for mongodb because it has a dependency on > openssl, and their licenses conflict. >

Re: dyld: Library not loaded: libmaloc.dylib

On 2012-12-9 14:42 , Ryan Schmidt wrote: > On Dec 8, 2012, at 17:26, Jeremy Huddleston Sequoia wrote: > >> On Dec 7, 2012, at 1:50 PM, "Yao, Xiaolan" wrote: >> >>> I installed Pymol and the APBS plugin using MacPorts. I tried to >>> run APBS calculations within Pymol, but it didn't give the prop

Re: Fetching anything segfaults when Pextlib calls system Tcl

> Thread 0 Crashed: Dispatch queue: com.apple.main-thread > 0 libSystem.B.dylib 0x7fff85270c00 strlen + 16 > 1 Tcl 0x00010008a350 Tcl_SetResult + 83 > 2 Pextlib.dylib 0x00010070e617 > SetResultFromCurlErrorCode +

Re: any way to use OS 10.3.9?

Ryan Schmidt wrote: > You can get an archive of ports from December 14, 2008, from the day MacPorts > 1.7.0 was released, here: > > https://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/ > > Using that, you could install the subversion port, then you could get > somewhat newer

Re: any way to use OS 10.3.9?

David Prager Branner wrote: > I have OS 10.3.9 on an old iBook, with Xcode v. 1.5 installed. No higher > versions of the OS can be installed on this hardware. > > I was able to install and build Macports 1.710, apparently without > problems, but on the initial > > sudo port -v selfupdate >

Re: I need consultation on running WINE on the Mac

On 2012-10-17 05:40 , William H. Magill wrote: > > On Oct 16, 2012, at 7:00 AM, Joshua Root wrote: > >> After installing wine-crossover, all you should need to run is (all one >> line, ignore any line breaks inserted by email software): >> >> WINEPREFIX="

Re: I need consultation on running WINE on the Mac

On 2012-10-16 22:33 , Ryan Schmidt wrote: > > On Oct 16, 2012, at 06:00, Joshua Root wrote: > >> I've just applied it to the wine-crossover port. Seems to work fine. > > But wine-crossover 11.2.2 is based on wine 1.4.1, with which William says his > game no lon

Re: I need consultation on running WINE on the Mac

> I know this is not a MacPorts issue, so please direct this to somewhere that > makes sense. > > Basically, I'm a total newbee when it comes to RAW WINE. I've historically > used Codeweavers Crossover which is Wine 1.4.1 > Which is packaged to run quite nicely under Mountain Lion (10.8.2) >

Re: Prebuilt alternatives

On 2012-9-26 04:05 , Kenneth Miller wrote: > Why does macports insist on using only local builds? It doesn't. If a prebuilt package is available, it will be used. There are a number of reasons why one might not be. - Josh ___ macports-users mailing list

gdk-pixbuf fails to build

> Hi, > gdk-pixbuf fails to build > logfile attached > ideas welcome > Thanks > > --R Out of curiosity, what do you need gdk-pixbuf for? - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/list

MacPorts 2.1.2 has been released

The MacPorts Project is pleased to announce the release of version 2.1.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs,

Re: xmms from ports uses Disk Writer Plugin for audio output?

On 2012-6-19 20:52 , Jim Graham wrote: > On Mon, Jun 18, 2012 at 11:28:51PM -0700, Jeremy Huddleston wrote: >> xmms was old and barely maintained a decade ago. > > Oh. Well, any suggestions for a similar port, then? xmms2? - Josh ___ macports-users ma

Re: post-pkg failing

(moving to -dev since this involves writing a portfile) On 2012-5-28 10:43 , Paulo Moura wrote: > Hi, > > I'm using the latest versions of MacPorts, Xcode, and PackageMaker. I have a > portfile where I define: > > post-pkg { > set resources ${workpath}/${name}-${version}.pkg/Contents/Reso

MacPorts 2.1.1 has been released

The MacPorts Project is pleased to announce the release of version 2.1.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs,

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 >>&g

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: 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

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: MacPorts 2.1.0-rc2 now available for testing

On 2012-5-13 05:48 , Jack Howarth wrote: > Is anyone else finding that a clean install of MacPorts 2.1.0-rc2 from > the source tarball on 10.7.4 with Xcode 4.3.2 results in the installed > MacPorts building packages with llvm-gcc rather than clang? Is there a quick > fix to hack port to properly de

MacPorts 2.1.0-rc2 now available for testing

Source code and pkg/dmgs for MacPorts 2.1.0-rc2 are now available [1]. Testing of either of these install methods is helpful. While there are no known regressions from 2.0.4 at this point, be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that y

MacPorts 2.1.0-rc1 now available for testing

Source code and pkg/dmgs for MacPorts 2.1.0-rc1 are now available [1]. Testing of either of these install methods is helpful. While there are no known regressions from 2.0.4 at this point, be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that y

Re: MacPorts 2.1.0-beta1 now available for testing

--beta) flag for updating easily to the testing versions? > > -d > > > On Mon, Apr 23, 2012 at 8:42 AM, Joshua Root <mailto:j...@macports.org>> wrote: > > Have many people tested this? We've only had one real bug reported so > far, and that o

  1   2   3   4   5   6   7   8   9   >