All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Gaël PORTAY" <gael.portay@rtone.fr>
Cc: "Alvaro G . M" <alvaro.gamez@hazent.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libxmlrpc: bump version to 1.60.00 (code/advanced@r3162)
Date: Sun, 22 Oct 2023 13:59:45 +0200	[thread overview]
Message-ID: <20231022115945.GH2607@scaer> (raw)
In-Reply-To: <20231020090949.2839604-1-gael.portay@rtone.fr>

Gaël, All,

On 2023-10-20 11:09 +0200, Gaël PORTAY spake thusly:
> Signed-off-by: Gaël PORTAY <gael.portay@rtone.fr>
> ---
>  package/libxmlrpc/libxmlrpc.hash | 2 +-
>  package/libxmlrpc/libxmlrpc.mk   | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/libxmlrpc/libxmlrpc.hash b/package/libxmlrpc/libxmlrpc.hash
> index 665ee31836..cad4d0e379 100644
> --- a/package/libxmlrpc/libxmlrpc.hash
> +++ b/package/libxmlrpc/libxmlrpc.hash
> @@ -1,3 +1,3 @@
>  # Locally computed
> -sha256  626e36295f43b320082bc7bdd961b46f39fbe2719535b5a417975a8e50c8f7f3  libxmlrpc-r3119-br3.tar.gz
> +sha256  ac5f5e83c6feaa5276fd0610b055c6e5d350089704b60c17d5af30afb08506c5  libxmlrpc-r3162-br3.tar.gz
>  sha256  db7a6d3f187b218c3534010a83424c6bcdef88e6a0b6b1aa3a8762238bd642e6  doc/COPYING
> diff --git a/package/libxmlrpc/libxmlrpc.mk b/package/libxmlrpc/libxmlrpc.mk
> index c1b0eae8ee..2d3ee66050 100644
> --- a/package/libxmlrpc/libxmlrpc.mk
> +++ b/package/libxmlrpc/libxmlrpc.mk
> @@ -4,8 +4,8 @@
>  #
>  ################################################################################
>  
> -# 1.58.02 (code/advanced@r3119)
> -LIBXMLRPC_VERSION = r3119
> +# 1.60.00 (code/advanced@r3162)
> +LIBXMLRPC_VERSION = r3162
>  LIBXMLRPC_SITE = https://svn.code.sf.net/p/xmlrpc-c/code/advanced

Why don't we use the "tag" rather than a revision in the dev branch:

    http://svn.code.sf.net/p/xmlrpc-c/code/release_number/01.60.00

OK, it looks like not all versions get a tag, and 01.06.01 is a;ready
released without a tag...

Regards,
Yann E. MORIN.

>  LIBXMLRPC_SITE_METHOD = svn
>  LIBXMLRPC_LICENSE = BSD-3-Clause (xml-rpc main code and abyss web server), BSD like (lib/expat), Python 1.5.2 license (parts of xmlrpc_base64.c)
> -- 
> 2.42.0
> 
> _______________________________________________
> 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-22 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  9:09 [Buildroot] [PATCH 1/1] package/libxmlrpc: bump version to 1.60.00 (code/advanced@r3162) Gaël PORTAY
2023-10-22 11:59 ` Yann E. MORIN [this message]
2023-10-22 12:06 ` Yann E. MORIN

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=20231022115945.GH2607@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=alvaro.gamez@hazent.com \
    --cc=buildroot@buildroot.org \
    --cc=gael.portay@rtone.fr \
    /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.