Path: csiph.com!eternal-september.org!feeder.eternal-september.org!weretis.net!feeder4.news.weretis.net!feeder1.news.weretis.net!newsfeed.CARNet.hr!news.spin.it!bofh.it!news.nic.it!robomod From: Jeremy Stanley Newsgroups: linux.debian.maint.python Subject: Re: mock 1.2 breaking tests (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental) Date: Tue, 06 Oct 2015 16:00:02 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 6 13:54:07 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RP_MATCHES_RCVD=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Sa-Exim-Connect-IP: 2001:4802:7801:102:be76:4eff:fe20:63e0 X-Sa-Exim-Rcpt-To: debian-python@lists.debian.org X-Sa-Exim-Mail-From: fungi@yuggoth.org X-Sa-Exim-Scanned: No (on azathoth.yuggoth.org); SAEximRunCond expanded to false X-Mailing-List: archive/latest/12817 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20151006135341.GR4731@yuggoth.org Approved: robomod@news.nic.it Lines: 24 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 6 Oct 2015 13:53:41 +0000 X-Original-Message-ID: <20151006135341.GR4731@yuggoth.org> X-Original-References: <561228AC.3090103@debian.org> <5612724E.9060007@debian.org> <206296351.XFVvngxEbP@kitterma-e6430> <5612EF95.5050505@debian.org> <20151006004919.GQ4731@yuggoth.org> <56137838.90401@debian.org> Xref: csiph.com linux.debian.maint.python:7506 On 2015-10-06 09:28:56 +0200 (+0200), Thomas Goirand wrote: > Master != kilo. It still means that I have to do all of the backport > work by myself. [...] > I know that it's the common assumption that, as the package maintainer > in Debian, I should volunteer to fix any issue in the 6+ million lines > of code in OpenStack ! :) > > I do try to fix things when I can. But unfortunately, this doesn't scale > well enough... In this particular case, it was really too much work. That is the trade-off you make by choosing to maintain as many packages as you do. You can obviously either spend time contributing stable backports upstream or time packaging software. Just accept that, as with Debian itself, "stable" means OpenStack upstream makes the bare minimum alterations necessary. This includes, in some cases, continuing to test the software in those branches with dependencies which were contemporary to the corresponding releases rather than chasing ever changing behavior in them. Sometimes it is done for expediency due to lack of interested volunteer effort, and sometimes out of necessity because dependencies may simply conflict in unresolvable ways. -- Jeremy Stanley