From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
"[ext] Jan Kiszka" <jan.kiszka@siemens.com>,
isar-users@googlegroups.com, Claudius Heine <ch@denx.de>,
Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH] conf/distro: Remove jessie updates
Date: Wed, 27 Mar 2019 11:24:57 +0100 [thread overview]
Message-ID: <cb002882-9393-4ed8-50c6-3e3148d45b4d@ilbers.de> (raw)
In-Reply-To: <d46c0af8-11f6-6e8d-877c-f391b5a99a55@siemens.com>
On 3/27/19 10:40 AM, Claudius Heine wrote:
> Hi Jan,
>
> On 26/03/2019 18.18, [ext] Jan Kiszka wrote:
>> On 26.03.19 17:13, Maxim Yu. Osipov wrote:
>>> On 3/26/19 5:04 PM, Maxim Yu. Osipov wrote:
>>>> jessie-updates were removed from ftp.debian.org.
>>>
>>> Applied to the both 'next' and 'master' otherwise CI procedure is
>>> blocked.
>>>
>>
>> Let's move forward and drop this completely. We have at least two
>> patches, if not three, pending that improve Isar but depend on
>> stretch+. Moreover, there are no products out there that use Isar with
>> jessie.
>>
>> Claudius, your removal patch(es) still apply?
>
> Probably. Those where just for raspbian-jessie though. But those might
> not be necessary since Baurzhan is willing to maintain raspberry 1 in
> isar and IIUC agreed to update that to stretch over a month ago. So I
> guess he is busy doing that at the moment. When he is finished, then we
> can drop jessie support altogether.
I'll take care ASAP on Raspberry Pi 1 support under Raspbian stretch.
After that we will proceed with dropping jessie from isar.
Regards,
Maxim.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2019-03-27 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 16:04 Maxim Yu. Osipov
2019-03-26 16:13 ` Maxim Yu. Osipov
2019-03-26 17:18 ` Jan Kiszka
2019-03-26 17:37 ` Maxim Yu. Osipov
2019-03-27 9:40 ` Claudius Heine
2019-03-27 10:24 ` Maxim Yu. Osipov [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=cb002882-9393-4ed8-50c6-3e3148d45b4d@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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