ok, you can delete the empty repo.
Thanks
schrieb am Mi., 8. Juli 2020, 18:21:
> Hello,
>
> On Sun, 5 Jul 2020 15:31:55 +0200 Andreas Tille
> wrote> Uploaded. Unfortunately I realised to late that the python3-*
> > dependencies are not resolved automatically. I've added these manually
> > in
Hello,
On Sun, 5 Jul 2020 15:31:55 +0200 Andreas Tille
wrote> Uploaded. Unfortunately I realised to late that the python3-*
> dependencies are not resolved automatically. I've added these manually
> in Git and will upload with the source-only upload that is needed after
> the package is accepte
On Mon, Jul 06, 2020 at 10:00:38AM +0800, zhao feng wrote:
> > Uploaded. Unfortunately I realised to late that the python3-*
> > dependencies are not resolved automatically. I've added these manually
> > in Git and will upload with the source-only upload that is needed after
> > the package is ac
Thanks a lot!
> Uploaded. Unfortunately I realised to late that the python3-*
> dependencies are not resolved automatically. I've added these manually
> in Git and will upload with the source-only upload that is needed after
> the package is accepted.
To run the unittest we need some more depen
On Sun, Jul 05, 2020 at 07:49:41PM +0800, zhao feng wrote:
> I have enabled the pipeline in one fork
> https://salsa.debian.org/zhaofeng-shu33-guest/python-ete3/-/pipelines/153000
> and I think the build error does not exist any more.
Yes, I've uploaded now.
> > Finally I'm wondering whether the
Got it, thanks!
I have enabled the pipeline in one fork
https://salsa.debian.org/zhaofeng-shu33-guest/python-ete3/-/pipelines/153000
and I think the build error does not exist any more.
> I also thin checking the DeprecationWarnings might be worth investigating.
This may be related with some upst
6 matches
Mail list logo
