Hi! In order to implement FS#7150 for Community packages I ask all TUs to use the following dependency scheme in next versions of your packages (which will happen when 2.6.24 will hit Core): depends=('kernel26>=2.6.24-2' 'kernel26<=2.6.25' 'foobar-utils') In this case when user has an older kernel version (e.g. 2.6.23.x) - (s)he won't be annoyed by pacman who will want to upgrade foobar module and broke the system. And when version 2.6.25 will be released - Pacman won't allow the user to upgrade to it when there's at least one not-yet-updated module. Note that it is 2.6.24-2, not -1 in above example - this is because there was a configuration change to important kernel subsystem that required all modules to be rebuilt. You should always change depends version in such cases, otherwise some people with out-of-sync kernel and module version will report that module is broken. I already added this to http://wiki.archlinux.org/index.php/Kernel_Module_Package_Guidelines (feel free to improve that text). -- Roman Kyrylych (Роман Кирилич)