From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: yegorslists@googlemail.com
Cc: "Wojciech M . Zabolotny" <wzab01@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/avrdude: bump to version 6.4
Date: Sun, 9 Jan 2022 21:39:16 +0100 [thread overview]
Message-ID: <20220109203916.GG1477939@scaer> (raw)
In-Reply-To: <20220109140421.27820-1-yegorslists@googlemail.com>
Yegor, All,
On 2022-01-09 15:04 +0100, yegorslists--- via buildroot spake thusly:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> The project moved to GitHub, hence change the download location.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/avrdude/avrdude.hash | 4 ++--
> package/avrdude/avrdude.mk | 11 +++++------
> 2 files changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/package/avrdude/avrdude.hash b/package/avrdude/avrdude.hash
> index ec43355451..1c7758afcd 100644
> --- a/package/avrdude/avrdude.hash
> +++ b/package/avrdude/avrdude.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> -sha256 2a09913450c6457c3fe8d43d5141de579d4e57d67e593e7399a4cd3768cc60f9 avrdude-r1450-br2.tar.gz
> -sha256 201babc7da198873304a77a30dbfc7ca449c9bba52df2dffa4cca0009dbdfcb2 avrdude/COPYING
> +sha256 bbe2cf09163b3561ea28e9d48c2a588838f7adcd7858e34ced9c886feacb5be6 avrdude-v6.4.tar.gz
> +sha256 201babc7da198873304a77a30dbfc7ca449c9bba52df2dffa4cca0009dbdfcb2 COPYING
> diff --git a/package/avrdude/avrdude.mk b/package/avrdude/avrdude.mk
> index ae623a7929..5bbbc4e8c2 100644
> --- a/package/avrdude/avrdude.mk
> +++ b/package/avrdude/avrdude.mk
> @@ -4,13 +4,12 @@
> #
> ################################################################################
>
> -AVRDUDE_VERSION = r1450
> -AVRDUDE_SITE_METHOD = svn
> -AVRDUDE_SITE = http://svn.savannah.nongnu.org/svn/avrdude/trunk
> +AVRDUDE_VERSION = v6.4
> +AVRDUDE_SITE = $(call github,avrdudes,avrdude,$(AVRDUDE_VERSION))
> AVRDUDE_LICENSE = GPL-2.0+
> -AVRDUDE_LICENSE_FILES = avrdude/COPYING
> -AVRDUDE_SUBDIR = avrdude
> -# Sources coming from svn, without generated configure and Makefile.in
> +AVRDUDE_LICENSE_FILES = COPYING
> +
> +# Sources coming from git, without generated configure and Makefile.in
> # files.
> AVRDUDE_AUTORECONF = YES
> AVRDUDE_CONF_OPTS = --enable-linuxgpio
> --
> 2.17.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
prev parent reply other threads:[~2022-01-09 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 14:04 [Buildroot] [PATCH] package/avrdude: bump to version 6.4 yegorslists--- via buildroot
2022-01-09 20:39 ` 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=20220109203916.GG1477939@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=wzab01@gmail.com \
--cc=yegorslists@googlemail.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