On 2020-04-29, Buck wrote: >> The maintainer scripts for each individual package and their debconf >> templates are where to look. > > I recommend putting this in the docs.
I'll consider that, or at least referencing the relevent information found in other existing documentation. >> I wouldn't expect the "hello" program to document the fundamentals of >> computer science, or the working of electricity, or atomic theory, or >> the origins of the universe... even though all of those are, ostensibly, >> all relevent. > > I would, in the way that docs are supposed to do that. I think you > don't know a lot about documentation theory. Given your response, clearly I do not. > You do all of that by saying "This project requires a computer running > Debian," and if people aren't sure they have that then they research > Debian, and computers, and their dependencies, etc. That's just the > way all documenation is always written. Anything else is just > scribbles. There are always, of course, some unstated assumptions in any documentation. The meaningful question is which assumptions are a reasonable starting point, in my opinion... and opinions on this will surely vary. > Anyway you effectively do that in yours, so it's not material here. > But it is similar to how the debian-installer doc should reference the > HowTo, which should reference the README as the authoritative doc. The debian-installer documentation should not reference simple-cdd documentation, though the debian-handbook you earlier referenced probably should. > Otherwise we're all just clicking around desperate for anything that > says "simple-cdd" on it. I do take issue with your previous assertions that READMEs aren't generally useful in Debian. I typically first look at the --help output of a program, the manpage, and then whatever I can find in /usr/share/doc/PACKAGE... and I daresay I find this to be quite productive approach. >>> Great idea! Are you aware that the README does not mention >>> "debconf-get-selections" once? So it would take someone who does this >>> every day to think of this excellent solution. Thank you for sharing >>> this. I recommend adding it to the README, maybe the HowTo.. >> >> This could perhaps be briefly touched on in the simple-cdd README, and >> referencing relevent chapters of the debian-installer manual. > > It probably belongs in the same section that the first item does about > debconf templates. In a section about how to create a useful preseed > file. Thanks. >> If you load the preseeding after the question has already been asked, >> then at best, it doesn't magically travel through time an un-ask the >> question... at best, it does nothing, at worst, it might trigger bugs. > > That makes sense but it does not relate to anything clear about how > NAME.preseed works, how --preseed works, and how --auto-preseed works. > Please, I've asked this every way that is possible. Please document > this interplay. There are no --preseed or --auto-preseed options for simple-cdd; I presume you're referring to --profiles and --auto-profiles. I've tried to explain over and over again how they behave, and I'm still unsure what would be documentation that would work for you on this point, so I am apparently every bit at a loss as you are, unfortunately. Let's come back to that once I've had a chance to troubleshoot the locale/country/keyboard selection issues; expected behavior is a bit difficult to demonstrate if there are bugs affecting exactly that behavior. >> an't know for sure, but sounds like it *might* be a bug in the code. >> >> If you could re-try with "simple-cdd --locale=en_CH --keyboard=us" with >> an empty ./profiles directory and empty ./images directory (you can >> probably leave ./tmp, since it sounds like you don't have much >> bandwidth), that would be great. > > I did this, moved profiles/ and deleted images/. The new image was > generated in seconds which makes me wonder if I was really doing what > you want. Thanks for testing. It shouldn't take long when you have all or most of the packages already in the local mirror under ./tmp, so it does not surprise me that the build went quickly. > Anyway, the result is the same. I am asked what installer to use, I > choose regular "Install" and The bootloader prompting you (e.g. where you had to choose "Install") is handled by something else entirely. The "test" profile included as part of simple-cdd sets the BOOT_TIMEOUT debian-cd option in order to handle this. > my first question is what language to use. Ok, I'll attempt to reproduce the issue locally and debug it. > One difference is you wrote "simple-cdd --locale=en_CH --keyboard=us" > but I used "build-simple-cdd --locale=en_CH --keyboard=us" and I think > that was just a typo right? Anyway I also did it your way and the > result was the same. It should make no difference, simple-cdd and build-simple-cdd are symlinks to the same file. > So it's looking like a bug. I will do more testing if you want, including a > new images/ directory. It sounds like I need to test it for myself at this point and see if I can reproduce the issue(s), so maybe best to wait until I get that chance. It may take me a week or so. live well, vagrant
signature.asc
Description: PGP signature
