Hello, Okay I think I got it, I thought apt would silence the whole process including the subsystems it calls. The man page just says "Force yes; This is a dangerous option that will cause apt to continue without prompting if it is doing something potentially harmful." That is what you assume it will do then...
I do have a backup kernel, but usually I boot into the compiled kernel, end up tweaking and recompiling then I want to boot into the newly compiled kernel. The complaint is that I'm removing the *running* kernel, not the *last* kernel. So it will go custom -> custom -> custom -> broken kernel -> backup. I'm not quite that ready to hose my system :) Thanks for your time, I'm going to see what force options dpkg has now then... Regards, Kjell Rune --- Den tir 2010-11-02 skrev David Kalnischkies <[email protected]>: > Fra: David Kalnischkies <[email protected]> > Emne: [Bug 669759] Re: Still get warning dialog with --force-yes > Til: [email protected] > Dato: Tirsdag 2. november 2010 18.33 > Many applications are involved in an > apt-get run. The application showing you this question is > for example debconf which is responsible for asking > questions for the package dpkg works on which is called by > apt-get. The --force-yes only influences the questions APT > will ask you - questions dpkg will present you about config > files are not included (question in which you have three or > more options aren't really yes/no questions anyway…) and > packages can ask very complicated non-yes/no questions, > too. > Where are options to silence them to, see the relevant > manpages for them (dpkg and debconf at least). > > But, and thats the turning point here: That you see that > question is > your own fault - as the question is included in your > package, so i would > suggest you don't ask this question if you don't want them > ;P > > > Beside that: Its really not a good idea to remove the > running kernel - as the question already says - and i really > don't see why you want that at all. Just imagine your new > custom kernel build is broken and unable to boot… > > -- > Still get warning dialog with --force-yes > https://bugs.launchpad.net/bugs/669759 > You received this bug notification because you are a direct > subscriber > of the bug. > > Status in “apt” package in Ubuntu: Invalid > > Bug description: > Binary package hint: apt > > Lately I've been experimenting with building my own kernel > from git and building a custom deb. For that reason I often > want to remove the currently running kernel and install a > new one. So basically I have a script: > > apt-get remove -y --force-yes linux-headers-2.6.36-custom > linux-image-2.6.36-custom > dpkg -i linux-headers-2.6.36-custom*.deb > linux-image-2.6.36-custom*.deb > > However, even with --force-yes I get a warning (screenshot > attached) removing the kernel. Now I understand this is > normally a really, really stupid thing to do but I thought > that was the point of --force-yes. If not I'd like an > --i-am-insane option to REALLY don't prompt. > > ProblemType: Bug > DistroRelease: Ubuntu 10.10 > Package: apt 0.8.3ubuntu7 > Uname: Linux 2.6.36-custom x86_64 > Architecture: amd64 > Date: Tue Nov 2 04:23:59 2010 > InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - > Release amd64 (20101008) > ProcEnviron: > LANGUAGE= > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: apt > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/669759/+subscribe > -- Still get warning dialog with --force-yes https://bugs.launchpad.net/bugs/669759 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
