It's definitely unexpected that you'd see duplicate data files in a delta upgrade path. This is an error condition on the server. Thus the client has three options:
1) fail, probably by raising a DuplicateDataFile error and providing some reasonable error string in the D-Bus error signal.
2) Ignore duplicates and carry on as if nothing's wrong.
3) Throw away the delta upgrade path and re-calculate as if --filter=full
#2 is problematic because duplicate data files *could* lead to unbootable devices. It's an unexpected condition with unknown effects on the upgrade results.
#3 is just masking over the problem.
So we'll do #1. It means that if this problem reoccurs (stgraber is fixing the server side) the user will be stuck because upgrades via the u/i will be impossible until the server is fixed. It should still be possible to perform an upgrade via cli with either --filter=full or -b 0. Still, this gives us the best opportunity to notice the problem and fix the server.
IRC discussion:
It's definitely unexpected that you'd see duplicate data files in a delta upgrade path. This is an error condition on the server. Thus the client has three options:
1) fail, probably by raising a DuplicateDataFile error and providing some reasonable error string in the D-Bus error signal.
2) Ignore duplicates and carry on as if nothing's wrong.
3) Throw away the delta upgrade path and re-calculate as if --filter=full
#2 is problematic because duplicate data files *could* lead to unbootable devices. It's an unexpected condition with unknown effects on the upgrade results.
#3 is just masking over the problem.
So we'll do #1. It means that if this problem reoccurs (stgraber is fixing the server side) the user will be stuck because upgrades via the u/i will be impossible until the server is fixed. It should still be possible to perform an upgrade via cli with either --filter=full or -b 0. Still, this gives us the best opportunity to notice the problem and fix the server.