Re: Poll: should Trac send email notifications when adding or replacing an attachment?
On Fri, 4 Nov 2016, Dominik Reichardt wrote: > For what it’s worth, as an admin of other projects and reporter of bugs > *I* do appreciate notifications of all those changes. When I report or > CC: me to a bug I want to know what happens to the report and attached > files. Me too :-) Seriously, I too want to be notified whenever the rug is about to pulled out from underneath me, and my utmost thanks go to the Macports bods for doing what must be a thankless job. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Guile broken again...
Sigh, this is becoming tedious: ---> Building guile Error: org.macports.build for port guile returned: command execution failed Please see the log file for port guile for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/main.log Error: Unable to upgrade port: 1 No point in showing the error log; it's been posted before. (I know; it's not Guile itself, but that's what's being reported back to the user.) -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Sierra 10.12.1 and NTP
Just upgraded to 10.12.1, and system.log began spewing out this: Oct 27 14:54:36 ozzie com.apple.xpc.launchd[1] (org.macports.ntp): Service only ran for 0 seconds. Pushing respawn out by 10 seconds. along with annoying pop-ups. Running "launchctl remove org.macports.ntp" fixed it, but I have a feeling that I need it for the NTP client. Anyone else seen this? Same thing happened with "rsyncd" and "lighttpd" too (all ports that I'd installed). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Guile appears to be broken again...
On Sun, 16 Oct 2016, Ryan Schmidt wrote: > A bug report was already filed for this: > > https://trac.macports.org/ticket/52613 Thanks; that's exactly what I'm seeing. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Guile appears to be broken again...
Building on Sierra 10.12.
---> Building guile
Error: org.macports.build for port guile returned: command execution failed
Please see the log file for port guile for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/main.log
Error: Unable to upgrade port: 1
Relevant part of main.log (complete log available upon request):
:info:build Making all in module
:info:build make[2]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13/module'
:info:build GUILE_INSTALL_LOCALE=1 GUILE_AUTO_COMPILE=0 \
:info:build ../meta/build-env \
:info:build guild compile --target="x86_64-apple-darwin16"
-Wunbound-variable -Warity-mismatch -Wformat \
:info:build -L
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13/module"
-L
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13/module"
\
:info:build -L
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13/guile-readline"
\
:info:build -o "ice-9/eval.go" "ice-9/eval.scm"
:info:build Backtrace:
:info:build In unknown file:
:info:build?: 3 [apply-smob/1 # #t ...]
:info:build?: 2 [apply-smob/1 #]
:info:build?: 1 [primitive-eval ((@ # %) (begin # # #))]
:info:build?: 0 [mkstemp! "ice-9/eval.go.XX" "wb"]
:info:build
:info:build ERROR: make[2]: *** [ice-9/eval.go] Error 1
:info:build make[2]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13/module'
:info:build make[1]: *** [all-recursive] Error 1
:info:build make[1]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13'
:info:build Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/work/guile-2.0.13"
&& /usr/bin/make -j2 -w all
:info:build Exit code: 2
:error:build org.macports.build for port guile returned: command execution
failed
:debug:build Error code: CHILDSTATUS 43879 2
:debug:build Backtrace: command execution failed
while executing
"system -nice 0 $fullcmdstring"
("eval" body line 1)
invoked from within
"eval system $notty $nice \$fullcmdstring"
invoked from within
"command_exec build"
(procedure "portbuild::build_main" line 8)
invoked from within
"portbuild::build_main org.macports.build"
("eval" body line 1)
invoked from within
"eval $procedure $targetname"
:info:build Warning: targets not executed for guile: org.macports.install
org.macports.build org.macports.destroot
:notice:build Please see the log file for port guile for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/guile/main.log
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: LLVM not supported on Sierra?
On Mon, 3 Oct 2016, Brandon Allbery wrote: > port installed variants:'\+llvm35' ozzie:~ dave$ port installed variants:'\+llvm35' None of the specified ports are installed. Hmmm... Maybe I'd better remember how I actually upgraded to Sierra; it's possible that I skipped a step or something. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: LLVM not supported on Sierra?
On Mon, 3 Oct 2016, Brandon Allbery wrote: > That seems like overkill. More likely something installed with a > then-default +llvm35 variant and needs to be reinstalled with a > different +llvmXX variant. (We could handle that better... somehow. > Figuring out how is, of course, the hard part.) Is there a port option to tell me what uses +llvm35 variant? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: LLVM not supported on Sierra?
On Sun, 2 Oct 2016, Jeremy Huddleston Sequoia wrote: > Possibly https://trac.macports.org/ticket/52424 Looks like it's related; the message "LLVM 3.5 is not supported on Sierra" is pretty clear :-) And something seems to want it; maybe I'd better re-install Macports or something, upgrade it, and see what wants it... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
LLVM not supported on Sierra?
Doing a "port upgraded outdated" after installing Sierra (and had some
trouble with X11), I get this:
---> Computing dependencies for llvm-3.5
---> Fetching distfiles for llvm-3.5
Error: llvm-3.5 is not supported on macOS Sierra or newer.
Error: org.macports.fetch for port llvm-3.5 returned: unsupported platform
Please see the log file for port llvm-3.5 for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.5/llvm-3.5/main.log
Error: Unable to upgrade port: 1
main.log:
version:1
:msg:main ---> Computing dependencies for llvm-3.5:info:main .:debug:main
Searching for dependency: xz
:debug:main Found Dependency: receipt exists for xz
:msg:main
:debug:main Executing org.macports.main (llvm-3.5)
:debug:main changing euid/egid - current euid: 0 - current egid: 20
:debug:main egid changed to: 20
:debug:main euid changed to: 502
:debug:fetch fetch phase started at Mon Oct 3 13:55:43 AEDT 2016
:notice:fetch ---> Fetching distfiles for llvm-3.5
:debug:fetch Executing proc-pre-org.macports.fetch-fetch-0
:debug:fetch Executing proc-pre-org.macports.fetch-fetch-1
:error:fetch llvm-3.5 is not supported on macOS Sierra or newer.
:error:fetch org.macports.fetch for port llvm-3.5 returned: unsupported platform
:debug:fetch Error code: NONE
:debug:fetch Backtrace: unsupported platform
while executing
"proc-pre-org.macports.fetch-fetch-1 org.macports.fetch"
("eval" body line 1)
invoked from within
"eval $pre $targetname"
:info:fetch Warning: targets not executed for llvm-3.5: org.macports.destroot or
rg.macports.configure org.macports.build
:notice:fetch Please see the log file for port llvm-3.5 for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.5/llvm-3.5/main.log
Is this a problem with Macports itself? Or have I screwed up as usual?
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Macports fails under Sierra?
Upgraded recently to 10.12 Sierra, and "port upgrade" now fails: Welcome to the RSYNC daemon on ftp.fau.de. Not all of our mirrors are available through rsync. receiving file list ... done rsync: mkstemp "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/.base.tar.sH7E8E" failed: Permission denied (13) inflate returned -3 (19 bytes) rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/token.c(419) [receiver=2.6.9] rsync: connection unexpectedly closed (31 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/io.c(453) [generator=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 12 Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed Yet the directory exists, and is certainly writable by root: ls -ld /opt/local/var/macports/sources/rsync.macports.org/release/tarballs drwxr-xr-x 5 root admin 170 Sep 26 06:12 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Qué? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
On Mon, 12 Sep 2016, Ryan Schmidt wrote: > > pirlouit:~ sinan$ sudo find -L /opt/local -type l > > /opt/local/lib/libpng.la > > pirlouit:~ sinan$ > > > > The one you say I shouldn’t get. And that is the only one. Hmmm... I've been following this thread, and I get: /opt/local/lib/libpng.la but I also get: /opt/local/libexec/texlive/binaries/a2ping /opt/local/libexec/texlive/binaries/a5toa4 /opt/local/libexec/texlive/binaries/adhocfilelist etc. What did I break this time? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports: install/uninstall failed?
On Fri, 10 Jun 2016, Kishalay Choudhury wrote: > I cleared the running processes by finding their PIDs with "ps -A | grep > tclsh”, and then restarted my machine. Now Macports is working fine. > Problem solved! No, you haven't solved the problem; you have merely done the M$ solution i.e. CTL-ALT-DEL. It will not be solved until you figure out what caused it in the first place. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Who is maintaining Guile?
Whoever it is, could they either please fix it, or give it to someone who can? I don't even know what Guile is, but it's obviously a dependency of something here. Error: org.macports.destroot for port guile18 returned: command execution failed Please see the log file for port guile18 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/main.log Error: Unable to upgrade port: 1 I've already posted the log, so won't do so again. I dimly recall that something in a TeX manpage is broken, or something... In the meantime, "port -p ..." is my friend. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Xsane fails to build
On Thu, 17 Mar 2016, Ryan Schmidt wrote: > I've seen people report this from time to time with gcc but I don't know > what causes it. It worked for me first time... I don't remember which Macports version I was running at the time, though, as I upgrade whenever a new version appears. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Is there a good version of Time Machine?
I ask because either it won't back up .dotfiles, or I've forgotten to click one of those box thingies... Specifically, I want my Firefox config back. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
libgstchromaprint is busted
El Capitan, 10.11.3.
Following my weekly "port -p upgrade outdated" ("-p" because Guile still
appears to be broken), I get:
---> Updating database of binaries
---> Scanning binaries for linking errors
---> Found 1 broken file(s), matching files to ports
---> Found 1 broken port(s):
gstreamer1-gst-plugins-bad @1.6.2
/opt/local/lib/gstreamer-1.0/libgstchromaprint.so
And I don't even know what it is...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Guile is broken, again...
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, and so little time... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Guile is broken, again...
Sigh... Looks like I have to shorten my messages for this list, even though we're asked to include as much info as possible... I don't like publishing my personal site, but said log can be found over on www.horsfall.org/Guile.log -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Full Disk?
On Mon, 1 Feb 2016, Ryan Schmidt wrote: > Probably our recommendation at this time is: do not let your disk get > more than 90% full. OS X already has dialog boxes that warn you when > your disk is very full; don't ignore them. Dunno about the Mac, but my experience with other OS file-systems is that once you hit 90%, performance goes through the floor (and that's a polite way of putting it). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Guile is still broken
On Mon, 25 Jan 2016, Ryan Schmidt wrote: > > Am I the only MacPorts user to have encountered this problem? > > If you're referring to this issue: > > https://trac.macports.org/ticket/48690 > > Someone posted in that ticket that the patches worked. So we would just > need to commit the patches to our repo. Thanks; I'll hurry up and wait, as they say in the military... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Guile is still broken
Yeah, it's something to do with a broken TeX dependency or something (I've posted upon this before), but who has to be beaten up to get this fixed? I'm getting annoyed by having to use "-p" all the time, and yes, I'm prepared to do any work myself. I don't use Guile (and I don't even know what it is), but something here obviously requires it. Am I the only MacPorts user to have encountered this problem? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: A question about macports perl and apple perl and versions and locations
On Mon, 14 Dec 2015, Daniel J. Luke wrote: > On Dec 14, 2015, at 5:15 AM, Robert Chalmers <rob...@chalmers.com.au> > wrote: > > Because yesterday I archived the existing perl binaries in /usr/bin, > > and put links to /opt/local/bin/perl* > > don't do that. Jeeze; how many times has this been mentioned here? Don't even *think* of monkeying with it, unless you *know* what you are doing (believing that you know is not good enough). Even *I* won't touch it, despite having over 40 years of programming experience. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Experiences with El Capitan
The actual update itself was more or less seamless; details can be found over on //horsfall.org/capitan . Now, did Macports really feel the need to re-compile the world, over three days? I got tired of seeing that bloody spinning beach-ball... Why did it not merely retrieve pre-built binaries, as usual? Oh, and a hint for new players: read the migration instructions! I'm using them as a check-list, and I'm still ploughing through. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Cannot licence Xcodebuild
Yosemite 10.10.5, Xcode 7.0.1 (I always install updates) So, after "port upgrade outdated" bleats about me not accepting the licence, it tells me to "sudo xcodebuild -license" (and I'll forgive the US spelling). And... # xcodebuild -license unknown option: -license Usage: xcodebuild [-project ] [-activetarget] [-alltargets] [-target ]... [-parallelizeTargets] [-activeconfiguration] [-configuration ] [-sdk |] [-xcconfig ] [=]... []... xcodebuild [-version [-sdk [|] [] ] xcodebuild [-showsdks] xcodebuild [-find -sdk |] xcodebuild [-list] On the off-chance that the real spelling of "licence" is used: unknown option: -licence Well, it was a try... My wild guess is that Xcode 7 will not work with Yosemite, and this is its way of telling me? After all, if it isn't licenced, it says so by saying unable to compile... Nothing like clarity in error messages. Or maybe it's here somewhere: ozzie:~ dave$ xcodebuild -version 2015-11-02 07:22:00.608 xcodebuild[12575:3550779] Error loading /Developer/Library/Xcode/Plug-ins/XcodeSubversionPlugin.xcplugin/Contents/MacOS/XcodeSubversionPlugin: dlopen(/Developer/Library/Xcode/Plug-ins/XcodeSubversionPlugin.xcplugin/Contents/MacOS/XcodeSubversionPlugin, 265): Library not loaded: /usr/lib/libsvn_client-1.0.dylib Referenced from: /Developer/Library/Xcode/Plug-ins/XcodeSubversionPlugin.xcplugin/Contents/MacOS/XcodeSubversionPlugin Reason: image not found 2015-11-02 07:22:00.609 xcodebuild[12575:3550779] WARNING: Failed to load plugin at: /Developer/Library/Xcode/Plug-ins/XcodeSubversionPlugin.xcplugin, skipping. Could not load bundle. Xcode 3.2.6 Component versions: DevToolsCore-1809.0; DevToolsSupport-1806.0 BuildVersion: 10M2518 Huh? Xcode 3.2.6? I've been steadily upgrading it for ages; my notes show: Xcode 5.1.1 plus command line tools, 6.0.1 on 20/9/2014, 6.1 on 23/10, 6.1.1 11/3/15, 6.3.2 19/5/1, 6.4 1/7/15, 7 on 18/9/15, 7.0.1 1/10/15. (For the Americans here, my date format is dd/mm/yy) -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Hand-holding please - openmotif
:error:archivefetch org.macports.archivefetch for port openmotif returned: xorg-libXt must be installed with +flat_namespace. How exactly do I do this? I have never ever touched anything to do with Macports, other than as a dumb user... Oops: one change (just the one, under advice) was "revupgrade_mode report" uncommented. With the Mac, I am but a lowly end-user, trying to learn more... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Hand-holding please - openmotif
On Mon, 2 Nov 2015, Dave Horsfall wrote: > :error:archivefetch org.macports.archivefetch for port openmotif returned: > xorg-libXt must be installed with +flat_namespace. Skip it; it's "port ... +whatever". -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Cannot licence Xcodebuild
On Sun, 1 Nov 2015, Brandon Allbery wrote: > sudo /Developer/Library/uninstall-devtools --mode=all Bingo! Blimey, but it sure removed a lot of old stuff... FB OM ES MNI TNX :-) > This shouldn't touch the newer version since it doesn't know about the > app bundle-based Xcode, although you might need to reinstall the command > line tools afterward to restore stuff in /usr/bin that it expected to be > symlinks into /Developer. Noted, but I wanted to make sure that my Macports was as clean as a whistle before going to El Capitan, just in case. Thanks again. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Command Line Tools warning
On Fri, 30 Oct 2015, Eneko Gotzon Ares wrote: > > I'm waiting for 10.11.1 > > Already released some days ago. On Fri, 30 Oct 2015, wood...@gmail.com wrote: > Version 10.11.1 (15B42) is out BTW. Thanks, all; I'll give it a bash when I have a free day :-) -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
RE: Command Line Tools warning
On Fri, 30 Oct 2015, Mathieu Deaudelin-Lemay wrote: > Just for the record, if you are planning on staying on OS X 10.10 > (Yosemite), do not upgrade to Xcode 7 as it does not include the SDK for > that OS (only 10.11). Now I find out... I'm waiting for 10.11.1 on principle (never use a version *.0 of anything unless you want to be a beta tester) and Xcode upgraded itself to 7.0, > This shouldn't be a problem much of the time, but there are some ports > that will fail to build (e.g. wireshark), as they'll be looking for a > SDK matching your system version and will fail to find it. And I occasionally use Wireshark... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Why was guile18 attempted when I told it not to?
On Sun, 18 Oct 2015, Brandon Allbery wrote: > As documented in the comment above it (or in macports.conf.default if > you didn't copy the comment over with the setting: > > revupgrade_mode report Oops - I was in a hurry to leave, and missed that. Sorry... port upgrade outdated and not \( guile18 gnucash \) Nothing to upgrade. Thanks! -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Why was guile18 attempted when I told it not to?
On Sun, 18 Oct 2015, Brandon Allbery wrote: > Yes, that would be revupgrade detecting that something was broken and > triggering an automatic rebuild. Take a look at "revupgrade_mode" in > /opt/local/etc/macports/macports.conf. (If it's not in there, then look > at macports.conf.default in the same directory, and while you're at it > compare it to your existing macports.conf and add any settings missing > from that.) #revupgrade_moderebuild I guess that's the culprit; how should it be nobbled? Or perhaps "not" should be honoured instead? BTW, I never touch any system stuff, and that includes the macports files (I know my limits). Mac has /opt/local, FreeBSD has /usr/local, dunno what Linux has (never installed custom software), and I have no idea how Wintel does it (and have no wish to know). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Why was guile18 attempted when I told it not to?
This worked until recently: port upgrade outdated and not \( guile18 gnucash \) This morning, it went ahead anyway... ¿Qué? (Yes, I'm a Fawlty Towers fan!) Methinks it has something to do with this: ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 1 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order guile18 @1.8.8 And as we know, guile18 is busted. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
[FD] Unicorn CPU Emulator Framework is out! (fwd)
Anyone have any plans to port this? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." -- Forwarded message -- Date: Fri, 16 Oct 2015 02:09:52 +0800 From: Nguyen Anh Quynh To: unicorn-eng...@freelists.org, "dailyd...@lists.immunityinc.com" <dailyd...@lists.immunityinc.com>, fulldisclosure <fulldisclos...@seclists.org> Subject: [FD] Unicorn CPU Emulator Framework is out! Greetings, Two months after our Blackhat USA talk, we are excited to announce the first release, version 0.9, of Unicorn Engine, the multi-arch, multi-platform CPU emulator framework you are all longing for! Unicorn CPU emulator offers some unparalleled features: - Multi-architectures: Arm, Arm64 (Armv8), M68K, Mips, PowerPC, Sparc, & X86 (include X86_64). - Clean/simple/lightweight/intuitive architecture-neutral API. - Implemented in pure C language, with bindings for Python, Java, Go & .NET available. - Native support for Windows & *nix (with Mac OSX, Linux, *BSD & Solaris confirmed). - High performance by using Just-In-Time compiler technique. - Support fine-grained instrumentation at various levels. - Thread-safe by design. - Distributed under open source license GPL. For further information, see our website at http://www.unicorn-engine.org Unicorn is a very young project, but we do hope that it will live a long life. The community support will be critical for this little open source framework! We would like show our gratitude to the beta testers for bug reports & code contributions during the beta phase! Their invaluable helps have been tremendous for us to keep this far. Huge thanks go to QEMU project, which Unicorn is based on, and extends much further in its special area. Without the almighty QEMU, Unicorn would not be existent! Our engine aims to lay the ground for innovative works. We look forward to seeing many advanced research & development in the security area built on this framework. Let the fun begin! Thanks, Quynh ___ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: http://seclists.org/fulldisclosure/ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: about fragmentation (of free disk space)
On Sun, 11 Oct 2015, Justin C. Walker wrote: > > Unix[tm] has been doing that for years (ISTR that it was even in > > Edition 5); has Apple only just caught up? > > The disk/paging/FS code is far beyond what Edition 5 (or System 5) was > doing. For sure, they did try to stream back then, but the code is much > more sophisticated these days (and I expect that OS X is not alone, > although I don't follow what's up on the Linux side). Not Sys 5, but good ol' Edition 5, back in 1975 or so. And I'm sure that Linux has pre-read as well. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: about fragmentation (of free disk space)
On Sat, 10 Oct 2015, René J.V. Bertin wrote: > I'm not expecting it to be in real world usage, of course. OTOH, > frequent defragmenting is probably not a good idea on SSDs. The only correct way to use an SSD is as part of a RAID; when (not if) one fails, you pull the thing, replace it, and rebuild the array whilst having your favourite brew. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: about fragmentation (of free disk space)
On Sat, 10 Oct 2015, Justin C. Walker wrote: > Also, OS X in recent incarnations does a pretty good job of detecting > when you are streaming a file and doing a lot of prefetching. Unix[tm] has been doing that for years (ISTR that it was even in Edition 5); has Apple only just caught up? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: pet project : LnxPorts
On Thu, 8 Oct 2015, Alejandro Imass wrote: > Perhaps it's a good time to evaluate a switch to PCBSD and ditch the > Linux ;-) Anything that ditches Linux is fine by me :-) I'm a bit of a BSD snob, after all... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Darwin Version
On Mon, 5 Oct 2015, Brandon Allbery wrote: > It was never derived from FreeBSD 4.1. I may have been thinking of this: https://en.wikipedia.org/wiki/Berkeley_Software_Distribution "Also Darwin, the system on which Apple's Mac OS X is built, is a derivative of 4.4BSD-Lite2 and FreeBSD." -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Darwin Version
On Mon, 5 Oct 2015, Daniel J. Luke wrote: > > You're saying that Darwin was written from scratch and not evolved > > from a modified FreeBSD 4.1, or am I thinking of an earlier MacOS? > > it all depends on what you mean by ‘written from scratch’, ‘evolved > from’, and how detailed you care to be with the history. See next reply. Anyway, "from scratch" => "clean-room implementation" e.g. Unix/Linux, whereas "evolved" => V5/V6/V7/4.nBSD/BSDI/FreeBSD/OpenBSD/etc. As for how detailed, I doubt we'll ever know the full story, as many versions of Unix were developed over the 40 years that I've been using it (SYS-III, SYS-V, SunOS, Solaris, Ultrix, IRIX, Xenix, SCO, AIX, etc; I've used all those and more). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MacPorts] #48690: Upgrading "guile18" fails
On Wed, 9 Sep 2015, Ryan Schmidt wrote: > sudo port upgrade outdated and not guile18 > > However if you have other ports outdated that depend on guile18 you > would have to exclude those too. > > For example if you had gnucash installed you would exclude guile18 and > gnucash: > > sudo port upgrade outdated and not \( guile18 gnucash \) Sorry for the late reply; that worked a treat! So it was gnucash that dragged in guile18... Thanks. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Darwin Version
On Sat, 3 Oct 2015, Ryan Schmidt wrote: > > Remember: under the bonnet (ObUSA: hood) the Mac runs FreeBSD. > > OS X is underpinned by Darwin, not FreeBSD. Darwin is based on NeXTSTEP, > BSD, XNU and other projects, and of course a great deal of independent > work by Apple. You're saying that Darwin was written from scratch and not evolved from a modified FreeBSD 4.1, or am I thinking of an earlier MacOS? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Darwin Version
On Fri, 2 Oct 2015, Ryan Schmidt wrote: > We're trying to make MacPorts into a system that just works, and that > means that when we discover common situations where MacPorts fails to > work, we try to modify MacPorts so that users are less likely to > encounter them. One of the common problems we discovered was when > MacPorts is built on one version of OS X and used on another version of > OS X. So now we prevent that, via the error message that caused you to > begin this thread. And with any luck, both MacPorts and FreeBSD-ports will learn from each other. Remember: under the bonnet (ObUSA: hood) the Mac runs FreeBSD. A family exchange, some years back: Ex: Iain, why did Dave buy a Mac? I thought he was a Unix person! Son (in a withering tone): Mum, the Mac *runs* Unix. Me: That's right, Iain; I wouldn't've bought it otherwise. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Darwin Version
On Sat, 3 Oct 2015, Rainer Müller wrote: > What should we change on the wiki page to make it more clear? > This is an honest question. I am open to suggestions. You cannot force the sheeple to read the instructions. "Warning: this gun will blow your foot off if you point it that way." -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Darwin Version
On Fri, 2 Oct 2015, Dominik Reichardt wrote: > Calm down and complain to Apple I've found that Penguin/OS users have a rather blinkered view of the real world; they seem to think that they invented Unix, for example. Personally, I'm a BSD bigot; at least the Mac is FreeBSD-based. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." Yet another mass shooting in America; turning now to other news... ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.4 has been released
On Fri, 2 Oct 2015, Joshua Root wrote: > 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. I don't see a mention of putting the post-install notes at the end; did it get included? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.4 has been released
On Thu, 1 Oct 2015, Clemens Lang wrote: > > I don't see a mention of putting the post-install notes at the end; > > did it get included? > > No, that's a new feature and is thus not contained in a bugfix release. > Doing this correctly also requires signal handling because otherwise > messages would get lost when you abort a build. MacPorts did not handle > signals at all yet, and the changes on trunk that add it need a little > more work: there are a couple of situations where you can press ^C and > MacPorts will actually not terminate. Since that's bad UX, that change > isn't ready for a release yet. Sounds reasonable :-) Thanks. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Weird SSH problem - Write failed: Broken pipe
Anyone else having SSH "Write failed: Broken pipe" lately, after updating a while back? I keep a window open to my (FreeBSD) mail server all the time (I handle my own email/DNS etc). Client is 10.10.5, OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 That OSSLShim date looks rather old... But: ozzie:~ dave$ ls -ltc `locate bin/ssh` -rwxr-xr-x 1 root wheel 1384208 Aug 15 04:19 /usr/sbin/sshd -rwxr-xr-x 1 root wheel 1222640 Aug 15 04:19 /usr/bin/ssh -rwxr-xr-x 1 root wheel 726752 Aug 15 04:19 /usr/bin/ssh-add -rwxr-xr-x 1 root wheel 744640 Aug 15 04:19 /usr/bin/ssh-agent -rwxr-xr-x 1 root wheel 1005328 Aug 15 04:19 /usr/bin/ssh-keygen -rwxr-xr-x 1 root wheel 681728 Aug 15 04:19 /usr/bin/ssh-keyscan ozzie:~ dave$ type ssh ssh is hashed (/usr/bin/ssh) No amount of playing with SSH keepalives etc will fix it; this was working up until about a month ago. No amount of "-" etc will reveal the problem; it craps itself just like that; my various remote "tail -F /var/log/blah" windows, being pretty busy, do not time out thus. No point in running the other end under GDB, as it (Alpine on FreeBSD) is heavily multi-threaded, and what little I can discern does not reveal anything useful anyway. I dimly recall (perhaps here, or perhaps elsewhere) that Apple's SSH (as indicated by the use of "/usr/bin/ssh") is thoroughly busted; not in a crypto sense, but in a "don't use it; use the MacPorts version if you wish to retain your sanity" sense... Should I be using a version of SSH/SSL not blessed by Cupertino etc? Thanks. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." I'll support shark-culling when they have been observed walking on dry land. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Xcode 7.0?
On Fri, 18 Sep 2015, Ryan Schmidt wrote: > No need for you to test anything. As I said before, OS X 10.11 requires > Xcode 7. But this thread was started by someone on OS X 10.10, and I > explained in my previous post why Xcode 7 on OS X 10.10 might be > problematic, in ways that Xcode 7 on OS X 10.11 would not be > problematic. So, would I be correct in concluding that Apple just pushed out a public release of Xcode (viz: 7) that may not be compatible with the current public release of OS/X (viz: 10.10)? I suppose, in a quantum sort of way, that that's taking security to the limits :-) Please note that I am *not* knocking the MacPorts bods; they do a great job, in what I know is a difficult and thankless task. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." I'll support shark-culling when they have been observed walking on dry land. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MacPorts] #48690: Upgrading "guile18" fails
OK, I'll be patient, but is there some way by which I can ignore this failure, so that the rest of the update may continue? I'm rather fussy about keeping my boxes up to date, you see... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." I'll support shark-culling when they have been observed walking on dry land. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Lynx color support broken by update
On Thu, 3 Sep 2015, Ryan Schmidt wrote: > > Same Lynx version on FreeBSD works OK, so Macports' is busted. > > Does FreeBSD use ncurses 5 or 6? Aha! It's (currently) using 5.9 (I did see that later reply). So yep, it appears to be a problem with the way that Lynx uses Ncurses 6. And I can't figure out what version of Ncurses that Lynxlet uses (I'm used to genuine BSD systems, not the Mac version). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." Concerned about shark attacks? Then don't go swimming in their food bowl... ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Lynx color support broken by update
On Thu, 3 Sep 2015, David Vergnaud wrote: > So now I'm annoyed that lynx got broken and surprised that the situation > doesn't seem consistent. Hmmm... Busted here too (2.8.8rel.2 on 10.10.5). Lynxlet still works, though, but I can't tell what version it is. Same Lynx version on FreeBSD works OK, so Macports' is busted. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." Concerned about shark attacks? Then don't go swimming in their food bowl... ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Connectivity problems with master server (distfiles.macports.org/rsync.macports.org)
On Tue, 25 Aug 2015, Brandon Allbery wrote: And as Jeremy pointed out, it is easy to imagine that the mailing list infrastructure might fall victim to the same problem. ...implying the people who need it won;t see this message Which is why I've just saved it... -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. RIP Cecil the Lion; he was in pain for two days, thanks to some brave dentist. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Connectivity problems with master server (distfiles.macports.org/rsync.macports.org)
On Tue, 25 Aug 2015, Mihai Moldovan wrote: To the best of my knowledge, at the time of writing, the problems seem to be mostly isolated to the western part of the US (including Alaska.) I was not able to reproduce these issues in Europe. Nor from Australia. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. RIP Cecil the Lion; he was in pain for two days, thanks to some brave dentist. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Upgrading guile18 fails
Yosemite 10.10.5 When doing my Monday penance viz. upgrading ports, something called guile18 (whatever it is) failed to proceed. Nearly 5000 lines in main.log so I won't attach it (unless someone really wants it), but the important bit seems to be: :info:destroot ./gh.texi:1000: must be after `@deftypefun' to use `@deftypefunx' :info:destroot ./fdl.texi:411: raising the section level of @appendixsubsec which is too low :info:destroot ./api-utility.texi:566: warning: node `C Hooks' is next for `Hook Reference' in menu but not in sectioning :info:destroot ./api-utility.texi:674: warning: node `Hook Reference' is prev for `C Hooks' in menu but not in sectioning :info:destroot ./api-options.texi:510: warning: node next `Printing options' in menu `Debugger options' and in sectioning `Evaluator options' differ :info:destroot ./api-options.texi:533: warning: node prev `Evaluator options' in menu `Debugger options' and in sectioning `Printing options' differ :info:destroot ./api-options.texi:544: warning: node next `Evaluator trap options' in menu `Examples of option use' and in sectioning `Debugger options' differ :info:destroot ./api-options.texi:625: warning: node next `Debugger options' in menu `Evaluator options' and in sectioning `Examples of option use' differ :info:destroot ./api-options.texi:625: warning: node prev `Debugger options' in menu `Printing options' and in sectioning `Evaluator trap options' differ :info:destroot ./api-options.texi:681: warning: node prev `Examples of option use' in menu `Evaluator trap options' and in sectioning `Debugger options' differ :info:destroot make[2]: *** [guile.info] Error 1 :info:destroot make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/work/guile-1.8.8/doc/ref' :info:destroot make[1]: *** [install-recursive] Error 1 :info:destroot make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/work/guile-1.8.8/doc' :info:destroot make: *** [install-recursive] Error 1 :info:destroot make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/work/guile-1.8.8' :info:destroot Command failed: cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/work/guile-1.8.8 /usr/bin/make -w install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/work/destroot :info:destroot Exit code: 2 :error:destroot org.macports.destroot for port guile18 returned: command execution failed :debug:destroot Error code: CHILDSTATUS 55711 2 :debug:destroot Backtrace: command execution failed while executing system -nice 0 $fullcmdstring (eval body line 1) invoked from within eval system $notty $nice \$fullcmdstring invoked from within command_exec destroot (procedure portdestroot::destroot_main line 2) invoked from within portdestroot::destroot_main org.macports.destroot (eval body line 1) invoked from within eval $procedure $targetname :info:destroot Warning: targets not executed for guile18: org.macports.destroot :notice:destroot Please see the log file for port guile18 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/main.log So, what have I not done this time? Oh, and are those bleatings about bouncing to root and back serious? -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. RIP Cecil the Lion; he was in pain for two days, thanks to some brave dentist. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Upgrading guile18 fails
On Sun, 23 Aug 2015, Jeremy Lavergne wrote: Create a ticket and upload the full log please. Done... And if there were multiple submissions it means that Firefox was ignoring some buttons (it does that sometimes). The error was not in the previous email. Yeah, well, my eyes sort of glazed over after the first few hundred lines, so I went right to the end... -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. RIP Cecil the Lion; he was in pain for two days, thanks to some brave dentist. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Upgrading guile18 fails
On Sun, 23 Aug 2015, Brandon Allbery wrote: It looks like the installed version of texinfo is much stricter about formatting, and the guile 1.8 texinfo documentation has errors in it. Thanks; it's been so long since I've used Texinfo that I've forgotten all about it. MacPorts does as much as it can as a dedicated unprivileged user, neither your user ID nor root. Thanks again; I've never seen those messages before. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. RIP Cecil the Lion; he was in pain for two days, thanks to some brave dentist. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OS X 10.11 status
On Wed, 19 Aug 2015, Chris Jones wrote: Yes, you should expect to compile all ports as there are no binary archives as of yet. Have you seen what your CPU temperature hits? I can boil water at 100ºC (that's 212ºF for Americans). I hate it when libpng has to be compiled again and again; I feel like fanning the CPU or something. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. RIP Cecil the Lion; he was in pain for two days, thanks to some brave dentist.___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Netcdf installation issues
On Wed, 12 Aug 2015, Ryan Schmidt wrote: Please keep the conversation on the mailing list by using the Reply All function when you reply. I've re-added the list address to my reply. Uh oh - you've just hit one of my buttons... A properly-configured mailing list will have Reply-To: set to the list. A properly-configured client will actually honour it. A properly-configured human will understand why. :-) -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer RIP Cecil the Lion; he was in pain for two days, thanks to some brave hunter. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: GCC and kernel.osversion
On Sat, 18 Jul 2015, Brandon Allbery wrote: On 10.10? You have an ancient Xcode installed and you are lucky it only spit out a complaint about kern.osversion instead of crashing. Do not bet on it being usable or stable. Get rid of it. I updated Xcode to 6.4 a couple of weeks ago; I always stay current. sudo /Developer/Library/uninstall-devtools --mode=all If you really insist on gcc, install one from MacPorts and use `port select` to make it default. I did install it from MacPorts, and that's what got installed... Sorry I didn't make that clear. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer The complexity for minimum component costs has increased at a rate of roughly a factor of two per year. -- G.Moore, Electronics, Vol 38 No 8, 1965 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
GCC and kernel.osversion
OS/X 10.10.4 Installed GCC 4.2.1 because I find CLANG is far too fussy and badly documented, and I get this: ozzie:ssem dave$ make cc -g ssem.c -o ssem couldn't understand kern.osversion `14.4.0' ssem.c: In function ‘main’: ssem.c:66: warning: return type of ‘main’ is not ‘int’ Ignore the warning, as I insist that main() calls exit() instead of merely returning; I'm old-school. ozzie:ssem dave$ sysctl kern.osversion kern.osversion: 14E46 I can sort of see a connection there, but what is the real problem? The program runs just fine, once I figured out: a) how to enable coredumps, and b) where it puts them... As an aside, I thought that Linux was bad enough in trying to distance itself from Unix, but Apple really takes the Tim-Tam; who would've guessed that GCC would be installed under /Developer? -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer The complexity for minimum component costs has increased at a rate of roughly a factor of two per year. -- G.Moore, Electronics, Vol 38 No 8, 1965___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: yosemite and 2008/9 macbookpro compatability, macports install settings for older architecture?
On Sat, 30 May 2015, Ryan Schmidt wrote: Sure, you can copy (not rename) macports.conf.default to macports.conf, if you've made no changes in macports.conf that you want to keep. Done. No rebuild should be necessary. No problem at all with this morning's update; it did build a bit more than usual, but that's probably normal anyway. Thanks. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: yosemite and 2008/9 macbookpro compatability, macports install settings for older architecture?
On Fri, 29 May 2015, Ryan Schmidt wrote: You should probably migrate any relevant changes from macports.conf.default to macports.conf every time you upgrade MacPorts, as described in the Migration instructions, section 2 a. Well, I've never made any changes (as I said, I don't know my way around MacPorts yet), so I should be safe in merely renaming them? And anyway, what then? Force a massive rebuild somehow, or will it happen all by itself? I thought I'd followed the instructions when going to Yosemite (it was the free upgrade from Snow Leopard), but I guess not... -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: yosemite and 2008/9 macbookpro compatability, macports install settings for older architecture?
On Thu, 28 May 2015, Ryan Schmidt wrote: No; the MacPorts default build_arch is x86_64 on Yosemite, but the user can override it by changing build_arch to i386 in macports.conf. In this case, the user probably didn't meant to do that, he just imported a pre-Snow Leopard Intel MacPorts installation onto his Yosemite Mac, and should now fully follow the Migration instructions to set things right. Hmmm... I've never touched macports.conf in my life (because I won't know what I'm doing), but I see this: -rw-r--r-- 1 root admin 5787 Dec 1 2010 macports.conf -r--r--r-- 1 root admin 8248 Nov 22 2014 macports.conf.default The first would be the original Snow Leopard file, and the second would be Yosemite (with attendant differences in default build architectures). Am I in trouble? I've had no problems with ports. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: what was up with ntp again?
On Tue, 28 Apr 2015, Brandon Allbery wrote: pacemaker *only* does the local time update stuff, not the network-based stuff or determining the exact updates to be done; it gets those from ntpd. Hmmm... ozzie:~ dave$ ps ax | egrep -i ntpd|pacemaker 197 ?? Ss 0:05.13 /usr/sbin/ntpd -c /private/etc/ntp-restrict.conf -n -g -p /var/run/ntpd.pid -f /var/db/ntp.drift 3161 s002 S+ 0:00.01 egrep -i ntpd|pacemaker Np sign of pacemaker. ozzie:~ dave$ ls -l /var/db/ntp.drift -rw-r--r-- 1 root wheel 8 Apr 28 10:38 /var/db/ntp.drift The drift file is being maintained. ozzie:~ dave$ cat /var/db/ntp.drift -52.896 Dunno how good that is. I don't seem to be running pacemaker, and I've never turned it off because I've yet to understand how launchd works (I'm a traditional Unix bod, still coming to grips with the idiosyncrasies of the Mac). This box is as bog-standard as possible. Does this mean that my clock is not being synchronised at all, and just happens to be more or less accurate, after having bedded down for 5 years? -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Error in selfupdate
Yosemite 10.10.3 (updated religiously), MacPorts 2.3.3 :info:build Making all in gpsd :info:build make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_geoclue/geoclue/work/geoclue-0.12.99/providers/gpsd' :info:build /usr/bin/clang -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/include -I../.. -I../.. -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/include -I /opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/inclu de -I/opt/local/include/libxml2 -I/opt/local/include -pipe -Os -arch x86_64 -g -Wall -Wno-format -MT geoclue_gpsd-geoclue-gpsd.o -MD -MP -MF .deps/geoclue_gps d-geoclue-gpsd.Tpo -c -o geoclue_gpsd-geoclue-gpsd.o `test -f 'geoclue-gpsd.c' | | echo './'`geoclue-gpsd.c :info:build sed -e s|\@libexecdir\@|/opt/local/libexec| org.freedesktop.Geoclue.Providers.Gpsd.service.in org.freedesktop.Geoclue.Providers.Gpsd.service :info:build geoclue-gpsd.c:379:33: error: no member named 'tag' in 'struct gps_data_t' :info:build char *tag_str = gpsd-gpsdata-tag; :info:build ~ ^ :info:build geoclue-gpsd.c:534:2: warning: 'g_type_init' is deprecated [-Wdeprecated-declarations] :info:build g_type_init (); :info:build ^ :info:build /opt/local/include/glib-2.0/gobject/gtype.h:681:23: note: 'g_type_init' has been explicitly marked deprecated here :info:build void g_type_init(void); :info:build ^ :info:build 1 warning and 1 error generated. :info:build make[3]: *** [geoclue_gpsd-geoclue-gpsd.o] Error 1 -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: problem with selfupdate
On Tue, 7 Apr 2015, David Epstein wrote: Here is the response I had to sudo port -v selfupdate --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) [...] One possible explanation that occurs to me is that I am connecting to the Internet from behind some kind of firewall. However, that is just wild conjecture. But it is true that I’m not at the usual place from where I have in the past successfully run selfupdate without a problem. Worked fine for me from Australia. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: something you always ...... about the X11 clipboard(s)
On Sun, 5 Apr 2015, Ian Wadham wrote: Schröder's cat [If it is not a savvy abbreviation…] [...] I hope New, Fara, Max, Ein, Bo and Heisberg will not come round to haunt you… Not to mention Charles Schulz... -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: something you always ...... about the X11 clipboard(s)
On Thu, 2 Apr 2015, Eneko Gotzon wrote: I can't stand CTF Please, what's that? Canadian Taxpayer's Federation? ;) Not quite; it's Click To Focus, which means the window receiving the keyboard is the one in front, making it impossible to type into a background window at the same time. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: something you always ...... about the X11 clipboard(s)
On Wed, 1 Apr 2015, René J.V. Bertin wrote: I know iTerm2, but its power features aren't appealing/useful enough to me to make up for the fact that it doesn't do focus follows mouse as well as Apple's Terminal.app . Ah; another FFM fan :-) I can't stand CTF, but I can understand why the Mac does it (single application etc). Easy. Trying OS X a bit over 11y ago on my gf's new laptop made me realise it was the only unix for the desktop that really gave the (almost) best of both worlds. I always have an X server running and not just because I prefer xterms over Terminal.app. Which I also use, just for different things, typically non-X things. I like to run xload on remote boxes, and annoy cow-orkers by firing up xroach on their screens :-) -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: thread CPU usage monitor?
On Tue, 24 Mar 2015, Pierre Malard wrote: Their is a lot of utilities like « MenuMeters » (http://www.ragingmenace.com) which can dodo that. A other Mac OS X integrated tool is « Activity Monitor » which can give you a lot of information about system. There's also iStat Menus; it's cheap, and you can get a trial version. Disclaimer: just a satisfied customer, contents may settle, contains nuts. -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Apache source?
On Mon, 23 Mar 2015, Brandon Allbery wrote: I would hope that Apache does not need anything beyond headers and libraries to create custom modules. Modules are dynamically loaded, not compiled in, these days. He may be after some sample source to build his own module... -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Announce: OpenSSH 6.8 released (fwd)
Someone might want to take a look at this; both the BSD people and the Penguins are all over it. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) -- Forwarded message -- Date: Wed, 18 Mar 2015 00:56:51 -0600 (MDT) From: Damien Miller To: openssh-unix-annou...@mindrot.org Subject: [openssh-unix-announce] Announce: OpenSSH 6.8 released OpenSSH 6.8 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested snapshots or donated to the project. More information on donations may be found at: http://www.openssh.com/donations.html Changes since OpenSSH 6.7 = This is a major release, containing a number of new features as well as a large internal re-factoring. Potentially-incompatible changes * sshd(8): UseDNS now defaults to 'no'. Configurations that match against the client host name (via sshd_config or authorized_keys) may need to re-enable it or convert to matching against addresses. New Features * Much of OpenSSH's internal code has been re-factored to be more library-like. These changes are mostly not user-visible, but have greatly improved OpenSSH's testability and internal layout. * Add FingerprintHash option to ssh(1) and sshd(8), and equivalent command-line flags to the other tools to control algorithm used for key fingerprints. The default changes from MD5 to SHA256 and format from hex to base64. Fingerprints now have the hash algorithm prepended. An example of the new format: SHA256:mVPwvezndPv/ARoIadVY98vAC0g+P/5633yTC4d/wXE Please note that visual host keys will also be different. * ssh(1), sshd(8): Experimental host key rotation support. Add a protocol extension for a server to inform a client of all its available host keys after authentication has completed. The client may record the keys in known_hosts, allowing it to upgrade to better host key algorithms and a server to gracefully rotate its keys. The client side of this is controlled by a UpdateHostkeys config option (default off). * ssh(1): Add a ssh_config HostbasedKeyType option to control which host public key types are tried during host-based authentication. * ssh(1), sshd(8): fix connection-killing host key mismatch errors when sshd offers multiple ECDSA keys of different lengths. * ssh(1): when host name canonicalisation is enabled, try to parse host names as addresses before looking them up for canonicalisation. fixes bz#2074 and avoiding needless DNS lookups in some cases. * ssh-keygen(1), sshd(8): Key Revocation Lists (KRLs) no longer require OpenSSH to be compiled with OpenSSL support. * ssh(1), ssh-keysign(8): Make ed25519 keys work for host based authentication. * sshd(8): SSH protocol v.1 workaround for the Meyer, et al, Bleichenbacher Side Channel Attack. Fake up a bignum key before RSA decryption. * sshd(8): Remember which public keys have been used for authentication and refuse to accept previously-used keys. This allows AuthenticationMethods=publickey,publickey to require that users authenticate using two _different_ public keys. * sshd(8): add sshd_config HostbasedAcceptedKeyTypes and PubkeyAcceptedKeyTypes options to allow sshd to control what public key types will be accepted. Currently defaults to all. * sshd(8): Don't count partial authentication success as a failure against MaxAuthTries. * ssh(1): Add RevokedHostKeys option for the client to allow text-file or KRL-based revocation of host keys. * ssh-keygen(1), sshd(8): Permit KRLs that revoke certificates by serial number or key ID without scoping to a particular CA. * ssh(1): Add a Match canonical criteria that allows ssh_config Match blocks to trigger only in the second config pass. * ssh(1): Add a -G option to ssh that causes it to parse its configuration and dump the result to stdout, similar to sshd -T. * ssh(1): Allow Match criteria to be negated. E.g. Match !host. * The regression test suite has been extended to cover more OpenSSH features. The unit tests have been expanded and now cover key exchange. Bugfixes * ssh-keyscan(1): ssh-keyscan has been made much more robust again servers that hang or violate the SSH protocol. * ssh(1), ssh-keygen(1): Fix regression bz#2306: Key path names were being lost as comment fields. * ssh(1): Allow ssh_config Port options set in the second config parse phase to be applied (they were being ignored). bz#2286 * ssh(1): Tweak
Re: Announce: OpenSSH 6.8 released (fwd)
On Wed, 18 Mar 2015, Lawrence Velázquez wrote: https://trac.macports.org/ticket/47190 Ah; someone beat me to it. I was so busy notifying other lists that I forgot about MacPorts... -- Dave Horsfall DTM (VK2KFU) Those who don't understand security will suffer. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Selfupdate doesn't work - solved
On Wed, 4 Mar 2015, Jim Goudie wrote: Then I got to thinking... what else would block it? I logged in to my router and found it has a firewall as well. I turned it off, and then the command worked! I'm finding that a lot of consumer routers have conservative firewalls by default; this is good. Think of it as a form of natural selection; if you know enough to turn it off or reconfigure it etc, then you probably aren't a danger to the Internet :-) -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: selfupdate doesn't work
On Mon, 2 Mar 2015, William H. Magill wrote: On Mar 1, 2015, at 11:53 PM, Jim Goudie jagou...@comcast.net wrote: 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. Xcode does not update -- it is a new version you have to search for it in the App store. Jesus H Christ upon a purple pogo stick! When I bought my MacBook, she ran Snow Leopard 10.6.8, and Xcode was 5.5.1 back then. After those years, she's now running Yosemite 10.10.2, and Xcode is 6.0.1 (which I think has been updated). Don't people check their boxen every so often, vulnerability-wise? No bloody wonder that the malware background noise is increasing... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: CD creation/burning: [MacPorts] #46840: new port submission: xcdroast
On Sun, 15 Feb 2015, René J.V. Bertin wrote: Things like burning images to disc (Finder will happily do so... making it a file on the disc, not the entire disc. Not real helpful). You can do it You mean I'm not the only one? :) Many's the time I thought I'd burned a CD, only to find that I've got one more addition to my coffee table... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
On reloading MacOS
Yeah, this MacBook is about as slow as a wet weekend (think of Snow Leopard = Mavericks = Yosemite etc), and I know what to do, but... So, before I wipe the thing, does anyone have any horror stories? Can I put complete trust in my Time Capsule etc? In the TC's defence, I've only ever had to use it once, when I deleted the wrong file... I had to go back about a week. Whew! -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: can't start mysql56 after move datadir
On Fri, 13 Feb 2015, Brandon Allbery wrote: I've never heard permission +x referred to as search permission. I thought +x is execute permission, which is surely more dangerous than +r read permission. How do you execute a directory? +x *on directories* is search. Likewise setuid/setgid/save-text bits have different meanings on directories (and setugid generally has other meanings non non-executable files), where they otherwise wouldn't be meaningful. Unix file permissions are subtle, and were very well thought out. The most beautiful example, of course, would be the permission to remove a file. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Fri, 6 Feb 2015, Michael wrote: /etc/paths? This is the first I've seen any indication of this. Where is this documented? Is this the apple-approved way to add stuff to PATH for programs run by launchD? And what other little secrets are there? I've learned more about OSX from reading this list than from anywhere else, and I go back Unix-wise for 40 years! I have the Big Dummies ebook, but I'd like to see a Guru's Guide... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please
On Thu, 22 Jan 2015, William H. Magill wrote: After a tremendous amount of effort on the part of numerous kernel programmers at DEC, they discovered that the bottom level BSD I/O modules had not been looked at (literally) since PDP days. Disk I/O was being done in 128 byte blocks. You sure abut this? My memory of the PDP days (ye olde 11/40) was that I/O was the same as the disk sector i.e. 512 bytes; this was V5/V6/V7 Unix. One thing which I noticed immediately when I turned on iCloud disk in Yosemite -- the lag involved with launching any program which stored anything in the cloud. Not unexpected, but significant none the less. I've never bothered with iCloud; I don't store much stuff anyway (see my signature), and it all gets backed up to my Time Capsule. Similarly, I had a problem where my internal hard drive would literally not spin-up. Took the iMac in to the Apple Store and they ran their diagnostics and pronounced nothing wrong -- the tests passed with flying colors! I finally convinced them that the drive was not spinning up and they got a tech to come out front who had a stethoscope and instantly verified that the drive was not spinning. Didn't they see the dreaded question mark on booting up? I've seen too many cases related to both BSD (and later Mach, i.e. NeXT and OSX) where much of the hardware level stuff is completely ignored by any of the upper-level reporting software. -- one of the main reasons why Drive manufacturers developed S.M.A.R.T. -- the OS does not do the job. Hmmm... I just tried SMART on my drive, but being an external USB drive (long story) it's not supported, so... In my experience, by the time the OS flags a Disk error, you have been suffering constant performance degrading failures which are simply below the reporting threshold, for quite some time. I have been seeing slow performance lately; I bought the MacBook early in 2010, but it's a late 2009 model. I wonder? -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please (fwd)
Oops; this was meant foe the list... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) -- Forwarded message -- Date: Fri, 23 Jan 2015 15:11:06 +1100 (EST) From: Dave Horsfall d...@horsfall.org To: René J.V. Bertin rjvber...@gmail.com Subject: Re: OT probably, help please Someone mentioned launchd.info (and I daftly deleted the message). Does it look as wonky for others as it does for me? I'm using Firefox 35.0 (haven't tried others, as the last time I did it buggered up a few things) and I get, in the top half, a static window with some sort of an index and a silhouette of something looking like a watering can, with a full-screen scrolling window under it. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /opt/local/macports/software
On Mon, 19 Jan 2015, René J.V. Bertin wrote: Just to be clear: I do agree with this, and practice it myself. One of the reasons MacPorts is not installed on my boot partition. (heck, I'm old and pedantic enough to care about free space fragmentation ...) I'm glad to know that I'm not the only pedantic old fart around here. I turn 63 this year, and I'm not getting much younger. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: port:imap-uw and mailbox corruption on 10.9.5?
On Mon, 12 Jan 2015, Brandon Allbery wrote: IIRC uw-imapd went from keeping the mailbox locked (low/no corruption, but clients error out a lot because they reasonably expect concurrent access) to locking only when necessary (gets it wrong a lot, partly due to concurrent delivery by MTAs, high corruption), as email volume increased from the fairly low levels when it was first written. In either mode it's a pretty lousy server even for single user use. BITD it was acceptable, but email is much higher volume these days and there are much more appropriate IMAP servers. As one who has struggled with UW-IMAPD for a while now, can you recommend any in particular? My situation is mail being stored on my FreeBSD server (accepted with Sendmail), and read there with Alpine; I SSH into it from the MacBook. I'd like to set up tasks on the Mac to email myself on the FreeBSD box (I loathe gooey MUAs with a passion), but the moment I start iMail (or whatever it's called), it pulls the rug out from underneath Alpine. I merely want to send mail from the Mac, not read it there. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Determining the date a given port was installed
On Thu, 8 Jan 2015, Clemens Lang wrote: $ stat -t '%Y-%m-%d %H:%M' -f '%Sc' $(port -q location zlib) which allows you to change the output formatting and doesn't print anything but the requested time? I think the key here is port -q location ..., something I never knew existed until now. ``This new learning amazes me, Sir Bedevere. Explain again how sheeps bladders may be employed in the prevention of earthquakes.'' -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: A question about Localhost with Safari
On Sat, 3 Jan 2015, Ryan Schmidt wrote: I experience the problem on Yosemite that localhost will randomly switch between accessing the IPv4 address of my server (which works) and the IPv6 address of my server (which apparently isn't working). I've had to start using 127.0.0.1 instead, which is the IPv4 address. This does not appear to be specific to Safari; I saw it in the terminal with curl too. I've seen it in Firefox from time to time, when my MacBook's FF refreshes itself against the pages on my FreeBSD server (which happens to support IPv6 as well, but it shows in the Apache logs). -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: You have a new notification from avijitshe...@gmail.com. View?
On Mon, 1 Dec 2014, Ryan Schmidt wrote: The second address you mentioned is not subscribed to the MacPorts lists. The first is. Aha... The old trick of steal a subscriber's address, and post to the list using it, thereby spamming the list. I haven't seen that for some years now. Not a lot you can do, short of requiring authentication, as SMTP was never designed with security in mind. Best you can do is run some sort of DNSBL check against posters, so had the malware site been listed then it would've been refused. As it happens, it's listed at a number of sites, but you'd need to balance running a spam-free list against losing subscribers posting from spammy ISPs... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: You have a new notification from avijitshe...@gmail.com. View?
On Mon, 1 Dec 2014, Ryan Schmidt wrote: The spam and spammer isn't really interesting though. I think it's more interesting that it was let through. The list software should do a bit more than a naïve string match against the From: field... I have no reason to believe that that's what the list software does. I don't know what it does though. The software is Mailman, so if anyone wants to investigate and let us know, that would be great. It would use either Return-Path: (derived from the envelope), or From: (which as we can see can be forged). I don't have the original message any more, unfortunately, as the only spam I save (yes, really) are those reported to SpamCop. The Subject: probably ought to be changed, as the OP would be feeling a little embarrassed by now... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: You have a new notification from avijitshe...@gmail.com. View?
When were spammers allowed on this list? -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: {distfiles,packages,rsync,trac}.macports.org are back up (eom)
Out of curiosity, why this sudden instability? -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: {distfiles,packages,rsync,trac}.macports.org are back up (eom)
On Thu, 27 Nov 2014, Rainer Müller wrote: Out of curiosity, why this sudden instability? This is something the server admins at Mac OS Forge should answer and I added them to CC in this message. Thanks; it's not a good look for those new to MacPorts. I saw multiple reports due to unreachable servers over the last weeks. We either need to stop that from happening or make the sync/selfupdate process more reliable with an automatic fallback to other mirrors. Which reminds me: I erred in a previous post about Mac/FreeBSD ports recovering in the face of helpful ISPs interfering with the DNS; FreeBSD merely keeps trawling through a local list (updated every so often) until it gets a bite, ignoring any silly responses along the way. I really must set up my own name server, instead of relying upon my broken ISP (they are The Phone Company, after all, and own all of the infrastructure). -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Ntp -- getting it to work
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 ntp.drift... no wonder things get confused. And is completely broken, from a computer-forensics point of view; in the past, I've nailed a few perps by using some of the more obscure flags on ls(1), such as c, u, and U. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...
On Mon, 24 Nov 2014, Lawrence Velázquez wrote: There's no particular reason to stick with the primary MacPorts servers, if you find a mirror that works better for you. I'm not aware of problems with any of the mirrors. If you're not in North America, you might even benefit from switching sources permanently. Seeing as MacPorts is based upon FreeBSD ports, perhaps it could copy the latter's trick of trying servers one by one? A minor problem with FreeBSD is that should an ISP-assigned DNS server report an error, said ISP helpfully redirects you elsewhere, but luckily FreeBSD handles this stupidity (I'm looking at you, BigPond Australia). -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: FiPy Port Out of Date
On Sun, 23 Nov 2014, Lawrence Velázquez wrote: Python 2.6 no longer receives security fixes. http://legacy.python.org/dev/peps/pep-0361/ Thanks. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Ntp -- getting it to work
On Sat, 22 Nov 2014, Brandon Allbery wrote: 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. Interesting; I had the opposite experience. With Snow Leopard the reachability was all over the place (using wireless; I didn't try Ethernet) and only settled down with Mavericks (and Yosemite). My FreeBSD server (8.2, 8.4, and now 9.3) has always been spot-on, using a different set of sources. This is using whatever came with the systems, not a ports version. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: FiPy Port Out of Date
On Fri, 21 Nov 2014, Marius Schamschula wrote: py26 versions are being dropped as this point. My regular FreeBSD security check says that py26 is insecure. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.3 has been released
Wasn't this the version that was to summarise any post-installation notes at the end? I just got told to: sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist I had to retrieve it from my scroll-back buffer; it's not important... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.3 has been released
On Sat, 22 Nov 2014, Lawrence Velázquez wrote: This release was fast-tracked to address registry performance. It does not contain any new features. Thanks; I was wondering why so few things were updated... Oh, and whilst I'm here, the 10.10.1 upgrade was seamless! -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Statically linked binaries killed by signal 9 on Yosemite
On Sat, 15 Nov 2014, Michael Crawford wrote: If you can't find a prepackaged valgrind build I'd be happy to build it for you then send you the binary. --- Fetching distfiles for valgrind Error: valgrind @3.10.0 is only compatible with Mac OS X 10.5, 10.6, 10.7, 10.8 and 10.9 Error: org.macports.fetch for port valgrind returned: incompatible Mac OS X version Please see the log file for port valgrind for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_valgrind/valgrind/main.log OK, port selfupdate and port upgrade outdated (and boy, did building webkit-gtk take a long time; I could've fried an egg on the CPU) and try again: Same thing. Let's see what the log says, then: :error:fetch valgrind @3.10.0 is only compatible with Mac OS X 10.5, 10.6, 10.7, 10.8 and 10.9 :error:fetch org.macports.fetch for port valgrind returned: incompatible Mac OS X version :debug:fetch Error code: NONE :debug:fetch Backtrace: incompatible Mac OS X version while executing proc-pre-org.macports.fetch-fetch-3 org.macports.fetch (eval body line 1) invoked from within eval $pre $targetname :info:fetch Warning: targets not executed for valgrind: org.macports.activate org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:fetch Please see the log file for port valgrind for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_valgrind/valgrind/main.log Hmmm... The port for 10.10 not yet available? -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Thank you!
On Wed, 12 Nov 2014, Eneko Gotzon wrote: What a pleasure getting software so easily installed!Thank you all MacPorters! :) I can see that you haven't been on this list for long :-) A couple of things I've learned here: 1) Don't change anything such as symlinks etc; it *will* break something. 2) After a major upgrade e.g. to Yosemite, you *must* do MacPorts/Xcode etc. Oh, and my thanks to the porters too; I know it's a difficult job. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Case-sensitive file system
There was a discussion here on the Mac's case-sensitive-but-not-quite file system, and I was convinced to leave it the way it is (it breaks something in MacPorts or something). Well, I've just been convinced otherwise... I am backing up my FreeBSD server to the MacBook (don't ask) and amongst the detritus accumulated last century I found this: aneurin% ls -l total 60 -rw-r--r-- 1 dave wheel 14414 Jul 18 2000 CHANGES -rw-r--r-- 1 dave wheel 5510 Jul 18 2000 EXAMPLES -rw-r--r-- 1 dave wheel 23253 Jul 18 2000 README -rw-r--r-- 1 dave wheel 5973 Jul 18 2000 UPDATE drwxr-xr-x 3 dave wheel512 Jul 18 2000 examples drwxr-xr-x 2 dave wheel512 Jul 18 2000 hack drwxr-xr-x 2 dave wheel512 Jul 18 2000 html drwxr-xr-x 2 dave wheel512 Jul 18 2000 patch See the problem? Sigh... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
