Hi, On Thu, 28 Oct 2010, Evgeni Golov wrote: > You are speaking about #601608?
Yes. > This should be trivial - build-depending on python (>= 2.5.4) [which > introduced python.mk] and droping python-sqlite [it is in python since > 2.5 and "we" do not support 2.4 anymore as it seems]. Yeah, but I don't know if there's a way to be more backporter-friendly. I haven't checked why we're using python.mk. > I can commit my stuff to python-modules svn, yeah. But marking as team > upload? I'm not in the team and thus calling this a NMU is imho the way > to do (you may have different in-team policy which I do not know). > > Do you want me to prepare and upload a new version? Or should I cancel > the NMU and you do the work? :) If you feel like preparing it, sure, go ahead! That way I can spend my time on other packages during the BSP this week-end (I'm attending the mini-Debconf Paris which host a BSP). Just make sure to inject everything in the SVN repository (including tag of the release if you upload it). Please avoid the NMU versioning, team upload is okay since you have my blessing. Otherwise don't upload, just commit everything and I'll take care of the upload. Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
