On Monday, March 25, 2024 11:42:55 PM PDT you wrote: > Ok, there is also this reply to consider from the developers of a2jmidid: > https://github.com/jackaudio/a2jmidid/issues/25#issuecomment-2019233806 > > Maybe we should hold back? > > ** Bug watch added: github.com/jackaudio/a2jmidid/issues #25 > https://github.com/jackaudio/a2jmidid/issues/25 > > > "%s [%d] (%s): %s", > > Kind regards, > > Reinaert > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/a2jmidid/+bug/2058799/+subscriptio > ns
There's one little caviat there: > Unless Ubuntu wants to pull in the fix manually... Which I have. Package is in our proposed pocket now awaiting migration. I've also been preparing a Stable Release Update for it. Regarding "breaking existing scripts", the naysayer in question has been known to use outdated methods (refers to ideas stemming back to 2008, so 16 years ago and only recently came back after a 10 year hiatus), so rather than break people's ability to use hardware, certain people should be more flexible and adapt their scripts to use newer methods. -- Erich Eickmeyer Ubuntu MOTU Project Leader - Ubuntu Studio Technical Lead - Edubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058799 Title: a2jmidid doesn't handle midi interfaces with two or more identical port names correctly and fails to expose them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/a2jmidid/+bug/2058799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
