On Tue, Sep 08, 2009 at 01:49:06AM +0700, Mikhail Gusarov wrote:
Twas brillig at 11:37:50 07.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL They were part of the design that came out of the python packaging
SL BoF in DebConf 6 that you then proceeded to ignore entirely.
On Mon, Sep 7, 2009 at 9:49 PM, Mikhail Gusarovdotted...@dottedmag.net wrote:
Twas brillig at 11:37:50 07.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL They were part of the design that came out of the python packaging
SL BoF in DebConf 6 that you then proceeded to ignore
Twas brillig at 20:21:31 07.09.2009 UTC-07 when vor...@debian.org did gyre and
gimble:
SL They were part of the design that came out of the python
SL packaging BoF in DebConf 6 that you then proceeded to ignore
SL entirely.
Is this design and rationale written down somewhere? It's
Twas brillig at 09:35:04 08.09.2009 UTC+01 when floris.bruynoo...@gmail.com did
gyre and gimble:
Is this design and rationale written down somewhere? It's hard to
follow policy which contains completely opaque requirements.
FB I recall watching a video of that BoF, so it should be
Le lundi 07 septembre 2009 à 20:21 -0700, Steve Langasek a écrit :
SL They were part of the design that came out of the python packaging
SL BoF in DebConf 6 that you then proceeded to ignore entirely.
Please don’t bring that topic again. I have spent more than enough time
implementing
Steve Langasek wrote:
On Sun, Sep 06, 2009 at 07:59:13PM +0200, Luca Falavigna wrote:
Il giorno Sun, 6 Sep 2009 19:32:34 +0200
Alessandro Dentella san...@e-den.it ha scritto:
pyversions: missing XS-Python-Version in control file, fall back to
debian/pyversions
It's fine to have
On Tue, Sep 08, 2009 at 03:53:31PM +0700, Mikhail Gusarov wrote:
Twas brillig at 20:21:31 07.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL They were part of the design that came out of the python
SL packaging BoF in DebConf 6 that you then proceeded to ignore
SL
Steve Langasek wrote:
The XS-Python-Version field was specified as a tool for detecting, without
having to download and inspect individual source packages, that a given
package can be successfully rebuilt for a python transition, to aid the
release team in this work.
As mentioned somewhere
Twas brillig at 02:42:09 08.09.2009 UTC-07 when vor...@debian.org did gyre and
gimble:
SL Spare me your ignorant preaching and go read the mailing list
SL archives.
Mailing list archives are not documentation.
SL It once lived at http://people.debian.org/~piman/python-policy/ -
SL before
On Tue, Sep 08, 2009 at 04:49:54PM +0700, Mikhail Gusarov wrote:
Twas brillig at 02:42:09 08.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL Spare me your ignorant preaching and go read the mailing list
SL archives.
Mailing list archives are not documentation.
They're
Steve Langasek wrote:
On Tue, Sep 08, 2009 at 03:53:31PM +0700, Mikhail Gusarov wrote:
Twas brillig at 20:21:31 07.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL They were part of the design that came out of the python
SL packaging BoF in DebConf 6 that you then
Twas brillig at 03:00:53 08.09.2009 UTC-07 when vor...@debian.org did gyre and
gimble:
SL plonk
So Steve went here for whining, not for fixing the situation. How sad :(
--
http://fossarchy.blogspot.com/
pgpxrPkrnQu1T.pgp
Description: PGP signature
Steve Langasek wrote:
On Tue, Sep 08, 2009 at 04:49:54PM +0700, Mikhail Gusarov wrote:
Twas brillig at 02:42:09 08.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL Spare me your ignorant preaching and go read the mailing list
SL archives.
Mailing list archives are not
On Tue, 08 Sep 2009 11:49:20 +0200 Bernd Zeimetz be...@bzed.de wrote:
Steve Langasek wrote:
The XS-Python-Version field was specified as a tool for detecting,
without
having to download and inspect individual source packages, that a given
package can be successfully rebuilt for a python
[Scott Kitterman, 2009-09-08]
Does pyversions offer any real advantages over XS-...? All things being
equal, if both helpers support a common method for this I think we should
just use it.
/me (while converting his packages back to python-support) is still
using XS-Python-Version
Twas brillig at 16:42:41 08.09.2009 UTC+02 when pi...@debian.org did gyre and
gimble:
PO I.e. using build dependencies to determine[1] requested Python
PO versions. Joss mentioned it on #debian-python recently so I guess
PO he's willing to remove pyversions...
Sounds good, getting rid of
On Tue, 08 Sep 2009 12:21:07 +0200 Bernd Zeimetz be...@bzed.de wrote:
There was a policy process?
Apparently we still need one of these. Can we work on solving this? I
think having a mechanism to create an actual current, maintained Python
policy is a pre-requisite to solving a lot of these
On Tue, Sep 08, 2009 at 09:53:09AM -0400, Scott Kitterman wrote:
On Tue, 08 Sep 2009 12:21:07 +0200 Bernd Zeimetz be...@bzed.de wrote:
There was a policy process?
Apparently we still need one of these. Can we work on solving this? I
think having a mechanism to create an actual current,
On Tue, 08 Sep 2009 15:52:57 +0200 Josselin Mouette j...@debian.org wrote:
Le mardi 08 septembre 2009 à 09:35 -0400, Scott Kitterman a écrit :
Does pyversions offer any real advantages over XS-...? All things being
equal, if both helpers support a common method for this I think we should
Le mardi 08 septembre 2009 à 09:35 -0400, Scott Kitterman a écrit :
Does pyversions offer any real advantages over XS-...? All things being
equal, if both helpers support a common method for this I think we should
just use it.
The advantages are cosmetic. And as already explained, this is
On Tue, Sep 8, 2009 at 1:00 PM, Steve Langasekvor...@debian.org wrote:
Twas brillig at 02:42:09 08.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL Spare me your ignorant preaching and go read the mailing list
SL archives.
Mailing list archives are not documentation.
Le mardi 08 septembre 2009 à 21:50 +0700, Mikhail Gusarov a écrit :
Twas brillig at 16:42:41 08.09.2009 UTC+02 when pi...@debian.org did gyre and
gimble:
PO I.e. using build dependencies to determine[1] requested Python
PO versions. Joss mentioned it on #debian-python recently so I guess
On Tue, 08 Sep 2009 17:48:18 +0200 Josselin Mouette j...@debian.org wrote:
Le mardi 08 septembre 2009 à 21:50 +0700, Mikhail Gusarov a écrit :
Twas brillig at 16:42:41 08.09.2009 UTC+02 when pi...@debian.org did gyre
and gimble:
PO I.e. using build dependencies to determine[1] requested
Le mardi 08 septembre 2009 à 19:06 +0200, Piotr Ożarowski a écrit :
Since the build-dep approach should have agreement from all the helper
maintainers before it moves forward, I think it would be a good first
step to mark pyversions deprecated (initially in favor of XS-* and
later in
[Josselin Mouette, 2009-09-08]
I think that’s the most efficient approach indeed. For that, we need to
either:
* patch /usr/bin/pyversions to use them instead
I will create a patch next week (my TODO list is too long to do it sooner)
and will try to convince Matthias to apply it.
--
On Tue, 8 Sep 2009 19:06:17 +0200 Piotr O|arowski pi...@debian.org wrote:
...
how about using build dependencies *if* pyversions and XS-P-V are not
set and removing support of these fields once all packages will
use the new approach?
Seems reasonable.
Scott K
--
To UNSUBSCRIBE, email to
On Tue, 08 Sep 2009 19:19:12 +0200 Josselin Mouette j...@debian.org wrote:
Le mardi 08 septembre 2009 à 19:06 +0200, Piotr O|arowski a écrit :
Since the build-dep approach should have agreement from all the helper
maintainers before it moves forward, I think it would be a good first
step
On Tue, Sep 8, 2009 at 6:45 PM, anatoly techtonik techto...@gmail.com wrote:
Mailing lists are not documentation. Wiki is some kind of docs, but it
still bears a high degree of uncertainty.
This is missing the point. The original point of contention was
whether or not certain communication
28 matches
Mail list logo
