The virtual repository support for Debian repos seems to be broken.
Create a new remote Debian repository. Then create a new virtual repository and assign the freshly created Debian repo to it.
The first question here is why I cannot enable "Debian support" for the new virtual repo.
Then grant the necessary permissions. Add the new virtual repo to your APT sources.list file (and only this one, comment all others out). Run apt-get update. Everything is fine so far.
Then create a new local Debian repo. Assign it to the virtual repository. Make sure repo indexes get updated. Now run apt-get update again. Now you get hash sum mismatches from apt-get and the local APT indexes do not get updated. Therefore the virtual repo is not usable.
I have also recognized that the hash sum mismatches only occur for distributions/components that intersect in the remote and local repo assigned to the virtual repo. For example, if the local repo only contains artefacts for jessie/non-free that only the hashes for jessie/non-free of the virtual repo do not match any more.
There is no specific documentation about Debian support for virtual repositories. Maybe this is not possible by design? But if it should be possible, what is the problem then?
This is a real showstopper for us because designing an APT deployment pipeline without being certain on how to organise the repos is simply not possible.
|Make default architecture a required field in UI||Ready For Merge|