Eztrace built on armhf in the end.
** Changed in: eztrace (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: papi (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: eztrace (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566326
Title:
FFe: Sync papi 5.4.3-2 (universe) from Debian unstable (main)
To
Thanks!
** Also affects: eztrace (Ubuntu)
Importance: Undecided
Status: New
** Changed in: papi (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, you can rush that through. You have an FFe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566326
Title:
FFe: Sync papi 5.4.3-2 (universe) from Debian unstable (main)
To manage notifications
I built papi and eztrace in a PPA:
https://launchpad.net/~ginggs/+archive/ubuntu/papi-testing/+packages
eztrace timed out on armhf during the tests:
Build killed with signal TERM after 150 minutes of inactivity
These tests actually fails on the Debian buildds anyway, so I plan to skip the
tests
Seems pretty reasonable. Does eztrace build against it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566326
Title:
FFe: Sync papi 5.4.3-2 (universe) from Debian unstable (main)
To manage
The only reverse-dependency is eztrace which will need to be rebuilt.
$ reverse-depends src:papi
Reverse-Depends
===
* libeztrace0 (for libpapi5.4.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream PAPI 5.4.3 release information:
https://icl.cs.utk.edu/papi/software/view.html?id=245
This release includes some new implementations of components and tools,
some general enhancements, and a number of bug fixes.
New Implementations:
libmsr component: Using LLNL's libmsr library to
