Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Luc Beaufils <luc.beaufils@savoirfairelinux.com>
Cc: Yunus Bas <Y.Bas@phytec.de>, buildroot <buildroot@buildroot.org>,
	Thomas Perrot <thomas.perrot@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 0/2] Support for i.MX Code Signing Tools
Date: Thu, 14 Aug 2025 09:54:13 +0200	[thread overview]
Message-ID: <20250814095413.45e41061@windsurf> (raw)
In-Reply-To: <1129278814.79180.1755157301522.JavaMail.zimbra@savoirfairelinux.com>

On Thu, 14 Aug 2025 03:41:41 -0400 (EDT)
Luc Beaufils <luc.beaufils@savoirfairelinux.com> wrote:

> The 3.4.0+dfsg version has been removed from the debian repository. 
> The series should bump to the 3.4.1+dfsg version.

The series is correctly using https://snapshot.debian.org/archive/,
where the tarballs never disappear and have a stable URL. That of
course doesn't mean a version bump would not be useful, but the current
series is correctly using tarballs that still exist.

Best regards,

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

  reply	other threads:[~2025-08-14  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <657a4a78e8df2a586faebb61d46ff3e8cfc7032d.camel@phytec.de>
2025-08-14  7:41 ` [Buildroot] [PATCH v2 0/2] Support for i.MX Code Signing Tools Luc Beaufils
2025-08-14  7:54   ` Thomas Petazzoni via buildroot [this message]
2025-08-14 11:04     ` Yunus Bas via buildroot
2025-03-07  9:59 Luc BEAUFILS

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=20250814095413.45e41061@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Y.Bas@phytec.de \
    --cc=luc.beaufils@savoirfairelinux.com \
    --cc=thomas.perrot@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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