@alkalien, you could have written the reason(s) in your very first message.
Obviously, the developers do not want to give support for Linux distributions other than the Ubuntu family. When I use some version of the package, and it works, and it does not show a "new version" when I check for updates, I see no reason to update the package. According to your diff, they have changed the dependency, which could have been enough for them to bump their versions in some way... such as, e.g., semver. Where do we draw the line? If they release Ubuntu XYZ deb files with the same version every week, should I need to follow this upstream? I just fire up the package and check for updates there.
Anyways, the package is updated. However, us being on a rolling release does not have anything to do with this package. When I look at their version numbers and check the program's own "Check for update" functionality, I can clearly see that both Trusty and Bionic versions are the same, which pisses me off and which was the main reason for me to stick with the version already working on my machine. If the upstream cares enough, they can bump their version and let us know through the package rather than sharing this info privately via emails.
Pinned Comments
carsme commented on 2023-12-28 16:59 (UTC)
NOTE: Issues regarding
iculibrary files not being found, such asare not strictly related to this package, but to
boost174. Each time theicupackage in the official repositories is updated to a new major version,boost174needs to be rebuilt.You don't need to install any version of
icuother than the package available in the official repositories. To resolve the issue, either rebuildboost174yourself or, even better, leave a comment inboost174so I can publish a new pkgver and as such force a rebuild for all users.