On Tue, May 20, 2008 at 10:46:33PM +, Ben Finney wrote:
> Pierre Habouzit <[EMAIL PROTECTED]> writes:
>
> > On Tue, May 20, 2008 at 10:59:05AM +, Ben Finney wrote:
> > > What makes you think 'foo.pyc' is /var material?
> >
> > Oh
On Tue, May 20, 2008 at 10:59:05AM +, Ben Finney wrote:
> Pierre Habouzit <[EMAIL PROTECTED]> writes:
>
> > On Mon, May 19, 2008 at 11:20:10PM +, Ben Finney wrote:
> > > Floris Bruynooghe <[EMAIL PROTECTED]> writes:
> > > > "/var/lib :
ous things in the first place. pysupport is forward compatible with
such a possible change in python, it would _just need_ to stop doing its
symlink farm and keep byte compiled stuff in /var/lib like it does right
now.
--
·O· Pierre Habouzit
··O
On Tue, May 20, 2008 at 07:55:44AM +, Emilio Pozuelo Monfort wrote:
> Pierre Habouzit wrote:
> > This is _wrong_ to put XB-PV: 2.4, 2.5 for an arch:all package, this
> > should be XB-PV: all or something similar.
>
> Even if you package doesn't work with some suppo
ner in XS-P-V, _AND_ the maintainer to build what he claimed to
have built, which may differ, which is brittle. pysupport just looks at
what has been built and computes things from that only, which is way
more robust, because information exists in a single place.
--
·O· Pierre Habouzit
··O
On Mon, Jan 07, 2008 at 05:52:52PM +, Vincent Bernat wrote:
> OoO Pendant le temps de midi du lundi 07 janvier 2008, vers 12:50,
> Pierre Habouzit <[EMAIL PROTECTED]> disait:
>
> >> > Le lundi 07 janvier 2008 à 07:56 +0100, Vincent Bernat a écrit :
> >
dh_pysupport before dh_installinit, the prerm will first stop the
> init
> > script and then remove the python files.
>
> Good news. I will check that it works and propose to close the bug I cited
> in another message.
It does work.
--
PROTECTED]
>
>
> Hi,
> I was surprised to find python2.{4,5}-doc in contrib and wondered why?
it needs latex2html to build.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madis
nse to stay like that, and an NMUer that does 10 of those in a
round may miss the reasons. I'd rather see a mass bug filling on those
packages, and see the maintainers that feel their package should be
built for one version only say it loud first.
Then maybe we will consider making it RC.
--
·
should work well.
yes, for some packages it makes sense, Joss didn't asked for an empty
list, merely a shorter one, and I agree with him.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpH9Vodhz2uc.pgp
Description: PGP signature
u put your installed files as it won't
be able to guess it, that's all.
> has anyone already looked into trac plugins? what is the best way to
> handle these?
IMHO you should rather contact the trac maintainer on this issue, as
he should be the one havin
On Tue, May 01, 2007 at 12:17:33AM +0100, Floris Bruynooghe wrote:
> Hi
>
> On Wed, Mar 28, 2007 at 08:39:42PM +0200, Pierre Habouzit wrote:
> > wrt the "current" thingie, I may have a proposal ready soon, I just
> > need to polish the details, and look how "
ot;hard" it would be to upgrade
the dh_py* tools to them. Well, I've a hard week of paid work ahead, so
I don't expect to have it ready before next week.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgp7rR0AyoICF.pgp
Description: PGP signature
On Fri, Mar 23, 2007 at 06:47:03PM +0100, Piotr Ożarowski wrote:
> [Pierre Habouzit, 23.03.2007]
> > On Fri, Mar 23, 2007 at 05:08:22PM +0100, Josselin Mouette wrote:
> > > Le vendredi 23 mars 2007 à 13:40 +0100, Piotr Ożarowski a écrit :
> > > > XB-Python-Typ
ne any proposal yet, because the problem does
not look obvious in the first glance.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgp4HR7FdPPua.pgp
Description: PGP signature
packages as pbuilder/debuild/...whatever are more
clever about that.
So there is no way to deal with packages that only support "future"
python versions yet. Though I expect it to concern only a few packages
that will need a sourcefull upload to migrate to a scheme where they
support the policy.
Your B-D + XS-P-V hack only works with brittle side effects, and for
arch:all packages, that are not subject to binNMUs anyway (at least not
untill we have arch:all buildd's).
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpomRVOLK4RV.pgp
Description: PGP signature
On Thu, Mar 22, 2007 at 10:13:40PM +0100, Piotr Ożarowski wrote:
> [Josselin Mouette, 22.03.2007]
> > Le jeudi 22 mars 2007 à 19:56 +0100, Pierre Habouzit a écrit :
> > > > Just nitpicking: the dh_ tool doesn't need to know that, as it can guess
> > > > it fro
On Thu, Mar 22, 2007 at 07:50:35PM +0100, Josselin Mouette wrote:
> Le jeudi 22 mars 2007 à 14:50 +0100, Pierre Habouzit a écrit :
> > exactly, putting current is just yet-another-place where the
> > maintainers declares that he will only prepare the package for "current&quo
On Thu, Mar 22, 2007 at 01:36:08PM +0100, Piotr Ożarowski wrote:
> [Tristan Seligmann, 22.03.2007]
> > * Pierre Habouzit <[EMAIL PROTECTED]> [2007-03-21 21:49:00 +0100]:
> > > On Wed, Mar 21, 2007 at 09:25:52PM +0100, Piotr Ożarowski wrote:
> > > > it's
On Thu, Mar 22, 2007 at 12:53:27AM +0100, Piotr Ożarowski wrote:
> [Pierre Habouzit, 22.03.2007]
> > On Thu, Mar 22, 2007 at 12:23:59AM +0100, Piotr Ożarowski wrote:
> > > * set XB-Python-Version to "current, >2.5" # here "current" can't be
> &
On Wed, Mar 21, 2007 at 04:50:30PM -0700, Steve Langasek wrote:
> On Thu, Mar 22, 2007 at 12:05:30AM +0100, Pierre Habouzit wrote:
> > On Wed, Mar 21, 2007 at 03:51:20PM -0700, Steve Langasek wrote:
> > > On Wed, Mar 21, 2007 at 11:16:14PM +0100, Pierre Habouzit wrote:
> &
ded in that case, even if pyversions -s
changes.
> case 4:
> * as above, binNMU needed
> * XB-Python-Version: >=2.4
> * Provides: python2.4-wavelets
no binNMU is needed here either for a default python change. It is
recommended for a python version removal (to avoid to waste space) and
needed for the introduction of a new python (to support the new one).
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpz9r8cZemBg.pgp
Description: PGP signature
On Wed, Mar 21, 2007 at 03:51:20PM -0700, Steve Langasek wrote:
> On Wed, Mar 21, 2007 at 11:16:14PM +0100, Pierre Habouzit wrote:
> > If we don't, I don't see the purpose of the policy alltogether.
>
> Allowing transitions between default versions of python without pac
t be installed at the same time. In that case, well, I don't
really know what to say. Having two things not really the same called
the same suck. I hardly see someone fork the openssl and say that the
new lib would be called libssl too. That would
> > Do I understand that we can drop all the multi-version stuff now?
>
> Who's "we"?
Please (and it's meant as much to both of you) that part of the thread
is going nowhere useful. We can avoid this easily, shall we ?
--
·O· Pierre Habouzit
··O
llow the spirit of the "new" (that is not so new
right now ;p) policy. So here current seems if not broken, nor
useless, at least against the idea of the policy.
Is there anything that I miss with those explanations ?
--
·O· Pierre Habouzit
··O
On Wed, Mar 21, 2007 at 10:38:30PM +0100, Piotr Ożarowski wrote:
> [Pierre Habouzit, 21.03.2007]
> > On Wed, Mar 21, 2007 at 09:25:52PM +0100, Piotr Ożarowski wrote:
> > > it's useful for Python applications that need specific Python version.
> > >
> > >
On Wed, Mar 21, 2007 at 09:25:52PM +0100, Piotr Ożarowski wrote:
> [Pierre Habouzit, 21.03.2007]
> > On Wed, Mar 21, 2007 at 08:28:47PM +0100, Piotr Ożarowski wrote:
> > > "current" keyword is deprecated? Why? I'm using it a lot and I like
> > > it...
&g
ing it for exactly ? I mean, please give an example,
with an actual package, that would be okay. Because I'm 100% sure that
current is (1) not a good idea (2) not needed in fact.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOO
(from python-support). (or
dh_pycentral from python-central). python-support comes with a very
friendly documentation in /usr/share/doc/python-support/README.Debian to
help you through python packaging.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgptc4dXk9fnl.pgp
Description: PGP signature
/.pyo
alongside the files for public modules but parallel to the install, e.g.
in /var/lib/python/pyc2.4/. what's crappy is the necessity for the .pyc
to be in the exact same directory than the .py (or a symlink to it).
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgp9YXhqiQrdS.pgp
Description: PGP signature
needs to, having run hg as root is enough to produce the
*.pyc if your package (even against the previous policy) did not managed
them.
To Wouter: to resolve your problem, just rm -rf
/usr/lib/python*/site-packages/mercurial. You can do that safely,
that'll solve your problem.
Cheers,
--
er too)
from the postinst. you will be able to drop that upgrade stanza
after the etch release.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpOMFfbQ8ARu.pgp
Description: PGP signature
ython/debian_defaults
Not sure what has to be done though to force the byte compilation and
links creation for the pure modules, and that won't compile binary
extention either anyway (but maybe pygtk already forces it I don't know
I shall say, I've not checked).
--
·O· Pier
rl -sPackage -FDepends python2.3
is your friend.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpNvN1WXBcfv.pgp
Description: PGP signature
again unlike me)?
with the autotools, to chose the python version you build for, you just
need:
PYTHON=pythonX.Y ./configure .
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgphG0gflqbJW.pgp
Description: PGP signature
Le ven 8 septembre 2006 14:51, Ludovic Rousseau a écrit :
> Le 07.09.2006, à 16:55:59, Pierre Habouzit a écrit:
> > # sorry pal, but such a bug renders the package completely
> > unusable, and # is also a policy violation.
>
> Why is the package completely unusable? I just s
n the preinst of
your package.
2. and then make it comply with the new policy, using dh_pysupport or
dh_pycentral that will take care of the byte-compilation of your
package, and the transitions also.
wich seems to be already done.
--
·O· Pierre Habou
Le lun 28 août 2006 12:27, Josselin Mouette a écrit :
> Le lundi 28 août 2006 à 09:12 +0200, Pierre Habouzit a écrit :
> > While working on the tool I promised I'll work on, I indeed agree
> > that the debian/pyversions beeing hidden is a major PITA.
>
> I'
Le lun 28 août 2006 09:12, Pierre Habouzit a écrit :
> so to me, the harm looks quite small, given the fact that my
> current experiments show that only a few packages do have an upper
> bound, and do not use XS-P-V already.
the list of suck packages (run on a fresh local miror) i
e on the
buildds. The lower bound is less useful as we should almost never
donwgrade the default python, or reintroduce lower python versions.
so to me, the harm looks quite small, given the fact that my current
experiments show that only a few p
Le sam 26 août 2006 00:39, Pierre Habouzit a écrit :
> Le ven 25 août 2006 22:26, Josselin Mouette a écrit :
> > Le vendredi 25 août 2006 à 13:09 -0700, Steve Langasek a écrit :
> > > I object to basing future work exclusively on dh_pysupport as
> > > long as it implemen
U candidates.
>
> What if I provide you with a script that does the same without the
> fields?
I will do that, I've promised it. I've had a hell of a week, but I will
work on that this week.
--
·O· Pierre Habouzit
··O[
ythonX.Y you should just B-D on
pythonX.Y-dev, if you build for current on python-dev, if you do a
multi-build you should use python-all-dev.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgp6dhSCgeDIt.pgp
Description: PGP signature
epend upon, you magically switch to a package built for
current. Though, I really think such packaging methods are
harmful, and that the python2.4-that-is-out-since-years should
not happen again thanks to the new policy, so that we can assume
that only
Le lun 21 août 2006 03:53, Russ Allbery a écrit :
> Pierre Habouzit <[EMAIL PROTECTED]> writes:
> > python-support is written in python (same is true for
> > python-central) and will *always* depend upon 'python'
>
> Maybe some examples to illustrate will help
a Python interpreter, that should be added to its long description so
> that there's documentation that this is an invariant and a promise
> that won't be changed later.
python-support is written in python (same is true for python-centra
s is not added.
lintian has to be fixed in that regard.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgp5lzVVNhHbb.pgp
Description: PGP signature
added or removed?
actually,it's not truly needed, it's needed iff a package do needs the
new provides or not.
and those reuploads are kind of binNMUs, the real problem here is that
tehre is no arch:all binNMU and maybe that's here the problem that need
fixi
e pre-installation phase of the python package, the
> > package supplied scripts are called with the parameter:
> > pre-rtupdate
> >
> > A failure in any script results in the failure of the
> >pre-installation script of the python package.
> >
/usr/lib/games/$pkg and /usr/share/games/$pkg. If he
finds a .so in there, he uses objdump to find out if the .so is python
related or not, and acts accordingly.
It just dont need current/current_ext at all, and uses different
implementations choices. that's all.
--
se the
common from vanilla python for the rest.
If that can work, I don't see any reason to refuse packaging stackless
(if anybody step up to do that btw).
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOO
ss python. At
least, it does not sounds horrible, one has to give it a try I'd say.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgp9CrK2xGsXp.pgp
Description: PGP signature
s been
built for python2.4 and python2.5. When you track transitions, that's
all the information you need to know.
but current as a XS-P-V is IMHO not correct, and that has been explained
in my mail, and in Manoj doc with very good arguments.
--
·O· Pierre Habouzit
··O
on.com/software/manoj-policy/
very nice. I'm going to review it comparing it with the initial python
policy by J.Wreschnig so that I'm sure we have not left anything apart,
or contradicted vital points.
Cheers,
--
·O· Pierre Habouzit
··O
Le mar 8 août 2006 00:18, Pierre Habouzit a écrit :
> § 2.3.3, 2.4.2, 2.5.3, 2.6.2:
> *here* the python$version alternative is correct,
> because /extensions/ can be used with a '/usr/bin/python' as soon
> as the python current version is in their supported range.
>
t;
> which works in principle but I wonder if there is some other
> reasonable way.
pyversions -vd will answer the short versions (2.3 today)
pyversions -d will answer python2.3
pyversions -s / -vs do the same with the supported versions.
It i
central implementation choice)
You should also mention that a package that mixes many of the previous
items *SHOULD* depend of all the pythonX.Y from the (1) clauses, and
the smallest range obtained from the (2)'s. and a
python (>= X.Y) | p
Le mer 2 août 2006 20:09, Iustin Pop a écrit :
> On Wed, Aug 02, 2006 at 08:02:05PM +0200, Pierre Habouzit wrote:
> > Le mer 2 août 2006 19:51, Iustin Pop a écrit :
> > > On Wed, Aug 02, 2006 at 07:42:40PM +0200, Pierre Habouzit wrote:
> > > > and the pyo and pyc fil
Le mer 2 août 2006 19:51, Iustin Pop a écrit :
> On Wed, Aug 02, 2006 at 07:42:40PM +0200, Pierre Habouzit wrote:
> > and the pyo and pyc files are generated by your build process. you
> > have to remove them manually, e.g. using some find -name '*.pyo'
> > mant
e
to remove them manually, e.g. using some find -name '*.pyo' mantra.
there should be no .pyo/.pyc in the packages you build, those are
created by pycentral at postinst / prerm time of your package, thanks
to debhelper magic.
--
·O· Pierre Ha
advertising, but exists.
[1] http://bugs.debian.org/from:[EMAIL PROTECTED]
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpStUj93TdFU.pgp
Description: PGP signature
ll be announced and coordinated with the RM
team).
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpYXThd7cENR.pgp
Description: PGP signature
ther
> hints for me?
python people usually use restructured text. it depends what you want to
do exactly, and what the users of that syntax are likely to be able to
learn ;)
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOO
ython2.4-foo. So, if the script uses a non
> default version of python, or the extension module was compiled for
> a non-default version of python, I must provide pythonX.Y-fooin case
> someone somewhere has a script calling a specific version
Le lun 24 juillet 2006 19:52, Adeodato Simó a écrit :
> * Pierre Habouzit [Mon, 24 Jul 2006 17:11:14 +0200]:
> > just FYI, it's not mandatory [XB-Python-Version], one can use
> > debian/pyversions instead (with python-support).
>
> Hm. I can see how debian/pyversion
field `Python-Version'
> > ...
> >
> > What effect does this have? Can the .deb be used or not?
>
> It's harmless, though perhaps a pity that the python maintainers
> decided on this ugly solution.
just FYI, it's not mandatory, one
as said, not knowing the package, I don't know how stable the more
recent upstream releases are, and can't take such a decision.
Cheers,
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpq4fjTi3Akf.pgp
Description: PGP signature
Le sam 1 juillet 2006 00:19, Pierre Habouzit a écrit :
> Le ven 30 juin 2006 21:03, Vincent Danjean a écrit :
> > Hi,
> >
> > I'm converting one of my package (commit-tool) to the new policy.
> > I was thinking it will be easy, but I found several difficulties
stall
the package, and if there is private modules, pass it to
dh_py{central,support}.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpKPFWOA2FoU.pgp
Description: PGP signature
Le jeu 29 juin 2006 16:37, Sam Morris a écrit :
> On Thu, 29 Jun 2006 16:25:17 +0200, Pierre Habouzit wrote:
> > Le mer 28 juin 2006 23:20, Raphael Hertzog a écrit :
> >> So you don't have any excuse to not update your packages any more.
> >> About 60% of the
.
7 other person like me, and it's old story !
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpcBRpNK6Eec.pgp
Description: PGP signature
he packages using an obsolete dh_pyton compat
level is indeed easy to find. hence I do think it's a better idea than
the XS-P-S-V.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpAEjCGEebZ9.pgp
Description: PGP signature
Le jeu 15 juin 2006 13:36, Piotr Ozarowski a écrit :
> Pierre Habouzit ([EMAIL PROTECTED]):
> > well the thing is there is no way to track all the packages that
> > *have* to follow the python subpolicy, and that makes the work of
> > tracking them for transition harder.
&g
Le jeu 15 juin 2006 10:50, Piotr Ozarowski a écrit :
> Pierre Habouzit ([EMAIL PROTECTED]):
> > I'd like to suggest a last minute amendment to the Python Policy,
> > that would help further transitions a lot. I'd suggest that
> > packages uses a XS-Python-Stan
ion has very few users. Building
> the module code twice, and making the package hard to backport to
> stable, is enough of a pain to make it reasonable to ask what benefit
> these users will get in return.
please follow-up on debian-python@
--
·O· Pierre Habouzit
··O
help
here) to use a:
XS-Python-Standards-Version: 0.4
to specify the python policy the package is conforming to. that would
help transitions a lot, and help to keep track of future transition
statuses.
comments ?
--
·O· Pierre Habouzit
··O[
http://people.debian.org/~hertzog/python/sources-by-maint
> >
> > Pierre Habouzit (Madcoder) did the mass-bug filing:
> > http://bugs.debian.org/submitter:[EMAIL PROTECTED]
> >org http://bugs.debian.org/usertag:debian-python@lists.debian.org
> >
> > And a wi
ility problems,
if the latter it will hide problems like the one above.
Is there anything planned to address that ?
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgprv4GVGAVi4.p
i?tag=policy;[EMAIL PROTECTED]
adding a ;pend-exc=done gives a good list of what the TODO is ;)
Cheers,
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpFXRFwUHgYp.pgp
Desc
Le Dim 9 Avril 2006 19:56, Pierre Habouzit a écrit :
> Le Dim 9 Avril 2006 14:18, Kurt Roeckx a écrit :
> > On Fri, Apr 07, 2006 at 09:47:25PM +0200, Pierre Habouzit wrote:
> > > what's the policy about them ?
> > >
> > > should the packages be built fo
.
Ubuntu does not AFAICT the same size requirements as debian do for base,
and I really think that python upstream can understand that the *full*
python suite on a embeded device just does not makes sense.
To me, this looks like a bad excuse.
--
·O· Pierre Habouzit
··O
82 matches
Mail list logo
