Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Edmundo Ferreira <fc.edmundo@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
	Thijs Vermeir <thijsvermeir@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 31/35] package/x265: fixes SITE since upstream repo was moved
Date: Fri, 23 Jul 2021 08:45:34 +0200	[thread overview]
Message-ID: <20210723084534.5a480291@windsurf> (raw)
In-Reply-To: <CAFv936FFHCcDM3LWC=A+Dd8pv4LSEbJuEHiDLZ2R9NVwf4xOJQ@mail.gmail.com>

Hello Edmundo,

On Thu, 22 Jul 2021 23:52:05 +0200
Edmundo Ferreira <fc.edmundo@gmail.com> wrote:

> Sure I'll check for a version bump on the new URL.
> 
> Sorry for that. I didn't take into consideration the caching of the
> packages in sources.buildroot.com.
> 
> As for the hash being wrong that is strange since I have that patch and our
> gitlab pipelines are fine. Maybe I'm being victim of our own package cache.

Probably not, check carefully your logs: just like me, you're probably
falling back to sources.buildroot.net, because the hash in
package/x265/x265.hash doesn't watch what you are downloading from the
new location.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2021-07-23  6:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 20:24 [Buildroot] [PATCH 31/35] package/x265: fixes SITE since upstream repo was moved Edmundo Ferreira
2021-07-22 21:07 ` Thomas Petazzoni
2021-07-22 21:52   ` Edmundo Ferreira
2021-07-23  6:45     ` Thomas Petazzoni [this message]

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=20210723084534.5a480291@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=fc.edmundo@gmail.com \
    --cc=thijsvermeir@gmail.com \
    /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