Hi Yaroslav,
On Mon, Sep 10, 2018 at 09:39:38PM +0200, Andreas Tille wrote:
> On Mon, Sep 10, 2018 at 11:44:00AM -0400, Yaroslav Halchenko wrote:
> >
> > > ... sorry to repeat myself but having team maintained packages on
> > > github is not inviting to others. Is there any reason not to
> > > use Salsa?
> >
> > yeap, let's make a repo on salsa. Would you be ok to retain my weird
> > "based on upstream git" setup?
>
> https://salsa.debian.org/science-team/scikit-learn
>
> (I did so about one year ago but you decided to stay on Github.
> I removed the old repo and injected what I cloned this morning
> and added a pristine-tar branch. I volunteer to do it even
> a third time but not more. ;-) )
I have not seen any commits of yours in the new repository. Did I
understood correctly that you have some pending changes you want to
push?
> Hope this helps and thanks for caring for the package. I agree that
> packaging the new upstream version is probably the best strategy if
> it is in the not too distant future (= we will not loose all the
> rdepends from testing)
I realised that the releases at Github are not tagged reliably (not even
the current release is tagged there). Thus I pointed d/watch to pypi
and also used Files-Excluded to strip joblib from upstream source.
When you talked about new upstream version: Do you want to give 0.20rc1
a try or do you want to wait for 0.20?
Kind regards
Andreas.
--
http://fam-tille.de
