Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Piotr =?utf-8?Q?O=C5=BCarowski?= Newsgroups: linux.debian.maint.python Subject: Re: Pushing a bunch of packages to jessie-backports Date: Thu, 26 Nov 2015 21:50:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Nov 26 20:42:59 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.879 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: Debian GNU/Linux (3.16.0-4-amd64) User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailing-List: archive/latest/13229 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20151126204240.GS16403@sar0.p1otr.com Approved: robomod@news.nic.it Lines: 39 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 26 Nov 2015 21:42:40 +0100 X-Original-Message-ID: <20151126204240.GS16403@sar0.p1otr.com> X-Original-References: <20151123205458.GB16403@sar0.p1otr.com> <56549EC0.7040205@debian.org> <20151124182903.GF16403@sar0.p1otr.com> <5654E438.404@debian.org> <20151124230008.GG16403@sar0.p1otr.com> <5654F7DA.4080802@debian.org> <20151125110750.GH16403@sar0.p1otr.com> <565719F0.6060909@debian.org> <20151126150204.GO16403@sar0.p1otr.com> Xref: csiph.com linux.debian.maint.python:7914 [Vincent Cheng, 2015-11-26] > > that's why I don't believe you built it in jessie. python-sphinx is not backported > > and you didn't mention any patches > > > > solutions: > > 1) backport python-sphinx, or > > 2) use patch from Ubuntu: https://patches.ubuntu.com/r/routes/routes_2.2-1ubuntu1.patch > > Backports packages are allowed to build-dep on other backported > packages of the same suite (i.e. you can build packages destined for that's right, same as in any other suite. That's why I mentioned backporting sphinx as one of solutions > jessie-backports in a chroot with packages from both jessie and > jessie-backports to satisfy build dependencies). Given that Thomas has > already mentioned in the very beginning of this thread that he intends > on backporting sphinx to jessie-backports as well (which satisfies the > unmet build-dep above), I think it's safe to assume that he will be > uploading packages to backports in the necessary order to satisfy > build dependencies. right, he listed sphinx among those he wants to backport (I missed that fact). I checked jessie-backports and it didn't contain it (it still doesn't). Building and uploading in the right order was always the plan, right? > FWIW, I see no *technical* reason to reject Thomas' backported > packages. It looks to me that he's done everything he needs to do > according to the backports rules, and that you're imposing additional > requirements that (strictly speaking) he doesn't have to meet (i.e. > providing debdiffs for every backports upload). I still stand by this requirement - I'm the one who gets all the emails and bug reports and I do not welcome NMUs that do not fix RC bugs. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645