All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] vim: update from 8.1.1518 to 8.2.0110
@ 2020-01-14 19:30 Oleg Polyakov
  2020-01-14 19:39 ` Alexander Kanavin
  0 siblings, 1 reply; 7+ messages in thread
From: Oleg Polyakov @ 2020-01-14 19:30 UTC (permalink / raw)
  To: openembedded-core

vim-tiny: update from 8.1.1518 to 8.2.0110
The date in the license was updated to 2020 and
a trailing space was removed from one line.

Signed-off-by: Oleg Polyakov <Oleg.Polyakov@windriver.com>
---
 .../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb}        | 0
 meta/recipes-support/vim/vim.inc                              | 4 ++--
 meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} | 0
 3 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} (100%)
 rename meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} (100%)

diff --git a/meta/recipes-support/vim/vim-tiny_8.1.1518.bb b/meta/recipes-support/vim/vim-tiny_8.2.0110.bb
similarity index 100%
rename from meta/recipes-support/vim/vim-tiny_8.1.1518.bb
rename to meta/recipes-support/vim/vim-tiny_8.2.0110.bb
diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 5a1bea6985..ec7ad443a4 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -5,14 +5,14 @@ DEPENDS = "ncurses gettext-native"
 # vimdiff doesn't like busybox diff
 RSUGGESTS_${PN} = "diffutils"
 LICENSE = "vim"
-LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=f1f82b42360005c70b8c19b0ef493f72"
+LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=909f1394892b7e0f9c2a95306c0c552b"
 
 SRC_URI = "git://github.com/vim/vim.git \
            file://disable_acl_header_check.patch \
            file://vim-add-knob-whether-elf.h-are-checked.patch \
            file://0001-src-Makefile-improve-reproducibility.patch \
 "
-SRCREV = "202d982b36d87cf91d992bd7e30d3223bdc72cd9"
+SRCREV = "e05a89ac6399a8c7d164c99fdab6841d999a9128"
 
 # Do not consider .z in x.y.z, as that is updated with every commit
 UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+\.\d+)\.0"
diff --git a/meta/recipes-support/vim/vim_8.1.1518.bb b/meta/recipes-support/vim/vim_8.2.0110.bb
similarity index 100%
rename from meta/recipes-support/vim/vim_8.1.1518.bb
rename to meta/recipes-support/vim/vim_8.2.0110.bb
-- 
2.23.0



^ permalink raw reply related	[flat|nested] 7+ messages in thread

* Re: [PATCH] vim: update from 8.1.1518 to 8.2.0110
  2020-01-14 19:30 [PATCH] vim: update from 8.1.1518 to 8.2.0110 Oleg Polyakov
@ 2020-01-14 19:39 ` Alexander Kanavin
  2020-01-14 20:09   ` Randy MacLeod
  0 siblings, 1 reply; 7+ messages in thread
From: Alexander Kanavin @ 2020-01-14 19:39 UTC (permalink / raw)
  To: Oleg Polyakov; +Cc: openembedded-core

Can you update to just 8.2 please? 0110 is an arbitrary commit as vimupstream adds a version tag for each of the commits.

Alex

> On 14 Jan 2020, at 20.30, Oleg Polyakov <Oleg.Polyakov@windriver.com> wrote:
> 
> vim-tiny: update from 8.1.1518 to 8.2.0110
> The date in the license was updated to 2020 and
> a trailing space was removed from one line.
> 
> Signed-off-by: Oleg Polyakov <Oleg.Polyakov@windriver.com>
> ---
> .../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb}        | 0
> meta/recipes-support/vim/vim.inc                              | 4 ++--
> meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} | 0
> 3 files changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-support/vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} (100%)
> rename meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} (100%)
> 
> diff --git a/meta/recipes-support/vim/vim-tiny_8.1.1518.bb b/meta/recipes-support/vim/vim-tiny_8.2.0110.bb
> similarity index 100%
> rename from meta/recipes-support/vim/vim-tiny_8.1.1518.bb
> rename to meta/recipes-support/vim/vim-tiny_8.2.0110.bb
> diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
> index 5a1bea6985..ec7ad443a4 100644
> --- a/meta/recipes-support/vim/vim.inc
> +++ b/meta/recipes-support/vim/vim.inc
> @@ -5,14 +5,14 @@ DEPENDS = "ncurses gettext-native"
> # vimdiff doesn't like busybox diff
> RSUGGESTS_${PN} = "diffutils"
> LICENSE = "vim"
> -LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=f1f82b42360005c70b8c19b0ef493f72"
> +LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=909f1394892b7e0f9c2a95306c0c552b"
> 
> SRC_URI = "git://github.com/vim/vim.git \
>            file://disable_acl_header_check.patch \
>            file://vim-add-knob-whether-elf.h-are-checked.patch \
>            file://0001-src-Makefile-improve-reproducibility.patch \
> "
> -SRCREV = "202d982b36d87cf91d992bd7e30d3223bdc72cd9"
> +SRCREV = "e05a89ac6399a8c7d164c99fdab6841d999a9128"
> 
> # Do not consider .z in x.y.z, as that is updated with every commit
> UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+\.\d+)\.0"
> diff --git a/meta/recipes-support/vim/vim_8.1.1518.bb b/meta/recipes-support/vim/vim_8.2.0110.bb
> similarity index 100%
> rename from meta/recipes-support/vim/vim_8.1.1518.bb
> rename to meta/recipes-support/vim/vim_8.2.0110.bb
> -- 
> 2.23.0
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] vim: update from 8.1.1518 to 8.2.0110
  2020-01-14 19:39 ` Alexander Kanavin
