From: Khem Raj <raj.khem@gmail.com>
To: akuster808 <akuster808@gmail.com>,
Alexander Kanavin <alex.kanavin@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 11/37] go: update 1.12.1->1.12.5
Date: Sat, 18 May 2019 21:46:10 -0700 [thread overview]
Message-ID: <aae4c321-973e-7a4e-9333-a2a64fc803a5@gmail.com> (raw)
In-Reply-To: <4723f59c-19d4-fafe-fa56-ee0e564d220b@gmail.com>
On 5/17/19 11:25 AM, akuster808 wrote:
>
>
> On 5/17/19 11:11 AM, Alexander Kanavin wrote:
>> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
>> ---
>> meta/recipes-devtools/go/go-1.12.inc | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/go/go-1.12.inc b/meta/recipes-devtools/go/go-1.12.inc
>> index 0cf0a63ff65..7c4cac1fc25 100644
>> --- a/meta/recipes-devtools/go/go-1.12.inc
>> +++ b/meta/recipes-devtools/go/go-1.12.inc
> any indication on testing?
I think we dont have extensive unit testing or ptest except go
helloworld, maybe we should have a ptest to run it on emulator
1.11 ia kept for users to migrate to 1.12, maybe we can remove it now.
>
> any reason why 1.11 can't be dropped?
>
> - armin
>> @@ -1,7 +1,7 @@
>> require go-common.inc
>>
>> GO_BASEVERSION = "1.12"
>> -GO_MINOR = ".1"
>> +GO_MINOR = ".5"
>> PV .= "${GO_MINOR}"
>> FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
>>
>> @@ -19,5 +19,5 @@ SRC_URI += "\
>> "
>> SRC_URI_append_libc-musl = " file://0009-ld-replace-glibc-dynamic-linker-with-musl.patch"
>>
>> -SRC_URI[main.md5sum] = "09fe592343465560b4b8431d870b3df3"
>> -SRC_URI[main.sha256sum] = "0be127684df4b842a64e58093154f9d15422f1405f1fcff4b2c36ffc6a15818a"
>> +SRC_URI[main.md5sum] = "cb6f594d22dd79af4fff9779607b1b47"
>> +SRC_URI[main.sha256sum] = "2aa5f088cbb332e73fc3def546800616b38d3bfe6b8713b8a6404060f22503e8"
>
next prev parent reply other threads:[~2019-05-19 4:46 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 18:11 [PATCH 01/37] librepo: upgrade 1.9.6 -> 1.10.2 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 02/37] libmodulemd: upgrade 2.2.3 -> 2.4.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 03/37] createrepo-c: upgrade 0.12.2 -> 0.14.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 04/37] libdazzle: upgrade 3.32.1 -> 3.32.2 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 05/37] adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 06/37] piglit: upgrade to latest revision Alexander Kanavin
2019-05-17 18:11 ` [PATCH 07/37] bison: upgrade 3.1 -> 3.3.2 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 08/37] atk: upgrade 2.30.0 -> 2.32.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 09/37] python3-mako: upgrade 1.0.9 -> 1.0.10 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 10/37] nss: upgrade 3.43 -> 3.44 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 11/37] go: update 1.12.1->1.12.5 Alexander Kanavin
2019-05-17 18:25 ` akuster808
2019-05-17 18:42 ` Alexander Kanavin
2019-05-19 4:46 ` Khem Raj [this message]
2019-05-17 18:11 ` [PATCH 12/37] systemtap: upgrade 4.0 -> 4.1 Alexander Kanavin
2019-05-17 18:29 ` akuster808
2019-05-17 18:44 ` Alexander Kanavin
2019-05-17 18:11 ` [PATCH 13/37] gawk: upgrade 4.2.1 -> 5.0.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 14/37] alsa-plugins: upgrade 1.1.8 -> 1.1.9 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 15/37] alsa-utils: " Alexander Kanavin
2019-05-17 18:11 ` [PATCH 16/37] alsa-lib: " Alexander Kanavin
2019-05-17 18:11 ` [PATCH 17/37] libpcre2: upgrade 10.32 -> 10.33 Alexander Kanavin
2019-05-17 18:28 ` Peter Kjellerstedt
2019-05-17 18:44 ` Alexander Kanavin
2019-05-17 18:11 ` [PATCH 18/37] lz4: upgrade 1.9.0 -> 1.9.1 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 19/37] libxcrypt: upgrade 4.4.4 -> 4.4.6 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 20/37] gnu-config: upgrade to latest revision Alexander Kanavin
2019-05-17 21:41 ` Adrian Bunk
2019-05-17 18:11 ` [PATCH 21/37] python3-pip: upgrade 19.0.3 -> 19.1.1 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 22/37] iproute2: upgrade 5.0.0 -> 5.1.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 23/37] pkgconf: upgrade 1.6.0 -> 1.6.1 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 24/37] at-spi2-core: upgrade 2.30.0 -> 2.32.1 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 25/37] at-spi2-atk: upgrade 2.30.0 -> 2.32.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 26/37] glib-networking: upgrade 2.60.1 -> 2.60.2 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 27/37] libsoup-2.4: upgrade 2.66.1 -> 2.66.2 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 28/37] x264: upgrade to latest revision Alexander Kanavin
2019-05-17 18:11 ` [PATCH 29/37] linux-firmware: " Alexander Kanavin
2019-05-17 18:11 ` [PATCH 30/37] python3-pbr: upgrade 5.1.3 -> 5.2.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 31/37] bash-completion: upgrade 2.8 -> 2.9 Alexander Kanavin
2019-05-19 4:48 ` Khem Raj
2019-05-19 9:58 ` Alexander Kanavin
2019-05-19 16:13 ` Khem Raj
2019-05-17 18:11 ` [PATCH 32/37] libdnf: upgrade 0.28.1 -> 0.33.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 33/37] gst-examples: upgrade to latest revision Alexander Kanavin
2019-05-17 21:43 ` Adrian Bunk
2019-05-18 8:43 ` Alexander Kanavin
2019-05-17 18:11 ` [PATCH 34/37] acpica: upgrade 20190405 -> 20190509 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 35/37] freetype: upgrade 2.9.1 -> 2.10.0 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 36/37] dnf: upgrade 4.2.2 -> 4.2.6 Alexander Kanavin
2019-05-17 18:11 ` [PATCH 37/37] usbutils: upgrade 010->012 Alexander Kanavin
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=aae4c321-973e-7a4e-9333-a2a64fc803a5@gmail.com \
--to=raj.khem@gmail.com \
--cc=akuster808@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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