livechecks of various ports are broken

[KubaO (Kuba Ober)]

port livecheck all returns plenty of errors (HTTP errors, non-matching regexes, etc.) I'll attach a current list. Patches will follow in an attempt to get this list as small as possible. Question: should a ticket be opened for each port in spite of it all being fixed by one-liners, or should there be a patch that can fix many portfiles at once?

[ryandesign (Ryan Carsten Schmidt)]

Usually you should file tickets for each port. Ports might be maintained by different maintainers and they might have different opinions on how the problem should be fixed. I realize that's inconvenient. If the ports are nomaintainer or openmaintainer then anyone can make the change, and I'd have no problem with seeing a large patch or many patches for that here.

Running "port livecheck all" is unexpected, and probably takes a very long time besides. Usually you run "livecheck" only on ports that interest you. For example, I run it on ports I'm maintainer of ("port livecheck maintainer:ryandesign"). Or you might run it on ports that you're actually using ("port livecheck active").

[KubaO (Kuba Ober)]

I'll start with ports that are maintainer and openmaintainer and file individual tickets for those. It's the smallest group. I'll then move on to openmaintainer ones and still submit tickets one-by-one. The nomaintainer ports will be done as large patches added to this ticket. Makes sense?

Yes, port livecheck all is pretty damn slow. I've cheated by splitting up the portlist in 30 chunks and running each of those in parallel. Makes it take 10 minutes :)

My reason is to get an idea for how many ports are there that are out of date. Seems like quite a lot, unfortunately.

[ryandesign (Ryan Carsten Schmidt)]

Replying to kuba@…:

I'll start with ports that are maintainer and openmaintainer and file individual tickets for those. It's the smallest group. I'll then move on to openmaintainer ones and still submit tickets one-by-one. The nomaintainer ports will be done as large patches added to this ticket. Makes sense?

That sounds ok.

Yes, port livecheck all is pretty damn slow. I've cheated by splitting up the portlist in 30 chunks and running each of those in parallel. Makes it take 10 minutes :)

In fact, I don't run "port livecheck maintainer:ryandesign"; I run a script​ that runs the livechecks in parallel.

My reason is to get an idea for how many ports are there that are out of date. Seems like quite a lot, unfortunately.

Yes. Of the ~9100 portfiles in our collection, ~3600 do not have a maintainer listed, so many of these are probably out of date or do not work. And many of the remaining ports probably need updates too, due to maintainers who have left and not notified us, or who have not checked for updates, or where the update does not work. So it would not surprise me if there were thousands of ports needing updates.

So it helps to prioritize the work based on what ports people actually want to use. If a port has an update available, or does not build, but nobody has filed a ticket about it, there's a chance nobody is actually using the port and we could work on fixing a different port instead.

[kurthindenburg (Kurt Hindenburg)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

I'll close this - you can open separate tickets if you're still interested.