Update trace-cmd and splited kernelshark

How to install

sudo dnf upgrade --refresh --advisory=FEDORA-2020-e78d4f1508

This update has been submitted for testing by zsun.

2 years ago

This update's test gating status has been changed to 'ignored'.

2 years ago

This update's test gating status has been changed to 'waiting'.

2 years ago

This update's test gating status has been changed to 'ignored'.

2 years ago

This update has been pushed to testing.

2 years ago
User Icon xosevp commented & provided feedback 2 years ago
karma

Broken!

Installing the same files as "perf":

Error: Transaction test error: file /usr/lib64/traceevent/plugins/plugin_cfg80211.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_function.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_hrtimer.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_jbd2.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_kmem.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_kvm.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_mac80211.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_sched_switch.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_scsi.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64 file /usr/lib64/traceevent/plugins/plugin_xen.so from install of trace-cmd-libs-2.9.1-1.fc33.x86_64 conflicts with file from package perf-5.8.11-300.fc33.x86_64

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

2 years ago

zsun edited this update.

New build(s):

  • trace-cmd-2.9.1-2.fc33

Removed build(s):

  • trace-cmd-2.9.1-1.fc33

Karma has been reset.

2 years ago

This update has been submitted for testing by zsun.

2 years ago
User Icon zsun commented & provided feedback 2 years ago

Hmm thanks for the report. I'll talk to the kernel maintainers.

This update has been pushed to testing.

2 years ago

This update can be pushed to stable now if the maintainer wishes

2 years ago
User Icon tseewald commented & provided feedback 2 years ago
karma

Along with the perf problem that that xosevp noted, I am also seeing a conflict with kernelshark.

Error: Problem: cannot install the best update candidate for package kernelshark-2.8.3-4.fc33.x86_64 - problem with installed package kernelshark-2.8.3-4.fc33.x86_64 - package kernelshark-2.8.3-4.fc33.x86_64 requires trace-cmd(x86-64) = 2.8.3-4.fc33, but none of the providers can be installed - cannot install the best update candidate for package trace-cmd-2.8.3-4.fc33.x86_64 - cannot install both trace-cmd-2.9.1-2.fc33.x86_64 and trace-cmd-2.8.3-4.fc33.x86_64 - cannot install both trace-cmd-2.8.3-4.fc33.x86_64 and trace-cmd-2.9.1-2.fc33.x86_64 (try to add '--skip-broken' to skip uninstallable packages)

User Icon zsun commented & provided feedback 2 years ago

Thanks for both of your testing. The two are different known issues.

For the perf conflicting issue, upstream is working on getting a libtraceevent as a standalone repo, so that perf and trace-cmd will both depend on it. I am working on a workaround for this before this is ready to go with both perf and trace-cmd upstream.

For the kernelshark issue, kernelshark need to be the same version (or a compatible version) with trace-cmd. kernelshark is now a separated package in Rawhide. And as it depends on the trace-cmd library to be compiled, I can only make an update to kernelshark after the trace-cmd workaround is done.

zsun edited this update.

New build(s):

  • trace-cmd-2.9.1-3.fc33

Removed build(s):

  • trace-cmd-2.9.1-2.fc33

Karma has been reset.

2 years ago

This update has been submitted for testing by zsun.

2 years ago

This update has been pushed to testing.

2 years ago

zsun edited this update.

New build(s):

  • kernelshark-1.2-1.fc33

Karma has been reset.

2 years ago

This update has been submitted for testing by zsun.

2 years ago

This update has been pushed to testing.

2 years ago

This update can be pushed to stable now if the maintainer wishes

2 years ago

This update has been submitted for stable by bodhi.

2 years ago

This update has been pushed to stable.

2 years ago
User Icon ferdnyc commented & provided feedback a year ago

@zsun: kernelshark is still conflicting with trace-cmd two months later, so I'm afraid something seems to have broken down with the updates chaining here.

The current F33 package is kernelshark-2.8.3-4.fc33 which requires 'trace-cmd(x86-64) = 2.8.3-4.fc33' and blocks the installation of trace-cmd-2.9.1-2.fc33.

If the kernelshark version numbering is going to be reset down to a lower value (I see kernelshark-1.2-1.fc33 attached to this update), then you'll need to set an Epoch number to get it to install in place of kernelshark-2.8.3-4.fc33, and to avoid it continually trying to upgrade itself to 2.8.3 after install.

User Icon ferdnyc commented & provided feedback a year ago

I can confirm that manually forcing a dnf downgrade kernelshark-1.2-1.fc33 unblocks the trace-cmd update, allowing a dnf upgrade trace-cmd to successfully install 2.9.1-4.fc33. But that's going to continue to cause problems due to the existence of kernelshark-2.8.3-4.fc33 in the fedora repo for F33.

The only workable solutions are to either raise the kernelshark version numbering above 2.8.3, or add an 'Epoch: 1' to the kernelshark.spec and push out a new kernelshark-1:1.2-2.fc33 package as an upgrade from kernelshark-2.8.3-4.fc33.

User Icon ferdnyc commented & provided feedback a year ago

I've submitted rhbz 1909725 to track the kernelshark version-numbering issue.


Please login to add feedback.

Metadata
Type
enhancement
Karma
0
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
3 days
Dates
submitted
2 years ago
in testing
2 years ago
in stable
2 years ago
modified
2 years ago
BZ#1858379 trace-cmd-2.9.1 is available
0
0
BZ#1882908 Review Request: kernelshark - GUI analysis for Ftrace data captured by trace-cmd
0
0

Automated Test Results