ated security holes with ypcat abuses as distant early 1990s
memories now).
Thank you in advance for any wisdom you may be able to share on this issue!
｜
グ
レ
ェ
ーgrey
p.s. Happy π day!
I realize I am late chiming in on this thread, and this is, without
a doubt, almost entirely tangential. However, I created a preliminary
Portfile for got-portable (got [Gameoftrees] is a BSD licensed, git
compatible tool aiming for something similar to be a drop in
replacement for git, though it i
I think neverpanic tends to be pretty responsive?
Moreover in the severity was downgraded from Critical to High between the
time the vulnerability was circulating through the grapevine until it
actually was disclosed. There are also no known exploits in the wild
thankfully.
LibreSSL (which is wha
This is a tangential, so please forgive me if this seems as if it is
the wrong time to bring this up, but I seem to have some Rustaceans
who may know more about this than I.
I was recently seeing if there might be a way to improve upon the
FFmpeg ports (there are currently three: ffmpeg, fffmpeg-d
Hello!
This https://trac.macports.org/ticket/67539 was opened about a week
ago, and while I have not been able to replicate it on any of my
systems locally, it seems as if the root cause is due to XCode's clang
(related: https://github.com/llvm/llvm-project/issues/57692 and
https://infosec.exchang
To chime in on this, and take what I write with a grain of salt since
I still feel relatively new to MacPorts, but too much dependence on
GitHub gives me the heebie jeebies.
I realize Trac isn't perfect, but there are far worse issue tracking
systems that I have administered over the decades.
If
Preliminary testing for the handful of ports for which I am listed as
a maintainer went off without a hitch!
However, I have a question which maybe someone who is a bit more of a
Python wizard can explain for me? Note: I don't think this is an issue
with the beta at all.
For example, I performed
Thanks for the explanation! I had done some dependency walks with some
pointers from neverpanic, but hadn't been able to make heads or tails
of why some of the things were the way they were.
On Tue, Jan 2, 2024 at 8:20 AM Joshua Root wrote:
>
> On 2/1/2024 11:24, grey wrote:
> >
I think I may have run into a similar issue with how tests have
changed in CI with 2.9.x MacPorts and the OpenSSH 9.7p1 PR I submitted
yesterday:
https://github.com/macports/macports-ports/pull/22981
Going back to reverting to 9.6p1 locally and running port -d -v test I
see that it fails with the
I am guessing this was fixed?
Regardless, I can't seem to reproduce a failed signature verification locally.
Output with debug and verbose flags added below:
% sudo port -d -v sync
---> Updating the ports tree
Synchronizing local ports tree from
rsync://rsync.macports.org/macports/release/tarba
g personally, I thought
it might be worth discussing more openly about how the project at
large might benefit more holistically than me as an individual
contributor and maintainer.
Other than that, I hope everyone has been doing OK with 2025 and the
year of the Wood Snake!
｜
グ
レ
ェ
ーgrey
Ken, sorry to see you go. By all means, prioritizing self care is
vital! I've experienced burn out with other libre/free open source
endeavors in the past (I stepped away as a contributing editor to
undeadly.org for over a decade when my marriage disintegrated and only
returned in a volunteer capac
I really don't know how I feel about this:
https://github.com/mistydemeo/tigerbrew
In general, I am not a fan of Homebrew. However, for Tiger users
feeling left out by MacPorts' recent changes, maybe that fork will be
helpful?
I've already seen mention on MacRumors of forking MacPorts to retain
on April 7th which seemed relatively uneventful and
I was thinking that removing the legacy_dsa variant was going to be
one of the bigger changes, but clearly I didn't test enough to get
ahead of this; my apologies.
Thank you in advance to anyone who can help!
｜
グ
レ
ェ
ーgrey
g obvious, so
hopefully someone else can help with something I am missing?
Thanks!
｜
グ
レ
ェ
ーgrey
I encountered something similar recently with the OpenSSH 9.9p2 PR I
submitted.
I took screen shots and documented it in the Pull Request:
https://github.com/macports/macports-ports/pull/27712
I have absolutely no idea what was causing that, reverting to classic view
(even though I never enabled
I'm not too sure since you didn't specify how legacy for older OS X
systems you are intending?
Since MacPorts deprecated Tiger and we lost kencu earlier this year;
maybe this blog post from Dr. Brian Robert Callahan will be helpful?
https://briancallahan.net/blog/20250329.html
Admittedly, it loo
Thanks for the perspective.
When you wrote:
"You indicated elsewhere your concern about malware"
I think you may be confusing me with uhm, well, someone who is not me:
https://trac.macports.org/ticket/72492#comment:3
(I am not, nor have I ever been mascguy (Christopher Nielsen)).
I guess I wa
This is tangential, my apologies in advance for any thread de-railing
as a result, but I saw mention of mirrors and thought maybe someone
with more expertise might be able to provide some perspective into
something I have been wondering about.
Namely: if there might be a way to populate the distfi
Hello!
I submitted this Pull Request a couple of days ago:
https://github.com/macports/macports-ports/pull/28613
If I dig into the checks view (e.g.
https://github.com/macports/macports-ports/pull/28613/checks), it
seems as if it's hanging with something similar to the following
message (timesta
20 matches
Mail list logo
