Bitbake repo using the same tag name as branch

Bitbake repo using the same tag name as branch

[Martin Jansa]

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

Is there some reason why bitbake started to use tag name identical as
branch name from 2.0?

It happens only with 2.0 and 2.2, because previous 1.52 branch had first
release named 1.52.0 not 1.52:
commit c78ebac71ec976fdf27ea24767057882870f5c60 (tag: yocto-3.4, tag:
2021-10-honister, tag: 1.52.0)

bitbake $ git show 1.52.0
tag 1.52.0
Tagger: Vineela Tummalapalli <vineela.tummalapalli@intel.com>
Date:   Mon Oct 25 15:16:54 2021 -0700

Tagging for 1.52.0 (yocto-3.4)

This new scheme has small disadvantage:

bitbake $ git push github 2.0
error: src refspec 2.0 matches more than one
error: failed to push some refs to 'github.com:shr-distribution/bitbake.git'

I can work around it by using refs/heads/2.0 and refs/tags/2.0 to
distinguish between them, but that's still a bit unusual and unfortunate.

Adding Chee Yang Lee who authored these 2 tags (see another warning there):

bitbake $ git show 2.0
warning: refname '2.0' is ambiguous.
tag 2.0
Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
Date:   Mon Apr 25 22:27:04 2022 -0700

bitbake $ git show 2.2
warning: refname '2.2' is ambiguous.
tag 2.2
Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
Date:   Sun Oct 23 20:33:14 2022 -0700

