On 2/01/2019 4:56 pm, Matthew Macy wrote: > I just updated world/kernel/ports to today's HEAD and packages and > pkg "upgraded" chrome to be broken in this way. This isn't an isolated > issue. > > On Tue, Jan 1, 2019 at 9:55 PM Matthew Macy <mat.macy_at_gmail.com> wrote: >> >> I just updated world/kernel/ports to today's HEAD and packages and >> pkg "upgraded" chrome to be broken in this way. This isn't an isolated >> issue. >> >> On Tue, Jan 1, 2019 at 9:53 PM Matthias Apitz <guru_at_unixarea.de> wrote: >>> >>> El día viernes, diciembre 28, 2018 a las 12:55:32p. m. -0800, Cy Schubert escribió: >>> >>>> In message <CAALwa8neThcas8V4ytdz1LuJnjYY0j0qHB__MHsE6uz4FohkeA_at_mail.gma >>>> il.com> >>>> , Antoine Brodin writes: >>>>> On Fri, Dec 28, 2018 at 8:39 PM Graham Perrin <grahamperrin_at_gmail.com> wrote: >>>>>> >>>>>> On Fri, 28 Dec 2018 at 16:31, Emiel Kollof <coolvibe_at_hackerheaven.org> wrot >>>>> e: >>>>>> >>>>>>> Confirmed with Chromium on my CURRENT box: >>>>>> >>>>>> … >>>>>> >>>>>> Thanks folks. Should I report it as a bug with devel/glib20? >>>>> >>>>> Hi, >>>>> >>>>> I think it's a regression in the toolchain (the problem doesn't occur >>>>> on 11.2 or 12.0), so it should be reported to freebsd-toolchain_at_ >>>> >>>> No issue here however I rebuilt glib on Dec 21. >>> >>> I see the same with www/chromium on r342378 and ports, both from Dec 23. >>> >>> matthias >>> >>> -- The issue is being tracked in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220103 Per my last comment (comment 36), any base change(s) required to resolve the issue, once identified, should be tracked separately as a blocking issue.Received on Wed Jan 02 2019 - 10:26:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:19 UTC