I'm trying to run systemtap on F29 and I'm getting the following error:
$ sudo stap -v journal.stap
Pass 1: parsed user script and 491 library scripts using
355824virt/129076res/9628shr/119256data kb, in 290usr/40sys/334real ms.
semantic error: while resolving probe point: identifier 'process' at
semantic error: no match (similar functions: read, free, getenv, page_size,
So, 'process' is not a valid identifier? There seems to be something wrong
with the basic systemtap installation. I do have matching debuginfo for
both kernel and systemd installed. Running stap-prep only wants to install
How do I make this basic use-case work?
Software Engineer, Red Hat
concurrentunit will be orphaned.
As the maintainer, I lost interest in general java packaging and I don't have the time any more to fully support all of my packages in Fedora. No idea why the new version [¹] does not build with current maven package in rawhide.
Please feel free to pick this package if you still think it's useful in Fedora.
as discussion was started week ago, Python2 is dying. As that, some
dependencies of mercurial will be orphaned soon (or they are already)
and mercurial as it is has to move in weeks on Python3. As I wrote
in , I already started some testing and investigation.
Currently it seems that with ugly hacky fix, we are able to run
somi-working mercurial with Python3. I did just simple testing
that worked for me and in the latest copr-build (below), it seems
that hgk extension is workin as well. But many of you extensions
will be probably broken. So, I guess the most probably mercurial
will be broken for the others who use it.
So it's question, should I rebase it in rawhide and setup for Python3
already even when it is so broken, or should I wait several weeks yet
for additional fixes?
If anyone is interested about testing before it will be done,
# dnf copr enable pstodulk/mercurial
- it's just first attempt.
Here is the list of RPMs depending on mercurial: