Some very concerning commits to plasma-discover

[Clive Johnston]

Hi folks,

I'm concerned about the following packaging for plasma-discover

https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/discover/
log/?h=kubuntu_zesty_archive

1) Basically a Debian merge was carried out and the VCS fields have somehow got 
changed.  As far as I understand, this should not and could not happen using 
the KA-NG tooling, but yet it is there in black and white?

2) The automatic nature of the tooling does not seem to be flagging up conflicts 
that need attention.  For example, in the merge the following was removed, 
from the rules file:

-override_dh_gencontrol:
-	dh_gencontrol -pmuon-discover -- -v4:$(DEB_VERSION_UPSTREAM_REVISION)
-	dh_gencontrol -pmuon-updater -- -v4:$(DEB_VERSION_UPSTREAM_REVISION)
-	dh_gencontrol -pmuon-notifier -- -v4:$(DEB_VERSION_UPSTREAM_REVISION)
-	dh_gencontrol --remaining-packages
-

These packages are transitional "dummy" packages from when discover was part 
of Muon, they therefore have an epoch in the archive.  Without this epoch they 
will fail to upload.

In addition to the above points, I am also concerned about changes/fixes others 
(Ubuntu Developers) have uploaded to the archive but have not been sync'ed 
into our packaging.  The old tooling used to flag these up and move them into a 
manual folder for attention.  The new tooling does not seem to pay any regard 
to this at all.  

If we are doing away with this in the tooling, surely we need another way of 
detecting if bug-fixes have been applied by non-Kubuntu people and reflecting 
those changes in our archive tracking branches? 

Clive