From: Andrei Gherzan <andrei@gherzan.ro>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: yocto@yoctoproject.org, Gary Thomas <gary@mlbassoc.com>
Subject: Re: [meta-raspberrypi][PATCH 0/2] Drop kernel versions 4.7 and 4.8
Date: Wed, 18 Jan 2017 15:40:24 +0000 [thread overview]
Message-ID: <20170118154024.GA31825@carbonA> (raw)
In-Reply-To: <E4828DAD-529B-4C43-A13B-67096B6741EE@paulbarker.me.uk>
[-- Attachment #1: Type: text/plain, Size: 4033 bytes --]
On Mon, Jan 16, 2017 at 03:12:51PM +0000, Paul Barker wrote:
> On 16 January 2017 14:51:55 GMT+00:00, Gary Thomas <gary@mlbassoc.com> wrote:
> >On 2017-01-16 15:48, Gary Thomas wrote:
> >> On 2017-01-16 08:26, Paul Barker wrote:
> >>> As discussed recently on the list, we can just keep LTS versions now
> >>> that v4.9 is available.
> >>>
> >>> I'm sending these so anyone who still needs v4.7 or v4.8 can shout
> >>> 'stop!' before we remove them.
> >>>
> >>> Paul Barker (2):
> >>> linux-raspberrypi: Drop v4.7
> >>> linux-raspberrypi: Drop v4.8
> >>>
> >>> .../0001-fix-dtbo-rules.patch | 44
> >----------------------
> >>> recipes-kernel/linux/linux-raspberrypi_4.7.bb | 9 -----
> >>> recipes-kernel/linux/linux-raspberrypi_4.8.bb | 8 ----
> >>> 3 files changed, 61 deletions(-)
> >>> delete mode 100644
> >recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
> >>> delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.7.bb
> >>> delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.8.bb
> >>>
> >>
> >> +1 at least for 4.7 given that with today's repo I get this:
> >>
> >> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
> >do_kernel_version_sanity_check: Package Version
> >> (4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built
> >(4.7.10). Please update the PV variable to match the
> >> kernel source.
> >> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
> >do_kernel_version_sanity_check: Function failed:
> >> do_kernel_version_sanity_check (log file is located at
> >>
> >/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.27925)
> >>
> >> ERROR: Logfile of failure stored in:
> >>
> >/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.27925
> >>
> >> ERROR: Task
> >>
> >(/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.7.bb:do_kernel_version_sanity_check)
> >> failed with exit code '1'
> >>
> >
> >
> >However, there is this error when I tried to switch to 4.9:
> >ERROR: linux-raspberrypi-1_4.9.2+gitAUTOINC+4052b0da7d-r0 do_fetch:
> >Fetcher failure: Unable to find revision
> >4052b0da7dbab0df22ca8733cf50b3e573e221e0 in branch rpi-4.9.y even from
> >upstream
> >ERROR: linux-raspberrypi-1_4.9.2+gitAUTOINC+4052b0da7d-r0 do_fetch:
> >Fetcher failure for URL:
> >'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y'.
> >Unable to fetch URL from any source.
> >ERROR: linux-raspberrypi-1_4.9.2+gitAUTOINC+4052b0da7d-r0 do_fetch:
> >Function failed: base_do_fetch
> >ERROR: Logfile of failure stored in:
> >/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.9.2+gitAUTOINC+4052b0da7d-r0/temp/log.do_fetch.13098
> >ERROR: Task
> >(/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:do_fetch)
> >failed
> >with exit code '1'
> >
> >Using meta-raspberrypi:e1f69daa805cb02ddd123ae2d4d48035cb5b41d0
>
> I think any upstream branch after 4.4.y is still at risk of being rebased at the minute. I think the best solution is to still drop 4.7.y and 4.8.y, but try to get an update in for 4.9.y first.
I totally agree with this. I left this thread for a while to see if
people are really attached to these versions. Our last decision was to
keep:
1. last LTS
2. current stable version as considered by the upstream [default]
3. the latest bleading edge
Based we should only keep 4.4 and 4.10 (or 4.9).
Ane comments before I proceed? :)
>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Andrei Gherzan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2017-01-18 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 7:26 [meta-raspberrypi][PATCH 0/2] Drop kernel versions 4.7 and 4.8 Paul Barker
2017-01-16 7:26 ` [meta-raspberrypi][PATCH 1/2] linux-raspberrypi: Drop v4.7 Paul Barker
2017-01-16 7:26 ` [meta-raspberrypi][PATCH 2/2] linux-raspberrypi: Drop v4.8 Paul Barker
2017-01-16 14:48 ` [meta-raspberrypi][PATCH 0/2] Drop kernel versions 4.7 and 4.8 Gary Thomas
2017-01-16 14:51 ` Gary Thomas
2017-01-16 15:12 ` Paul Barker
2017-01-18 15:40 ` Andrei Gherzan [this message]
2017-01-18 16:24 ` Leon Woestenberg
2017-01-18 16:30 ` Andrei Gherzan
2017-01-18 18:31 ` Leon Woestenberg
2017-01-18 6:06 ` Herve Jourdain
2017-01-18 6:03 ` Herve Jourdain
2017-01-18 16:08 ` Andrei Gherzan
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=20170118154024.GA31825@carbonA \
--to=andrei@gherzan.ro \
--cc=gary@mlbassoc.com \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.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 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.