From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 1/2] mesa: correct download location
Date: Wed, 19 Mar 2025 10:29:48 +0000 [thread overview]
Message-ID: <d5992c2c2013bf7ff5ce2d76b1b223f020764d03.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_9RmwiA4=PDE1BR-njjX0y0FrCto8H9DTSROJwUjpZCA@mail.gmail.com>
On Wed, 2025-03-19 at 11:28 +0100, Alexander Kanavin wrote:
> On Wed, 19 Mar 2025 at 11:20, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > > -SRC_URI =
> > > "https://mesa.freedesktop.org/archive/glu/glu-${PV}.tar.xz \
> > > +SRC_URI = "https://archive.mesa3d.org/glu/glu-${PV}.tar.xz \
> > > "
> >
> > Doesn't this have issues with the "older-versions" directory that
> > archives are moved off into?
>
> I suspect this is the same directory as the previous location, and
> the issue was already present there? I can't check that anymore: it's
> now 404.
I think we may need to wait for the dust to settle on the
freedesktop.org changes before we update urls...
Cheers,
Richard
next prev parent reply other threads:[~2025-03-19 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 10:09 [PATCH 1/2] mesa: correct download location Alexander Kanavin
2025-03-19 10:09 ` [PATCH 2/2] mesa-demos: update 8.5.0 -> 9.0.0 Alexander Kanavin
2025-03-19 10:20 ` [OE-core] [PATCH 1/2] mesa: correct download location Richard Purdie
2025-03-19 10:28 ` Alexander Kanavin
2025-03-19 10:29 ` Richard Purdie [this message]
2025-03-19 10:32 ` Alexander Kanavin
[not found] ` <182E2DB6117AAA9A.9767@lists.openembedded.org>
2025-03-19 14:04 ` Alexander Kanavin
2025-03-19 14:30 ` Richard Purdie
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=d5992c2c2013bf7ff5ce2d76b1b223f020764d03.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
/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.