Bug#918206: Pandas

[Yaroslav Halchenko]

On Wed, 27 Feb 2019, Andreas Tille wrote:

> Dear Rebecca,

> On Wed, Feb 27, 2019 at 07:25:26AM +0000, Rebecca N. Palmer wrote:
> > On 27/02/2019 07:00, Andreas Tille wrote:
> > > Dear Rebecca,
> > > I do not think that there is any
> > > need for a separate branch.  Just stick to the debian branch.

> > It's needed because the debian branch contains the attempt at packaging 0.24
> > described earlier in this thread, which it's now too late for.

> You are right.  Considering the branching jungle (Yaroslav, could you possibly

for someone jungle is a sweet sweet home! ;)

	$> git br -a | grep salsa | grep -e bf- -e enh- -e cythoned | while read b; do git push salsa :${b//*salsa\//}; done
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             __tent/debian-cythoned-quilt
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             bf-cython
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             bf-i386
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             bf-native-endianness
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             bf-skips
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             bf-unser
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             bf-versions-etc
	To salsa.debian.org:science-team/pandas.git
	 - [deleted]             enh-tests-compat-pytables-2.1

and will try to not forget to not push them again ;)

	$> git br -a | grep salsa # -- with my annotations
	  remotes/salsa/master     -- some upstream's point of master -- could also be removed if you like
	  remotes/salsa/releases   -- linear progression of upstream releases
	  remotes/salsa/debian     -- sits on top of releases and carries packaging
	  remotes/salsa/debian-experimental -- the one for uploads to experimental

better now?

> cleanup branches that are not used any more?) I'd prefer if you would move the
> 0.24 packaging to some separate branch (debian-experimental is covered but may
> be debian-0.24 or something like this?) and keep branch debian for what we are
> really releasing.

well "releasing" is a loaded term. I guess you are talking about uploading to
unstable so it manages to get into buster.  Since "debian" branch already got
its 0.24, what about starting debian-buster branch off debian/0.23.3-1 ?

otherwise -- I am ok to hard-reset and force push debian to the debian/0.23.3-1
state -- everyone should just beware of it, and then progress
debian-experimental to current state of debian (v0.24.1-972-g1cfbd07c7)

your call

> Thanks again for your work on this

yeap, Thank you Rebecca!

-- 
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