From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9189 invoked by alias); 10 Sep 2012 13:11:27 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17252 Received: (qmail 3046 invoked from network); 10 Sep 2012 13:11:15 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at sym2.noone.org does not designate permitted sender hosts) Date: Mon, 10 Sep 2012 15:11:08 +0200 From: Axel Beckert To: zsh-users@zsh.org Subject: Re: Zsh on Debian is beginning to rot Message-ID: <20120910131108.GA5515@sym.noone.org> Mail-Followup-To: zsh-users@zsh.org References: <20120909131050.15057aa6@internecto.net> <87mx0ze7sr.fsf@ft.bewatermyfriend.org> <20120910080650.GG16413@xvii.vinc17.org> <2012-09-10T10-42-59@devnull.michael-prokop.at> <20120910115932.GH16413@xvii.vinc17.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120910115932.GH16413@xvii.vinc17.org> X-Operating-System: Linux 2.6.32-5-xen-amd64 X-Machine: sym2 x86_64 X-Editor: GNU Emacs 23.2.1 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAAAAAC3mUtaAAAABGdBTUEAALGPC/xhBQAAADh0RVh0U29mdHdhcmUAWFYgVmVyc2lvbiAzLjEwYSAgUmV2OiAxMi8yOS85NCAoUE5HIHBhdGNoIDEuMindFS5JAAACGElEQVQ4jXXQMU8UYRDG8f8shNjdDH4AbpfGDjAWlKiJiZ0ajL1aGCvsNCbGaCGG1koLaztaTYz6ATy+gOyehYmF3MxVxgg3FnDsHcTpJr/M+8w7Rf6nCsaVTTDqxbg9hoOXmw83H71+Eyfg4E1d7/Z2fG9rGkZbTQiu+K+3U/C+76lmkvAhJuDndnoAiftou4V84okAGclop4U/jYACZDTxrYWP0gkxVfAm/W//GLZpxIzwIN0Hn8dw0B+IWkZmQmRsj2HfhwokEklHfNCCiQCRgAR7YyhQVRVTCKCzP4Y5zBBE0t0zY3Q8oQaBqqAMlVEcgVQd9706zGirAFium8HXumlMIeMwqQCInju+2+uB6MRENupdpMt8pRlHZyuAW0F+Mb6XSIVqtxjD+iVmVqqystLEzFTGT92YqRaXpNT5eTVjeJhbALPnrTxLUZUKZsgxcNm64hAOYisT/xhF+oKTGU5RegtC3Rt6eEDi/QnIevdTx9Md2EMmYBRmCQR1026FCGQQJJExsRUqgkMGaWSbwYLnoO4T6VgpbQbdELPMBAHWWrhYrcxXnYgAsatPWygkFCBD4K62MAsOTqA6szYRPpsu6e6Y8mPiVrBMNuGIMrgwBUu4p2DgG1Ownu6hpuTv7hScefHAzAC/yRRw5U5pALMbJ4AUALvHSZhxgHPXTsHcdWD1GadAHr9avP+c0wCr7263Df8ASLwXWHWs+KIAAAAHdElNRQfYBQEBODPr Organization: DeuxChevaux.org -- The =?iso-8859-1?Q?Citr?= =?iso-8859-1?B?b+tu?= 2CV Database User-Agent: Mutt/1.5.20 (2009-06-14) Hi Vincent, On Mon, Sep 10, 2012 at 01:59:32PM +0200, Vincent Lefevre wrote: > On 2012-09-10 10:56:38 +0200, Michael Prokop wrote: > > *If* subversion 1.7 is targeted for wheezy (pointers to release > > exceptions please) There is no freeze exception for Subversion. But the opposite exists: [1] says: "Not touching package due to block request" -- so the Debian Release Team explicitly prevents Subversion 1.7 to migrate to Testing currently. I don't expect this to change. [1] http://qa.debian.org/excuses.php?package=subversion > > then we will try to care of the svn completion. > > Well, unstable (sid) is still affected, and I don't see why different > rules should be applied to subversion and zsh. During the freeze it is preferred that updates to Testing happen via an upload to unstable. So if we upload 5.0.0 to Unstable, we hurt ourselves if he have to fix an important bug in 4.3.17 from testing afterwards. The same may count for uploading a 4.3.17 with a fix for Subversion 1.7 (but would be easier to revert). There is a side-channel for such cases via an upload testing-proposed-updates, but according to the freeze policy[2] for Debian Wheezy this is only an option for release-critical bugs (i.e. those of the severities "serious", "grave" or "critical"), but not for bugs which just have the severity "important". [2] http://release.debian.org/wheezy/freeze_policy.html That's why during the freeze for a new stable release we and most other Debian maintainers upload new upstream versions or stuff only relevant for Unstable just to Experimental and not to Unstable. (And yes, Subversion updates for Testing are only possible via testing-proposed-updates. But that's not our team's problem.) If you think that's the wrong approach please have a look at [3] (keywords CUT and Rolling) and help to make that idea becoming reality. [3] https://lists.debian.org/debian-devel/2011/06/msg00136.html > 1. The freeze just prevents unstable packages from entering testing, > in which case it would be OK to make zsh 5.0.0 enter unstable (sid) If you want that fixed in your Unstable installation, add the Experimental repository and install zsh from there. > The idea is to keep zsh synchronized with Subversion incompatible > changes at every level. No, the idea is to make the next Debian stable release as stable as possible and therefore to not put any tripping hazard in its way. Everything else is subject to Debian Experimental until the freeze is over. Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail) X See http://www.asciiribbon.org/ | abe@noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)