Bug#948372: Please push your changes to nibabel
On Mon, 20 Jan 2020, Andreas Tille wrote: > On Mon, Jan 20, 2020 at 01:01:00PM -0500, Yaroslav Halchenko wrote: > > > I'm fine with re-doing what I changed if you consider it really of > > > practical relevance. If you ask me we two would spent time we could > > > use more productively but its OK if you want to do it. > > You just rename and I will do the rest (push your pristine-tar, align > > branches properly). then debcheckout should work for old people (if > > gitlab redirects correctly as github does in such cases), and you could > > proceed with your work ;) > Just ping me if you are done. Next time I should try to move first. :-) I guess we got some communication disconnect... anyways -- since I have needed super-powers in debian-med I did the move myself: - changed name and adjusted path for yours to become https://salsa.debian.org/med-team/nibabel-andreas - went to https://salsa.debian.org/neurodebian-team/nibabel and in Settings -> General -> Advanced -> Transfer to Debian Med to get https://salsa.debian.org/med-team/nibabel - verified -- debcheckout nibabel does the right thing, all the way from original elderly https://salsa.debian.org/neurodebian-team/pynifti.git redirecting to https://salsa.debian.org/med-team/nibabel - did following dance (extracting from bash history): git remote add --fetch andreas https://salsa.debian.org/med-team/nibabel-andreas git co --track andreas/pristine-tar git push salsa -u pristine-tar git co upstream git push salsa -u upstream git co master git reset --hard andreas/master git push salsa -u master I think that should do it. Please let me know if nothing is forgotten, and then we could remove nibabel-andreas, and I would remove andreas remote ;) after above I did debcheckout nibabel to see that it checks out old dist/debian/proper which is unavoidable since it is what was in Vcs fields. But I guess whenever you upload new version with new Vcs -- all should work standard ways PS note that nibabel is the core library for many python neuroimaging toolkits. Typically before uploading it I was running our https://github.com/neurodebian/neurodebian/blob/master/tools/nd_build_testrdepends to see what next nibabel possibly breaks for other toolkits. I see that I haven't done that for 3.0.0 yet, which IIRC did break API, so I expect surprises to come with 3.0.0 upload Cheers and thanks! -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#948372: Please push your changes to nibabel
On Mon, Jan 20, 2020 at 01:01:00PM -0500, Yaroslav Halchenko wrote: > > > I'm fine with re-doing what I changed if you consider it really of > > practical relevance. If you ask me we two would spent time we could > > use more productively but its OK if you want to do it. > > You just rename and I will do the rest (push your pristine-tar, align > branches properly). then debcheckout should work for old people (if > gitlab redirects correctly as github does in such cases), and you could > proceed with your work ;) Just ping me if you are done. Next time I should try to move first. :-) Kind regards Andreas. -- http://fam-tille.de
Bug#948372: Please push your changes to nibabel
On Mon, 20 Jan 2020, Andreas Tille wrote: > > so I should be able to transfer over to debian-med. May be rename yours > > into nibabel-med-initial so I could do it? > I'm fine with re-doing what I changed if you consider it really of > practical relevance. If you ask me we two would spent time we could > use more productively but its OK if you want to do it. You just rename and I will do the rest (push your pristine-tar, align branches properly). then debcheckout should work for old people (if gitlab redirects correctly as github does in such cases), and you could proceed with your work ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#948372: Please push your changes to nibabel
On Mon, Jan 20, 2020 at 11:20:08AM -0500, Yaroslav Halchenko wrote: > > > I admit I have no idea how I can technically move a repository. Since I > > googled up > https://docs.gitlab.com/ee/user/project/settings/ > > Navigate to your project’s Settings > General > Advanced settings. > Under “Transfer project”, choose the namespace you want to transfer the > project to. > Confirm the transfer by typing the project’s path as instructed. > > so I should be able to transfer over to debian-med. May be rename yours > into nibabel-med-initial so I could do it? I'm fine with re-doing what I changed if you consider it really of practical relevance. If you ask me we two would spent time we could use more productively but its OK if you want to do it. Kind regards Andreas. -- http://fam-tille.de
Bug#948372: Please push your changes to nibabel
On Mon, 20 Jan 2020, Andreas Tille wrote: > Hi Yaroslav, > On Mon, Jan 20, 2020 at 10:50:07AM -0500, Yaroslav Halchenko wrote: > > > I think it would be helpful if you would remove the old repository > > > in neurodebian-team. > > shouldn't I (you) just "move" it on salsa under debian-med and then push > > updated branches? so if anyone clones old url, it would get redirected > > to the new one? > > otherwise I would probably need not just to remove it (imagine ppl doing > > debcheckout on stable debian with older urls) but add some README > > describing the move > I admit I have no idea how I can technically move a repository. Since I googled up https://docs.gitlab.com/ee/user/project/settings/ Navigate to your project’s Settings > General > Advanced settings. Under “Transfer project”, choose the namespace you want to transfer the project to. Confirm the transfer by typing the project’s path as instructed. so I should be able to transfer over to debian-med. May be rename yours into nibabel-med-initial so I could do it? > do not have permission to remove from neurodebian-team I doubt that any > move is possible. Thus I simply forked. I agree with you that it would > be better to inform the user directly. I was simply trusting that any > user of the repository would read out the current Vcs-Git fields from > unstable - but I agree with you that its not sure that every user will > do this. > In any case the old repository is now lagging behind the new one in > med-team. That's the worst situation while your suggestion to simply > drop a README there would be the best. Simply removing it and let users > seek in case they do not find anything is somewhere inbetween those two > situations. ;-) let's try moving first? ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik signature.asc Description: PGP signature
Bug#948372: Please push your changes to nibabel
Hi Yaroslav, On Mon, Jan 20, 2020 at 10:50:07AM -0500, Yaroslav Halchenko wrote: > > > I think it would be helpful if you would remove the old repository > > in neurodebian-team. > > shouldn't I (you) just "move" it on salsa under debian-med and then push > updated branches? so if anyone clones old url, it would get redirected > to the new one? > > otherwise I would probably need not just to remove it (imagine ppl doing > debcheckout on stable debian with older urls) but add some README > describing the move I admit I have no idea how I can technically move a repository. Since I do not have permission to remove from neurodebian-team I doubt that any move is possible. Thus I simply forked. I agree with you that it would be better to inform the user directly. I was simply trusting that any user of the repository would read out the current Vcs-Git fields from unstable - but I agree with you that its not sure that every user will do this. In any case the old repository is now lagging behind the new one in med-team. That's the worst situation while your suggestion to simply drop a README there would be the best. Simply removing it and let users seek in case they do not find anything is somewhere inbetween those two situations. ;-) Kind regards Andreas. -- http://fam-tille.de
Bug#948372: Please push your changes to nibabel
On Mon, 20 Jan 2020, Andreas Tille wrote: > Hi Yaroslav, > On Sun, Jan 19, 2020 at 02:41:52PM -0500, Yaroslav Halchenko wrote: > > actually as far as I see it Sando has pushed everything for > > 2.5.1-2 > > https://salsa.debian.org/neurodebian-team/nibabel/blob/dist/debian/proper/debian/changelog > > which is the latest AFAIK > Ahhh. > > PS I have changed the default branch on salsa to dist/debian/proper to > > match the one we used as one of our utopian plans to stay organized for > > different distributions/releases ;) > OK, I moved the nibabel repository to Debian Med and while doing so I > moved the "interesting" branches to the default layout that is described > in team policy (master, upstream, pristine-tar). I hope I did not > spoiled your utopian plan to much in favour of easier access for all > team members. > I think it would be helpful if you would remove the old repository > in neurodebian-team. shouldn't I (you) just "move" it on salsa under debian-med and then push updated branches? so if anyone clones old url, it would get redirected to the new one? otherwise I would probably need not just to remove it (imagine ppl doing debcheckout on stable debian with older urls) but add some README describing the move -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#948372: Please push your changes to nibabel
Hi Yaroslav, On Sun, Jan 19, 2020 at 02:41:52PM -0500, Yaroslav Halchenko wrote: > > actually as far as I see it Sando has pushed everything for > 2.5.1-2 > https://salsa.debian.org/neurodebian-team/nibabel/blob/dist/debian/proper/debian/changelog > which is the latest AFAIK Ahhh. > PS I have changed the default branch on salsa to dist/debian/proper to > match the one we used as one of our utopian plans to stay organized for > different distributions/releases ;) OK, I moved the nibabel repository to Debian Med and while doing so I moved the "interesting" branches to the default layout that is described in team policy (master, upstream, pristine-tar). I hope I did not spoiled your utopian plan to much in favour of easier access for all team members. I think it would be helpful if you would remove the old repository in neurodebian-team. Kind regards Andreas. -- http://fam-tille.de
Bug#948372: Please push your changes to nibabel
On Sun, 19 Jan 2020, Andreas Tille wrote: > Hi Yaroslav, > can you please push your latest changes to nibabel? I'd volunteer > to fix #948372 and when doing so move the repository to Debian Med > if you do not mind. actually as far as I see it Sando has pushed everything for 2.5.1-2 https://salsa.debian.org/neurodebian-team/nibabel/blob/dist/debian/proper/debian/changelog which is the latest AFAIK PS I have changed the default branch on salsa to dist/debian/proper to match the one we used as one of our utopian plans to stay organized for different distributions/releases ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#948372: Please push your changes to nibabel
Hi Yaroslav, can you please push your latest changes to nibabel? I'd volunteer to fix #948372 and when doing so move the repository to Debian Med if you do not mind. Kind regards Andreas. -- http://fam-tille.de
