>Side note: Considering that the maintainer of the package has no time >to care for RC bugs in copyright with patch attached the package might >be a good candidate for some force-modernise effort.
That's a rather unfair way of phrasing it. I worked closely with wilmer on this issue, and we didn't take the first patch as it was clearly inadequate. But he said he's willing to take patches. After I merged my own PR we started discussing how to actually get it in testing, since as you have now found, the versions in testing and unstable are different upstream releases, which complicates things. Anyway, you figured that out, that's sorted, thanks for that. That said, about that "force-modernise", we'd definitely be happy to take any improvements to the packaging as PRs. It's certainly not the most modern thing out there, but our previous attempts to clean it up didn't get too far as the way we split bitlbee, bitlbee-libpurple, and bitlbee-common means we actually require a lot of the garbage in the rules file. So personally I decided I'd rather work on the longer term plan of refactoring the code to make libpurple into a real plugin.
