nomeata at debian.org
Fri Jan 2 11:50:18 UTC 2009
[About uploading a work-around python-evas to the pkg-fso repository]
Am Freitag, den 02.01.2009, 14:20 +0300 schrieb Nikita V. Youshchenko:
> > i'd say: not going to happen.
> > - my package is not an official one
> > - cython is at 0.10 already
> > - the issue itself is not fixed
> > - building a recent python-evas against an old cython is nothing but a
> > hack/workaround
> It may make a month or so until updated eina and evas will pass NEW.
> I think it is better to have your package at pkg-fso than have broken
> system during all that time.
There is another possibility: Get a new python-evas package in shape and
put it in NEW. Until it is through there, we put all the libe* and
python-e* package that are waiting in NEW in the pkg-fso repository. I’d
prefer this, as it would allow me to go ahead with the packaging of SHR.
But if this can’t happen in, say, a few days (at least with a package
that is “okish”), we (well, I :-)) should indeed upload a workaround
Albin, how much work is it to have a usable, not necessary perfect,
python-e* package set?
Joachim "nomeata" Breitner
nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-e-devel/attachments/20090102/360eb623/attachment.pgp
More information about the Pkg-e-devel