Hi Phil, Quoting Philip Hands (2022-05-13 11:52:05) > Johannes Schauer Marin Rodrigues <jo...@debian.org> writes: > > I'm confused. Shouldn't preseed_fetch try to obtain the setup-testbed > > relative to the preseed file it just obtained? > > preseed_fetch gets things relative to the place the previous > preseed_fetch got things from, which is one step later than you are > expecting because it has not really been setup while you're in the > context of the initial preseed.cfg. > > See: > https://salsa.debian.org/installer-team/preseed/-/blob/master/README.preseed_fetch > > The point is that you need to have done a preseed/include or a > preseed/run (which can be relative paths) in order to have populated the > previous download path, whereas I think you are trying to run the > preseed_fetch while we're still on the first time through the code, in > the loop above this line: > > > https://salsa.debian.org/installer-team/preseed/-/blob/master/preseed.sh#L120 > > I guess there should be some documentation that's easier to find than > the above README, to say that you should not use relative paths for > preseed_fetch from the early_command (and possibly the late_command?) in > preseed.cfg itself, but only from within files that were grabbed via at > least one preseed/run or preseed/include -- or something like that.
I found and read README.preseed_fetch just fine, so I don't think it's a problem of find-ability of the docs. But the README should maybe contain the things you said above and maybe even an example as you reference below. From my reading of README.preseed_fetch I did not understand this limitation. > Here's another example that may be instructive: > > https://hands.com/d-i/bug/846002/ > > (which is referred to here: https://bugs.debian.org/846002#304 ) Ah yes, that worked! I documented the solution in my reply to #678694 and will keep using that. It feels a bit odd to download a one-line script which does nothing else than downloading yet another script but since it's automated I guess I don't care. :) > I seem to have learnt to avoid doing anything interesting in preseed.cfg > itself -- assuming that's not already mentioned somewhere, if you have a > suggestion for where that tip could have been placed to have been helpful to > you, please report a bug against the relevant documentation. I think README.preseed_fetch is fine as I was able to find it via searching for preseed_fetch via codesearch.debian.net. I think it just needs the bits that you explained to me above copypasted into it. Thanks again! cheers, josch
signature.asc
Description: signature
