From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Cc: bruno.thomsen@gmail.com
Subject: [ptxdist] [PATCH 1/6] atop: update URL
Date: Sat, 10 May 2025 23:06:23 +0200 [thread overview]
Message-ID: <20250510210628.49297-1-bruno.thomsen@gmail.com> (raw)
Current download URL returns 301 Moved Permanently.
Download log:
GNU Wget2 2.2.0 - multithreaded metalink/file/website downloader
[0] Downloading 'http://www.atoptool.nl/download/atop-2.10.0.tar.gz' ...
HTTP response 301 Moved Permanently [http://www.atoptool.nl/download/atop-2.10.0.tar.gz]
Adding URL: https://www.atoptool.nl/download/atop-2.10.0.tar.gz
[0] Downloading 'https://www.atoptool.nl/download/atop-2.10.0.tar.gz' ...
Saving '/home/bruno/ptxdist/src/atop-2.10.0.tar.gz.SBb3UIXT7U'
HTTP response 200 [https://www.atoptool.nl/download/atop-2.10.0.tar.gz]
Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
---
rules/atop.make | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rules/atop.make b/rules/atop.make
index 193ced1fc..8933700a4 100644
--- a/rules/atop.make
+++ b/rules/atop.make
@@ -18,7 +18,7 @@ PACKAGES-$(PTXCONF_ATOP) += atop
ATOP_VERSION := 2.10.0
ATOP_MD5 := 6d14559b59e25d15dbcfa978ed0ec50e
ATOP := atop-$(ATOP_VERSION)
-ATOP_URL := http://www.atoptool.nl/download/$(ATOP).tar.gz
+ATOP_URL := https://www.atoptool.nl/download/$(ATOP).tar.gz
ATOP_SOURCE := $(SRCDIR)/$(ATOP).tar.gz
ATOP_DIR := $(BUILDDIR)/$(ATOP)
ATOP_LICENSE := GPL-2.0-or-later
base-commit: dabd1471febfa4bc3a072b63061ad6deae012c72
--
2.49.0
next reply other threads:[~2025-05-10 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 21:06 Bruno Thomsen [this message]
2025-05-10 21:06 ` [ptxdist] [PATCH 2/6] blktrace: " Bruno Thomsen
2025-05-10 21:06 ` [ptxdist] [PATCH 3/6] cppunit: " Bruno Thomsen
2025-05-10 21:06 ` [ptxdist] [PATCH 4/6] iptables: " Bruno Thomsen
2025-05-10 21:06 ` [ptxdist] [PATCH 5/6] libmnl: " Bruno Thomsen
2025-05-10 21:06 ` [ptxdist] [PATCH 6/6] nftables: " Bruno Thomsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250510210628.49297-1-bruno.thomsen@gmail.com \
--to=bruno.thomsen@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox