Yuri <yuri_at_FreeBSD.org> wrote on Date: Wed, 18 Dec 2024 22:16:46 UTC : > For example, these 2 recent failures don't appear on > https://portsfallout.com/: > > * > https://pkg-status.freebsd.org/ampere2/data/main-arm64-default/peb87cb7f3aa2_saf66ffbf69e/logs/onnxruntime-1.18.2_1.log > > * > https://pkg-status.freebsd.org/beefy15/data/133i386-default/545eb5d3ac42/logs/olive-video-editor-0.2.0.log > > > > Additionally, bugzilla doesn't have a category to report bugs for > https://portsfallout.com/ > > My request to add such category went unanswered: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276267
I've added the following note to the above bugzilla, other than fixing a bad typo here: QUOTE There is an upstream project for this, with https://github.com/dbaio/portsfallout as the project's place for https://portsfallout.com/ . The upstream project is not part of FreeBSD and not maintained by FreeBSD. Its official repository is not on FreeBSD servers, but instead on github. Why not submit problem reports to the upstream project instead of someplace the developer is not using to develop or maintain the project? That place is at least directly tied to the author/maintainer (dbaio). Avoidin[g] [the] upstream as where to have problem reports seems odd to me. END QUOTE === Mark Millard marklmi at yahoo.com