@ 2020-01-14 20:09   ` Randy MacLeod
  2020-01-14 22:18     ` Alexander Kanavin
  0 siblings, 1 reply; 7+ messages in thread
From: Randy MacLeod @ 2020-01-14 20:09 UTC (permalink / raw)
  To: Alexander Kanavin, Oleg Polyakov; +Cc: openembedded-core

On 1/14/20 2:39 PM, Alexander Kanavin wrote:
> Can you update to just 8.2 please? 0110 is an arbitrary commit as vimupstream adds a version tag for each of the commits.

Hi Alex,

Oleg is getting started using Yocto so I'll reply on his behalf since
I asked him to update vim as his first commit.

I'm not sure what you mean by 8.2. Are you talking about calling the recipe:
    vim_8.2.bb
instead of vim_8.2.0110.bb?

Vim tags on a daily or more frequent basis. Are you saying that we 
should keep the
same SRCREV for 8.2.0110 but use a different name?

I looked at:
    git log v8.2.0000..v8.2.0118
and all the commits seem to fix bugs so I prefer to take this tested 
v8.2.0110
update and update vim every month or two so that we get the latest fixes.

../Randy


>
> Alex
>
>> On 14 Jan 2020, at 20.30, Oleg Polyakov <Oleg.Polyakov@windriver.com> wrote:
>>
>> vim-tiny: update from 8.1.1518 to 8.2.0110
>> The date in the license was updated to 2020 and
>> a trailing space was removed from one line.
>>
>> Signed-off-by: Oleg Polyakov <Oleg.Polyakov@windriver.com>
>> ---
>> .../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb}        | 0
>> meta/recipes-support/vim/vim.inc                              | 4 ++--
>> meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} | 0
>> 3 files changed, 2 insertions(+), 2 deletions(-)
>> rename meta/recipes-support/vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0110.bb} (100%)
>> rename meta/recipes-support/vim/{vim_8.1.1518.bb => vim_8.2.0110.bb} (100%)
>>
>> diff --git a/meta/recipes-support/vim/vim-tiny_8.1.1518.bb b/meta/recipes-support/vim/vim-tiny_8.2.0110.bb
>> similarity index 100%
>> rename from meta/recipes-support/vim/vim-tiny_8.1.1518.bb
>> rename to meta/recipes-support/vim/vim-tiny_8.2.0110.bb
>> diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
>> index 5a1bea6985..ec7ad443a4 100644
>> --- a/meta/recipes-support/vim/vim.inc
>> +++ b/meta/recipes-support/vim/vim.inc
>> @@ -5,14 +5,14 @@ DEPENDS = "ncurses gettext-native"
>> # vimdiff doesn't like busybox diff
>> RSUGGESTS_${PN} = "diffutils"
>> LICENSE = "vim"
>> -LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=f1f82b42360005c70b8c19b0ef493f72"
>> +LIC_FILES_CHKSUM = "file://runtime/doc/uganda.txt;endline=287;md5=909f1394892b7e0f9c2a95306c0c552b"
>>
>> SRC_URI = "git://github.com/vim/vim.git \
>>             file://disable_acl_header_check.patch \
>>             file://vim-add-knob-whether-elf.h-are-checked.patch \
>>             file://0001-src-Makefile-improve-reproducibility.patch \
>> "
>> -SRCREV = "202d982b36d87cf91d992bd7e30d3223bdc72cd9"
>> +SRCREV = "e05a89ac6399a8c7d164c99fdab6841d999a9128"
>>
>> # Do not consider .z in x.y.z, as that is updated with every commit
>> UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+\.\d+)\.0"
>> diff --git a/meta/recipes-support/vim/vim_8.1.1518.bb b/meta/recipes-support/vim/vim_8.2.0110.bb
>> similarity index 100%
>> rename from meta/recipes-support/vim/vim_8.1.1518.bb
>> rename to meta/recipes-support/vim/vim_8.2.0110.bb
>> -- 
>> 2.23.0
>>
>> -- 
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
# Randy MacLeod
# Wind River Linux



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] vim: update from 8.1.1518 to 8.2.0110
  2020-01-14 20:09   ` Randy MacLeod
@ 2020-01-14 22:18     ` Alexander Kanavin
  2020-01-14 22:37       ` Randy MacLeod
  2020-01-16 17:02       ` Tom Rini
  0 siblings, 2 replies; 7+ messages in thread
