Am Freitag, 7. Juni 2024, 18:24:11 CEST schrieb Michael Kjörling: Hi Michael, > On 7 Jun 2024 18:01 +0200, from hans.ullr...@loop.de (Hans): > > For my own purposes I am building a live-debian ISO with installer. > > How are you doing this? I am starting with lb config (to get a straight live-build environment).
After this I am edititing all entries in ~/config/bootstrap | binary | common from "bullseye" to "bookworm". At last I am editing the entry for the name of the image from "live-image" to "RustDesk-live- image" (I want it so be named). Then lb config --purge. After this, I am starting with my own shell script, which contents this line: -------------------- ... lb config --purge lb config --debian-installer live --bootappend-live "boot=live username=myname hostname=my_hostname..............." (keyboard definitions and so on) lb build -------------------- This worked, but from one day to another no more, and this is strange! I also did a fresh live-build-environment installation, then it worked 3 or 4 times, and then it broke again. > > Can you post a script (or something similar) which reliably > demonstrates the issue when executed within a fresh Debian system? > The issue is not in the Debian itself, but it happens, when I want to install it. It happens as well on a native system as in Virtualbox itself. Maybe I could upload the ISO somewhere, it can be used in Virtualbox and shows the crash there, too. However, the ISO is 700MB and you need 8GB harddrive in Virtualbox. Think, not a goo idea. > > I also tried to install grub manually in the console during installation > > process, using "grub-installer /target", but this did neither work nor > > show > > much usefull information. > > Should we take this to mean that it did show _some_ "useful > information"? If so, what _did_ it show? No, it did not show any usefull information. Messages like "grub-installer failed" is no usefull information! No reason why... > > It appears that you are trying something; having some issue; see > symptoms; draw conclusions; and then tell us about your conclusions > and ask for a solution to your issue so as to be able to continue with > what you're trying to do. But without us being able to see what you > are doing and what happens when you do, _in full_, it's nearly > impossible to guess from your conclusions what might cause the issue > you're having in the first place. > Yeah, I know. If I got more information for myself, maybe I could find the reason for myself, too. But the installer does not show > Show us _exactly_ what's happening, as far as you are able. At a > minimum, make it easy for others to recreate a situation in which you > see the specific problem. > > In other words, a minimal (non)working example. At the moment, I try to use the installer from bullsyeye and the system of bookworm. It can be set in the live-build configurations. Maybe it is a problem with the debian-bookworm repo (mirroring in process, whatever) and tomorrow it will magiacally work again. So, I suppose, we should wait. I will try some things here and maybe I can fix it though. Thanks for help anyway. Best regards Hans
