zsh-users
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-users@zsh.org
Subject: Re: Zsh on Debian is beginning to rot
Date: Mon, 10 Sep 2012 13:59:32 +0200	[thread overview]
Message-ID: <20120910115932.GH16413@xvii.vinc17.org> (raw)
In-Reply-To: <2012-09-10T10-42-59@devnull.michael-prokop.at>

On 2012-09-10 10:56:38 +0200, Michael Prokop wrote:
> * Vincent Lefevre [Mon Sep 10, 2012 at 10:06:50AM +0200]:
> > On 2012-09-09 13:48:20 +0200, Frank Terbeck wrote:
> 
> > > There is a 5.0.0 package in experimental. It's not in sid, because of
> > > the current freeze in debian..
> 
> > That's stupid. Subversion was moved to 1.7 in sid, but in sid, zsh
> > remains with svn completion rules that are incompatible with svn 1.7.
> > So, unless some zsh update is done (possibly only the completion rules),
> > this will be an important regression for users of zsh and svn in the
> > next stable version.
> 
> In wheezy there currently is subversion 1.6.17dfsg-4,

Ah, OK, but...

> so I don't see your point in calling "That's stupid".

> *If* subversion 1.7 is targeted for wheezy (pointers to release
> exceptions please) 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. There are 2 cases:

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)
   and the sentence "It's not in sid, because of the current freeze in
   debian." is wrong, or at least very inaccurate.

2. The freeze prevents unstable updates, with the goal to move current
   unstable packages to testing, in which case it would be better to
   take care of the svn completion now (that would fix the bug in
   unstable now and would allow more tests by Debian/unstable users,
   while still not affecting testing immediately).

The idea is to keep zsh synchronized with Subversion incompatible
changes at every level.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


  reply	other threads:[~2012-09-10 11:59 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 [this message]
2012-09-10 13:11         ` Axel Beckert
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=20120910115932.GH16413@xvii.vinc17.org \
    --to=vincent@vinc17.net \
    --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).