From: Alexander Kanavin @ 2020-01-14 22:18 UTC (permalink / raw)
  To: Randy MacLeod; +Cc: OE-core

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

On Tue, 14 Jan 2020 at 21:10, Randy MacLeod <randy.macleod@windriver.com>
wrote:

> Oleg is getting started using Yocto so I'll reply on his behalf since
> I asked him to update vim as his first commit.
>
> I'm not sure what you mean by 8.2. Are you talking about calling the
> recipe:
>     vim_8.2.bb
> instead of vim_8.2.0110.bb?
>
> Vim tags on a daily or more frequent basis. Are you saying that we
> should keep the
> same SRCREV for 8.2.0110 but use a different name?
>
> I looked at:
>     git log v8.2.0000..v8.2.0118
> and all the commits seem to fix bugs so I prefer to take this tested
> v8.2.0110
> update and update vim every month or two so that we get the latest fixes.
>

Vim adds a tag for every single commit they make, fixes or not, so this
approach would in effect be updating to random development snapshots. I
would rather have a more conservative update strategy, and update to the
original 8.2 release. If you look at the homepage, 8.2 is the version they
announced as the new release: https://www.vim.org/

That's also what 'devtool latest-version vim' should currently report and
'devtool upgrade' upgrade to: I purposely cut off the point releases and
left only the major.minor part there.

Alex

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] vim: update from 8.1.1518 to 8.2.0110
  2020-01-14 22:18     ` Alexander Kanavin
@ 2020-01-14 22:37       ` Randy MacLeod
  2020-01-15  8:14         ` Alexander Kanavin
  2020-01-16 17:02       ` Tom Rini
  1 sibling, 1 reply; 7+ messages in thread
From: Randy MacLeod @ 2020-01-14 22:37 UTC (permalink / raw)
  To: Alexander Kanavin; +Cc: OE-core

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

On 1/14/20 5:18 PM, Alexander Kanavin wrote:
> On Tue, 14 Jan 2020 at 21:10, Randy MacLeod 
> <randy.macleod@windriver.com <mailto:randy.macleod@windriver.com>> wrote:
>
>     Oleg is getting started using Yocto so I'll reply on his behalf since
>     I asked him to update vim as his first commit.
>
>     I'm not sure what you mean by 8.2. Are you talking about calling
>     the recipe:
>     vim_8.2.bb <http://vim_8.2.bb>
>     instead of vim_8.2.0110.bb <http://vim_8.2.0110.bb>?
>
>     Vim tags on a daily or more frequent basis. Are you saying that we
>     should keep the
>     same SRCREV for 8.2.0110 but use a different name?
>
>     I looked at:
>         git log v8.2.0000..v8.2.0118
>     and all the commits seem to fix bugs so I prefer to take this tested
>     v8.2.0110
>     update and update vim every month or two so that we get the latest
>     fixes.
>
>
> Vim adds a tag for every single commit they make, fixes or not, so 
> this approach would in effect be updating to random development 
> snapshots. I would rather have a more conservative update strategy, 
> and update to the original 8.2 release. If you look at the homepage, 
> 8.2 is the version they announced as the new release: https://www.vim.org/