[-- Attachment #2: Type: text/html, Size: 1673 bytes --]

Re: [bitbake-devel] Bitbake repo using the same tag name as branch

[Richard Purdie]

On Fri, 2023-02-24 at 12:09 +0100, Martin Jansa wrote:
> Is there some reason why bitbake started to use tag name identical as
> branch name from 2.0?
> 
> It happens only with 2.0 and 2.2, because previous 1.52 branch had
> first release named 1.52.0 not 1.52:
> commit c78ebac71ec976fdf27ea24767057882870f5c60 (tag: yocto-3.4, tag:
> 2021-10-honister, tag: 1.52.0)
> 
> bitbake $ git show 1.52.0
> tag 1.52.0
> Tagger: Vineela Tummalapalli <vineela.tummalapalli@intel.com>
> Date:   Mon Oct 25 15:16:54 2021 -0700
> 
> Tagging for 1.52.0 (yocto-3.4)
> 
> This new scheme has small disadvantage:
> 
> bitbake $ git push github 2.0
> error: src refspec 2.0 matches more than one
> error: failed to push some refs to 'github.com:shr-
> distribution/bitbake.git'
> 
> I can work around it by using refs/heads/2.0 and refs/tags/2.0 to
> distinguish between them, but that's still a bit unusual and
> unfortunate.
> 
> Adding Chee Yang Lee who authored these 2 tags (see another warning
> there):
> 
> bitbake $ git show 2.0
> warning: refname '2.0' is ambiguous.
> tag 2.0
> Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
> Date:   Mon Apr 25 22:27:04 2022 -0700
> 
> bitbake $ git show 2.2
> warning: refname '2.2' is ambiguous.
> tag 2.2
> Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
> Date:   Sun Oct 23 20:33:14 2022 -0700

We should probably drop the 2.0 and 2.2 tags and put 2.0.0 and 2.2.0
tags in place instead.

Cheers,

Richard

Re: [bitbake-devel] Bitbake repo using the same tag name as branch

[Martin Jansa]

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

Michael: can you please recreate/rename the tags as suggested by RP?

On Fri, Feb 24, 2023 at 2:41 PM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Fri, 2023-02-24 at 12:09 +0100, Martin Jansa wrote:
> > Is there some reason why bitbake started to use tag name identical as
> > branch name from 2.0?
> >
> > It happens only with 2.0 and 2.2, because previous 1.52 branch had
> > first release named 1.52.0 not 1.52:
> > commit c78ebac71ec976fdf27ea24767057882870f5c60 (tag: yocto-3.4, tag:
> > 2021-10-honister, tag: 1.52.0)
> >
> > bitbake $ git show 1.52.0
> > tag 1.52.0
> > Tagger: Vineela Tummalapalli <vineela.tummalapalli@intel.com>
> > Date:   Mon Oct 25 15:16:54 2021 -0700
> >
> > Tagging for 1.52.0 (yocto-3.4)
> >
> > This new scheme has small disadvantage:
> >
> > bitbake $ git push github 2.0
> > error: src refspec 2.0 matches more than one
> > error: failed to push some refs to 'github.com:shr-
> > distribution/bitbake.git'
> >
> > I can work around it by using refs/heads/2.0 and refs/tags/2.0 to
> > distinguish between them, but that's still a bit unusual and
> > unfortunate.
> >
> > Adding Chee Yang Lee who authored these 2 tags (see another warning
> > there):
> >
> > bitbake $ git show 2.0
> > warning: refname '2.0' is ambiguous.
> > tag 2.0
> > Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
> > Date:   Mon Apr 25 22:27:04 2022 -0700
> >
> > bitbake $ git show 2.2
> > warning: refname '2.2' is ambiguous.
> > tag 2.2
> > Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
> > Date:   Sun Oct 23 20:33:14 2022 -0700
>
> We should probably drop the 2.0 and 2.2 tags and put 2.0.0 and 2.2.0
> tags in place instead.
>
> Cheers,
>
> Richard
>
>
>

[-- Attachment #2: Type: text/html, Size: 2509 bytes --]

Re: [bitbake-devel] Bitbake repo using the same tag name as branch

[Tim Orling]

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

On Fri, Feb 24, 2023 at 5:41 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Fri, 2023-02-24 at 12:09 +0100, Martin Jansa wrote:
> > Is there some reason why bitbake started to use tag name identical as
> > branch name from 2.0?
> >
> > It happens only with 2.0 and 2.2, because previous 1.52 branch had
> > first release named 1.52.0 not 1.52:
> > commit c78ebac71ec976fdf27ea24767057882870f5c60 (tag: yocto-3.4, tag:
> > 2021-10-honister, tag: 1.52.0)
> >
> > bitbake $ git show 1.52.0
> > tag 1.52.0
> > Tagger: Vineela Tummalapalli <vineela.tummalapalli@intel.com>
> > Date:   Mon Oct 25 15:16:54 2021 -0700
> >
> > Tagging for 1.52.0 (yocto-3.4)
> >
> > This new scheme has small disadvantage:
> >
> > bitbake $ git push github 2.0
> > error: src refspec 2.0 matches more than one
> > error: failed to push some refs to 'github.com:shr-
> > distribution/bitbake.git'
> >
> > I can work around it by using refs/heads/2.0 and refs/tags/2.0 to
> > distinguish between them, but that's still a bit unusual and
> > unfortunate.
> >
> > Adding Chee Yang Lee who authored these 2 tags (see another warning
> > there):
> >
> > bitbake $ git show 2.0
> > warning: refname '2.0' is ambiguous.
> > tag 2.0
> > Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
> > Date:   Mon Apr 25 22:27:04 2022 -0700
> >
> > bitbake $ git show 2.2
> > warning: refname '2.2' is ambiguous.
> > tag 2.2
> > Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
> > Date:   Sun Oct 23 20:33:14 2022 -0700
>
> We should probably drop the 2.0 and 2.2 tags and put 2.0.0 and 2.2.0
> tags in place instead.
>

I noticed this as well and this is solution I was hoping for.


> Cheers,
>
> Richard
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#14486):
> https://lists.openembedded.org/g/bitbake-devel/message/14486
> Mute This Topic: https://lists.openembedded.org/mt/97203651/924729
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/bitbake-devel/leave/10722602/924729/2064237243/xyzzy
> [ticotimo@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 3630 bytes --]

Re: [bitbake-devel] Bitbake repo using the same tag name as branch

[Michael Halstead]

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

I've renamed these tags and kept everything else the same:

2.0 -> 2.0.0
2.2 -> 2.2.0

I left these much older tags alone:

1.0
1.1
1.2

On Fri, Mar 10, 2023 at 7:55 PM Tim Orling <ticotimo@gmail.com> wrote:

>
>
> On Fri, Feb 24, 2023 at 5:41 AM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
>> On Fri, 2023-02-24 at 12:09 +0100, Martin Jansa wrote:
>> > Is there some reason why bitbake started to use tag name identical as
>> > branch name from 2.0?
>> >
>> > It happens only with 2.0 and 2.2, because previous 1.52 branch had
>> > first release named 1.52.0 not 1.52:
>> > commit c78ebac71ec976fdf27ea24767057882870f5c60 (tag: yocto-3.4, tag:
>> > 2021-10-honister, tag: 1.52.0)
>> >
>> > bitbake $ git show 1.52.0
>> > tag 1.52.0
>> > Tagger: Vineela Tummalapalli <vineela.tummalapalli@intel.com>
>> > Date:   Mon Oct 25 15:16:54 2021 -0700
>> >
>> > Tagging for 1.52.0 (yocto-3.4)
>> >
>> > This new scheme has small disadvantage:
>> >
>> > bitbake $ git push github 2.0
>> > error: src refspec 2.0 matches more than one
>> > error: failed to push some refs to 'github.com:shr-
>> > distribution/bitbake.git'
>> >
>> > I can work around it by using refs/heads/2.0 and refs/tags/2.0 to
>> > distinguish between them, but that's still a bit unusual and
>> > unfortunate.
>> >
>> > Adding Chee Yang Lee who authored these 2 tags (see another warning
>> > there):
>> >
>> > bitbake $ git show 2.0
>> > warning: refname '2.0' is ambiguous.
>> > tag 2.0
>> > Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
>> > Date:   Mon Apr 25 22:27:04 2022 -0700
>> >
>> > bitbake $ git show 2.2
>> > warning: refname '2.2' is ambiguous.
>> > tag 2.2
>> > Tagger: Chee Yang Lee <chee.yang.lee@intel.com>
>> > Date:   Sun Oct 23 20:33:14 2022 -0700
>>
>> We should probably drop the 2.0 and 2.2 tags and put 2.0.0 and 2.2.0
>> tags in place instead.
>>
>
> I noticed this as well and this is solution I was hoping for.
>
>
>> Cheers,
>>
>> Richard
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#14486):
>> https://lists.openembedded.org/g/bitbake-devel/message/14486
>> Mute This Topic: https://lists.openembedded.org/mt/97203651/924729
>> Group Owner: bitbake-devel+owner@lists.openembedded.org
>> Unsubscribe:
>> https://lists.openembedded.org/g/bitbake-devel/leave/10722602/924729/2064237243/xyzzy
>> [ticotimo@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

[-- Attachment #2: Type: text/html, Size: 4521 bytes --]