> As far as I know, there is work ongoing. But unfortunately, I don't
> know any time-frame for that effort.
>
Ok, thanks.
Not sure what the conclusion should be here then though, I'll have to
think about that.
johannes
___
Patchwork mailing list
Pat
Hi,
2015-11-06 00:00, Thomas F Herbert:
> Thomas,
>
> I am replicating the DPDK patchwork for upgrading. What user should I
> run uwsgi as?
On dpdk.org, it is www-data.
> The text file says to put the ini in the user's home directory. Can I
> assume it doesn't matter?
# cat /root/config/patc
Hi,
On Thu, Nov 05, 2015 at 06:58:42PM +0100, Johannes Berg wrote:
> On Thu, 2015-11-05 at 16:00 +, Stephen Finucane wrote:
> > Django 1.6 is no longer supported, neither with feature bugfixes nor
> > security fixes. Additionally, Django 1.6 does not support the use of
> > Django Migrations, n
Hi,
> A possible solution: [...]
I'm not involved in the maintenance of kernel.org, so I can't really
say. However, in the past we've been told that they can only upgrade
patchwork if the django requirement can be fulfilled from RHEL/EPEL,
and the admins there are generally very competent so I'm
On Fri, Nov 06, 2015 at 01:04:10PM +0100, Johannes Berg wrote:
> Hi,
>
> > A possible solution: [...]
>
> I'm not involved in the maintenance of kernel.org, so I can't really
> say. However, in the past we've been told that they can only upgrade
> patchwork if the django requirement can be fulfil
Hi Stephen,
Em Thu, 5 Nov 2015 18:18:36 +
"Finucane, Stephen" escreveu:
> The problem with continuing support for Django 1.6 is, as mentioned, that
> it incurs a huge amount of overhead due to the SQL migrations (this affects
> not only developers but also sysadmins, who must validate and
On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > Django 1.8 is LTS so I imagine there should be support coming for this in
> > EPEL, SLES etc. I'm little to no experience with these distros though, and
> > I have no idea how these folks plan/publish their roadmaps. Could
> On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > > Django 1.8 is LTS so I imagine there should be support coming for this
> in
> > > EPEL, SLES etc. I'm little to no experience with these distros though,
> and
> > > I have no idea how these folks plan/publish their roadm
Em Fri, 6 Nov 2015 15:52:02 +
Damien Lespiau escreveu:
> On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > > Django 1.8 is LTS so I imagine there should be support coming for this in
> > > EPEL, SLES etc. I'm little to no experience with these distros though,
> > > a
+Konstantin, the kernel.org sysadmin. The context is that patchwork has
just removed (see subject) support for Django 1.6, but I've been told
that RHEL/EPEL7 which you run has only that version, so updating to the
latest patchwork would now be impossible (again)
> We can't support Django 1.4: it's
Em Fri, 06 Nov 2015 17:37:47 +
"Finucane, Stephen" escreveu:
> > On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > > > Django 1.8 is LTS so I imagine there should be support coming for this
> > in
> > > > EPEL, SLES etc. I'm little to no experience with these distros
Em Fri, 06 Nov 2015 19:02:31 +0100
Johannes Berg escreveu:
> > If not, then we're going to have (a) roll back the Django 1.6 removal
> > patches, (b) put together a roadmap for future Django version support and
> > (c) avoid using non-stdlib libraries (outside of Django) going forward. As
> > Dam
On 06 Nov 16:38, Mauro Carvalho Chehab wrote:
> Em Fri, 06 Nov 2015 19:02:31 +0100
> Johannes Berg escreveu:
>
> > > If not, then we're going to have (a) roll back the Django 1.6 removal
> > > patches, (b) put together a roadmap for future Django version support and
> > > (c) avoid using non-stdl
On 06 Nov 15:57, Mauro Carvalho Chehab wrote:
> Em Fri, 6 Nov 2015 15:52:02 +
> Damien Lespiau escreveu:
>
> > On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > > > Django 1.8 is LTS so I imagine there should be support coming for this
> > > > in
> > > > EPEL, SLES e
On 20 Oct 23:34, Finucane, Stephen wrote:
> > I did a full pass on the REST API I had and extracted a documented subset
> > that
> > should be easy to extend in the future.
> >
> > http://patchwork-freedesktop.readthedocs.org/en/latest/api.html
> >
> > A list of entry points is available, that'
Quick question: does anyone have any preferences for issue tracking? I'd like
to use Launchpad as it seems a little more "fleshed-out" that GitHub's issue
tracker. It's also based on open source software, which is nice. However, I'm
also OK with using GitHub's issue tracker if anyone has a hard req
Em Fri, 06 Nov 2015 20:41:20 +
"Finucane, Stephen" escreveu:
> On 06 Nov 15:57, Mauro Carvalho Chehab wrote:
> > Em Fri, 6 Nov 2015 15:52:02 +
> > Damien Lespiau escreveu:
> >
> > > On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > > > > Django 1.8 is LTS so I i
17 matches
Mail list logo
