Yesterday, a last round of bugs has been filled against packages that
may need an upgrade to comply with the recent python policy[1].
Some developpers have raised concerns directly to me about the 0-day NMU
policy warning in that report.
This § has been added because /usr/bin/python beeing
Le mer 2 août 2006 11:23, Loïc Minier a écrit :
- status of the transition Wiki page: a summary of steps which are
in progress (pointer to python transition pseudo-bug, pointers to
the list of bugs to be fixed in the mass bug filing, description of
the step)
that could have been
On Wed, Aug 02, 2006, Pierre Habouzit wrote:
that could have been more clear, but I do have such tools to follow the
transition, I use[1]. The two rounds of mass bug have been package that
build public modules and extensions, and then all the other ones (+
some missed one at the first
Le mer 2 août 2006 12:37, Sven Hoexter a écrit :
Hello,
I've been working on the lyx package to get it in a state complying
with the new python policy.
LyX generates some .pyc and .pyo files during build time and I'm not
sure what to do with them because I thought that the dh_pycentral
call
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 files are generated by your build process.
5 matches
Mail list logo