From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bzip2: change upstream site
Date: Sun, 12 Aug 2018 11:33:45 +0200 [thread overview]
Message-ID: <20180812093345.GE2402@scaer> (raw)
In-Reply-To: <7f5f3c1bfdc21cad97c41dfba00c53f935ef6a73.1533875056.git.baruch@tkos.co.il>
Baruch, All,
On 2018-08-10 07:24 +0300, Baruch Siach spake thusly:
> The bzip.org website is down. Use the Buildroot backup download site.
> Change the website link to a gitlab repo that mirrors the content of the
> tarball.
>
> https://lwn.net/Articles/762264/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/bzip2/Config.in | 2 +-
> package/bzip2/bzip2.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/bzip2/Config.in b/package/bzip2/Config.in
> index dbc82496df7e..89e4d5de9a03 100644
> --- a/package/bzip2/Config.in
> +++ b/package/bzip2/Config.in
> @@ -6,4 +6,4 @@ config BR2_PACKAGE_BZIP2
> available techniques, while being around twice as fast at
> compression and six times faster at decompression.
>
> - http://www.bzip.org
> + https://gitlab.com/bzip/bzip2
Not sure this is the best upstream location. The LWN thread also has
this comment https://lwn.net/Articles/762340/ which points to this
webpage https://sourceware.org/bzip2 which has a canonical locations
pointing to https://www.sourceware.org/bzip2/
So, I am not sure which is better: an out-dated (but soon to be revived)
webpage, or a git tree made by a random guy on a random forge (there are
also github trees as well, and no doubt we can also find more random git
trees elesewhere).
Regards,
Yann E. MORIN.
> diff --git a/package/bzip2/bzip2.mk b/package/bzip2/bzip2.mk
> index e43533072b2d..a3af32299370 100644
> --- a/package/bzip2/bzip2.mk
> +++ b/package/bzip2/bzip2.mk
> @@ -5,7 +5,7 @@
> ################################################################################
>
> BZIP2_VERSION = 1.0.6
> -BZIP2_SITE = http://www.bzip.org/$(BZIP2_VERSION)
> +BZIP2_SITE = http://sources.buildroot.net
> BZIP2_INSTALL_STAGING = YES
> BZIP2_LICENSE = bzip2 license
> BZIP2_LICENSE_FILES = LICENSE
> --
> 2.18.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-08-12 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 4:24 [Buildroot] [PATCH] bzip2: change upstream site Baruch Siach
2018-08-12 9:33 ` Yann E. MORIN [this message]
2018-08-13 4:05 ` Baruch Siach
2018-08-13 15:50 ` Yann E. MORIN
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=20180812093345.GE2402@scaer \
--to=yann.morin.1998@free.fr \
--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.