somewhere that it stores all your passwords on the disk in
cleartext the entire time you're logged in.
I have no objection to having the osxkeychain feature, but I don't
recommend actually using it.
Fred Wright
On Apr 19, 2024, at 23:52, Kirill A. Korinsky wrote:
On Sat, 20 Apr 2024 00
t, so it never gave up
and never moved on to the mirrors. The response when I reported this was
"gee, it's supposed to have timeouts". I don't know exactly what got
fixed, but I haven't seen this lately.
Livecheck is completely different, since there's no mirroring of the
content that livecheck is looking at.
Fred Wright
pendencies in the Makefile.
Fred Wright
, not 1.3.0).
Fred Wright
On Fri, 29 Mar 2024, Blair Zajac wrote:
I’m seeing it at 5.6.1 in our GitHub repoisory:
https://github.com/macports/macports-ports/blob/master/archivers/xz/Portfile
Ah, OK. The 5.4.6 was based on a selfupdate from two days ago.
On Mar 29, 2024, at 10:40 AM, Fred Wright wrote:
CCing
5.4.5 to fix it. It's not 100% clear
from that whether 5.4.6 is affected, but it sounds like it's not. Since
MacPorts is currently at 5.4.6, the port is probably OK as long as it
doesn't do any overzealous upgrading.
CCing the users list so they don't panic. :-)
Fred Wright
other
packaging systems) MacPorts doesn't have a way to directly make multiple
versions of something available without resorting to the kludge of
building the version number into the name.
Fred Wright
since even the length of the pathname is mirror-dependent, that means
that in some cases the success of a build and/or test may depend on which
mirror provided the Portfile. Sheesh.
Fred Wright
not even be an unreasonable practice to include the output of
"port info --description " in such emails.
Fred Wright
all" usually does. If you skip the separate "make"
without sudo, then the implied build products wind up owned by root, and
even "make clean" requires sudo.
Fred Wright
falls on its
face trying to include ppc-specific code. The Qt4 build itself works,
just not building gpsd against it.
Fred Wright
it doesn't support i386, that might be
a clue that 32-bit support would be significant work.
Fred Wright
inked code is for an emulator, and
is providing a *C* implementation, not a ppc32 machine-code
implementation.
Fred Wright
installed it.
Another possibility would be a receiver-side hook on GitHub, but those
aren't intended for this sort of purpose, so constructing such a hook
would be more complicated.
Fred Wright
On Sat, Jul 15, 2023 at 2:58 PM Fred Wright wrote:
In recent times, commit messages failing
t log --oneline" and "git branch -v"
becomes quite annoying with this error.
Fred Wright
if it is portable or not.
You'd have to be more specific about the intended context. AFAIK,
OSX/macOS didn't have anything like KVM until 10.10, so this specific
patch wouldn't be relevant.
Fred Wright
t 19 hours, and the
whole process took over 24.
BTW, on 10.11, upgrading clang-14 wants clang-11, which fails to build,
apprently due to building something for i386 and failing to link against
the non-uiniversal libxslt.
Fred Wright
On Tue, 7 Feb 2023, Ryan Schmidt wrote:
On Feb 6, 2023, at 14:09, Fred Wright wrote:
Based on a couple of ports where I've had PRs merged recently, it looks
like the buildbots are mostly back in service, but Mojave and arm64 are
still out.
Yes. Disk first aid found a minor problem
, but Mojave and arm64 are
still out.
Fred Wright
On Thu, 29 Dec 2022, Joshua Root wrote:
On 2022-12-29 15:59 , Fred Wright wrote:
Twice recently I've had changes made to ports I maintain without respecting
the maintainer timeout (and not for any urgent security-related reasons).
The first was py-serial, where the change was merged without
it to a broken version of ruby, which I've actually
been working on fixing.
Is this now the Wild West?
Fred Wright
On Sat, 15 Oct 2022, Joshua Root wrote:
On 2022-10-15 13:20 , Fred Wright wrote:
IMO, it should ask before following replaced_by, since replaced_by is
sometimes a matter of opinion. For example, sometimes "port X is replaced
by port Y" really means "We don't want to bother
've encountered is when a fetch dependency needs to be
satisfied even when the distfile archive(s) is/are already present.
Fred Wright
--(host|host_alias)=.* / /g' mpregex.txt
echo "--prefix=/opt/local --with-jemalloc-prefix= CC=/usr/bin/clang"
Fred Wright
On Tue, 5 Apr 2022, Joshua Root wrote:
On 2022-4-5 15:49 , Fred Wright wrote:
Empirically, it was ignored in this case, probably due to a bug. The
sequence was:
sudo port uninstall qt6-qtbase
sudo port -sk install qt6-qtbase
The install didn't build anything, unless I
On Tue, 5 Apr 2022, Joshua Root wrote:
On 2022-4-5 08:23 , Fred Wright wrote:
The fact that you have no 10.15 SDK at all suggests that you're running
Xcode 10.x, though up through 11.3.1 runs on 10.14. I usually run the
latest Xcode for each OS version, which is what the MacPorts
On Mon, 4 Apr 2022, Fred Wright wrote:
Meanwhile, it looks like the update was already pushed, since I had to fight
the port command's refusal to honor -s during further testing. It seems that
an explicit clean is needed to make -s work, in spite of the two alleged
cleans during
On Sun, 3 Apr 2022, Joshua Root wrote:
On 2022-4-3 14:05 , Fred Wright wrote:
lrwxr-xr-x 1 root wheel 15 Sep 26 2020 MacOSX.sdk -> MacOSX10.15.sdk
drwxr-xr-x 7 root wheel 224 Sep 26 2020 MacOSX.sdk 1
lrwxr-xr-x 1 root wheel 10 Aug 17 2019 MacOSX10.14.sdk -> MacOSX.sdk
drwx
On Sun, 3 Apr 2022, Joshua Root wrote:
On 2022-4-3 12:00 , Fred Wright wrote:
I got a warning about the 10.14 SDK not being installed, which I found
surprising since I know I have the CLTs installed. Running the suggested
"xcode-select --install" complains that the CLTs a
re already installed,
and suggests Software Update, which doesn't do anything. Looking in the
SDKs directory within the Xcode bundle, I see 10.15 but not 10.14, though
that ought to work and seems to work. Perhaps the SDK check (which I
think is separate from the port itself) is overly picky.
Fred Wright
Any edit to a port potentially conflicts with something the maintainer(s)
may be doing. The only justification for bypassing the normal maintainer
timeout is when deploying the change is time-critical. Removing an
obsolete port that's been in place for months hardly qualifies.
Fred Wright
in the 64-bit
cases, though not the 32-bit case.
The total build time was about 39 minutes, though I think the prep took
longer than that, due to the requirement to start from a fresh install,
and my wanting to preserve my existing installs in a restorable state,
Fred Wright
cially if the only end benefit is the license. Remember,
OpenSSL is the poster child for why *not* to assume that that newer is
more secure. :-)
Fred Wright
On Fri, 16 Apr 2021, Ryan Schmidt wrote:
On Apr 16, 2021, at 20:33, Fred Wright wrote:
[...]
For that matter, IMO this whole business of the OpenSSL license
conflicting with the GPL is a bunch of nonsense (at least in the
typical MacPorts scenario). Since when does *dynamically* linking
yone tries to claim that merely including the bits necessary to
link against the library is "redistribution", the recent SCOTUS ruling in
Oracle v. Google should put that to rest.
Fred Wright
of ports are not able to be built in
non-root installations).
Does MacPorts play nicely with chroot?
A VM would be another possibility, but chroot would make more sense if it
works.
Fred Wright
n't verify that the code actually works correctly.
Remember Apple was shipping Intel Macs to end users before they'd fixed
all the endian bugs.
Fred Wright
hey're probably also not reasonable
choices for gcc_select or clang_select.
Fred Wright
SuiteSparse_SPQR @2.0.9_0+atlas
SuiteSparse_SPQR @2.0.9_1+atlas (active)
I believe all three of those ports have alternative variants with similar
functionality, but one has to be careful to distinguish such cases from
cases where atlas is the only means of providing its functionality.
Fred Wright
d-mirror.savannah.gnu.org/releases/00_MIRRORS.txt
Fred Wright
On Wed, 29 Jul 2020, Daniel J. Luke wrote:
On Jul 29, 2020, at 9:30 PM, Fred Wright wrote:
[...]
Personally, I'd prefer the MacPorts approach if it were less stingy
with the binary archives. Ideally, one should be *able* to build from
source, but not be *required* to do so.
How
at all?
Personally, I'd prefer the MacPorts approach if it were less stingy with
the binary archives. Ideally, one should be *able* to build from source,
but not be *required* to do so.
Fred Wright
a compatibility du jour list for mirrors
versus OS versions is just an added hassle. The mirrors that are actually
down are more annoying, since that involves timeouts, but that's not
something that one would expect to be reflected in a list (except for
permanent decommisioning).
Fred Wright
On Tue, 28 Jul 2020, Ryan Schmidt wrote:
On Jul 27, 2020, at 18:27, Fred Wright wrote:
[...]
DEBUG: Fetching distfile failed: Unknown SSL protocol error in connection to
jnb.za.distfiles.macports.org:-9824
It appears they've enabled mandatory SSL on this server, which they weren't
doing
DEBUG: Fetching distfile failed: Failed connect to
nou.nc.distfiles.macports.org:80; Operation now in progress
The other mirrors report the expected 404.
Fred Wright
Most sites that complain
still work fine, but some things on GitHub actually don't work, including
some of the PR features. I have to switch to Firefox in such cases.
Fred Wright
/CoreServices/SystemVersion.plist. Will SYSTEM_VERSION_COMPAT
somehow mangle the file contents?
Maybe it should have been code-named "Spinal Tap". :-)
Fred Wright
eam support seems preferable when possible, but
some upstream developers refuse to support old OS versions, sometimes
using "security" as a lame justification.
Fred Wright
On Sun, 28 Jun 2020, Ryan Schmidt wrote:
On Jun 27, 2020, at 23:18, Fred Wright wrote:
On Fri, 26 Jun 2020, Ryan Schmidt wrote:
[...]
Looks like neither shellescape nor quotemeta are documented in the guide.
Perhaps with good reason:
MacML @21:03:49.192:: Error: Failed to extract curl-ca
and 10.12. The missing binary archives are
consistent with this.
Fred Wright
IncludeByPath" => [
0 => "/Applications"
1 => "/Developer"
2 => "/Library"
3 => "/System"
4 => "/bin"
5 => "/private"
6 => "/sbin"
7 => "/usr"
]
[...]
Note that this is for 10.9.
Fred Wright
for
X11 apps.
Fred Wright
Fill in your fav then, with your extensive x11 experience. If there is no
such library, well then, let's move on.
I suspect that there is, but that it's provided by the system rather than
by a port.
New users can segfault, and let them sort it out. It's a litm
On Wed, 20 May 2020, Ryan Schmidt wrote:
On May 20, 2020, at 21:09, Fred Wright wrote:
Just because XQuartz is "out of date" doesn't mean that it might not be
adequate in many cases, and I've found that switching from one X11 to
another involves wrestling with some poorly
*some* X11 server is present, and
gives a warning with an installation suggestion if not.
Fred Wright
see <https://trac.macports.org/ticket/60169>
I thought that the naming scheme change involved how the version suffixing
is handled, but I don't see how that relates to the ticket referenced
here.
Fred Wright
?
Fred Wright
cPorts alias for non-MacPorts uses.
There are both global and per-repo settings in git. In the general case,
one would use the per-repo settings for the MacPorts-related repo(s).
It's the same commands without the --global, but while cd'ed to the
relevant repo(s).
Fred Wright
upgrade of gcc7 on the PowerBook took about 15 hours.
Give an i386 build a try and see if you can come up with something. I
don't love this plan either.
On Fri, 6 Mar 2020, Ken Cunningham wrote:
I am discussing with the gcc darwin lead to see if any other options are
available.
Maybe that will help.
Fred Wright
d it's
hard to see how option 2 would be more awful than creating yet another "X
can't build while Y is active" abomination.
Fred Wright
On Sun, 20 Oct 2019, Joshua Root wrote:
On 2019-10-20 02:37 , Fred Wright wrote:
Recently I've been seeing this on 10.5 (both x86 and ppc):
MacXS:~ fw$ sudo port upgrade outdated
Warning: No port clang-9.0 found in the index.
Warning: No port llvm-3.7 found in the index.
Warning: No port
: No port ld64 found in the index.
Warning: No port perl5 found in the index.
I thought the libc++ change in 2.6 wasn't being applied to 10.5, but the
problem seems to be roughly coincident with the new base. Perhaps the
index generator script was updated incorrectly?
Fred Wright
) Python extensions need source-level differences between Python 2 and
Python 3, though most likely getting this wrong would result in a build
failure, not a runtime failure.
Fred Wright
that from happening like we
do with python.
Such as some way to make the non-interactive response "n" rather than "y":
Install Module::Build now from CPAN? [y] y
Fred Wright
.
At Google, C++ exceptions are considered unreliable enough to be
completely forbidden, and that's on x86.
Fred Wright
es or not,
but even if it does, it blocks updating the port. What's causing this and
how do I get around it?
Fred Wright
builds from PATH as much as possible. I already
suggested two possible alternatives in this case.
Fred Wright
necessary to run SCons with the target Python to get around a
dumb build procedure, there's no reason to alter the SCons installation.
Just invoke SCons with the desired Python. I.e., instead of:
scons
use:
$/bin/pythonX.Y scons
Fred Wright
a 16-month-old ticket "urgent", it might be nice if
someone could look at:
https://trac.macports.org/ticket/56437
This might become more significant with the libcxx churn.
Fred Wright
is nonfunctional if Javascript is
disabled, which isn't ideal.
Fred Wright
ive variants. To avoid
this, one needs to determine the installed variants and then include them
in the 'notes' command.
Fred Wright
some cases, and the
poor discoverability of the option to change that (as well as the change
in the default from 1.0) makes that default even more undesirable.
Also note that the benefit of out-of-source builds is negligible in the
MacPorts environment, anyway.
Fred Wright
grade outdated"
returns error status if nothing is outdated. :-)
Fred Wright
silly, like complaining about "/opt".
This is completely orthogonal to performance issues, of course.
Fred Wright
should still be
signed)?
Fred Wright
ptimizer can completely remove the switch()
and degenerate into just the inline code needed (quite simple for
CLOCK_REALTIME) in the relevant case. And of course it also avoids
adding new link-time dependencies.
Fred Wright
f one were to remove all ports
without dependents, and iterate, there would be no ports at all. :-)
Fred Wright
. Python is perfectly capable of comparing lists directly,
but:
1) The lengths of the lists matter, so you may need either padding or
truncation to make the comparison correct.
2) Comparing lists of strings uses a "naive" comparison of the elements.
If they're known to be purely numeric, that can be fixed with int().
In this particular case, you should be able to replace the first two
lines with:
if map(int, v.split('.')[:2]) >= [10, 12]:
Fred Wright
the Compare
page and then using the PR button from there. Though I expect that
merging the PR would have used the correct commit message, and only the PR
text would have been incorrect.
Fred Wright
r ntpsec
which I haven't submitted yet since I haven't tested it as well as I'd
like, but I'm in the middle of a major move right now and don't have time.
Fred Wright
Although
asking before switching variants might make sense, in that case it should
be more informative about what it's actually proposing to change.
Fred Wright
d any commits
> > from the repository.
> >
>
>
> What happened here?
Probably the removal of a misnamed tag.
> We still seem to have a "v2.3.4" tag in the repo like we should.
But not a "release_2_3_4" tag.
Fred Wright
n update
mechanism for this.
With this approach, all content except the locally modified ports comes
from rsync as usual, and the local portindex only contains the modified
ports. The usual selfupdate/upgrade works fine, and mostly doesn't care
whether the git repo is up to date.
Fred Wright
82 matches
Mail list logo
