[pacman-dev] [PATCH] libalpm/sync.c: restrict alpm_sync_newversion by USAGE_UPGRADE

Allan McRae allan at archlinux.org
Wed Aug 29 04:30:37 UTC 2018

On 25/07/18 04:48, Dave Reisner wrote:
> On Tue, Jul 24, 2018 at 05:53:00PM +0100, morganamilo wrote:
>> Commit 106d0fc54 Added the usage option for databases and
>> alpm_sync_newversion was restricted by USAGE_SEARCH instead of
> I don't recall exactly what my thinking was when I wrote this patch, but
> looking at 'pacman -Qu' output right now, I think I actually I like
> seeing potential upgrades, not just "actual" upgrades.
> Anyone else have an opinion?

I just spent some time looking into this...  only a month after submission!

My thoughts:

1) Implementing --print-format usage for -Su is the correct way to
determine updates.  (I guess in combination with --no-confirm?)

2) -Qu should label those package updates that are available but won't
be updated by -Su due to database restriction.  We currently do this for
packages in IgnorePkg, so should be an "easy" extension.

Would that be suitable for everyone?


More information about the pacman-dev mailing list