Sure, that's fine for now. Most of the commits are bug fixes after 8.2 
but we don't need to
worry about any of them now and I guess if we stick with this approach, 
and say there as
a CVE for vim that we wanted to fix, we'd just backport the single 
commit rather than
bump the version to 8.2.1248 or some such version.

>
> That's also what 'devtool latest-version vim' should currently report 
> and 'devtool upgrade' upgrade to: I purposely cut off the point 
> releases and left only the major.minor part there.

Right. This will also give Oleg an excuse to try 'devtool upgrade' to 
compare manually upgrading. :)

../Randy


>
> Alex


-- 
# Randy MacLeod
# Wind River Linux


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] vim: update from 8.1.1518 to 8.2.0110
  2020-01-14 22:37       ` Randy MacLeod
@ 2020-01-15  8:14         ` Alexander Kanavin
  0 siblings, 0 replies; 7+ messages in thread
From: Alexander Kanavin @ 2020-01-15  8:14 UTC (permalink / raw)
  To: Randy MacLeod; +Cc: OE-core

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

On Tue, 14 Jan 2020 at 23:37, Randy MacLeod <randy.macleod@windriver.com>
wrote:

> That's also what 'devtool latest-version vim' should currently report and
> 'devtool upgrade' upgrade to: I purposely cut off the point releases and
> left only the major.minor part there.
>
> Right. This will also give Oleg an excuse to try 'devtool upgrade' to
> compare manually upgrading. :)
>

Thanks, that is of course appreciated. Run 'devtool check-upgrade-status'
to get an overview of what needs updating, maybe you can help Oleg to pick
the easier updates from that list.

Alex

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH] vim: update from 8.1.1518 to 8.2.0110
  2020-01-14 22:18     ` Alexander Kanavin
  2020-01-14 22:37       ` Randy MacLeod
@ 2020-01-16 17:02       ` Tom Rini
  1 sibling, 0 replies; 7+ messages in thread
From: Tom Rini @ 2020-01-16 17:02 UTC (permalink / raw)
  To: Alexander Kanavin; +Cc: OE-core

On Tue, Jan 14, 2020 at 11:18:44PM +0100, Alexander Kanavin wrote:
> On Tue, 14 Jan 2020 at 21:10, Randy MacLeod <randy.macleod@windriver.com>
> wrote:
> 
> > Oleg is getting started using Yocto so I'll reply on his behalf since
> > I asked him to update vim as his first commit.
> >
> > I'm not sure what you mean by 8.2. Are you talking about calling the
> > recipe:
> >     vim_8.2.bb
> > instead of vim_8.2.0110.bb?
> >
> > Vim tags on a daily or more frequent basis. Are you saying that we
> > should keep the
> > same SRCREV for 8.2.0110 but use a different name?
> >
> > I looked at:
> >     git log v8.2.0000..v8.2.0118
> > and all the commits seem to fix bugs so I prefer to take this tested
> > v8.2.0110
> > update and update vim every month or two so that we get the latest fixes.
> >
> 
> Vim adds a tag for every single commit they make, fixes or not, so this
> approach would in effect be updating to random development snapshots. I
> would rather have a more conservative update strategy, and update to the
> original 8.2 release. If you look at the homepage, 8.2 is the version they
> announced as the new release: https://www.vim.org/
> 
> That's also what 'devtool latest-version vim' should currently report and
> 'devtool upgrade' upgrade to: I purposely cut off the point releases and
> left only the major.minor part there.

What we had talked about before was trying to follow (more or less)
updating to versions that one of the desktop distros had chosen, to
avoid the fact that yes, every commit to vim is a new version number
thus making it hard to know what's an important/good release but also
still getting bug fixes and so forth.

-- 
Tom


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2020-01-16 17:02 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-14 19:30 [PATCH] vim: update from 8.1.1518 to 8.2.0110 Oleg Polyakov
2020-01-14 19:39 ` Alexander Kanavin
2020-01-14 20:09   ` Randy MacLeod
2020-01-14 22:18     ` Alexander Kanavin
2020-01-14 22:37       ` Randy MacLeod
2020-01-15  8:14         ` Alexander Kanavin
2020-01-16 17:02       ` Tom Rini

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.