Re: git: a4245a4c6ce1 - main - devel/boost: update to 1.87.0 release (+)

From: Jason E. Hale <jhale_at_freebsd.org>
Date: Sat, 15 Feb 2025 08:00:33 UTC
On Sat, Feb 15, 2025 at 1:33 AM Cy Schubert <Cy.Schubert@cschubert.com> wrote:
>
> In message <6c28366e-b7c2-47b7-9a04-13b963ac6889@freebsd.org>, Matthias
> Fechner
>  writes:
> > Dear Dima,
> >
> > Am 14.02.2025 um 05:17 schrieb Dima Panov:
> > >      devel/boost: update to 1.87.0 release (+)
> > >
> > >      New port devel/boost-mpi-libs, Message Passing Interface library,
> > >      for use in distributed-memory parallel application programming.
> > >
> > >      In this release Boost have dropped some long-time-ago deprecated asio
> > facilites
> > >      Seehttps://www.boost.org/doc/libs/1_87_0/doc/html/boost_asio/history.h
> > tml for details.
> > >
> > >      Release Notes:https://www.boost.org/users/history/version_1_87_0.html
> > >      Sponsored by:   Future Crew, LLC
> >
> > so you really think it is a good idea to break kea and icinga2 by this
> > upgrade without giving the maintainers a change to prepare an update?
>
> I don't think that was a good idea either. When broken ports are discovered
> during an exp-run it's the responsibility of the committer to either fix
> the ports or open PRs, assigned to the maintainers, to address the problems.
>

+1 I was pretty shocked, myself, to see 30+ ports simply marked
BROKEN. Maintaining libraries with lots of consumers is a pain I know
all too well, but this kind of breakage is unacceptable. It's unfair
to the downstream maintainers to dump an update on them without an
exp-run or even a heads-up, mark their ports BROKEN, and leave them
scrambling.

> >
> > I personally had to rollback this change as kea is crucial as it
> > distributes IPs to all my servers and icinga2 is used to monitor all
> > system/services.
>
> I'm importing kea 2.7.6 (development branch) as kea-deevl. It addresses the
> problem. I will backport the fix to the 2.6 branch (kea).
>
> boot-libs 1.87 fails to patch. I've emailed the committer and cc'd this
> list. All we've heard are crickets.
>

To be fair, though, fluffy@ fixed this patch failure 11 minutes after
you raised the issue in [1]. boost-libs 1.87 builds fine for me after
this change.

[1] https://cgit.freebsd.org/ports/commit/?id=4625f8a0686f9d78566867e38e614349ae9db866

>
> > Maybe give it next time a little more reaction time for the consumers of
> > this lib?
>
> Agreed.
>
> Certainly disappointing.
>
> >
> > Gruß
> > Matthias
> >

- Jason