Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Apr 2022 14:31:39 +0200
From:      Mark Tinka <mark@tinka.africa>
To:        questions@freebsd.org
Subject:   Re: libxml2 Port Blocking Upgrades - RESOLVED!
Message-ID:  <f4d8f3f4-ffbf-4fed-3db6-4695959c8b22@tinka.africa>
In-Reply-To: <87pmlr90bq.wl-herbert@gojira.at>
References:  <77f02d06-0252-e8d2-f53f-0fa39fc0d58b@tinka.africa> <CAN6yY1s3q3bRUNm_hZzxFB1Y_1i5z-F2dyCUYYxvWRcbs7WjMw@mail.gmail.com> <8d1e18fb-9888-25bb-87dd-b3ac2f47559f@tinka.africa> <Yk7GVG9FA0ZZA2EX@doctor.nl2k.ab.ca> <23c640c7-29c1-7eb0-1e15-8b3da916cff4@tinka.africa> <20220407121855.caaf6ec77583fc8c0f93d781@sohara.org> <711b74f9-d53f-b4a1-686b-ff0c1d58b312@tinka.africa> <5627cce982c4063a660dabc438ccf7a1a409e631.camel@mail.ru> <46eabc8d-3b45-984c-6ad8-b36167f57b82@tinka.africa> <87pmlr90bq.wl-herbert@gojira.at>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------hfRWk4fQR0HshsINVSH9CTGp
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi all.

Just an update - looks like the latest Ports update has fixed this issue.

Based on what I can find online, it seems the issues were related to this:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262940

It would appear the developers were trying to switch from CMake to 
Autotools for libxml2, and that turned out pretty nasty.

Both the latest libxml2 (2.9.13_2) and libxslt (1.1.35_3) ports had the 
exact same update for their recent fix, this week:

     textproc/{,py-}libxml2: switch back to autotools

     See notes in Makefile and linked PRs.

     While here, disable the ICU option by default. CFLAGS for libicu
     are passed to libxml2's consumers when the option is enabled. As
     icu's API is not stable between versions, PORTREVISION bumps can
     get missed.

     Additionally, properly exclude all OPTIONS from py-libxml2 and
     prevent do-configure from unnecessarily running.

     Co-authored-by: diizzy
     PR: 262853, 262940, 262877
     Approved by: fluffy (mentor)

I can confirm that all problematic boxes that failed this update for me 
are now updating fine.

Thank you all for your support, including those who reached out 
privately. It's most appreciated. Thanks.

Mark.
--------------hfRWk4fQR0HshsINVSH9CTGp
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="Tahoma">Hi all.<br>
      <br>
      Just an update - looks like the latest Ports update has fixed this
      issue.<br>
      <br>
      Based on what I can find online, it seems the issues were related
      to this:<br>
      <br>
          <a class="moz-txt-link-freetext" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262940">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262940</a><br>;
      <br>
      It would appear the developers were trying to switch from CMake to
      Autotools for libxml2, and that turned out pretty nasty.<br>
      <br>
      Both the latest libxml2 (2.9.13_2) and libxslt (1.1.35_3) ports
      had the exact same update for their recent fix, this week:<br>
      <br>
          textproc/{,py-}libxml2: switch back to autotools<br>
      <br>
          See notes in Makefile and linked PRs.<br>
      <br>
          While here, disable the ICU option by default. CFLAGS for
      libicu<br>
          are passed to libxml2's consumers when the option is enabled.
      As<br>
          icu's API is not stable between versions, PORTREVISION bumps
      can<br>
          get missed.<br>
      <br>
          Additionally, properly exclude all OPTIONS from py-libxml2 and<br>
          prevent do-configure from unnecessarily running.<br>
      <br>
          Co-authored-by: diizzy<br>
          PR: 262853, 262940, 262877<br>
          Approved by: fluffy (mentor)<br>
      <br>
      I can confirm that all problematic boxes that failed this update
      for me are now updating fine. <br>
      <br>
      Thank you all for your support, including those who reached out
      privately. It's most appreciated. Thanks.<br>
      <br>
      Mark.<br>
    </font>
  </body>
</html>

--------------hfRWk4fQR0HshsINVSH9CTGp--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f4d8f3f4-ffbf-4fed-3db6-4695959c8b22>