Created attachment 202942 [details]
ports-mgmt/portmaster failed to update devel/libdbusmenu-qt@qt5
Seems like there is some mis-logic - the port devel/libdbusmenu-qt is already qt5 and has name `libdbusmenu-qt5-0.9...` and has no FLAVORS , but easily compiles and installs without using `make FLAVOR=qt5 ...` .
Who is to blame?)
The port is installed in the flavored version and has to be reinstalled in the nonflavored version. Portmaster has some problems to manage this automatically, the following helps for me:
portmaster -o devel/libdbusmenu-qt libdbusmenu-qt-0.9.3.160420160218_9
The difference is the absence of @qt5. The are some other ports (like qca, qjson, quazip, ...), for which this approach seems to work.
(In reply to Rainer Hurling from comment #1)
What will happen when version is changed, for e.g., from libdbusmenu-qt5-0.9.3.160420160218_9 to libdbusmenu-qt5-6.15.22 ?
Should I re-origin via `portmaster -o ...` on each version change?
(In reply to mikhail.rokhin from comment #2)
As far as I understand, 'portmaster -o' is only needed once, to change back from flavored to unflavored installation.
I removed the qt4/qt5 flavors of devel/libdbusmenu-qt when removing Qt4 -- there is a moved entry for it:
devel/libdbusmenu-qt@qt5|devel/libdbusmenu-qt|2019-03-16|Flavor has been removed
Maybe se@ can weigh in on what portmaster needs to be happy with it.
portmaster cannot handle well the MOVED entries where the origins merge.
In that case, the following operations will be required.
pkg info -r originmerged # check required by ...
# got result of dependonoriginmerged
pkg delete -f originmerged
portmaster dependonoriginmerged # install a new dependent port or package by reinstalling.