On Thu, Oct 9, 2014 at 12:25 PM, Barrie Stott wrote:
> This is the sequence of events that led to me getting the error in the
> Subject line.
Check your .bash_profile / .bashrc; you appear to be defining a function
named ttr%%, which is an illegal function name.
--
brandon s allbery kf8nh
On Thu, Oct 9, 2014 at 4:06 PM, Barrie Stott wrote:
> function ttr()
You should use wither "ttr()" or "function ttr", not both. It's replacing
() with %% and then tripping over it later (possibly it accepts it when
defined for some reason, but it still knows it's illegal).
--
brandon s allber
On Thu, Oct 9, 2014 at 4:17 PM, Barrie Stott wrote:
> >> If anyone can tell me what is wrong or suggest how I can proceed I'd be
> pleased to hear about it.
> >
> > The `mvim` script doesn't contain the string "BASH_FUNC".
It won't; that's the hackaround for the "Shellshock" exported functions
On Thu, Oct 9, 2014 at 4:46 PM, Barrie Stott wrote:
>
> On 9 Oct 2014, at 21:10, Brandon Allbery wrote:
> > On Thu, Oct 9, 2014 at 4:06 PM, Barrie Stott
> wrote:
> > function ttr()
> >
> > You should use wither "ttr()" or "function ttr", no
On Thu, Oct 9, 2014 at 5:41 PM, Barrie Stott wrote:
> BASH_FUNC_ttr%%=() { d="Jan 25: Feb 22: Mar 29: Apr 26: May 31: Jun 28:
> Sep 27: Oct 25: Dec 6";
> BASH_FUNC_usenosql%%=() { PS1="\[\](nosql):\W \$ \[\]";
> BASH_FUNC_mymup2pdf%%=() { mup-prog $@ > /tmp/x.ps
>
> ;
> BASH_FUNC_b12%%=() { d
On Fri, Oct 10, 2014 at 6:13 AM, Barrie Stott wrote:
> Wouldn't the stopping of function export from MacPorts' bash be a big
> restriction on bash use. For example, I want to be able to type "mvim",
> with or without parameters, to open a MacVim window. At present, I get the
> error:
> "/bin/sh:
On Fri, Oct 10, 2014 at 7:19 AM, Mathias Laurin
wrote:
> #!/usr/bin/env -i /bin/sh
I expect MacVim would behave very poorly without $HOME and possibly $SHELL
set. Probably others as well.
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Fri, Oct 10, 2014 at 10:07 AM, Barrie Stott wrote:
>
> Where is this Debian/FreeBSD patch? What is it patching? Are there
> instructions for its use?
>
https://svnweb.freebsd.org/ports/head/shells/bash/files/extrapatch-import-functions?revision=369467&view=markup
It's a patch to bash to only i
On Fri, Oct 10, 2014 at 11:06 AM, Barrie Stott wrote:
> I've done that and I've doe something similar with /bin/sh as well.
> Surprisingly, I found original /bin/bash and /bin/sh different. The new
> stuff is:
> -rwxr-xr-x 1 root wheel 1893232 10 Oct 15:43 /bin/bash
> -rwxr-xr-x 1 root wheel
On Fri, Oct 10, 2014 at 6:45 PM, Greg Earle wrote:
> Personally I wouldn't replace Apple's bash/sh with MacPorts' versions.
I did suggest building it himself first, with copying MacPorts' bash as a
fallback. I even provided a caveat as to why it might not be a good idea.
--
brandon s allbery
On Sat, Oct 11, 2014 at 5:31 AM, René J.V. wrote:
> Actually, you can. Either update the addresses in your
> /etc/apt/sources.list and sources.list.d/*
Ubuntu is moderately infamous for even stepping up one version not working;
multiple versions in a single go usually fails in my experience. (T
On Sat, Oct 11, 2014 at 8:35 AM, Ryan Schmidt
wrote:
> It's the version of bash the scripts that came with your operating system
> were tested with. It's possible there are backwards-incompatible changes in
> bash 4.
There are definitely backwards incompatible changes; most notably, they
remove
On Sat, Oct 11, 2014 at 9:10 AM, René J.V. wrote:
> Linux Mint is right to do so because they have a habit of modifying things
> to their own tastes and against established "rules"
...which they picked up from Ubuntu and is why Ubuntu upgrades are risky
--
brandon s allbery kf8nh
On Sat, Oct 11, 2014 at 9:07 AM, René J.V. wrote:
> Maybe it's time for me to get re-acquainted with TcL ... ;)
MacPorts' filter syntax has nothing to do with Tcl, aside from happening to
have been written in it; it's also been around for over a decade. :p
Perhaps getting (re)acquainted with `m
On Sat, Oct 11, 2014 at 11:37 AM, René J.V. wrote:
> >...which they picked up from Ubuntu and is why Ubuntu upgrades are
> risky
>
> I'm not so sure about that ...
>
I am. Ubuntu takes a lot of things from testing and does its own release
engineering, but misses a lot of stuff Debian does as
On Sat, Oct 11, 2014 at 3:22 PM, Chris Jones
wrote:
> Did Apple make that scanner ? I presume not, in which case its not Apples
> responsibility to provide drivers for all possible third party devices, but
> the vender of those devices. If they choose not to provide an Intel driver
> supporting 1
On Sun, Oct 12, 2014 at 4:14 PM, Alex Tomkins wrote:
> However could the 3.2 and 3.3 ports be reconsidered?
I suspect only if someone steps forward to maintain them.
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Sun, Oct 12, 2014 at 6:11 PM, Peng Yu wrote:
> I get the following problem when running cssh. My mac is of version OS
> X 10.9.5. Does anybody know what the problem is? Thanks.
>
> $ cssh machine1 machine2
> Can't connect to display `tmp/launch-KZPKti/org.macosforge.xquartz:0':
> Invalid argum
On Sun, Oct 12, 2014 at 6:50 PM, René J.V. wrote:
> Do this weird kind of $DISPLAY specifications exist outside of OS X? I
> remember having tripped over it myself in my early days on 10.6 (or was it
> 10.4?), but nowadays XQuartz (thank goodness) uses a normal
> host:display:screen syntax.
No,
On Sun, Oct 12, 2014 at 6:50 PM, René J.V. wrote:
> Do this weird kind of $DISPLAY specifications exist outside of OS X?
By the way, this implies you think programs have some right to be aware of
what $DISPLAY has in it, and/or should be able to randomly mess with it? I
think that limits future
On Sun, Oct 12, 2014 at 6:37 PM, Brandon Allbery
wrote:
> On Sun, Oct 12, 2014 at 6:11 PM, Peng Yu wrote:
>
>> $ cssh machine1 machine2
>> Can't connect to display `tmp/launch-KZPKti/org.macosforge.xquartz:0':
>> Invalid argument at
>> /opt/local/lib/
On Sun, Oct 12, 2014 at 7:21 PM, Brandon Allbery
wrote:
> It's the Perl module, which on line 2256 is assuming that a slash simply
> must indicate an X11R3-style Unix socket (DISPLAY=unix/localhost:0). Sadly
> there's no maintainer, and the bug is filed at least twice (
On Sun, Oct 12, 2014 at 8:05 PM, René J.V. wrote:
> Only if you leave the launchd plist in place. I prefer to launch my X11
> server by hand or not at all, so the plist gets thrown out 1st thing after
> each XQuartz update.
> Maybe that's simply the explanation why $DISPLAY is :0 for me (or :1 or
On Mon, Oct 13, 2014 at 6:50 AM, René J.V. wrote:
> Come to think of it, I can't (or maybe, refuse to) see a good, compelling
> reason why a local X11 server would have to use a non-human-readable
> $DISPLAY spec if it can be identified uniquely through :0 (or :1, :2 etc
> for subsequent instance
On Mon, Oct 13, 2014 at 8:53 AM, René J.V. wrote:
> >The simple reason to why Linux does it one way and OS X another, however,
> >is that on Linux X11 is primary and gets "naming rights". on OS X, it is
> an
> >interloper and does not get to choose for itself how the system it's on
> >works or wh
On Mon, Oct 13, 2014 at 9:34 AM, Chris Jones
wrote:
> My argument is not based on what some standard says about what DISPLAY
> should or should look like, but the basic premise that extracting
> information from $DISPLAY is just a bad idea and should be avoided.
Note that p5-x11-protocol has le
On Mon, Oct 13, 2014 at 10:09 AM, René J.V. wrote:
> As long as there is documentation that's not contradicted/superseded by
> more recent/authoritative documents and that states that the 1st element of
> $DISPLAY refers to the X server host, using that information in code may
> not be the most f
On Mon, Oct 13, 2014 at 11:15 AM, René J.V. wrote:
> > view towards the way things are in Linux-land.
>
> Correction: Unix. X11 was around (long) before Linux, and no matter how
> you turn it, OS X *is* a Unix OS.
>
So unix/hostname:display was somehow not Unix? You're just digging the hole
deep
On Mon, Oct 13, 2014 at 11:59 AM, René J.V. wrote:
> I'm going to stop this discussion here, and not even try to understand
> where this comes from.
> Take your own advice, and see if you can make any sense out of your own
> proclamations.
>
If you will stop parroting Linux propagandists almost
On Wed, Oct 15, 2014 at 8:02 PM, Terry Barnum wrote:
> ---> Verifying checksums for postfix
> Error: org.macports.checksum for port postfix returned:
> postfix-2.11.2.tar.gz does not exist in /
>
This means it thinks it downloaded it already but it's not there for some
reason. `sudo port clean
On Thu, Oct 16, 2014 at 7:04 PM, Dave Horsfall wrote:
> Short of using "script" or scrolling way way back, is there a facility to
> save some of the notifications during an installation? For example, I've
> just installed GIMP, and there were quite a few "you might want to do
> this" sort of thi
On Sat, Oct 18, 2014 at 5:20 PM, Gregory Shenaut
wrote:
> And I note that in the cmake log, it appears to require the
> MacOSX10.10.sdk, which is a component of XCOde 6.1.
>
> I could download a pre-release version of XCode 6.1 from the Apple site,
> but it seems odd to me that the ports won't co
On Sun, Oct 19, 2014 at 5:19 AM, René J.V. wrote:
> That's a really curious requirement for a FOSS utility ... doesn't it
> build on earlier versions of OS X that lack the 10.10 SDK by definition? Or
> doesn't a binary built on, say, 10.6, run on 10.10?
If you build on 10.6, it looks for the 10
On Sun, Oct 19, 2014 at 1:00 PM, Carlo Tambuatco
wrote:
> before I do a clean wipe of all my macports and spend the next 10 hours or
> so downloading, configuring, building and reinstalling 459 separate ports.
> There may be a simpler solution.
If there were one, someone would have found it by
On Sun, Oct 19, 2014 at 1:46 PM, Dave Horsfall wrote:
> OK, I have to bite: can someone please tell this non-American just how
> "Yosemite" is pronounced?
>
Yoh-SEH-mih-tee
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Sun, Oct 19, 2014 at 2:15 PM, Chris Jones
wrote:
> ... it is not a matter of 'seeing fit'. Unless you want ongoing problems,
> the only correct thing to do is to reinstall *all* your ports...
Uninstalling port you don't want any more is perfectly legitimate, provided
it's not a dependency of
On Sun, Oct 19, 2014 at 2:21 PM, Chris Jones
wrote:
> Well yes, you do not have to reinstall everything after removal. The
> important bit is the removal step... ;)
But the thing you complained about was exactly "remove or reinstall (...)
as you see fit". It was not admitting to other possibili
On Sun, Oct 19, 2014 at 2:25 PM, Lawrence Velázquez
wrote:
> It looks like you used `port select` to make Python 3.x your default, and
> LLVM's configure is choking on it.
This sounds like a bug in the port, to be honest. (And it's not the first
time I've heard of ports tripping over `port sele
On Sun, Oct 19, 2014 at 2:33 PM, Carlo Tambuatco
wrote:
> Supported or not...this way seemed to work for a majority of my ports and
> I was wondering whether nuking all 459 of my ports for the sake of a few
> that don't work seems like an inefficient solution. It seems there are
> other ways to a
On Sun, Oct 19, 2014 at 2:35 PM, Carlo Tambuatco
wrote:
> But the doesn't the -u option do exactly what is in the migration guide?
> ie: uninstall old ports in favor of the new upgraded version? What's the
> difference?
-u means remove archived old versions of the port that is currently being
u
On Sun, Oct 19, 2014 at 2:42 PM, Carlo Tambuatco
wrote:
> When you upgrade a port, everything it depends on gets updated first,
> right? What doesn't get upgraded should not affect what does get upgraded
> during the configure/build/install/activate phase, right? So how is using
> -u different fr
On Sun, Oct 19, 2014 at 2:52 PM, Carlo Tambuatco
wrote:
> Even if this process accumulates useless or redundant ports over time, it
> should not affect the build of the newer ports, right?
But they will still be installed and will therefore be in your list of
reinstalls.
--
brandon s allbery
On Sun, Oct 19, 2014 at 2:54 PM, Carlo Tambuatco
wrote:
> I mean, would not a better more efficient method be to create a list of
> your requested ports and just migrate those?
>
I think the Migration page used to hint at that. In fact I generally do,
instead of listing all installed ports, limi
On Sun, Oct 19, 2014 at 3:02 PM, Carlo Tambuatco
wrote:
> ...in particular, how is it going to change the situation of pypy which is
> due to a checksum error, not a build error at all?
Checksum errors mean either you have a bad download (try `port clean` on
the port in question) or the upstrea
On Sun, Oct 19, 2014 at 8:52 PM, Jason Mitchell
wrote:
> Is there a buildbot in the works for Yosemite ports? I checked
> https://build.macports.org/buildslaves but didn't see anything for
> Yosemite yet. Maybe I've misunderstood the process, or am just being
> greedy?
>
It was requested; the
On Sun, Oct 19, 2014 at 9:05 PM, Tim Johnson wrote:
> I've installed emacs 24.
>
> If I do
> which -a emacs
>
> I get
> /opt/local/bin/emacs ## New emacs
> /usr/bin/emacs ## Old emacs
>
1. "which" lies a lot. use "type".
2. Which one is found depends on a number of things:
a. the order o
On Wed, Oct 22, 2014 at 5:46 PM, William H. Magill wrote:
> 1- This release of OSX TIGHTLY integrates local I/O with iCloud (i.e.
> network) I/O. This implies that there was probably some significant work
> done in the Kernel Level I/O routines.
I am under the impression that this integration i
On Thu, Oct 23, 2014 at 11:17 AM, Jameson Merkow wrote:
> This works perfectly on linux (automatic and cron) and on mac when I
> initiate the build manually, but when I added it to a launchd (or cronjob).
>
> I believe that the issue lies with the toolchain, when I run the script,
> the tool chai
On Thu, Oct 23, 2014 at 7:06 PM, William H. Magill wrote:
> What I'm looking for is the "notes" (or explanations) which were in the
> install stream.
> Are they recorded anywhere? Or do you have to remember to copy them down
> on the fly?
>
port notes installed
--
brandon s allbery kf8nh
On Thu, Oct 23, 2014 at 9:23 PM, William H. Magill wrote:
> On Oct 23, 2014, at 8:34 PM, William H. Magill wrote:
> > On Oct 23, 2014, at 7:09 PM, Brandon Allbery
> wrote:
> >> port notes installed
> >
> > Aha useful.
> >
> > Except that Apache2 yie
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 also w3m and
netrik.
("port search browser" also tells me there is indee
On Thu, Oct 23, 2014 at 9:52 PM, William H. Magill wrote:
> Finding /opt/local/apache2/bin/apachectl was "obvious." But not from any
> pllist file.
>
> Looking at that file and comparing it with Apple's they are significantly
> different.
> I.e. /opt/local/apache2/bin/apachectl contains no refer
On Thu, Oct 23, 2014 at 10:43 PM, William H. Magill wrote:
> They should be something like:
>
> sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper stop
> sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper
> start
> sudo /opt/local/etc/LaunchDaemons/org.macp
On Thu, Oct 23, 2014 at 10:49 PM, William H. Magill wrote:
> At one time there were instructions in the port on how to start and stop
> the Apache server -- they are now missing.
>
Actually, the way you are *supposed* to do it --- and I suspect this will
infuriate you --- is
sudo port load
On Thu, Oct 23, 2014 at 10:49 PM, William H. Magill wrote:
> At one time there were instructions in the port on how to start and stop
> the Apache server -- they are now missing.
>
> The technique to be used is anything but obvious for anyone familiar with
> Apache.
>
By the way, could you expla
On Sat, Oct 25, 2014 at 9:02 PM, Ryan Schmidt
wrote:
>
> On Oct 25, 2014, at 9:55 AM, Dave Horsfall wrote:
> > Getting various installation notes during the build, which I've probably
> > lost in my scroll-back buffer. I wish these were squirreled away
> > somewhere, with a note at the end saying
On Thu, Oct 30, 2014 at 3:17 PM, Eneko Gotzon wrote:
> The gimp2 port and all its dependencies are apparently correctly installed
> and active.
I believe you want the gimp-app port. (Note that it is reported to have
problems on Yosemite.)
--
brandon s allbery kf8nh
On Fri, Oct 31, 2014 at 9:54 PM, James Linder wrote:
>
> I was debating a ‘me too’ reply since it works for me, but looking in the
> Apps directory shock, horror, gasp it is indeed not there! I always click> open with gimp and have never noticed it NOT in apps. Platypus is a
> nice launcher creat
On Sat, Nov 1, 2014 at 12:35 PM, Dave Horsfall wrote:
> Not enough memory? I've got 4GB here!
The dbus client library synthesizes that error message when it can't
connect to the dbus session agent, as indicated by the earlier messages.
(That said, 4GB isn't much on OS X.)
--
brandon s allber
On Sat, Nov 1, 2014 at 1:24 PM, Dave Horsfall wrote:
> I'm still baffled, though. Signal 11 is SIGSEGV? That tells me "program
> bug".
>
Yes. Also not clear from this if it's the child of gimp that is segfaulting
or if the child had exec()ed launchtl by then (which would be an Apple
bug). But
On Tue, Nov 4, 2014 at 12:49 PM, Artur Szostak
wrote:
> I cant seem to figure out the appropriate variable to use for the extract
> phase. Or more specifically post-extract. Anyone know this? I thought
> ${workdir} would work but its not defines during that phase.
http://guide.macports.org/#ref
On Sun, Nov 9, 2014 at 3:07 PM, Nick Johnson wrote:
> went ok spewing out lots of info about the packages it was deactivating,
> as far as the following line, and then it hung
>
> ---> Deactivating boost @1.56.0_1+no_single+no_static+python27
>
I suspect if you run with -d to see what it's doin
On Sat, Nov 15, 2014 at 12:17 PM, René J.V. wrote:
> Have you asked your users to start the executable in the debugger to see
> if the SIGTERM results from an abort function being called or something
> else?
9 is SIGKILL, not SIGTERM.
I am under the impression that Apple doesn't like fully sta
On Sat, Nov 15, 2014 at 12:53 PM, Qianqian Fang wrote:
> On 11/15/2014 12:17 PM, René J.V. Bertin wrote:
>
>> Have you asked your users to start the executable in the debugger to see
>> if the SIGTERM results from an abort function being called or something
>> else?
>>
>
> I asked my users to try
On Sat, Nov 15, 2014 at 11:51 AM, Qianqian Fang wrote:
> I have compiled a set of binaries on previous versions of Mac (mostly OSX
> 10.6) with macports gcc/g++ using static linking, and thought that these
> binaries will be supported in the future versions of MacOS.
I should note that the corr
On Mon, Nov 17, 2014 at 2:18 AM, Kevin Burnett wrote:
> :debug:main No nee
>
> Yes, it ends on “No nee”, and it sits on that for hours.
>
Use "port -d" so it logs the debug output to the terminal, possibly running
under script(1); the default buffering strategy for output to files is
block-based
On Wed, Nov 19, 2014 at 10:45 AM, René J.V. wrote:
> > That though does not make what I said incorrect. clang 3.4 fully
> > supports c++11. A statement of fact.
>
> Please don't take my statement about C++11 support out of context.
> Relevant earlier thread: "clang++-mp-3.4 doesn't find initializ
On Thu, Nov 20, 2014 at 2:44 AM, Michael wrote:
> I can't get it to actually load a kernel driver to get the user fuse stuff
> going, and mount_ntfs never gets called.
>
Are you on Yosemite? Apple no longer allows unsigned kernel drivers unless
you tweak a magic boot setting, so ports like osxfu
On Sat, Nov 22, 2014 at 10:01 AM, René J.V. wrote:
> Out of curiosity, what's wrong with the system's ntp?
For what it's worth, starting with 10.8 I've been seeing the clock go out
of sync a lot. On my current 10.9 the system usually ends up 2 minutes
ahead of my other ntp-synced devices.
I've
On Sat, Nov 22, 2014 at 5:28 PM, Mark Brethen
wrote:
> I had to do a clean install of the OS (Mavericks) and now ready to
> re-install macports. Should I install xcode 6.1 or stick with 5? (I've
> heard that 6 is buggy).
>
5 won't have Mavericks support (and it probably won't even install). 6.0
On Sun, Nov 23, 2014 at 4:51 AM, Jeremy Lavergne wrote:
> Sounds like macports cannot connect to download the list of packages
> available. Are you able to run the rsync command manually? Any rsync
> outside your network?
>
rsync.macorts.org and trac.macports.org are not responding.
--
brandon
On Sun, Nov 23, 2014 at 10:28 PM, René J.V. wrote:
> On Saturday November 22 2014 20:10:08 Michael wrote:
> > Pacemaker wants to skew the system clock.
> No, you misread (and Apple's grammar is no longer what it used to be) ...
> : "By default, pacemaker will call adjtime(2) once per second to *s
On Sun, Nov 23, 2014 at 10:41 PM, Brandon Allbery
wrote:
> FWIW I disabled pacemaker here and it solved the problem of ntpd not being
> able to adjust the clock (pacemaker was apparently undoing it). But it is
> still not *syncing* the clock after the initial sync, it is building up
On Mon, Nov 24, 2014 at 12:38 AM, Hinckley Dan wrote:
> On 23 Nov 2014, at 17:50, Brandon Allbery wrote:
>
> On Sun, Nov 23, 2014 at 10:41 PM, Brandon Allbery
> wrote:
>
> So I will kill off Apple's foo and use ntpd from ports, I think. It may
> not "save bat
On Mon, Nov 24, 2014 at 3:37 AM, René J.V. wrote:
> They'd done better by providing some kind of profile (mechanism) allowing
> to disable ntp or reduce its polling frequency when on battery ...
> Maybe it's possible to come up with something like that ourselves?
>
openntpd would be a good start
On Mon, Nov 24, 2014 at 11:29 AM, Daniel J. Luke wrote:
> > On Nov 24, 2014, at 11:11 AM, Michael wrote:
> > Frankly, I don't understand how the drift file can be changed by ntpd
> while the timestamp remains constant. I'd be very interested to hear if
> anyone else can confirm this observation.
On Mon, Nov 24, 2014 at 12:09 PM, Dave Horsfall wrote:
> On Mon, 24 Nov 2014, Brandon Allbery wrote:
> > >
> http://prod.lists.apple.com/archives/darwin-kernel/2014/Nov/msg00015.html
> >
> > Ooh. That's especially fun given that pacemaker checks the mod time on
&
On Tue, Nov 25, 2014 at 5:13 AM, Mojca Miklavec wrote:
> Indeed. Starting a new shell or running "hash -r" fixed the problem.
> Weird, I didn't know that binary locations are cached.
>
Shells have cached locations since the original csh (which uses "rehash";
"hash -r" came from ksh). "type" will
On Thu, Nov 27, 2014 at 10:38 AM, Clemens Lang wrote:
> I think you are missing the gnustep foundation libs and some other
> packages. The
> MacPorts configure script should automatically figure out the right flags
> to pass
> for this linking step, and -framework CoreFoundation -framework
> Syst
On Fri, Nov 28, 2014 at 10:59 AM, René J.V. wrote:
> >>So apparently some version of gnustep provides this header?
>
> No, at least not that I know. https://code.google.com/p/cocotron/
>
So I find at http://www.cocotron.org that you are supposed to not only
install the frameworks, but also a mod
On Fri, Nov 28, 2014 at 12:27 PM, René J.V. wrote:
> On Friday November 28 2014 11:14:38 Brandon Allbery wrote:
> >On Fri, Nov 28, 2014 at 10:59 AM, René J.V. wrote:
>
> >So I find at http://www.cocotron.org that you are supposed to not only
> >install the framewo
On Mon, Dec 1, 2014 at 1:58 AM, Carlo Tambuatco
wrote:
> First I've heard about this.
>
> On Mon, Dec 1, 2014 at 1:42 AM, Dave Horsfall wrote:
>
>> When were spammers allowed on this list?
>>
>
Just arrived here. :(
For the record, keeping spammers off a mailing list is difficult these days.
-
On Mon, Dec 1, 2014 at 4:37 PM, William H. Magill wrote:
> Actually the increase in SPAM started sometime in August or maybe July.
A couple months before that, would be when the GameOver ZeuS botnet came
back online. There was a significant drop in spam during the months when it
was offline ---
On Sat, Dec 6, 2014 at 10:07 PM, Jacob Walchuk
wrote:
> Hello, I’m having a problem, the xfce panel won’t install. The logs are in
> a pastebin: http://pastebin.com/UD399vuW
>
http://trac.macports.org/ticket/32651 and the specific error indicates that
it's using functionality that was deprecated
On Sun, Dec 7, 2014 at 4:10 PM, Marko Käning wrote:
> Joshua, how can we advertise mpstats to more users???
>
Message in the installer dmg (maybe even a checkbox to auto-install the
port?) and after selfupdate to a new version? The latter would even be
better as a "display notes for base
On Tue, Dec 9, 2014 at 10:32 AM, FritzS - gmx wrote:
> If I want start it comes the error: dyld: Library not loaded:
> /usr/local/lib/libgtk-x11-2.0.0.dylib / Referenced from: /opt/local/bin/pan
> / Reason: image not found (1005)
> but libgtk-x11-2.0.0.dylib is in /opt/local/lib/libgdk-x11-2.0.0.
On Tue, Dec 9, 2014 at 11:19 AM, FritzS - gmx wrote:
>
> Am 09.12.2014 um 16:39 schrieb Brandon Allbery :
>
> On Tue, Dec 9, 2014 at 10:32 AM, FritzS - gmx wrote:
>
>> If I want start it comes the error: dyld: Library not loaded:
>> /usr/local/lib/libgtk-x11-2.0.0.dy
On Wed, Dec 10, 2014 at 2:27 PM, René J.V. wrote:
> >> The thing is, if ever we want to allow Qt4 and Qt5 to be present at the
> same time, the installation location will *have* to change, and dependent
> ports will have to comply with that.
> >
> >Yes, but not by using variants. MacPorts doesn't
On Thu, Dec 11, 2014 at 4:07 AM, René J.V. wrote:
> > How about a main port with the new paths, and a stub port or subport that
> > depends on the main port, conflicts with qt4-mac, and installs the
> > symlinks? Then we can replace qt4-mac with the stub port at some point.
>
> I like the idea. I
On Thu, Dec 11, 2014 at 12:38 PM, René J.V. wrote:
> No, it doesn't. I figured I had to edit it, but how?
>
> Alternatively, couldn't I change the destroot command so that it executes
> make with an appropriate set of options?
>
>
You would still have to at least inspect the Makefile to find out
On Thu, Dec 11, 2014 at 1:42 PM, René J.V. wrote:
> > We already pass DESTDIR=$destroot to the make invocation. Make can't
> force a makefile to use it.
>
>
>
> See, that's the bit I was missing :)
>
>
It's only the same thing RPM has conditioned Linux devs into doing for
years now
--
brand
On Thu, Dec 11, 2014 at 4:30 PM, David Lyon wrote:
> Following a recent update to Yosemite, I have reinstalled Xcode and
> Macports. Upon running install Gimp2 followed by install ufraw, there is
> no evidence e of Wilber in the Macport folder in Applications. I have read
> that Wilber should be
On Thu, Dec 18, 2014 at 8:25 AM, Mark Fulton wrote:
>
> I'm trying to install byobu on my Mac which depends on a diff file hosted
> on trac.macports.org
>
> . However, when trying to download the file the connection times out.
>
Yes, trac's down again. The admin's been notified.
--
brandon s al
On Thu, Dec 18, 2014 at 10:15 AM, Daniel J. Luke wrote:
>
> also, why would homebrew be using a patch from macports like that anyway?
Homebrew's been "reusing" stuff for a while now.
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Thu, Jan 1, 2015 at 11:32 PM, P Kishor wrote:
> Hi, I am not sure what to make of your email. The log file is 2562
> lines long, so I included the last 20 or so lines where the actual
> error message appears (or so it seems to me).
>
That's not the actual error message; it is where the build
On Thu, Jan 1, 2015 at 11:28 PM, William H. Magill wrote:
> File:///Users/magill/ports
>
I'm pretty sure the URL scheme needs to be all lowercase; that is, "file:"
not "File:".
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Fri, Jan 2, 2015 at 12:46 AM, P Kishor wrote:
> https://dl.dropboxusercontent.com/u/3526821/main.log
So, the actual error is a link error for a bunch of missing symbols.
Looking for why those symbols might be missing, I find this:
:info:build ld: warning: ignoring file
/Applications/GRASS-6
On Sun, Jan 4, 2015 at 2:06 AM, William H. Magill wrote:
> It also appears that the function of the ServerName directive has changed.
> The current Apache manual
> http://httpd.apache.org/docs/2.2/mod/core.html#servername
>
>
> describes its syntax as requiring a FQDN -- which neither Localhost n
On Sun, Jan 4, 2015 at 10:34 AM, René J.V. wrote:
> On Sunday January 04 2015 09:05:42 Brandon Allbery wrote:
>
> >From the standpoint of DNS, "localhost" is fully qualified: it is not the
> >short form of a name that is meaningful only in the context of a
> part
On Sun, Jan 4, 2015 at 11:20 AM, William H. Magill wrote:
> > BIND9 at least comes with a local zone definition that includes
> "localhost." as a name, with the usual mapping. That said, people *usually*
> get it from /etc/hosts... *but* OS X is a little weird in how/when it uses
> the hosts file
501 - 600 of 1169 matches
Mail list logo
