From: Keith Thompson <Keith.S.Thompson@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Keith Thompson <Keith.S.Thompson@gmail.com>
Subject: Re: Linux xz issue
Date: Mon, 1 Apr 2024 01:11:29 -0700 [thread overview]
Message-ID: <CAAHpriOvxx41xU=8tdSMruLBighQDX28AtShGyriZ4hpxFLajA@mail.gmail.com> (raw)
In-Reply-To: <CAAHpriNXOQxk6JaWZZ9axn0Ndh7-+iYrUcNYPeB5hVZR7DcKzg@mail.gmail.com>
On Sun, Mar 31, 2024 at 9:15 PM Keith Thompson
<Keith.S.Thompson@gmail.com> wrote:
>
> Achim Gratz Stromeko@Nexgo.DE wrote:
> > Beyond that, the version 5.4.6 that everybody is currently reverting to
> > (and is also still available for Cygwin if you want to go back) was
> > already released when the presumed bad actor was co-maintainer and their
> > involvement goes back even farther based on the Xz developer mailing
> > list. The repository has been deactivated by GitHub so I can't check
> > there, but there is already some discussion about rolling back to 5.3.1
> > or thereabouts.
>
> The GitHub repo at <https://github.com/tukaani-project/xz> has been
> deactivated, but there's another xz repo (likely the original one)
> at <https://github.com/tukaani-project/xz>. The most recent commit
> in that repo is "CMake: Fix sabotaged Landlock sandbox check.".
>
> I have no inside knowledge about any of this.
>
> I'm running the Cygwin setup right now. It reverts the xz package
> from 5.6.1-1 to 5.4.6-1. Only 5.4.2-1 and 5.4.6-1 are available.
Sorry, I pasted the same link twice.
The deactivated GitHub repo is:
https://github.com/tukaani-project/xz
The tukaani.org repo (still active) is:
https://git.tukaani.org/xz.git
Thanks to oskar for pointing out my error.
next prev parent reply other threads:[~2024-04-01 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 4:15 Keith Thompson
2024-04-01 8:11 ` Keith Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-29 22:43 Ron Murray
2024-03-30 10:14 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAHpriOvxx41xU=8tdSMruLBighQDX28AtShGyriZ4hpxFLajA@mail.gmail.com' \
--to=keith.s.thompson@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).