About the problem of failure of the source code of the ports package management project, causing it to fail to install

Hello, I'm using freebsd to check the raid card, but I found
This toolkit can no longer be installed, its source code download connection seems to have expired. I like the package management method of ports, but users seem to be powerless in the face of this situation.
 
I like the package management method of ports, but users seem to be powerless in the face of this situation.
See what it says on that page you linked to: "To install the port: cd /usr/ports/sysutils/arcconf/ && make install clean".
Just make sure your ports tree is up-to-date.
 
See what it says on that page you linked to: "To install the port: cd /usr/ports/sysutils/arcconf/ && make install clean".
distfile fails to fetch, that's the whole problem. It's been failing for quite some time.


oldcat I suggest opening a PR for it, maybe the maintainer can figure out where the file has been moved to. Or just deprecate the whole port (no sense in keeping something that doesn't work).

 
distfile fails to fetch, that's the whole problem. It's been failing for quite some time.


oldcat I suggest opening a PR for it, maybe the maintainer can figure out where the file has been moved to. Or just deprecate the whole port (no sense in keeping something that doesn't work).

I've seen that someone has raised pr, but no relevant maintainer responds
 
After two weeks a maintainer time-out should be applied. But you might need to ping the freebsd-ports@ mailing list. The attached patch looks good, so all you need is a ports committer willing to apply it.
 
After two weeks a maintainer time-out should be applied. But you might need to ping the freebsd-ports@ mailing list.
The patch exists since 2025-04-17 01:06:27 UTC
On 2025-05-06 12:06:09 UTC the reporter said: "Maintainer timeout?"
Nothing happened since.

What's wrong with writing patches if someone writes a patch and still have to beg on a mailing-list?
Next thing "prayers" are needed?
 
What's wrong with writing patches if someone writes a patch and still have to beg on a mailing-list?
Nothing is wrong, but most people are busy. It is kind of self-centered to expect that everyone has free time to grab a patch when it appears, or remember to test and implement it a few weeks later. Thus, you have the option to gently remind folks on the mailing list.
 
Nothing is wrong, but most people are busy. It is kind of self-centered to expect ...
Sorry, I do not buy that. Claiming to be busy is one of the most used and cheapest form of excuse for not taking responsibility, and that is "self-centered" behavior.
 
Sorry, I do not buy that. Claiming to be busy is one of the most used and cheapest form of excuse for not taking responsibility, and that is "self-centered" behavior.
Remember these folks are not getting paid to work on the ports collection. They may be on vacation. Maybe they had a life event.

I think being patient and asking politely on the mailing list are not big asks considering what we get for free in exchange.
 
Sorry, I do not buy that. Claiming to be busy is one of the most used and cheapest form of excuse for not taking responsibility, and that is "self-centered" behavior.
All Open Source operates like that - somebody's got a personal itch to do it right, and merely takes advantage of available mechanisms to share it. It's all unpaid volunteer efforts. If something is not working out, just go look for an alternative.
 
Sorry, I do not buy that. Claiming to be busy is one of the most used and cheapest form of excuse for not taking responsibility, and that is "self-centered" behavior.
As multiple person already noted, it's only applicable for PAID, yes, PAID PROPRIETARY SOFTWARES ONLY, AND APPLICABLE TO THE FULL TIME EMPROYEE OF THEM. Not at all applicable for volunteer-based projects like FreeBSD project. It's toooo many times mangled and mis-understood. Sigh.

For a referense, my post to freebsd-hackers ML related with x11/nvidia-driver-390. Read especially last 2 paragraphs.

Recently I'm de-facto ports-side (not upstream) maintainer of x11/nvidia-driver, x11/linux-nvidia-libs and their legacy versions. But I'm not an employee nor founder of nvidia, unpaid from them nor any other parties. 100% volunteer. Yes, purely a volunteer. Most of maintainers / committers would be, too. (I'm not a committer, so I myself cannot commit my proposed patches by myself. But thankfully 2 committers are quite active to review, frankly discuss [including privately for too early ideas] with me and commit when they feel the patches acceptable.)

So I can resign whenever I want/need, for example, when my current health issues somehow goes worse and cannot continue.
 
Yeah, and I was the de-facto AMD support around here. I never bothered to sign up anywhere or formalize any kind of commitment. I merely did a bit of research for my own hardware, nothing formal or academic, and Forums were just a convenient way to help other casual owners of AMD hardware.

I don't always have the time to take the problem-solving process (for the AMD hardware to run under FreeBSD properly) all the way to the end - I do have commitments IRL to keep. Fortunately, there is someone else on these Forums who can respond and provide the same kind of help that I provide. If not me, then erichans...

I'm not an employee of AMD or the FreeBSD foundation, and NVidia actually has a fairly big presence in US West Coast. At some point, I may decide to formalize my AMD hardware expertise - POSIX.1 , are you willing to be my sponsor and pay me to do that? That's what it will take for me to decide to do it sooner rather than later. You basically get what you pay for, even in the Open Source world.
 
Back
Top