Hi Yaroslav, On Thu, Jan 11, 2018 at 10:12:52AM -0500, Yaroslav Halchenko wrote: > Regarding the original report: > > $> grep python-pil debian/control > python-pytest, python-pil | python-imaging, > Recommends: python-pytest, python-pil, python-imaging > > so the only "harm" here is a possible recommends of python-imaging. > IMHO severity is exaggerated.
I agree that it is exaggerated. On the other hand an RC bug requires some action (be it by reseting severity or in this pretty simple case just fixing it). Lots of rdepends got a "removal from testing" warning since nothing happened. > Anyways, I will remove now python-imaging "linkage" altogether since it > seems from http://neuro.debian.net/pkgs/python-openpyxl.html that we build > recent openpyxl only on the systems which already have python-pil, so > backports > shouldn't be harmed at this point. As I said, I volunteer to do it. > On Thu, 11 Jan 2018, Andreas Tille wrote: > > > I assume your aggrement if I do not hear from you in the next 24h hours > > for the following action: > > > If you do not uncover the real Vcs where openpyxl is actively maintained > > I'll create a fresh Git repository using > > > gbp import-dscs --debsnap --pristine-tar openpyxl > > > move the package to Debian Science team on salsa while fixing the bug. > > I'd prefer to move the active Git repository over one via import-dscs, > > thought. > > I am quite confused here > > 1. > (git)hopa:~exppsy/openpyxl[debian] > $> grep Maintainer debian/control > Maintainer: NeuroDebian Team <t...@neuro.debian.net> > > so it is not under Debian Science team maintenance... you are officially > stating that you will hijack the package if we do not reply in 24h? My first mail was 4 days before where I was asking for the VCS. > not nice IMHO... BUT I would appreciate if you do ;) If seen out of historic context not only not nice but inacceptable. >From other packages moved from NeuroDebian to Debian Science I somehow assumed you would be happy if packages that are used by many scientific packages would be moved. Please assume the same for any future case when I suggest to move a package and sorry if my mail was to short in this regard. > the package is of general > interest etc, with only one IF: do not drop Python 2 support until it is a > very strong mandate that we MUST not support python 2. I follow the same strategy to drop Python 2 only if *really* necessary. > Let me know if you would like to do that, then I will leave the removal > of python-imaging for you I'll do. > 2. > hopa:/tmp > $> debcheckout python-openpyxl > declared git repository at git://git.debian.org/git/pkg-exppsy/openpyxl.git > git clone git://git.debian.org/git/pkg-exppsy/openpyxl.git python-openpyxl ... Hmmmm, this works for me now. No idea why I ended up in debian-release branch which is totally outdated. Thanks for pushing my nose to the right place and sorry for the noise. > So we are all up to date and have full packaging available. > So, are you confused by the debian branch? > Or an overlay mechanism of gbp? No idea. > $> grep overlay debian/gbp.conf > overlay = True > > ? > > we indeed missed the prestine-tar though. I'll add this when moving. Kind regards Andreas. -- http://fam-tille.de
