[Pkg-zsh-devel] Plans for the next zsh upload (was: zsh FTBFS since yodl 3.08.00-1 in the same way that c++-annotations FTBFSed with 3.07.00-1)

Axel Beckert abe at debian.org
Sat May 7 14:32:16 UTC 2016


Hi Debian Zsh Team,

Axel Beckert wrote:
> Debian Bug Tracking System wrote:
> >  yodl (3.08.00-1) unstable; urgency=medium
> >  .
> >    * New upstream release fixes a bug in handling multiple identical options.
> >      (Closes: #823043).
> 
> Frank B. Brokken wrote:
> > Thanks for your bug report. It looks like you encountered a real bug, and I'm
> > still somewhat in the dark as to why it never has been observed
> > before. Because of that (i.e., me satisfying my own curiosity) I'll need a bit
> > more time to submit a fix, but at least I think I've located the cause of the
> > problem. I'll probably have a fix ready by Monday or a bit earlier.
> > 
> > One minor thing: it's not an Annotations issue, but a bug in the Yodl
> > package.
> 
> I'm not 100% sure what's going on, but it seems to me that while
> c++-annotations indeed FTBFS with 3.07.00-1 and builds fine again with
> 3.08.00-1 (verified it :-), it's the opposite way round with zsh:
> 
> It builds fine with yodl 3.07.00-1, but FTBFS with 3.08.00-1 as
> follows:

JFYI: Frank B. Brokken sent me a proof-of-concept yodl package (dubbed
3.08.01-1) which fixes this issue. He'll probably upload it on Sunday.

Since zsh 5.3 is probably still a while away (and I misinterpreted the
5.2-dev-1 upstream tag as beta-release), I'll backport all the
packaging changes from 5.2-dev-1-1 in experimental into a 5.2-4 for
unstable to .

From doing that (plus some more recent changes) I have seven commits
locally queue for pushing. But due to the above mentioned #823043 I
think I should wait for the fixed yodl upload because otherwise the
builds on Jenkins will FTBFS. (Or do you think it's better to push
anyway for backup and sharing purposes?)

Since forced pushes are disabled (probably by default, and probably
for a reason), I intend to use a branch named "debian-stretch" until
the 5.3 upstream release is out. I'll merge the "debian" and
"debian-stretch" branches again once 5.3 is out to be able to use the
"debian" branch again. (Not sure if I should drop the duplicated
changelog entries from the mislabeled 5.2-dev-1-1 upload or not. Any
suggestions on this are appreciated.)

I hope that plan is fine for all of us.

		Regards from LUG-Camp at Bruchsal, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-zsh-devel/attachments/20160507/d9eb05e6/attachment.sig>


More information about the Pkg-zsh-devel mailing list