mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libcap-ng: Add another fetch option.
Date: Mon, 28 Aug 2023 17:35:51 +0200	[thread overview]
Message-ID: <ZOy+12Ym8/RUEadz@pengutronix.de> (raw)
In-Reply-To: <20230811173859.1426260-1-christian.melki@t2data.com>

On Fri, Aug 11, 2023 at 07:38:59PM +0200, Christian Melki wrote:
> people.redhat.com is down again.
> Not a lot depend on it but libcap-ng is common in a lot of builds.
> The github variant doesn't come in a "make dist" release.
> A debian mirror of the source might do.

The problem with the Debian pool is, that it only contains the archives for
the releases currently available in a Debian release. So the archive may
disappear. And as a secondary URL, 'ptxdist urlcheck' will not fail while
the primary URL is available.

The server seems to be back now anyway. So I'd like to stick to just the
original URL for now. I'll reconsider if this happens more often, but it
doesn't look like it so far from what I can tell from my regular checks.

Michael

> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
>  rules/libcap-ng.make | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/rules/libcap-ng.make b/rules/libcap-ng.make
> index 530af64ef..64786e872 100644
> --- a/rules/libcap-ng.make
> +++ b/rules/libcap-ng.make
> @@ -18,7 +18,9 @@ LIBCAP_NG_VERSION	:= 0.8.3
>  LIBCAP_NG_MD5		:= cdfc750af32f681293e43c5c1bd427c8
>  LIBCAP_NG		:= libcap-ng-$(LIBCAP_NG_VERSION)
>  LIBCAP_NG_SUFFIX	:= tar.gz
> -LIBCAP_NG_URL		:= http://people.redhat.com/sgrubb/libcap-ng/$(LIBCAP_NG).$(LIBCAP_NG_SUFFIX)
> +LIBCAP_NG_URL		:= \
> +	https://people.redhat.com/sgrubb/libcap-ng/$(LIBCAP_NG).$(LIBCAP_NG_SUFFIX) \
> +	https://deb.debian.org/debian/pool/main/libc/libcap-ng/libcap-ng_$(LIBCAP_NG_VERSION).orig.$(LIBCAP_NG_SUFFIX)
>  LIBCAP_NG_SOURCE	:= $(SRCDIR)/$(LIBCAP_NG).$(LIBCAP_NG_SUFFIX)
>  LIBCAP_NG_DIR		:= $(BUILDDIR)/$(LIBCAP_NG)
>  LIBCAP_NG_LICENSE	:= LGPL-2.1-or-later AND GPL-2.0-or-later
> -- 
> 2.34.1
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2023-08-28 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 17:38 Christian Melki
2023-08-28 15:35 ` Michael Olbrich [this message]
2023-08-31 10:31   ` Roland Hieber

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=ZOy+12Ym8/RUEadz@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.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