					number	op	packagefile	localfile	ucfr	UCF_FORCE_	expected result
helper_update_noch			01	update	unchanged	unchanged	1			local
helper_update_locch			02	update	unchanged	changed		1			local
helper_update_locdel			03	update	unchanged	deleted		1			deleted
helper_update_pkgch			04	update	changed		unchanged	1			package
helper_update_bothch_forceold		05	update	changed		changed		1	CONFFOLD	local
helper_update_bothch_forcenew		06	update	changed		changed		1	CONFFNEW	package
helper_update_pkgch_locdel_forceold	07	update	changed		deleted		1	CONFFOLD	deleted
helper_update_pkgch_locdel_forcenew	08	update	changed		deleted		1	CONFFNEW	package
helper_update_pkgdel			09	update	deleted		unchanged	0			deleted
helper_update_pkgdel_locch_forceold	10	update	deleted		changed		0	CONFFOLD	local
helper_update_pkgdel_locch_forcenew	11	update	deleted		changed		0	CONFFNEW	deleted
helper_update_bothdel			12	update	deleted		deleted		0	(*)		deleted
helper_rename_noch			13	rename	unchanged	unchanged	1			newname
helper_rename_locch			14	rename	unchanged	changed		1			changed newname
helper_rename_locdel			15	rename	unchanged	deleted		1			oldname and newname deleted
helper_rename_pkgch			16	rename	changed		unchanged	1			package newname
helper_rename_bothch_forceold		17	rename	changed		changed		1	CONFFOLD	local
helper_rename_bothch_forcenew		18	rename	changed		changed		1	CONFFNEW	package
helper_rename_pkgch_locdel_forceold	19	rename	changed		deleted		1	CONFFOLD	local
helper_rename_pkgch_locdel_forcenew	20	rename	changed		deleted		1	CONFFNEW	package

the column ucfr says how many files should be registered (check_ucfq_number)
after the second ucf run. Tests do also check this.

(*) the second ucf call causes a question to be asked while that it not
strictly necessary. Since both options yield the same result, and this is an
exotic corner case, we can live with that.

