https://bugs.kde.org/show_bug.cgi?id=400590
Harald Sitter <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Ever confirmed|0 |1 Status|REPORTED |CONFIRMED --- Comment #1 from Harald Sitter <[email protected]> --- I've been digging through the job archive and found that heaptrack, which is now forks/heaptrack, used to be kde-extras/heaptrack. To get the issue at hand: I am almost certain kde-extras/heaptrack was at 1.2 while the new forks/heaptrack is at 1.1 which is causing that version problem. The easy solution is probably to go to 1.2 (although I also do not understand why it would be at 1.1 when the old thing was a 1.2) I have no actual proof of that because we don't keep old repos. On top of that is the problem that the build history wasn't preserved in the rename, so through jenkins we also get no better metadata. And the fact that xenial currently does not contain 1.2 either raises yet more questions: what happened to the heaptrack 1.2 deb in the xenial repos. There is a test specifically verifying that all packages in bionic are greater than xenial, if xenial in of itself is not version consistent (as appears to be the case here) that becomes meaningless though. CCing Scarlett since she's been working on both incarnations of heaptrack -- You are receiving this mail because: You are watching all bug changes.
