Use official tarball (this will also have the nice side-effect of making
MINICOM_VERSION compatible with release-monitoring.org)
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Reviewed-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
# Locally calculated
-sha256 18fa02dc32523834ed1e5dbc3d24ff3860e74fa3c6eb817f9bdf693dde3f7d4e minicom-v2.8-br1.tar.gz
+sha256 38cea30913a20349326ff3f1763ee1512b7b41601c24f065f365e18e9db0beba minicom-2.8.tar.bz2
sha256 cf80a758014eefbf068afffe3d462fc34ff4f528527524d8e100329c42094e15 COPYING
#
################################################################################
-MINICOM_VERSION = v2.8
-MINICOM_SITE = https://salsa.debian.org/minicom-team/minicom.git
-MINICOM_SITE_METHOD = git
+MINICOM_VERSION = 2.8
+MINICOM_SOURCE = minicom-$(MINICOM_VERSION).tar.bz2
+MINICOM_SITE = \
+ https://salsa.debian.org/minicom-team/minicom/-/archive/$(MINICOM_VERSION)
MINICOM_LICENSE = GPL-2.0+
MINICOM_LICENSE_FILES = COPYING
MINICOM_AUTORECONF = YES