All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: seth.raymond@matrixspace.com
Cc: nicolas@saliencelabs.ai, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Failed to fetc qemu-project/u-boot
Date: Tue, 30 Sep 2025 10:10:07 -0600	[thread overview]
Message-ID: <20250930161007.GE6093@bill-the-cat> (raw)
In-Reply-To: <13254.1759242231298370764@lists.yoctoproject.org>

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

On Tue, Sep 30, 2025 at 07:23:51AM -0700, seth.raymond@matrixspace.com wrote:

> We've also started running into this issue. I did some searching and
> found that the tarballs are no longer available at any of the MIRRORS,
> which is why I think this recently started breaking. Does anyone know
> why those packages aren't available?

The QEMU project was having to do some workarounds for Gitlab's
automatic license checker failing out on U-Boot for lacking a top-level
COPYING file. We (U-Boot) have accepted adding a symlink from
Licenses/gpl-2.0.txt to COPYING so that every project using Gitlab with
the open source license doesn't need to get a human involved to correct
their automatic checker failing projects.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2025-09-30 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 10:21 Failed to fetc qemu-project/u-boot nicolas
2025-09-29 10:29 ` [yocto] " Alexander Kanavin
2025-09-29 10:35   ` nicolas
2025-09-29 10:40     ` Alexander Kanavin
2025-09-29 10:55       ` nicolas
2025-09-29 11:59         ` Gyorgy Sarvari
2025-09-30  6:36           ` nicolas
2025-09-30 14:23             ` seth.raymond
2025-09-30 16:10               ` Tom Rini [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=20250930161007.GE6093@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=nicolas@saliencelabs.ai \
    --cc=seth.raymond@matrixspace.com \
    --cc=yocto@lists.yoctoproject.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.