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) http://qgqlochekone.blogspot.com El mar., 21 de may. de 2019 a la(s) 02:38, Roland Clobus (rclo...@rclobus.nl) escribió: > Hello PICCORO, > > On 20/05/2019 15:42, PICCORO McKAY Lenz wrote: > > when try to build live jessie image using strecht i got those errors > > > > lb config: unrecognized option '--mirror-chroot-updates' > > lb config: unrecognized option '--parent-mirror-binary-updates' > > lb config: unrecognized option '--parent-mirror-chroot-updates' > > When working on the documentation, I've noticed these command line > options as well. They are not present in the scripts, they are only in > the documentation. > Unfortunately due to the migration from alioth to salsa the git history > got lost, so I cannot trace it back. I would assume that the > functionality was remove from the scripts at some time, and that someone > forgot to update the documentation accordingly. I've downloaded the > package 1:20151215 [1], and the command line is mentioned there also > only in the documentation, which confirms my assumption. > > Instead of (re-)implementing these options, I would update the > documentation instead. > > With kind regards, > Roland Clobus > > [1] https://snapshot.debian.org/package/live-build/1%3A20151215/ > > > >
