From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] package/unzip: fix URL of patches
Date: Mon, 18 Jan 2021 22:29:44 +0100 [thread overview]
Message-ID: <20210118222944.13ef7ead@windsurf.home> (raw)
In-Reply-To: <20210117175208.366428-2-fontaine.fabrice@gmail.com>
On Sun, 17 Jan 2021 18:52:05 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> https://sources.debian.org/data/main/u/unzip/6.0-25 is unreachable so
> replace it by
> https://sources.debian.org/data/main/u/unzip/6.0-26
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
The problem is that this patch is not really going to fix it for the
long term. Stuff on sources.debian.org come and goes, which is why we
use snapshot.debian.org whenever possible.
So we should probably use
http://snapshot.debian.org/archive/debian-debug/20210110T203547Z/pool/main/u/unzip/unzip_6.0-26.debian.tar.xz
which contains all the Debian patches, but at a stable URL.
Could you have a look at doing this ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-18 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 17:52 [Buildroot] [PATCH 1/5] package/unzip: make version compliant with release-monitoring Fabrice Fontaine
2021-01-17 17:52 ` [Buildroot] [PATCH 2/5] package/unzip: fix URL of patches Fabrice Fontaine
2021-01-18 21:29 ` Thomas Petazzoni [this message]
2021-01-17 17:52 ` [Buildroot] [PATCH 3/5] package/unzip: add two debian security patches Fabrice Fontaine
2021-01-17 17:52 ` [Buildroot] [PATCH 4/5] package/unzip: add UNZIP_IGNORE_CVES entries Fabrice Fontaine
2021-01-17 17:52 ` [Buildroot] [PATCH 5/5] package/unzip: set UNZIP_CPE_ID_VALID Fabrice Fontaine
2021-01-18 21:30 ` Thomas Petazzoni
2021-01-18 21:26 ` [Buildroot] [PATCH 1/5] package/unzip: make version compliant with release-monitoring Thomas Petazzoni
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=20210118222944.13ef7ead@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.