What happens with
/usr/bin/open some_file.pdf
?
> On Apr 15, 2023, at 15:57, Kenneth Wolcott wrote:
>
> Hi;
>
> off-topic question: Apple open command and/or apps in /Applications
> are half-broken now
>
> I'm asking the question here because I think that there are lots of
> people who
Also, for whatever reason, Mountain Lion does not source .bash_profile on
login. So on that box, I have to source it after I login and whenever I sudo. I
guess I could add a script to source it at login, but it's not a big deal.
> On Mar 20, 2023, at 13:10, chilli.names...@gmail.com wr
Really? Do you never edit your .bash_profile to add functions?
> On Mar 20, 2023, at 13:01, Will Senn wrote:
>
> bash_profile is executed for login shells, so it shouldn't be sourced more
> than once per login.
>
> On 3/20/23 11:49 AM, chilli.names...@gmail.com wrote:
fixed duplicates when sourcing .bash_profile by clearing PATH before the export
command with
PATH=
LOL
ugly, but it works
> On Mar 20, 2023, at 12:49, chilli.names...@gmail.com wrote:
>
>
> I was checking. echo $PATH reports correctly. If I source the .bash_profile
>
t a matter of
> figuring out which ruby comes first.
>
> Will
>
>> On 3/20/23 11:33 AM, chilli.names...@gmail.com wrote:
>> This is the only way I can get it to work right without error
>>
>>> export
>>> PATH="$PATH:$HOME/bin:/opt/local/bin:/opt/local/sbin:/
gt; Mark E. Anderson
>> Find me on LinkedIn
>>
>>
>>> On Sat, Mar 11, 2023 at 5:57 PM Austin Ziegler wrote:
>>> Change that to
>>>
>>> export
>>> PATH=$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin:$PATH
&
ATH=$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin:$PATH
>>
>> -a
>>
>>>> On Mar 11, 2023, at 14:03, chilli.names...@gmail.com wrote:
>>>>
>>>
>>> Thank you, I will check that
>>>
>>> I
They all point to the old system versions
My $PATH is pretty screwed up.
Thanks.
> On Mar 11, 2023, at 13:50, Bill Cole
> wrote:
>
> On 2023-03-11 at 13:05:54 UTC-0500 (Sat, 11 Mar 2023 13:05:54 -0500)
>
> is rumored to have said:
>
>> Hi,
>> I need a quick ruby primer, please.
>>
>> I'd
gt; `/usr/bin`. Typically, one wants to have Macports (or other third-party
> package systems) *before* /usr/local/bin and /usr/bin.
>
> -a
>
>> On Sat, Mar 11, 2023 at 1:46 PM chilli.names...@gmail.com
>> wrote:
>>
>>
>>> root@mac:~$ ruby -S ge
orts Ruby (I use `ruby-install`), but try this:
>
> sudo ruby -S gem install coltrane
>
> Ruby since Ruby 2.x has included Rubygems, and since a bit later than that,
> Bundler.
>
> -a
>
> On Sat, Mar 11, 2023 at 1:06 PM chilli.names...@gmail.com
> wrote:
>
Hi,
I need a quick ruby primer, please.
I'd like to install this,
https://github.com/pedrozath/coltrane
> sudo gem install coltrane
won't work because I'm on Mojave with an an ancient ruby and this requires ruby
2.7 or above.
> sudo port -vsN install ruby
installs ruby18 by default
> sudo
Whenever I find something not on MacPorts, I always request it from the
developer, who is usually accommodating.
> On Feb 15, 2023, at 14:55, André-John Mas wrote:
>
> Hiya,
>
> What is the current status of co-existence of Brew and MacPorts on the same
> machine?
> Previously this was
is deleted on
success. :/
> On Feb 12, 2023, at 14:05, Dave Allured - NOAA Affiliate
> wrote:
>
>
> Nope. That's a dual python310/311 ticket. Same issue for both.
>
>
>> On Sun, Feb 12, 2023 at 1:47 PM chilli.names...@gmail.com
>> wrote:
>> Nope. Tha
this one?
>
>
> #66242 (python311 @3.11.0 +lto +optimizations fails to build with broken
> symlink in include path)
> trac.macports.org
>
> —
>
>
>> On 12 Feb 2023, at 18:47, chilli.names...@gmail.com wrote:
>>
>> Where is a recent ticket for python31
Where is a recent ticket for python310 build failure? All I see is a few recent
tickets closed as duplicates. Duplicates of what? I don't see any previous
recent python310 ticket. My build is failing on Mojave and holding up cairo and
gnutls upgrades. Whenever there is an upgrade holdup, it
Hi,
It's unclear if you tried
sudo port install pandoc
or to build it
sudo port -s install pandoc
Should install version 3. Sometimes fetch fails at all the sites, but that is
rare, and you just try again, and usually it resolves itself.
> On Jan 25, 2023, at 16:40, Will Senn wrote:
>
>
What's strange is port outdated doesn't show anything, so I expect these ports
are broken and my install doesn't know it. I bet it has something to do with
port reclaim running when I tried to selfupdate. I deleted all the build
directories out of habit.
gegl @0.4.40_0+quartz+vala (active)
I just tried upgrade outdated this morning before Mr. Root's notice, and rust
is building. I appreciate the assistance of you both.
> On Dec 29, 2022, at 12:58, mcalh...@macports.org wrote:
> Thank you for providing the correct ticket URL.
> I had too many tabs open.
>
> Please forgive my
I spoke too soon, that ticket is ancient. I'll do as you suggest tonight.
Thanks again.
> On Dec 28, 2022, at 14:41, chilli.names...@gmail.com wrote:
>
>
> Thank you! I searched for, but could not find that ticket. As long as there's
> an incident ticket I feel secure, but by
upgrades simultaneously. Why would rust be available for Mojave but 404 on
Mountain Lion?
> On Dec 28, 2022, at 00:04, chilli.names...@gmail.com wrote:
>
> Error: Problem while installing rust
>
>
>
>
>
> This has been going on for a day at least, maybe more. Why can't I fetch rust?
Error: Problem while installing rust
main.log
Description: Binary data
This has been going on for a day at least, maybe more. Why can't I fetch rust?
postfix has no dependencies btw
> On Dec 23, 2022, at 08:36, chilli.names...@gmail.com wrote:
>
>
> port rdeps postfix
>
> shows it's dependencies. Probably want to pipe into more.
>
> But to see what depends on postfix, it's a little different.
>
> port echo
port rdeps postfix
shows it's dependencies. Probably want to pipe into more.
But to see what depends on postfix, it's a little different.
port echo depends:postfix
> On Dec 23, 2022, at 07:49, Gerben Wierda via macports-users
> wrote:
> Ik keep struggling when I try to find out
logged back in.
>>
>> When running evince with a Postscript file I still get the flashing
>> and I get the following:
>>
>> dbus[66621]: Dynamic session lookup supported but failed: launchd did
>> not provide a socket path, verify that
>> org.freedesktop.
oops, probably want to add
sudo port install xorg-server
so, altogether,
sudo port install xorg xorg-server; sudo port load dbus
Log out. Log in.
> On Dec 19, 2022, at 07:03, chilli.names...@gmail.com wrote:
>
> I just went through this on Mountain Lion and Mojave. I bel
I just went through this on Mountain Lion and Mojave. I believe it's
sudo port install xorg
Installs XQuartz X11.app in /Applications/MacPorts
but I think also may need to
sudo port load dbus
and log out and back in again.
IMO, Homebrew is a bloody mess. Good luck uninstalling it. Probably
18:51, chilli.names...@gmail.com wrote:
>
>
> There was no 10.4.
>
> Try looking for XCode 10.1
>
>>> On Dec 16, 2022, at 18:46, James wrote:
>>>
>> Hi
>> many folk here run older macos. Perhaps someone can help me
>>
>> I've a 20
There was no 10.4.
Try looking for XCode 10.1
> On Dec 16, 2022, at 18:46, James wrote:
>
> Hi
> many folk here run older macos. Perhaps someone can help me
>
> I've a 2011 iMac27 pegged at High Sierra
> I was trying to build mythtv; all my attempts to create a High Sierra VM
> failed, and
to initialise (BadParameter)
Of course, org.freedesktop.dbus-session.plist is neither loaded nor installed.
Using Pacifist, I looked in the XQuartz package, and it is not in there, thus
it was not installed.
[sigh]
> On Dec 15, 2022, at 10:30, chilli.names...@gmail.com wrote:
>
> Thanks J
Thanks Josh. port reclaim did the trick.
I'm still preparing a ticket for gtk3 build fail on Mojave, but thought I
should double check here to make sure this is a gtk3 ticket and not a NetSurf
ticket.
-
NetSurf build appears to have been successful on OS X 10.8.5 w/ Xcode 5.1.1 on
Hello,
I wanted to check out NetSurf today on Mojave. A lot of dependencies built
fine, but gtk3 choked. I'm in the process of creating a ticket for this, but
the same build is still in progress on Mountain Lion, and I want to wait to see
if it completes (started early this morning and still
oops.
sudo port -v selfupdate
srry
> On Dec 9, 2022, at 08:17, Kaustubh Bansal wrote:
>
>
> I get following error
>
> $ port -v selfupdate
> Error: Insufficient privileges to write to MacPorts install prefix.
>
>> On Fri, Dec 9, 2022 at 1:49 PM chilli.names..
Try
port -v selfupdate
then try to install clang-15 again?
> On Dec 9, 2022, at 07:40, Kaustubh Bansal wrote:
>
>
> Hi
>
> I recently installed MacPorts on my machine (MacOs Ventura 13.0)
> Installation succeeded.
> I then added /opt/local/bin to PATH
>
> I am trying to install clang-15.
> On Nov 29, 2022, at 06:55, Gerben Wierda via macports-users
> wrote:
>
> Before Monterey I was running Mojave and that worked very well. I skipped
> Catalina and went straight for Monterey so I would have a long period of 'no
> large migrations'.
I'm running file servers on Snow
There is documentation for port command flags in the online manual pages:
man port
also in Chapter 3 of the MacPorts Guide with examplese
https://guide.macports.org/chunked/using.html
Hope that helps.
> On Nov 14, 2022, at 04:14, Lukas Oberhuber wrote:
>
>
> Hi,
>
> I was wondering
If it helps, it can be hidden from the Finder:
sudo chflags hidden /Applications/MacPorts
(undo with "nohidden")
> On Nov 10, 2022, at 09:56, Chris Jones wrote:
>
>
> May I ask, what exactly is your problem with having the Apps installed by
> MacPorts under /Applications/MacPorts ? I am not
> On Sep 29, 2022, at 17:54, Dave Horsfall wrote:
> On Thu, 29 Sep 2022, chilli.names...@gmail.com wrote:
>
>> The initial reported spec, "a High Sierra MBP," is ambiguous. That could
>> mean a 2010 MBP, that can be updated up to High Sierra with a third
>&
> On Sep 27, 2022, at 13:19, Ralph Seichter via macports-users
> wrote:
> * Chris Jones:
>
>> For the purposes of the original question here, its more than good enough.
>
> That is, of course, for the OP to decide. I stand by my recommendation
> to use 'git log ...' on a cloned repository,
> On Sep 29, 2022, at 15:51, Dave Horsfall wrote:
> On Thu, 29 Sep 2022, Ces VLC wrote:
>
>> I'm planning an update of a High Sierra MBP up to Monterey [...]
>
> The MPP won't go beyond High Sierra (I've tried); there is a chart
> somewhere showing the supported releases.
>
> -- Dave
Is it possible to see the version history of a port? For instance, how would
one discover how long a port has been available through MacPorts, or the date
the first available version of that port appeared?
Not critical, it's just for curiosity.
>> port upgrade outdated and not \( badport1 or badport2 \)
that works perfect, thank you!
feel free to mock me, I deserve it.
> On Sep 12, 2022, at 15:19, chilli.names...@gmail.com wrote:
>
> No, I got it. Ignore.
>
> And thank you all.
>
>> On Sep 12, 2022,
> looks a bit like the line above with the parenthesized list of what not to
> update, except rather longer.
>
>
>> On Sep 12, 2022, at 3:02 PM, chilli.names...@gmail.com wrote:
>>
>>
>> Yes, you got it. How do I command MacPorts to upgrade all outdated p
itual. My usual
> looks a bit like the line above with the parenthesized list of what not to
> update, except rather longer.
>
>
>> On Sep 12, 2022, at 3:02 PM, chilli.names...@gmail.com wrote:
>>
>>
>> Yes, you got it. How do I command MacPorts to upgrade all out
Excellent. Thank you. I suspected there was, just unaware of syntax. Whenever I
consult the manual, I seem to only see that which I already knew, and what I
wanted to know, hidden in plain sight, often eludes me. Thanks again.
> On Sep 12, 2022, at 15:12, Bill Cole
> wrote:
>
> On
Yes, you got it. How do I command MacPorts to upgrade all outdated ports "and
not" this whatever troublesome port? Is there a way? If you just told me,
you'll have to be less subtle.
> On Sep 12, 2022, at 14:00, Bill Cole
> wrote:
> On 2022-09-12 at 12:04:41 UTC-0400 (Mon, 12 Sep 2022
(note: my reply all does not include the list, annoyingly)
That is pretty unsettling.
uname -p gives i386
uname -m gives x86_86
I vaguely recall that in the past MacPorts has ignored the arch specification.
If macports.conf arch setting is ignored, is there a way I can force x86_64?
Thanks.
Thanks for catching that.
From my macports.conf file:
# CPU architecture to target. Supported values are "ppc", "ppc64",
# "i386", "x86_64", and "arm64". Defaults to:
# - Mac OS X 10.5 and earlier: "ppc" on PowerPC, otherwise "i386".
# - Mac OS X 10.6 - 10.15: "x86_64" on 64-bit Intel, otherwise
With Mojave on Macmini6,1 & XCode 11.3.1
I get this:
port -vsN upgrade libgcc9
---> Computing dependencies for libgcc9.
---> Fetching distfiles for libgcc9
Error: gcc9 9.5.0 is not supported on Darwin 18 i386
Error: Failed to fetch libgcc9: incompatible macOS version
Error: See
You don't want to build software? You only want to install binaries? I am the
opposite. If it doesn't build on my machine, I don't want it.
> On Sep 3, 2022, at 04:02, Mark Bestley wrote:
>
> I have just done a port seflupdate and upgrade outdated.
>
> Rust was needed but it had to be built
for a
> time, until you production is back up and solid” is not a feasible option, if
> one is trading in to Apple the old machine: Apple provides only a 14-day
> window in which to receive the old machine (after one receives the return
> carton).
>
>
> OnSun, 31 Ju
I've been debating about responding because I don't know the particulars of
your migration. But in my experience working in IT for more than 2 decades is
that it is almost always better to manually migrate rather than use Apple's
Migration Assistant.
First, consider what the Migration
Your grievance is with whatever macOS version you're using, not with the Gimp.
This should get you half way back:
https://9to5mac.com/2018/08/15/mac-how-to-restore-save-as-functionality/
if Finder--> open with gimp means right-click contextual menu open with, that
menu list is just like
022, at 14:10, James Secan wrote:
>
> Should have mentioned I’ve already done that as my final fall-back, but I’d
> rather be able to get back to exactly where I was vis-a-vis MacPorts if I
> step on something I shouldn’t have.
>
> Jim
> Seattle, WA
>
>> On May 7
May want to save a copy of output of
port list requested
to make it easy to restore if it all goes South. When I'm migrating, I take
that list and turn it into an install script.
> On May 7, 2022, at 13:55, Jim Secan wrote:
>
> I’m about to embark on a major mucking-out of my MacPorts
Uh, I guess 1988 called and wants the IRC channel fixed?
> On May 6, 2022, at 15:17, Michele Venturi wrote:
>
>
> They don't seem to care very much sadly,
> at least in my well grounded opinion,right?
>
> Il ven 6 mag 2022, 20:02 Eric Gallager via macports-users
> ha scritto:
>> Any
First look at
port info php80
if that doesn't satisfy you, then try
port echo depends:php80
will show all dependencies
> On May 5, 2022, at 14:13, JEFFRY KILLEN wrote:
>
> Hello:
>
> I am new to macports. My current interest to so install php on
> MacOS Monterey. But I do no see specific
Well, I am able to selfupdate, and I was able to upgrade freetype, harfbuzz &
libnetpbm
But curl is unavailable due to 404, even thru VPN
also html2text, 404
No bananas today. Bananas tomorrow. Always bananas tomorrow.
> On May 5, 2022, at 12:02, "chilli.names...@gmail.co
n May 5, 2022, at 11:54, Chris Jones wrote:
>
>
>
>> On 05/05/2022 4:51 pm, chilli.names...@gmail.com wrote:
>> I can't upgrade because of 404? Is this a problem on my end?
>
> Most probably yes. Update built just fine here.
>
> Check your local network
I can't upgrade because of 404? Is this a problem on my end?
> ---> Computing dependencies for curl-ca-bundle.
> ---> Fetching distfiles for curl-ca-bundle
> ---> curl-7.83.0.tar.xz does not exist in
> /opt/local/var/macports/distfiles/curl
> ---> Attempting to fetch curl-7.83.0.tar.xz from
> On Apr 30, 2022, at 06:27, Al Varnell via macports-users
> wrote:
>
> On Apr 30, 2022, at 12:08 AM, Mike Alexander wrote:
>>
>>> On 23 Apr 2022, at 8:06, Steven Smith wrote:
>>>
>>> The only issue I’ve seen with the disappearance of macOS native Python is
>>> some minor thing my own
> On Apr 14, 2022, at 14:56, Peter Serocka wrote:
>
>
>
>> On Apr 14, 2022, at 14:10, chilli.names...@gmail.com wrote:
>>
>>
>>
>> Thinking more about upgrading, maybe there's an Xcode version issue?
>> MacPorts requires Xcode's command
> On Apr 14, 2022, at 07:54, Peter Serocka wrote:
>
>
>
>> On Apr 14, 2022, at 13:08, chilli.names...@gmail.com wrote:
>>
>>
>>
>>
>> I don't get it. What is stopping MacPorts users that don't use custom
>> prefixes fr
> On Apr 14, 2022, at 06:45, Peter Serocka wrote:
>
>
>
>> On Apr 14, 2022, at 11:48, Ryan Schmidt wrote:
>>
>>> On Apr 14, 2022, at 04:34, Peter Serocka wrote:
>>>
>>> Sure. On the other hand -- let me suggest MacPorts to adopt
>>> OS/architecture-specific prefixes by default.
MacPorts is, by a long margin, the best package manager for macOS and Mac OS X
before it.
Homebrew is more like a cult than a package manager, and it has always been
redundant and inferior to MacPorts. It is inferior due to the way it botches
permissions, and specifically the way it creates
Bug reporter worked today. I had a feeling it would.
> On Mar 5, 2022, at 09:36, "chilli.names...@gmail.com"
> wrote:
>
>
> Thanks everyone, with the bug reporter flaking on me, and never having seen a
> listserv message sit... I got paranoid.
>
&g
lso, I don’t think the log says what OS you’re building on, so you probably
> need to say that. Does rsync only build or can you try downloading a binary?
> Does the binary not work if that option is available?
>
> Lenore
>
>> On Mar 5, 2022, at 08:29, chilli.names...@gm
Maybe I'm losing it, but I'm getting the feeling I've been shadow banned.
Can anyone hear me? Thanks.
>> On Mar 4, 2022, at 20:39, "chilli.names...@gmail.com"
>> wrote:
>
>
> https://trac.macports.org/ is refusing to let me submit a ticket returning an
&g
https://trac.macports.org/ is refusing to let me submit a ticket returning an inscrutable "invalid parameters" complaint. rsync build log here
main.log
Description: Binary data
https://trac.macports.org/ is refusing to let me submit a ticket returning an inscrutable "invalid parameters" complaint. rsync build log here
main.log
Description: Binary data
https://trac.macports.org/ is refusing to let me submit a ticket returning an inscrutable "invalid parameters" complaint. rsync build log here
main.log
Description: Binary data
26, 2022, at 16:07, "chilli.names...@gmail.com"
> wrote:
>
> I don't know if this will be all that helpful because it is pretty old
> information. Bought a Mac in 2010 with Snow Leopard, but I didn't want the
> default install, trimmed it down to a bare minimum system
I don't know if this will be all that helpful because it is pretty old
information. Bought a Mac in 2010 with Snow Leopard, but I didn't want the
default install, trimmed it down to a bare minimum system that still had a
desktop, disabled all possible features and removed them, etc. I think my
Hope this isn't a dumb comment, but recently noticed on the aggregator an
article about sending sms using python.
https://news.ycombinator.com/item?id=29915412
Does MacPorts have any python at all? I'm kidding.
> On Jan 16, 2022, at 21:31, Ryan Schmidt wrote:
>
> On Jan 15, 2022, at
> On Jan 13, 2022, at 23:15, Ryan Schmidt wrote:
>
> On Jan 13, 2022, at 17:01, Bill Cole wrote:
>
>> On 2022-01-13 at 16:26:01 UTC-0500 (Thu, 13 Jan 2022 15:26:01 -0600) Will
>> Senn is rumored to have said:
>> [...]
>>>
>>> My question for y'all goes like this - How long will macports
I don't consider /Applications/MacPorts part of the installation. And deleting
binaries I built would be like... not only uprooting the tree, but destroying
the fruit as well. That said, you have fair point.
> On Nov 27, 2021, at 03:22, Pieter van Oostrum wrote:
>
> &quo
To uninstall macports entirely, I use the three commands below in a script
(which I assume I got from the manual, but it's been awhile, I do not recall),
but they work just as well one at a time:
sudo port -vfp uninstall --follow-dependencies installed
sudo port -vfp uninstall all
sudo rm
> I recently downloaded a prebuilt version of both basiliskii and sheepshaver
> from the 'macemulation' website that is 64bit and runs on BigSur, and that
> works well too.
I think you meant
https://www.emaculation.com/forum/viewtopic.php?t=7361
Interesting idea to attempt coax Mojave to build for 32-bit. However, I find
when I stray from conventional installations to custom, even when I take
detailed notes, over time I forget what I did, and it becomes an issue when
recreating an installation.
I'm not sure "need" is accurate, but
Thanks Ryan, that's answered everything.
The reason I chose Mojave was because it is the last macOS to support running
32-bit applications, but obviously my research was not deep enough. Since it
can not build 32-bit applications... looks like I'll be backing up the Mojave
install and
Hi mailing list participants.
I'm going to introduce several topics. At your choice, leisure and convenience,
a response to any is appreciated.
1) First of all, as a user, I am tremendously grateful to all the macports
developers. MacPorts is really great stuff. Well done.
2) I wrote a
Hello,
A little embarrassing, but I need some direction. I realize macports user
support does not really exactly support the port I need (ffmpeg), I have a
feeling someone reading this will know what's up from the brief details I can
provide. Please allow me to describe my situation, and where
81 matches
Mail list logo
