zsh-users
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-users@zsh.org
Subject: Re: Zsh on Debian is beginning to rot
Date: Mon, 10 Sep 2012 15:11:08 +0200	[thread overview]
Message-ID: <20120910131108.GA5515@sym.noone.org> (raw)
In-Reply-To: <20120910115932.GH16413@xvii.vinc17.org>

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)


  reply	other threads:[~2012-09-10 13:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 11:10 Mark van Dijk
2012-09-09 11:48 ` Frank Terbeck
2012-09-10  8:06   ` Vincent Lefevre
2012-09-10  8:42     ` Frank Terbeck
2012-09-10 12:13       ` Vincent Lefevre
2012-09-10  8:56     ` Michael Prokop
2012-09-10 11:59       ` Vincent Lefevre
2012-09-10 13:11         ` Axel Beckert [this message]
2012-09-09 17:51 ` Axel Beckert
2012-09-09 18:38   ` Mark van Dijk
2012-09-10  0:16     ` Axel Beckert
2012-09-10 14:59       ` Ray Andrews
2012-09-10 18:42         ` Axel Beckert
2012-09-11  0:15           ` Vincent Lefevre
2012-09-11 11:45             ` zsh-beta vs zsh Debian package (was: Re: Zsh on Debian [...]) Axel Beckert
2012-09-12  0:40               ` Clint Adams
2012-09-12 11:41                 ` Vincent Lefevre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120910131108.GA5515@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).