> >standard enough IMO, people should know how to use it.
> I prefer to address all lintian warnings since it makes things cleaner
> in the long run... yes I can read Build-Depends to discover dependency
> on quilt and figure out how it works by browsing the web (yes I do not
> use quilt on reg
First of all -- Thanks!
On Mon, 23 Nov 2009, Cyril Brulebois wrote:
> - The best way to contribute is to send patches against current
>packaging, be it against the latest versions in the archive, or
>against the current git repository. “debcheckout $pkg” is your
>friend to fetch it if
Yaroslav Halchenko (14/10/2009):
> Updated packaging is ready (see attached)
Some remarks about your patch:
- The best way to contribute is to send patches against current
packaging, be it against the latest versions in the archive, or
against the current git repository. “debcheckout $pkg”
tag 549996 pending
thanks
Yaroslav Halchenko (21/11/2009):
> FWIW -- AFAIK upstream has finalized all the changes they have
> planed.
>
> Last revision from 6th of Nov (2 weeks ago) 1492: passes all
> unittests.
Nice, updating packaging. Expect it soonish.
Mraw,
KiBi.
signature.asc
Descripti
FWIW -- AFAIK upstream has finalized all the changes they have planed.
Last revision from 6th of Nov (2 weeks ago) 1492: passes all unittests.
Would you be kind to either upload current trunk of networkx into
Debian? If I hear no objects I would proceed with NMU to 2-days delayed
queue within 2
Hi Cyril,
Any luck? FWIW the failed doctest was fixed in SVN, so it passes all
unittests now... developers are just twisting their heads about making a
decision for remove_edge (or whatever it is called) destiny. But as far
as I see, it is in a good state to be uploaded into debian as some
1.0rc
Yaroslav Halchenko (14/10/2009):
> Updated packaging is ready (see attached)
Hi,
thanks! I hoped to tackle it last weekend, but apparently failed. :(
I'll try and give it a shot in the next days, probably through
experimental, which should be sufficient for you since you have to go
through NEW I
Updated packaging is ready (see attached) but there is an issue with
this rc1:
rc1 -- .test() crashes python ;)
current svn trunk (rev 1479) has 2 doctests failing. Usually doctests
is the least of the worries but... I emailed upstream
to address the issue so current head could be uploaded into
8 matches
Mail list logo
