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 <g...@unixarea.de> wrote: > > El día viernes, diciembre 28, 2018 a las 12:55:32p. m. -0800, Cy Schubert > escribió: > > > In message <caalwa8nethcas8v4ytdz1lujnjyy0j0qhb__mhse6uz4foh...@mail.gma > > il.com> > > , Antoine Brodin writes: > > > On Fri, Dec 28, 2018 at 8:39 PM Graham Perrin <grahamper...@gmail.com> > > > wrote: > > > > > > > > On Fri, 28 Dec 2018 at 16:31, Emiel Kollof <coolv...@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@ > > > > 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 > > -- > Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, > Druschba > instead of Nazis, to live instead of to survive. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
