[pkgsrc/trunk]: pkgsrc/ham/hamlib ham/hamlib: Recover from using a github dis...

[gdt <gdt%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/088e7a6e9c5d
branches:  trunk
changeset: 387922:088e7a6e9c5d
user:      gdt <gdt%pkgsrc.org@localhost>
date:      Thu Nov 10 12:59:13 2022 +0000

description:
ham/hamlib: Recover from using a github distfile

The distfile from github is currently broken, or has been attacked,
and our distinfo scheme caught that.  Or perhaps it was always not ok.
Switch to sourceforge which serves a file that has a sensible diff
from 4.3.1 and matches the distinfo I generated earlier.

No change to binary package, but PKGREVISION++ because of MASTER_SITES change.

diffstat:

 ham/hamlib/Makefile |  11 +++++++----
 1 files changed, 7 insertions(+), 4 deletions(-)

diffs (24 lines):

diff -r 2a46cf7821f3 -r 088e7a6e9c5d ham/hamlib/Makefile
--- a/ham/hamlib/Makefile       Thu Nov 10 12:24:38 2022 +0000
+++ b/ham/hamlib/Makefile       Thu Nov 10 12:59:13 2022 +0000
@@ -1,13 +1,16 @@
-# $NetBSD: Makefile,v 1.56 2022/11/01 17:28:14 gdt Exp $
+# $NetBSD: Makefile,v 1.57 2022/11/10 12:59:13 gdt Exp $
 #
 
 VERSION=       4.5
+PKGREVISION=   1
 DISTNAME=      hamlib-${VERSION}
 CATEGORIES=    ham
-# hamlib is both at github and sourceforge; code is more at github and
+# hamlib is both at github and sourceforge.  Upstream is not clear
+# about which is primary and which is secondary.  The github-fetchable
+# distfile appears broken (or attacked?) as of 2022-11-09.
 # mailinglists are at sourceforge.
-MASTER_SITES=  ${MASTER_SITE_GITHUB:=Hamlib/}
-#MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=hamlib/}
+MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=hamlib/}
+#MASTER_SITES= ${MASTER_SITE_GITHUB:=Hamlib/}
 
 MAINTAINER=    gdt%NetBSD.org@localhost
 HOMEPAGE=      https://hamlib.github.io/