This bug was fixed in the package trace-cmd - 3.3.3-1ubuntu1
---------------
trace-cmd (3.3.3-1ubuntu1) resolute; urgency=medium
* Merge with Debian unstable (LP: #2130149). Remaining changes:
- trace-utest: return non-zero when tests have failed
- trace-utest: run trace-cmd with --compression none on s390x
(LP 2114514)
* Dropped changes, included in Debian:
- debian/patches: fallback to using /usr/bin/trace-cmd in trace-utest
- debian/tests: add trace-utest and trace-cmd-examples dep8 tests
trace-cmd (3.3.3-1) unstable; urgency=medium
[ Nick Rosbrook ]
* debian/patches: fallback to using /usr/bin/trace-cmd in trace-utest
* debian/tests: add trace-utest and trace-cmd-examples dep8 tests
[ Adriaan Schmidt ]
* Fix install location for tracecmd.py
[ Sudip Mukherjee ]
* New upstream version 3.3.3
* Fix bash-completion install path.
* Update Standards-Version to 4.7.2
* Remove old fsf address from d/copyright.
-- Nick Rosbrook <[email protected]> Wed, 03 Dec 2025 10:09:48 -0500
** Changed in: trace-cmd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2130149
Title:
Merge trace-cmd from Debian Unstable for resolute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/2130149/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
