llvm rebuild gets confused

[John Klos <john%klos.com@localhost>]

Hi,

I'm not sure why, but doing a pkg_rolling-replace fails on many systems 
with:

=> Creating binary package 
/usr/pkgsrc/lang/llvm/work/.packages/llvm-16.0.6nb1.tgz
===> package-message [llvm-16.0.6nb1] ===> Building binary package for 
llvm-16.0.6nb1
=> Creating binary package /usr/pkgsrc/packages/All/llvm-16.0.6nb1.tgz
===> replace-message [llvm-16.0.6nb1] ===> Replacing for llvm-16.0.6nb1
===> replace-destdir [llvm-16.0.6nb1] ===> Updating using binary package 
of llvm-16.0.6nb1
/usr/bin/env  /usr/local/sbin/pkg_add -K /usr/local/pkgdb -U -D 
/usr/pkgsrc/lang/llvm/work/.packages/llvm-16.0.6nb1.tgz
pkg_admin: cannot find package rust-1.70.0nb1
*** Error code 1

Where does "rust-1.70.0nb1" come from? This system never had 
rust-1.70.0nb1. I thought on other systems that there were things left 
around from older builds, but this is a new system and rust was at:

rr> lang/rust - rust-1.73.0 < rust-1.74.1

There were no work directories, pkg_admin rebuild & rebuild-tree showed no 
issues (I've been checking regularly since it's nearly impossible to have 
an unattended pkg_rolling-replace these days).

How would one go about fixing this without necessarily rebuilding llvm 
again?

Thanks,
John