On Tue, 28 Mar 2017, Ghislain Vaillant wrote: > On 28/03/17 10:37, Andreas Tille wrote: > > PS: Yaroslav, you know my opinion about using Vcs outside of debian.org and > > deriving from policies that are widely established. Currently > > git://github.com/neurodebian/pandas.git > > is not even featuring the latest uploads - last changelog entry is
> > pandas (0.19.2-2) unstable; urgency=medium > > * Exclude a number of tests while running on non-amd64 platforms > > due to bugs in numpy/pandas > > -- Yaroslav Halchenko <[email protected]> Wed, 11 Jan 2017 12:13:05 > > -0500 > > I'm sorry to repeat myself but you are not creating a welcoming > > environment for people who intend to help. > This sentiment is shared on my side too. > It was very disappointing to discover that nipype will not be part of > Stretch due to an RC, which looks like many of those the team fixed during > the Numpy 1.12 migration [1]. Besides, the packaging repository is quite > frankly a mess [2] and is outdated. > Looking at the other packages maintained by NeuroDebian and affected by RCs > [3] (which include nipy, dipy and pandas), the repository layout is > inconsistent from one package to the next [4, 5, 6]. IMO, as an experienced > packager who has contributed to many different teams, this completely > cancels out the benefits of having packages team-maintained in the first > place. > I am wondering whether NeuroDebian should instead be focusing on maintaining > high-quality backports of neuroimaging software for supported Debian and > Ubuntu releases (a goal it currently fulfills very well), and leave the main > packaging effort to other Debian packaging teams (Science, Med, Python...). I will try to be short - I have already stated many times that if you want to move any of the core packages under bigger (-med, -science, etc) maintenance -- I don't mind. But it shouldn't complicate my own work on those packages. Someone's "mess" might as well be my "consistency" and I often can't afford spending time figuring out how this are now. And even worse time "fixing" up packaging (e.g. re-enabling testing, re-introducing dropped patches, etc) to make it as "messy" as it was before ;) - so far I still see only myself as the one who took care about pandas even after I cried out loud for help. So helping instead of complaining (again) would be more helpful (I started reading this with an idea that we are talking about tzdata issue, but apparently we are just making water harder) - regarding original tzdata issue -- since we are just expressing sentiments here -- it would have been cool if maintainers of core packages would do 'reverse depends testing' before uploading (as I am trying to do in such cases) so we stop running after a gone train [see e.g. our ad-hoc messy helper https://github.com/neurodebian/neurodebian/blob/master/tools/nd_build_testrdepends which I usually use successfully when preparing next uploads for cython, nibabel, etc] - outdated (not pushed) git on github or alioth is all the same -- just me forgetting to push. "Fixed now" (thanks) - and present on both github and alioth git://git.debian.org/git/pkg-exppsy/pandas.git Thanks in advance for your help! -- 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
