Hi, I'm the new bwm-ng Debian maintainer and i'm preparing the packaging of 0.6.1 right now, which contains this fix.
Could this new release 0.6.1 enter Xenial? If not, what can i do to fix this on Xenial? As Yaketty will sync from Debian Unstable and fix the bug.
Hi, I'm the new bwm-ng Debian maintainer and i'm preparing the packaging of 0.6.1 right now, which contains this fix.
Could this new release 0.6.1 enter Xenial? If not, what can i do to fix this on Xenial? As Yaketty will sync from Debian Unstable and fix the bug.