On 25 Nov 17:45, Mauro Carvalho Chehab wrote:
[snip]
> > I'd love to get a few of these patches, should you have the time/inclination
> > to release them (either via patches or a public Git). I won't re-add Django
> > 1.4/1.5 support myself, but if someone has the work done and it's
> >
On Mon, Nov 09, 2015 at 05:17:49PM -0500, Don Zickus wrote:
> On Mon, Nov 09, 2015 at 08:03:09PM +, Finucane, Stephen wrote:
> > > > I notice Rails is listed as a package there. What's the possibility of
> > > getting
> > > > Django added? Nigh-on non-existent? To say Django is widespread
On Mon, Nov 09, 2015 at 08:03:09PM +, Finucane, Stephen wrote:
> > > I notice Rails is listed as a package there. What's the possibility of
> > getting
> > > Django added? Nigh-on non-existent? To say Django is widespread would be
> > an
> > > understatement. I'd envision quite a few users for
> Hi,
>
> Just to throw another datapoint at folks. RHEL-7 has this notion of
> software collections. It allows customers to update a collection tools to
> a
> newer version (RH supported) in the /opt area. Then using a script (which
> sets env variables), a program can easily use python3 and
On Mon, Nov 09, 2015 at 05:20:00PM +, Finucane, Stephen wrote:
> > Hi,
> >
> > Just to throw another datapoint at folks. RHEL-7 has this notion of
> > software collections. It allows customers to update a collection tools to
> > a
> > newer version (RH supported) in the /opt area. Then
On Fri, Nov 06, 2015 at 07:02:31PM +0100, Johannes Berg wrote:
> +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
Hi Don,
Em Mon, 09 Nov 2015 11:22:50 -0500
Don Zickus escreveu:
> On Fri, Nov 06, 2015 at 07:02:31PM +0100, Johannes Berg wrote:
> > +Konstantin, the kernel.org sysadmin. The context is that patchwork has
> > just removed (see subject) support for Django 1.6, but I've been
> On Mon, Nov 09, 2015 at 05:20:00PM +, Finucane, Stephen wrote:
> > > Hi,
> > >
> > > Just to throw another datapoint at folks. RHEL-7 has this notion of
> > > software collections. It allows customers to update a collection tools
> to
> > > a
> > > newer version (RH supported) in the /opt
> 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
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
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
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
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
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
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
>
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
> >
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
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
> 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, necessitating the continued use of manual SQL
> migration files. Drop support for Django 1.6 thus encouraging users to
> move to Django
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, necessitating the continued use of manual SQL
migration files. Drop support for Django 1.6 thus encouraging users to
move to Django 1.7 or,
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, necessitating the continued use of manual SQL
> migration files. Drop
On Fri, 2015-11-06 at 08:36 +0100, Matthias Runge wrote:
> If I got the context right here, the question is, when (and if) there
> will be a Django upgrade for epel7 to Django-1.8.x, right?
Yeah that would be the most obvious "question" here. I wasn't even sure
that it was going to be possible
22 matches
Mail list logo