This bug was fixed in the package triforce-lv2 - 0.3.2-5 Sponsored for Tobias Heider (tobhe)
--------------- triforce-lv2 (0.3.2-5) unstable; urgency=medium * Change my email address to @debian.org -- NoisyCoil <[email protected]> Fri, 29 Aug 2025 21:28:49 +0200 triforce-lv2 (0.3.2-4) unstable; urgency=medium * Upload to unstable -- NoisyCoil <[email protected]> Sun, 10 Aug 2025 18:53:02 +0200 triforce-lv2 (0.3.2-3) experimental; urgency=medium * Enable amd64 builds -- NoisyCoil <[email protected]> Sun, 10 Aug 2025 14:13:21 +0200 triforce-lv2 (0.3.2-2) unstable; urgency=medium * Upload to unstable -- NoisyCoil <[email protected]> Sun, 10 Aug 2025 14:11:59 +0200 triforce-lv2 (0.3.2-1) experimental; urgency=medium * New upstream release. -- NoisyCoil <[email protected]> Sat, 17 May 2025 11:14:05 +0200 triforce-lv2 (0.3.0-1) experimental; urgency=medium * New upstream release. -- NoisyCoil <[email protected]> Sat, 10 May 2025 15:19:33 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2121902 Title: FFe: Please sync triforce-lv2 0.3.2-5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/triforce-lv2/+bug/2121902/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
