Le Ven 1 mars 2013 17:41, Miloslav Trmač a écrit :
> (In the recent years, the number of upstreams and packagers that can't
> or won't support a smooth upgrade path and want to have several
> versions of the same package installed has noticeably increased, and
> we may need to react to this by de
On 02/28/2013 12:58 PM, Matthias Runge wrote:
> Dear list,
>
> Django 1.5 was released about two days ago. I'd like to push a build to
> rawhide, but I assume, that will break many dependent packages.
>
> The plan is, to delay the push, until other packages are fixed, or to
> push in about 14 day
On Fri, Mar 1, 2013 at 2:47 PM, Stephen Gallagher wrote:
> Well, I'm also looking at EPEL here (though I suppose we could just
> implement a different solution on that side as well). EPEL has a much
> longer life than Fedora releases (and much, much longer than the
> Django upstream release mainte
On Fri, Mar 1, 2013 at 8:56 AM, Bohuslav Kabrda wrote:
>> Now, I'm more attracted to rename the python-django package (yeay,
>> another Django-rename) to python-django14 and to submit a new package
>> python-django15 for review. When 1.6 comes out, python-django14 will
>> get deprecated and python
- Original Message -
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/01/2013 02:56 AM, Bohuslav Kabrda wrote:
> > - Original Message - On 02/28/2013 05:46 PM, Stephen
> > Gallagher wrote:
> > That seems to be a good proposal for me. Review request is
> > here[1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/01/2013 02:56 AM, Bohuslav Kabrda wrote:
> - Original Message - On 02/28/2013 05:46 PM, Stephen
> Gallagher wrote:
> That seems to be a good proposal for me. Review request is
> here[1], based on the current python-django packag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/01/2013 08:41 AM, Matthias Runge wrote:
> But still, currently, we're carrying provides like this: Provides:
> django = %{version}-%{release} Provides: Django =
> %{version}-%{release} and also provide python-django. The question
> remains
- Original Message -
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/28/2013 05:46 PM, Stephen Gallagher wrote:
> >> That seems to be a good proposal for me. Review request is
> >> here[1], based on the current python-django package. Shouldn't
> >> be an issue. For EPEL, we hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2013 05:46 PM, Stephen Gallagher wrote:
>> That seems to be a good proposal for me. Review request is
>> here[1], based on the current python-django package. Shouldn't
>> be an issue. For EPEL, we have the Django14 package. This
>> shouldn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2013 11:13 AM, Matthias Runge wrote:
> On 02/28/2013 02:16 PM, Stephen Gallagher wrote:
>> On Thu 28 Feb 2013 06:58:36 AM EST, Matthias Runge wrote:
>>> Dear list,
>
>>> Django 1.5 was released about two days ago. I'd like to push a
>>> buil
Hi
On Thu, Feb 28, 2013 at 11:22 AM, Matthias Runge wrote:
> I see your point not to touch any Django-package to change the
> requirements, but also this will make things more confusing:
> Django (as F17) is 1.4.x
> python-django is 1.4.x
> python-django15 is 1.5
>
> what about Django-1.6? So I'd
On 02/28/2013 03:57 PM, Rahul Sundaram wrote:
> You should introduce a python-django15 package instead and let dependent
> packages slowly move over. We cannot handle this within a single
> release timeframe. Every release introduces incompatibilities and
> upstream projects aren't willing to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2013 02:16 PM, Stephen Gallagher wrote:
> On Thu 28 Feb 2013 06:58:36 AM EST, Matthias Runge wrote:
>> Dear list,
>
>> Django 1.5 was released about two days ago. I'd like to push a
>> build to rawhide, but I assume, that will break many depe
Hi
On Thu, Feb 28, 2013 at 6:58 AM, Matthias Runge wrote:
> Dear list,
>
> Django 1.5 was released about two days ago. I'd like to push a build to
> rawhide, but I assume, that will break many dependent packages.
>
> The plan is, to delay the push, until other packages are fixed, or to
> push in
Stephen Gallagher wrote:
> How many Django-based packages are we talking about? Should we be
> considering putting things together in a side tag before landing in
> Rawhide?
Add cobbler to the list. Cobbler was forgotten about in Fedora 17 and an
update to support Django in Fedora 17 is /still/ si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu 28 Feb 2013 06:58:36 AM EST, Matthias Runge wrote:
> Dear list,
>
> Django 1.5 was released about two days ago. I'd like to push a build to
> rawhide, but I assume, that will break many dependent packages.
>
> The plan is, to delay the push, unt
Dear list,
Django 1.5 was released about two days ago. I'd like to push a build to
rawhide, but I assume, that will break many dependent packages.
The plan is, to delay the push, until other packages are fixed, or to
push in about 14 days.
I have a scratch-build build ready, one might to try, it
17 matches
Mail list logo
