From: "Reyna, David" <david.reyna@windriver.com>
To: Tim Orling <ticotimo@gmail.com>
Cc: "toaster@lists.yoctoproject.org" <toaster@lists.yoctoproject.org>
Subject: Re: toaster-requirements.txt
Date: Wed, 27 May 2020 22:41:38 +0000 [thread overview]
Message-ID: <BY5PR11MB4167FE8AFE8DB218223565C9EAB10@BY5PR11MB4167.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CANx9H-A6s9Uek7i-16mtH_VLAyS-9TG+1Gi8zks+7xYzq4YMjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
> I can send the patch. I just wanted confirmation I wasn’t missing something.
That would be great, for 3.1.1 and master!
- David
From: Tim Orling [mailto:ticotimo@gmail.com]
Sent: Wednesday, May 27, 2020 3:40 PM
To: Reyna, David
Cc: toaster@lists.yoctoproject.org
Subject: Re: toaster-requirements.txt
I
On Wed, May 27, 2020 at 3:39 PM Reyna, David <david.reyna@windriver.com<mailto:david.reyna@windriver.com>> wrote:
Yes, I will submit that patch today or tomorrow.
I can send the patch. I just wanted confirmation I wasn’t missing something.
From: Tim Orling [mailto:ticotimo@gmail.com<mailto:ticotimo@gmail.com>]
Sent: Wednesday, May 27, 2020 3:38 PM
To: Reyna, David; toaster@lists.yoctoproject.org<mailto:toaster@lists.yoctoproject.org>
Subject: toaster-requirements.txt
I’m working on CROPS toaster-container again and noticed bitbake/toaster-requirements.txt still bounds Django>1.8,<1.12.
Aren’t we intending to be Django>2.2,<2.3
?
If I’m missing something, let me know.
I can confirm running locally (not in Docker) that 2.2.12 appears to work fine on Dunfell.
Cheers
—Tim
[-- Attachment #2: Type: text/html, Size: 6540 bytes --]
next prev parent reply other threads:[~2020-05-27 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 22:38 toaster-requirements.txt Tim Orling
2020-05-27 22:39 ` toaster-requirements.txt Reyna, David
2020-05-27 22:40 ` toaster-requirements.txt Tim Orling
2020-05-27 22:41 ` Reyna, David [this message]
2020-05-27 22:49 ` toaster-requirements.txt Tim Orling
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=BY5PR11MB4167FE8AFE8DB218223565C9EAB10@BY5PR11MB4167.namprd11.prod.outlook.com \
--to=david.reyna@windriver.com \
--cc=ticotimo@gmail.com \
--cc=toaster@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).