From: Jelle Licht <jlicht@fsfe.org>
To: Gabriel Wicki <gabriel@erlikon.ch>, 63530@debbugs.gnu.org
Subject: bug#63530: Missing library in package procps
Date: Sun, 28 May 2023 13:54:24 +0200 [thread overview]
Message-ID: <877cssd633.fsf@fsfe.org> (raw)
In-Reply-To: <87mt243dlp.fsf@erlikon.ch>
Hello,
Gabriel Wicki <gabriel@erlikon.ch> writes:
> A little more hacking leads me to the conclusion that (probably with
> version 4 but it's not exactly clear from the changelog) procps has made
> some significant changes to it's API. So, unless igt-gpu-tools (and
> probably others) are fixed upstream they remain broken. Fixes through
> simple regex-magic in our build-phases might be possible, but I am not
> confident enough in the matter to guarantee that the package would not
> just build but be broken in a more specific manner.
>
> Is there an easy way to check which dependents of procps are actually
> broken currently? Or is it really just igt-gpu-tools?
>
> There's two ways to go (I'd be happy for some input and volunteer to do
> the actual leg-work):
> 1. Add an additional procps-3 package with the older API to fix the
> broken packages.
> 2. Leave it as-is and wait for an upstream change of the currently
> broken packages.
I have found the upstream issue:
https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/116
We can wait it out until the release, which will be out Soon (tm), or we
make use of the patch that debian applies to igt-gpu-tools so it can
work with the new libproc2 API:
https://salsa.debian.org/xorg-team/app/intel-gpu-tools/-/blob/067ddd789fd80c12972fb92db8f93fadbdc4530e/debian/patches/libproc2_library
AFAICS, this would not lead to a world-rebuild.
Thoughts?
- Jelle
next prev parent reply other threads:[~2023-05-28 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 22:13 bug#63530: Missing library in package procps Gabriel Wicki
2023-05-15 22:36 ` Csepp
2023-05-16 8:05 ` Gabriel Wicki
2023-05-28 11:54 ` Jelle Licht [this message]
2023-11-28 16:24 ` bug#63530: Issue was fixed Gabriel Wicki
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=877cssd633.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=63530@debbugs.gnu.org \
--cc=gabriel@erlikon.ch \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.