From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-06-27
Date: Mon, 28 Jun 2021 14:15:14 +0200 [thread overview]
Message-ID: <20210628141514.67c4957b@windsurf> (raw)
In-Reply-To: <CAHp75VfAoLq1HEDdh+3ZNhrF-+upsQN1cPu8z3+4jMG6caEQ=Q@mail.gmail.com>
Hello Andy,
On Mon, 28 Jun 2021 12:11:03 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > name | found by | link to release-monitoring.org | version | upstream
> > -------------------------------+----------+----------------------------------------------+--------------+--------------
> > fb-test-app | DISTRO | https://release-monitoring.org/project/206162 | rosetta-1... | 1.0.0
>
> Anything I should do?
Yes:
(1) Change the release-monitoring.org entry so that it drops the
"rosetta-" prefix from the version numbers, and ask the
release-monitoring.org maintainers to refresh the fb-test-app
entry.
(2) Change the Buildroot fb-test-app package to not have "rosetta-" in
the <pkg>_VERSION variable, but only in the <pkg>_SITE variable. You
will find lots of other github-fetched packages in this situation,
for example:
AZMQ_VERSION = 1.0.2
AZMQ_SITE = $(call github,zeromq,azmq,v$(AZMQ_VERSION))
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2021-06-28 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60d962ee.1c69fb81.dd5ce.3e2dSMTPIN_ADDED_MISSING@mx.google.com>
[not found] ` <CAHp75VfAoLq1HEDdh+3ZNhrF-+upsQN1cPu8z3+4jMG6caEQ=Q@mail.gmail.com>
2021-06-28 12:15 ` Thomas Petazzoni [this message]
[not found] ` <CAHp75VfSqadj1w0qPAnzBFy1sq3ygAJTbDb69WxnEVz+qnMTRw@mail.gmail.com>
2021-06-28 13:39 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-06-27 Thomas Petazzoni
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=20210628141514.67c4957b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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