This is a duplicate of  FS#9515 . But I'd like to point out that the discussion there began with the desire to hold of upgrading until the next major version. (The OP wanted kernel26<2.6.25). However what would be more useful is holding off upgrading *to* the next major version: kernel26>=2.6.25

yeah, this is different. the other one was about skipping minor versions until the next major is out.

this bug is about skipping certain defined versions, for which the issues raised with the other feature request don’t apply.

skipping certain versions would be useful e.g. if some package version has some known issues (which are expected to be fixed in the upcoming version) or if some big package (or lengthy AUR building process) doesn’t warrant the minor changes in the to-be-skipped version.

the latter is of course only of value if you use a AUR helper, but the former is a very valid point, e.g. skype was incompatible with one lib32-qt version at one point.

jeese guys, 9 years later and we still can't do this?

For people running with testing environments enabled, this would be really useful if new update brings the regression. Then you ignore this specific version, downgrade and when new update shows up, you test it right away. Right now may need to manually write down the affected version and check it each time you do system upgrades, which is less than convenient.

Here I am again, 10 years after the last time, still in search of the same feature!

skype and lib32-* (from my previous comment) are dead, but xorg is still around and therefore there’s still buggy versions one wants to skip: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1392

I'm a new user of Arch Linux and I'm shocked that it's not possible to ignore a specific version of a package! Am I suppose to keep track of buggy versions of packages in my head like in the middle ages??