From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] swupdate: bump to version 2017.11
Date: Sun, 14 Jan 2018 18:53:48 +0100 [thread overview]
Message-ID: <1515952428.8426.2.camel@embedded.rocks> (raw)
In-Reply-To: <20180113222803.GI3226@scaer>
Yann,
On Sat, 2018-01-13 at 23:28 +0100, Yann E. MORIN wrote:
> J?rg, All,
>
> On 2018-01-10 23:28 +0100, J?rg Krause spake thusly:
> [--SNIP--]
> > diff --git a/package/swupdate/swupdate.mk b/package/swupdate/swupdate.mk
> > index fbb092da05..d1afbc4882 100644
> > --- a/package/swupdate/swupdate.mk
> > +++ b/package/swupdate/swupdate.mk
> > @@ -4,7 +4,7 @@
> > #
> > ################################################################################
> >
> > -SWUPDATE_VERSION = 2017.07
> > +SWUPDATE_VERSION = 2017.11
> > SWUPDATE_SITE = $(call github,sbabic,swupdate,$(SWUPDATE_VERSION))
> > SWUPDATE_LICENSE = GPL-2.0+, MIT, Public Domain
> > SWUPDATE_LICENSE_FILES = COPYING
> > @@ -39,8 +39,13 @@ else
> > SWUPDATE_MAKE_ENV += HAVE_LIBCURL=n
> > endif
> >
> > -ifeq ($(BR2_PACKAGE_LUA_5_2)$(BR2_PACKAGE_LUA_5_3),y)
> > -SWUPDATE_DEPENDENCIES += lua host-pkgconf
> > +
>
> This is adding an extra empty line, which would have been caught by
> running:
>
> $ ./utils/check-package package/swupdate/swupdate.mk
> package/swupdate/swupdate.mk:42: consecutive empty lines
> 140 lines processed
> 1 warnings generated
>
> Care to fix, please?
Thanks for reporting! Fix is on his way...
J?rg
prev parent reply other threads:[~2018-01-14 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 22:28 [Buildroot] [PATCH] swupdate: bump to version 2017.11 Jörg Krause
2018-01-12 21:16 ` Thomas Petazzoni
2018-01-13 22:28 ` Yann E. MORIN
2018-01-14 17:53 ` Jörg Krause [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=1515952428.8426.2.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/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