On Mon, Feb 29, 2016, at 14:11, Sergey B Kirpichev wrote:
> > So a FTBFS on non-release arch with outdated PHP version.
> 
> I did some work to keep my packages in installable status for all arch's,
> no matter how important they seems to you.

It's not how important they seem to *me*, but to the release team. The
FTBFS on non-release archs are not "serious", just "normal" at most and
mostly it's "wishlist".

> Why you break this so easily?
> (btw, how such archs could get release status if you refuse to assist them?).

This is a breakage that was caused by libtool 2.4.6-0.1 upload. If you
want to blame somebody blame libtool maintainers for moving ltmain.sh to
different directory _again_.

And as you can see in #814271, I fixed this bug within one week when it
was reported. So please consider your words.

> > And with serious severity.
> 
> Whatever it is by severity - this a bug and it's not fixed yet.  And there is 
> no FTBFS bug
> for php7.0-dev on kfreebsd (as far, as I can see).

This bug is already fixed in 7.0.3-4:

php7.0 (7.0.3-4) unstable; urgency=medium

  * Resolve ltmain.sh link based on libtool version (Closes: #814271)

 -- Ondřej Surý <ond...@debian.org>  Mon, 15 Feb 2016 12:41:07 +0100

When libperl and libsnmp get's resolved on kfreebsd-*, this situation
will fix itself after newer php7.0 is built.

Somehow I cannot fix packages that are not up-to-date. Sergey, please
take your bitterness elsewhere. This is neither place nor time to hinder
the PHP 7.0 transition.

Cheers,
-- 
Ondřej Surý <ond...@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

Reply via email to