[PATCH] openssh: upgrade to 7.5p1

[PATCH] openssh: upgrade to 7.5p1

[Dengke Du]

Signed-off-by: Dengke Du <dengke.du@windriver.com>
---
 .../openssh/{openssh_7.4p1.bb => openssh_7.5p1.bb}                    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-connectivity/openssh/{openssh_7.4p1.bb => openssh_7.5p1.bb} (97%)

diff --git a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb b/meta/recipes-connectivity/openssh/openssh_7.5p1.bb
similarity index 97%
rename from meta/recipes-connectivity/openssh/openssh_7.4p1.bb
rename to meta/recipes-connectivity/openssh/openssh_7.5p1.bb
index c8093d4..5b96745 100644
--- a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_7.5p1.bb
@@ -29,8 +29,8 @@ SRC_URI = "http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar
 
 PAM_SRC_URI = "file://sshd"
 
-SRC_URI[md5sum] = "b2db2a83caf66a208bb78d6d287cdaa3"
-SRC_URI[sha256sum] = "1b1fc4a14e2024293181924ed24872e6f2e06293f3e8926a376b8aec481f19d1"
+SRC_URI[md5sum] = "652fdc7d8392f112bef11cacf7e69e23"
+SRC_URI[sha256sum] = "9846e3c5fab9f0547400b4d2c017992f914222b3fd1f8eee6c7dc6bc5e59f9f0"
 
 inherit useradd update-rc.d update-alternatives systemd
 
-- 
2.8.1

Re: [PATCH] openssh: upgrade to 7.5p1

[Dengke Du]

Ping.


On 2017年04月11日 10:01, Dengke Du wrote:
> Signed-off-by: Dengke Du <dengke.du@windriver.com>
> ---
>   .../openssh/{openssh_7.4p1.bb => openssh_7.5p1.bb}                    | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>   rename meta/recipes-connectivity/openssh/{openssh_7.4p1.bb => openssh_7.5p1.bb} (97%)
>
> diff --git a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb b/meta/recipes-connectivity/openssh/openssh_7.5p1.bb
> similarity index 97%
> rename from meta/recipes-connectivity/openssh/openssh_7.4p1.bb
> rename to meta/recipes-connectivity/openssh/openssh_7.5p1.bb
> index c8093d4..5b96745 100644
> --- a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
> +++ b/meta/recipes-connectivity/openssh/openssh_7.5p1.bb
> @@ -29,8 +29,8 @@ SRC_URI = "http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar
>   
>   PAM_SRC_URI = "file://sshd"
>   
> -SRC_URI[md5sum] = "b2db2a83caf66a208bb78d6d287cdaa3"
> -SRC_URI[sha256sum] = "1b1fc4a14e2024293181924ed24872e6f2e06293f3e8926a376b8aec481f19d1"
> +SRC_URI[md5sum] = "652fdc7d8392f112bef11cacf7e69e23"
> +SRC_URI[sha256sum] = "9846e3c5fab9f0547400b4d2c017992f914222b3fd1f8eee6c7dc6bc5e59f9f0"
>   
>   inherit useradd update-rc.d update-alternatives systemd
>   

Re: [PATCH] openssh: upgrade to 7.5p1

[Richard Purdie]

On Mon, 2017-04-17 at 12:37 +0800, Dengke Du wrote:
> Ping.

We do not take upgrades after feature freeze when we're stabilising
unless there is a pressing reason to do so. Your commit messages makes
no mention of any pressing reason.

Cheers,

Richard

Re: [PATCH] openssh: upgrade to 7.5p1

[Dengke Du]

Sorry for my rude.


On 2017年04月17日 14:43, Richard Purdie wrote:
> On Mon, 2017-04-17 at 12:37 +0800, Dengke Du wrote:
>> Ping.
> We do not take upgrades after feature freeze when we're stabilising
> unless there is a pressing reason to do so. Your commit messages makes
> no mention of any pressing reason.
>
> Cheers,
>
> Richard
>
>

Re: [PATCH] openssh: upgrade to 7.5p1

[Alexander Kanavin]

On 04/17/2017 09:43 AM, Richard Purdie wrote:
> On Mon, 2017-04-17 at 12:37 +0800, Dengke Du wrote:
>> Ping.
>
> We do not take upgrades after feature freeze when we're stabilising
> unless there is a pressing reason to do so. Your commit messages makes
> no mention of any pressing reason.

Yes, but... people keep doing it despite you and me and everyone else 
telling them not to. How about someone would stash those updates to a 
kind of 'master-next-next' branch, and dump them to the list again when 
the merge window reopens? I can do that, if I would get a clear 
indication of when that work should start and finish.

Alex

Re: [PATCH] openssh: upgrade to 7.5p1

[Burton, Ross]

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

On 18 April 2017 at 11:18, Alexander Kanavin <
alexander.kanavin@linux.intel.com> wrote:

> Yes, but... people keep doing it despite you and me and everyone else
> telling them not to. How about someone would stash those updates to a kind
> of 'master-next-next' branch, and dump them to the list again when the
> merge window reopens? I can do that, if I would get a clear indication of
> when that work should start and finish.
>

FWIW I'm collecting patches in ross/mut for when master re-opens. They've
been posted to the list so don't need re-posting.

Ross

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

Re: [PATCH] openssh: upgrade to 7.5p1

[Alexander Kanavin]

On 04/18/2017 01:20 PM, Burton, Ross wrote:
>     Yes, but... people keep doing it despite you and me and everyone
>     else telling them not to. How about someone would stash those
>     updates to a kind of 'master-next-next' branch, and dump them to the
>     list again when the merge window reopens? I can do that, if I would
>     get a clear indication of when that work should start and finish.
>
>
> FWIW I'm collecting patches in ross/mut for when master re-opens.
> They've been posted to the list so don't need re-posting.

That's great, then I can send some things that have piled up now :)


Alex