From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Daniel Lang <dalang@gmx.at>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/check: fix compile issue
Date: Thu, 24 Aug 2023 21:44:07 +0200 [thread overview]
Message-ID: <20230824194407.GB3722679@scaer> (raw)
In-Reply-To: <20230807220645.546836bc@windsurf>
Thomas, Waldemar, All,
On 2023-08-07 22:06 +0200, Thomas Petazzoni via buildroot spake thusly:
> On Mon, 7 Aug 2023 17:32:33 +0200
> Waldemar Brodkorb <wbx@openadk.org> wrote:
> > Switch to the tagged version of check.
> > See here for details:
> > https://github.com/libcheck/check/issues/303
[--SNIP--]
> Until upstream publishes a new release with a complete tarball, switch
> to fetching the Github-generated tarball, which does contain the
> missing file.
[--SNIP--]
> > CHECK_VERSION = 0.15.2
> > -CHECK_SITE = https://github.com/libcheck/check/releases/download/$(CHECK_VERSION)
> > +CHECK_SOURCE = $(CHECK_VERSION).tar.gz
> > +CHECK_SITE = https://github.com/libcheck/check/archive/refs/tags
> Switched to using the github helper, exactly like Daniel Lang suggested.
This is incorrect, because the archive content changes, but the archive
filename does not; hence the copy we host on s.b.o. is invalid, and
since we've had check-0.15.2 since 2021-04-06, we've had a few releases
already that uses that version.
So we can't replace the one on s.b.o with the new one.
Instead, the only solution is to switch to using a git hash instead of
the tag.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-24 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 15:32 [Buildroot] [PATCH] package/check: fix compile issue Waldemar Brodkorb
2023-08-07 18:42 ` Daniel Lang
2023-08-07 20:06 ` Thomas Petazzoni via buildroot
2023-08-24 19:44 ` Yann E. MORIN [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=20230824194407.GB3722679@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=dalang@gmx.at \
--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