Created attachment 250894 [details] Add PORTSCOUT restriction Add PORTSCOUT restriction to avoid triggering daily message, as upstream has daily releases. Moved a line in the Makefile to please portlint.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=66ba27fdfb7a001ea97ce5ee578e2f2364f7d898 commit 66ba27fdfb7a001ea97ce5ee578e2f2364f7d898 Author: Larry Rosenman <ler@FreeBSD.org> AuthorDate: 2024-06-07 15:11:41 +0000 Commit: Larry Rosenman <ler@FreeBSD.org> CommitDate: 2024-06-07 15:11:41 +0000 cad/ifcopenshell: Quiet portscout Add PORTSCOUT restriction to avoid triggering daily message, as upstream has daily releases. Moved a line in the Makefile to please portlint. PR: 279244 Reported by: Laurent Chardon <laurent.chardon@gmail.com> cad/ifcopenshell/Makefile | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
Committed, thanks!
Is there a delay before this takes effect? It's still in the previous email. https: //lists.freebsd.org /archives/freebsd-ports/2024-June/006274.html
I've noticed that too, and I don't know the reason why it's still showing up. The restriction has been correctly added to portscout database: https://portscout.freebsd.org/restricted-ports.html. I will try to understand why it's not working.
https: //github.com /freebsd/portscout/blob/f1a90b0883ec7c8f712d11ed824450fea801d2d1/portscout.pl#L1008 The above line makes it seem that blenderbim- part is not included in the comparison. But if that is the cause, I don't know why it was suppressed normally until yesterday :)
Ah, I had an epiphany :) Committing comment #1 probably didn't have any effect. The email in comment #3 was the last email that blenderbim- was written on. https: //lists.freebsd.org /archives/freebsd-ports/2024-June/006274.html After that day, the release tag became such a number that we had to bump portepoch. The version that was the largest number fell to the point where it had to be retrieved by adding ?page=2. portscout doesn't seem to be doing that much. It is thought that this is the cause...
(In reply to Tatsuki Makino from comment #5) I think you are right, good call! It also seems that the versioning scheme of ifcopenshell has changed recently. One option would be to match strictly 3 digits, as in "0.7.9", with a limit of '^\d\.\d\.\d$$'. This would match every stable release with the current versioning scheme. In the recent releases, blenderbim-0.7.9, ifcsverchok-0.7.9 and ifcopenshell-python-0.7.9, would match. Daily builds such as blenderbim-0.7.9.240710 would not. Unfortunately, there doesn't seem to be a way to target ifcopenshell-X.Y.Z only. Does this make sense to you?