When trying to build the port net-im/farstream with poudriere I am experiencing a checksum mismatch error preventing the port to build. Below is the excerpt of the error from the build log: => Attempting to fetch https://gitlab.collabora.com/farstream/farstream/commit/11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch fetch: https://gitlab.collabora.com/farstream/farstream/commit/11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch: size unknown fetch: https://gitlab.collabora.com/farstream/farstream/commit/11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch: size of remote file is not known 11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch 2164 B 57 MBps 00s ===> Fetching all distfiles required by farstream-0.2.8_1 for building ===> Fetching all distfiles required by farstream-0.2.8_1 for building => SHA256 Checksum OK for farstream-0.2.8.tar.gz. => SHA256 Checksum mismatch for 11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch. ===> Giving up on fetching files: 11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch Make sure the Makefile and distinfo file (/usr/ports/net-im/farstream/distinfo) are up to date. If you are absolutely sure you want to override this check, type "make NO_CHECKSUM=yes [other args]". *** Error code 1 Stop. make[1]: stopped in /usr/ports/net-im/farstream *** Error code 1 Stop. make: stopped in /usr/ports/net-im/farstream =>> Cleaning up wrkdir ===> Cleaning for farstream-0.2.8_1 build of net-im/farstream | farstream-0.2.8_1 ended at Sat Sep 28 13:18:43 EDT 2019 build time: 00:00:07 !!! build failure encountered !!!
The patch file includes git version number at the bottom, so it is likely that the checksum will change every time the server is upgraded. I think we should just add a copy of the patch file to the port under its files directory.
A commit references this bug: Author: jbeich Date: Sat Sep 28 17:47:45 UTC 2019 New revision: 513145 URL: https://svnweb.freebsd.org/changeset/ports/513145 Log: net-im/farstream: regen patches (gitlub bug) --- 11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch.orig +++ 11dde55cbaf5179e8e1885cf1483e538a8d5a4a9.patch @@ -52,5 +52,5 @@ index e8684fd5..99ea03a0 100644 } -- -2.21.0 +2.22.0 PR: 240906 Reported by: Robert Cina Changes: head/net-im/farstream/distinfo
(In reply to Ting-Wei Lan from comment #1) Or report to GitLab developers. GitHub doesn't have such an issue. Copying patches has downsides: easy to introduce typos and often obfuscates origin.
(In reply to Jan Beich from comment #3) The behavior of GitLab here is the same as 'git format-patch', and 2.22.0 looks like a git version number. While the behavior of GitHub is better for this use case, it is probably not considered as bug if GitLab doesn't behave in the same way.
*** This bug has been marked as a duplicate of bug 242657 ***
242657 has been fixed as of r521277