From: Pavel Zhukov <pavel@zhukoff.net>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] fetch2/tests: Add parameter to recipe_uri
Date: Wed, 18 Jan 2023 11:13:25 +0100 [thread overview]
Message-ID: <878ri02lpi.fsf@desktop.zhukoff.net> (raw)
In-Reply-To: <87cz7c2m2a.fsf@desktop.zhukoff.net>
Pavel Zhukov <pavel@zhukoff.net> writes:
> Quentin Schulz <quentin.schulz@theobroma-systems.com> writes:
>
>> Hi Pavel,
> Hi Quentin!
>>
>> On 1/18/23 08:28, Pavel Zhukov wrote:
>>> While the parameter is not required it allows testing of possible
>>
>> I was convinced it was required for a year already but no :)
>>
>> I see Richard added a warning in Bitbake when the branch parameter is
>> missing and nobranch is not set to 1,
>> c.f. https://git.openembedded.org/bitbake/commit/?id=86a9c26828479be55865bcce72bcc7e12b93caa7
> Right, I saw this warning in the past but not this time... Anyway at the
> scope of this patch branch parameter can be changed with any other
> (rebaseable,bareclone etc) parameter git fetcher accpes.
> branch one is just first that came into my mind
> :) .
Well. The warning is there but it's diplayed only if test failed:
Stdout:
URL: git://git.fake.repo/bitbake does not set any branch parameter. The future default branch used by tools and repositories is uncertain and we will therefore soon require this is set in all git urls.
So yes, we don't fail test if it's missed. And even more, test will fail
if it's specified and premirror is used in current bitbake
>>
>> Maybe it's time we make this a fail?
>>
>> Cheers,
>> Quentin
next prev parent reply other threads:[~2023-01-18 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 7:28 [PATCH] fetch2/tests: Add parameter to recipe_uri Pavel Zhukov
2023-01-18 9:58 ` [bitbake-devel] " Quentin Schulz
2023-01-18 10:02 ` Pavel Zhukov
2023-01-18 10:13 ` Pavel Zhukov [this message]
2023-01-18 10:17 ` Quentin Schulz
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=878ri02lpi.fsf@desktop.zhukoff.net \
--to=pavel@zhukoff.net \
--cc=bitbake-devel@lists.openembedded.org \
--cc=quentin.schulz@theobroma-systems.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 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.