Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libcodec2: bump version to 1.2.0
Date: Tue, 3 Oct 2023 22:46:54 +0200	[thread overview]
Message-ID: <20231003204654.GH2957@scaer> (raw)
In-Reply-To: <20231003124336.2837869-1-bernd@kuhls.net>

Bernd, All,

On 2023-10-03 14:43 +0200, Bernd Kuhls spake thusly:
> Release notes: https://github.com/drowe67/codec2/releases/tag/1.2.0
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
>  package/libcodec2/libcodec2.hash | 2 +-
>  package/libcodec2/libcodec2.mk   | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/libcodec2/libcodec2.hash b/package/libcodec2/libcodec2.hash
> index edaa275bbc..828efa3e4d 100644
> --- a/package/libcodec2/libcodec2.hash
> +++ b/package/libcodec2/libcodec2.hash
> @@ -1,3 +1,3 @@
>  # Locally computed
> -sha256  44015b071968d98ee326012c498db6a8308bed1a7a914ecb6d4d8e2a354a4611  libcodec2-1.1.1.tar.gz
> +sha256  cbccae52b2c2ecc5d2757e407da567eb681241ff8dadce39d779a7219dbcf449  libcodec2-1.2.0.tar.gz
>  sha256  9ebb6f82b7380a62ac74c5f0322c88e6744dedf2ebe1f54d6f088282b39844bf  COPYING
> diff --git a/package/libcodec2/libcodec2.mk b/package/libcodec2/libcodec2.mk
> index 295dd8983f..5fc190aefd 100644
> --- a/package/libcodec2/libcodec2.mk
> +++ b/package/libcodec2/libcodec2.mk
> @@ -4,8 +4,8 @@
>  #
>  ################################################################################
>  
> -LIBCODEC2_VERSION = 1.1.1
> -LIBCODEC2_SITE = $(call github,drowe67,codec2,v$(LIBCODEC2_VERSION))
> +LIBCODEC2_VERSION = 1.2.0
> +LIBCODEC2_SITE = $(call github,drowe67,codec2,$(LIBCODEC2_VERSION))

I was curious to see that they dopped the leading 'v' in front of tags,
so I had a look at the repository, and indeed the 1.2.0 tag has no
leading 'v'.

But surprisingly, *there is no other tag*! Even the v1.1.1 tag that we
were using so far is missing!

So I had a look, and stumbled on:
    https://github.com/drowe67/codec2/issues/5

Basically, the full history was rewritten for some reason, the old
repository has been moved to;
    https://github.com/drowe67/codec2-dev/

So, this is an important bit of information: we need to fix the existing
maintenance branches to refer to the old repository (or backport this
commit).

I have added a blurb about that in the commit log, and applied to
master.

Regards,
Yann E. MORIN.

>  LIBCODEC2_LICENSE = LGPL-2.1
>  LIBCODEC2_LICENSE_FILES = COPYING
>  LIBCODEC2_INSTALL_STAGING = YES
> -- 
> 2.39.2
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  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

  reply	other threads:[~2023-10-03 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 12:43 [Buildroot] [PATCH 1/1] package/libcodec2: bump version to 1.2.0 Bernd Kuhls
2023-10-03 20:46 ` Yann E. MORIN [this message]
2023-10-13 15:41   ` Peter Korsgaard

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=20231003204654.GH2957@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    /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