On 8/15/24 12:29, Dimitry Andric wrote:
On 15 Aug 2024, at 19:13, henrichhart...@tuta.io wrote:

There's been a lot of packages that haven't been built in quarterly because of 
a checksum mismatch. I think this affected latest as well for a little while, 
but that's been resolved.

Here's some information on the extent of the issue:
https://forums.freebsd.org/threads/disappearance-of-desktop-applications-firefox-thunderbird-from-repositories.94550/

And a bug for a quick fix: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280833

Moving forward, it sounds like this is not the first time this has happened. 
Something about the patch format coming back slightly differently from 
Bitbucket. Could we move the patch to the patches/ folder so this can't be an 
issue in the future, or could we update to x265 3.6, which doesn't need it?

The problem is that Bitbucket appends a line with the Git version they're using 
at the end of the patch, or at least they don't filter it out. This should 
probably be reported to Bitbucket as a bug, but past experiences with Atlassian 
are not encouraging. :-)

Maybe implement a workaround for bitbucket ports such as (used diff to express the idea of the change, don't recommend using this as the patch directly):

--- /usr/ports/multimedia/x265/Makefile 2024-07-10 16:18:58.395378000 -0700
+++ multimedia/x265/Makefile    2024-08-15 13:44:05.236522000 -0700
@@ -112,6 +112,9 @@
 POWER8=        false
 .endif

+post-fetch:
+       @${SED} '$d' x265-asm-warnings.patch
+
 pre-build::
        @${ECHO_MSG} "---> Building the $b-bit library ---"
        ${MKDIR} ${WRKSRC:H}/$bbit

-Dimitry




Reply via email to