Roland, i track back all the history and get not lost.. BUT IN ANY CASE THAT BEHAVIOUR ARE NOT VIABLE, lest see:
about the commits history: seems the migration was not as espected (migrations was done good but the results are not same as xpected)
the commits are : https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2
and also https://salsa.debian.org/live-team/live-build/commit/68700f466c142082e7423282ca4caaf7552bf8e9
I EXPLAIN WHY THAT COMMITS MUST BE REVERTED
1. - the mirror are track from default mirror.. so oldstable moving of backports (as seems always) are not in same repository, that made this behaviour ilogic and ridiculus, due for olstable the repository will be archived .. same for updates repository!
2. -for low performance networks it's a good practice have differents mirrors so download task will be separatelly, i mean event have normal and backports in same domain.. i setup different origin domains sources for normal repository and backports repository... that's a good practice
there's more reason but in my case those are enouoght
Please therat that issue quick due i cannot build any jessie image property or i cannot use any strecth image in good shape!
Lenz McKAY Gerardo (PICCORO)