Skip site navigation (1)Skip section navigation (2) 
Date:      Fri, 2 Feb 2024 11:48:51 -0800
From:      Yuri Victorovich <yuri@freebsd.org>
To:        Piotr Kubaj <pkubaj@anongoth.pl>
Cc:        ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org
Subject:   Re: git: ca4a04286353 - main - devel/gitoxide: Broken on powerpc64, powerpc64le
Message-ID:  <195e2ba6-7920-46ec-a350-cd0bce72d036@freebsd.org>
In-Reply-To: <Zb05RQqh_UpxF4Jd@KGPE-D16>
References:  <202402021844.412IiU3v019503@gitrepo.freebsd.org> <Zb05RQqh_UpxF4Jd@KGPE-D16>
next in thread | previous in thread | raw e-mail | index | archive | help 
This is a multi-part message in MIME format.
--------------Y0kqFAonjKNUagn9IKQcRoYe
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Piotr,


The gitoxide project has a ton of tags, it's not clear what the last 
release is.
The latest code doesn't use ring at all.
I just don't have resources to figure out what the latest version is for 
this project.
I notified their upstream about the problem.


Yuri




On 2/2/24 10:49, Piotr Kubaj wrote:
> That's not really the right explanation.
> The port just uses older version of zlib-ng. Upstream zlib-ng fixed it sincehttps://github.com/zlib-ng/zlib-ng/commit/bd321660c916266cd98b496212114ba29d48aaed.
>
> I tried using newer zlib-ng, but then it fails later with the true
> culprit - ring 0.16.20. 0.17 would need to be used, but it will require
> some work from gitoxide.


--------------Y0kqFAonjKNUagn9IKQcRoYe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Hi Piotr,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">The gitoxide project has a ton of tags,
      it's not clear what the last release is.</div>
    <div class="moz-cite-prefix">The latest code doesn't use ring at
      all.</div>
    <div class="moz-cite-prefix">I just don't have resources to figure
      out what the latest version is for this project.</div>
    <div class="moz-cite-prefix">I notified their upstream about the
      problem.</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Yuri</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 2/2/24 10:49, Piotr Kubaj wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:Zb05RQqh_UpxF4Jd@KGPE-D16">
      <pre>That's not really the right explanation.
The port just uses older version of zlib-ng. Upstream zlib-ng fixed it since <a
      class="moz-txt-link-freetext"
href="https://github.com/zlib-ng/zlib-ng/commit/bd321660c916266cd98b496212114ba29d48aaed"
      moz-do-not-send="true">https://github.com/zlib-ng/zlib-ng/commit/bd321660c916266cd98b496212114ba29d48aaed</a>.

I tried using newer zlib-ng, but then it fails later with the true 
culprit - ring 0.16.20. 0.17 would need to be used, but it will require 
some work from gitoxide.</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------Y0kqFAonjKNUagn9IKQcRoYe--

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?195e2ba6-7920-46ec-a350-cd0bce72d036>