From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Package up for grabs: dev-util/cvise
Date: Tue, 07 Nov 2023 16:14:30 +0100 [thread overview]
Message-ID: <5e2b15e50585be2c76a1ba16f2a3517a4aa2f167.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Hello,
dev-util/cvise is now looking for a new maintainer.
It is fairly low maintenance package. It's in need of a version bump
right now, as well as testing with llvm:17 and python:3.12 (both seem to
work fine).
The main problem with it is that it happens to hit some bugs in sys-
devel/clang[debug] that cause crashes, and I don't really have the
resources to rebuild sys-devel/clang just to test this one package.
Note that these are actually upstream bugs of clang and not cvise. They
haven't been fixed for years because big tech just doesn't care that
clang sometimes crashes on random code.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next reply other threads:[~2023-11-07 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 15:14 Michał Górny [this message]
2023-11-08 6:44 ` [gentoo-dev] Package up for grabs: dev-util/cvise Sam James
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=5e2b15e50585be2c76a1ba16f2a3517a4aa2f167.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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