Hi,
On Thu, 22 Jun 2006, Matthias Klose wrote:
> > Updated files attached.
> >
> > Matthias, this time you can safely integrate this version in the official
> > python package.
>
> The patch itself looks ok to me.
Good, can you upload the new pyversions today then ?
> Maybe you could help me
Raphael Hertzog writes:
> On Tue, 20 Jun 2006, Raphael Hertzog wrote:
> > On Tue, 20 Jun 2006, Raphael Hertzog wrote:
> > > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > > - pyversions needs to be modified to not fail if the field
> > > > XS-Python-Version is not present. He should in that ca
On Tue, 20 Jun 2006, Raphael Hertzog wrote:
> On Tue, 20 Jun 2006, Raphael Hertzog wrote:
> > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > - pyversions needs to be modified to not fail if the field
> > > XS-Python-Version is not present. He should in that case
> > > use the information of
On Tue, 20 Jun 2006, Raphael Hertzog wrote:
> On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > - pyversions needs to be modified to not fail if the field
> > XS-Python-Version is not present. He should in that case
> > use the information of the debian/pyversions file. I will
> > hopefully soo
Le mardi 20 juin 2006 à 01:34 +0200, Raphael Hertzog a écrit :
> On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > - uses "XS-Python-Standards-Version: 0.4" as reference field to run in
> > new
> >policy mode. The presence of XS-Python-Version will also trigger the
> > new
> >p
* Joe Wreschnig ([EMAIL PROTECTED]) [060620 07:35]:
> What does it mean? This thread more or less started when Raphael updated
> dh_python to change behavior based on the presence/absence of the
> Python-Standards-Version field -- exactly analogous to what debhelper's
> compat levels are.
Well, I
Le mar 20 juin 2006 06:49, Andreas Barth a écrit :
> * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > - uses "XS-Python-Standards-Version: 0.4" as reference field
> > > to run in new policy mode. The presence of XS-Python-Version will
On Tue, 20 Jun 2006, Andreas Barth wrote:
> * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > - uses "XS-Python-Standards-Version: 0.4" as reference field to run
> > > in new
> > >policy mode. The presence of XS-Python-Version
On Tue, 2006-06-20 at 07:27 +0200, Andreas Barth wrote:
> * Joe Wreschnig ([EMAIL PROTECTED]) [060620 07:14]:
> > On Tue, 2006-06-20 at 06:49 +0200, Andreas Barth wrote:
> > > * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > > > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > > > -
* Joe Wreschnig ([EMAIL PROTECTED]) [060620 07:14]:
> On Tue, 2006-06-20 at 06:49 +0200, Andreas Barth wrote:
> > * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > > - uses "XS-Python-Standards-Version: 0.4" as reference field to
> >
On Tue, 2006-06-20 at 06:49 +0200, Andreas Barth wrote:
> * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > - uses "XS-Python-Standards-Version: 0.4" as reference field to run
> > > in new
> > >policy mode. The presence of XS-P
* Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > - uses "XS-Python-Standards-Version: 0.4" as reference field to run in
> > new
> >policy mode. The presence of XS-Python-Version will also trigger the
> > new
> >policy mod
On Tue, Jun 20, 2006 at 01:34:35AM +0200, Raphael Hertzog wrote:
> On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > - uses "XS-Python-Standards-Version: 0.4" as reference field to run in new
> >policy mode. The presence of XS-Python-Version will also trigger the new
> >policy mode (this is
On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> - uses "XS-Python-Standards-Version: 0.4" as reference field to run in
> new
>policy mode. The presence of XS-Python-Version will also trigger the
> new
>policy mode (this is for short-term compatibility, it may be removed in
>
On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> - pyversions needs to be modified to not fail if the field
> XS-Python-Version is not present. He should in that case
> use the information of the debian/pyversions file. I will
> hopefully soon provide a patch for this.
Here's a patch and the re
Coin,
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> What still needs to be done:
> - pyversions needs to be modified to not fail if the field
> XS-Python-Version is not present. He should in that case
> use the information of the debian/pyversions file. I will
> hopefully soon provide a pa
Hi all,
given that nobody complained to my proposal of last evening, I went ahead
and implemented it.
I've updated dh_python (and the upcoming debhelper NMU 5.0.37.2) here:
http://people.debian.org/~hertzog/python/
Here's what has changed in this dh_python (taken from my debhelper
changelog):
17 matches
Mail list logo