Comment # 11 on bug 1077726 from Rick Stockton

Just a month-later "final update" on my status:

I'm not sure why the reporter has not responded. For Doug, the problem was
resolved by using zypper dup. For me the problem was resolved by a one-time
fixup; and correct use of zyper dup on subsequent upgrades has led to good
results.

The only remaining question from my POV is a choice between 3 alternative
"resolution" strategies: 

#1) Make a dependency on an RFE: A Zypper option to (very slowly) verify that
all installed packages are "consistent" with their stated content and not
missing any files? (Feature, and I hate this idea.)

Or #2 Do we want to re-label the Bug as one apparent root cause: "Yast2 package
version/release names were not properly CHANGED when new files were added
during January 2018" ? I like that scheme, it seems have been the root cause of
my problem and inability to solve by executing only "zypper dup". My comment #5
https://bugzilla.suse.com/show_bug.cgi?id=1077726#c5. Change the Description,
and then close as "Resolvd").

Or #3, close as user error, the other root cause: Tumbleweed users should only
upgrade by using "zypper dup" from the command line, and never use "Update all
packages if newer versions exist" from the GUI. I got some packages "update"
packages which were present in the correct Update Repo, but not yet declared
ready as part of a genuine "DUP". This is also accurate and results in good
instructions to users.

If I were a T&I person, I would prefer #2: There was a mess in pushing a group
of not-yet-ready package set into the Official "Update" Repo, they should have
been left in staging until it was DONE. But #3 also has my support as a
Tumbleweed User, it is a test Distro and I created a mess (in my box) by using
the wrong procedure.