Processed: block 941627 with 840248
Processing commands for cont...@bugs.debian.org: > block 941627 with 840248 Bug #941627 [wnpp] ITP: grub-btrfs -- provides grub entries for btrfs snapshots (boot environments/restore points) 941627 was not blocked by any bugs. 941627 was not blocking any bugs. Added blocking bug(s) of 941627: 840248 > thanks Stopping processing here. Please contact me if you need assistance. -- 941627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Avoiding low-memory warning in preseed mode
On Thu, 3 Oct 2019 at 13:38, David wrote: [...] Sorry, I forgot to mention that I also tried Samuel's suggestion, just for self-education purposes, to follow along and see what I can learn. On Wed, 2 Oct 2019 at 21:11, Samuel Thibault wrote: > As suggested in the "Creating a preconfiguration file" section of the > installation manual, the easiest way is to install by hand in these > conditions and then use debconf-get-selections --installer On this machine I am running now I get the below output, which I hope is useful just as an example for discussion. All the lines in it look similar to what you provided in your original message. So I'm not clear how running that command will provide any extra information that would solve your issue. I can understand how it would be helpful in the case of Type:boolean, but I don't see how it helps in the situation of Type:note, that I've just learned about today. # debconf-get-selections --installer | grep -E '\bnote\b' d-isave-logs/httpd_runningnote partman-cryptopartman-crypto/nothing_to_setupnote d-icdrom-checker/firstcdnote finish-installfinish-install/reboot_in_progressnote partman-lvmpartman-lvm/displayallnote partman-basepartman/show_partition_chsnote d-ilocalechooser/translation/none-yetnote d-ilocalechooser/help/localenote d-icdrom-detect/successnote partman-basepartman/show_free_chsnote nobootloadernobootloader/confirmation_powerpc_paseminote partman-lvmpartman-lvm/helpnote d-icdrom-detect/unetbootin_detectednote netcfgnetcfg/dhcp_failednote d-idi-utils-shell/do-shellnote lilo-installerlilo-installer/serial-consolenote d-isave-logs/insert_floppynote d-icdrom-checker/askmountnote d-icdrom-checker/passednote nobootloadernobootloader/confirmation_powerpc_chrp_pegasosnote d-isave-logs/no_networknote netcfgnetcfg/wpa_supplicant_failednote netcfgnetcfg/kill_switch_enablednote partman-cryptopartman-crypto/tools_missingnote d-ilowmem/lownote partman-targetpartman-target/helpnote d-ilocalechooser/translation/no-selectnote nobootloadernobootloader/confirmation_commonnote partman-basepartman/exception_handler_notenote
Re: Avoiding low-memory warning in preseed mode
On Thu, 3 Oct 2019 at 02:11, Fred Boiteux wrote: Previously, I wrote: > > I do not know the answer, but I can tell you what I would try: > > > > d-i lowmem/low boolean true > > d-i lowmem/insufficient boolean true I now think that my advice there was wrong. > > You can see the sentences in the code here: > > https://sources.debian.org/src/lowmem/1.47/debian/lowmemcheck.templates/ The exact error message that you provided confirms that the relevant code in that file is this: """ Template: lowmem/low Type: note # Note: not translatable, runs before language is chosen Description: Entering low memory mode This system has relatively little free memory, so it will enter low memory mode. Among other things, this means that this program will proceed in English. You should set up swap space as soon as possible. """ > > I showed "true" as an example. But I can't know if you > > need "true" or "false" because it depends > > which button in the dialog is the one you want. I now think this is wrong advice. Because the above code says "Type: note" not "Type: boolean" So I tried to learn more about Type: note. At https://wiki.debian.org/DebianInstaller/Preseed#Notes I found two relevant advices: Be aware there is only one space in preseed files between subkey and value on "owner key/subkey value" lines. Look in debconf-devel(7) in the debconf-doc package for more docs about d-i and debian-installer preseed questions. In 'man 7 debconf-devel' I read about Type: note Searching the web for example use of Type: note, I found https://wiki.ubuntu.com/Enterprise/WorkstationAutoinstallPreseed which contains """ # Avoid that last message about the install being complete. d-i finish-install/reboot_in_progress note """ which is the same technique as what you tried in your first message, so it is strange that it does not work in your use case. I could not find any other documentation on how to handle this situation. So I apologise for wasting your time. As I mentioned I'm still a newbie in this area, but I hope to learn by engaging and discussing things that I don't yet understand. Maybe someone else knows how to handle this situation, or can confirm that it's buggy if it works in that Ubuntu situation but does not work in your situation.
Bug#935931: Re: Bug#935931: debian-installer: Reinstalling Debian on a current Debian installation without erasing or fomatting the home folder
On Mon, Sep 30, 2019 at 12:51:33PM -0400, Daniel wrote: > Dear Lennart, > > I hope that when one opens a "whishlist bug" at least there is a chance to > have a confrontation. > > The main point I want to address is when you do a "smart installation" it is > supposed to perform a clean installation hence the only folder that must to > be untouched is "/home". The same concept when you have "/" and "/home" in > separated partitions and you perform a clean installation. I think that is > pretty trivial, the smart parts are: > > * the installer is able to check for a previous Debian installation before > to begin the process; > > * and in case it founds a previous installation, the installer, is able to > perform a fresh installation without overwriting the "/home" folder. Well I believe you have the option to not format a mountpoint during the install already, so at least that part should be pretty easy. > I can confirm that ElementaryOS and POP!_OS, that share the same installer, > can do that. Well hopefully someone will try to contribute that then. I suspect the main thing is finding someone that wants to implement it and do the work to add it and maintain it. > Last point I want touch is about the swap partition. With the SSD and the OS > able to boot in a bunch of seconds the hibernation doesn't make any sense > today. For example I have 16GB of ram, based on the standard rules I should > use at least 1.5x of the ram if not the double. It means that I should use > 32GB just to hibernate my session, no way... With the SSD disks the lesser > you write on the disk the better, I put just 2GB of swap-file and > "swappiness" at 1 and the swap is never used and I didn't waste 30GB of > space. Only advantage to huibernation is not having to close all the things you are working on and opening them again after the next boot. I do find hibernation takes too long with a lot of ram and hence never do it myself. :) > To conclude I think I elaborated everything clearly, I see a lot of benefits > and improvement with the suggestions I gave to Debian, I also think that are > pretty trivial to implement. I don't want introduce a Windows behavior of > "reinstall when it broken", but back to time when I hadn't a fast internet > connection it was faster download the full ISO and performing a fresh > installation rather than doing a "dist-upgrade". I remember upgrades over dial up. Still did not make me want to go download full iso images elsewhere. It could do it while I slept. Things have gotten a lot bigger since then though. I have seen people keep a subset mirror of Debian on a USB drive that they would update with rsync once in a while at work, and bring home to use for upgrades where the connection was slow. Still in place upgrades of course, not using the installer. > The bottom line is with a smart installer you don't need to separate your > disk(s) in partitions but you can throw everything in "/" including the > "swap" as swap-file that you can modify freely based on your needs (if you > can't live without hibernation[1]). There is also a dynamic swap manager > available on Debian as well: https://github.com/Tookmund/Swapspace -- Len Sorensen
how to setup a small local Debian mirror to install a VM without an internet access
Hello, I'm trying to install automatically (using preseed) a Debian Buster 10.1 system on a VM hosted on a system without internet access, using a netboot. Thanks to Steve McIntyre explanations (see #940801), I know how to update the netboot's initrd to include the virtio_blk driver, and the debian installer is now well detecting the VM's disk, and after partitionning it, it tries to download some Debian packages to install a minimal system on this new disk. For this purpose, i've setup a local Debian mirror copying the files on DVD-1 debian installer, but the debian-installer refuse to use it, because it's not GPG-signed, and so fails to install any package : Sep 26 07:35:26 apt-install: Queueing package keyboard-configuration for later installation Sep 26 07:35:26 apt-install: Queueing package console-setup for later installation Sep 26 07:35:26 base-installer: Ign:1 http://192.168.254.254/buster_debian_installer buster InRelease Sep 26 07:35:26 base-installer: Get:2 http://192.168.254.254/buster_debian_installer buster Release [33.5 kB] Sep 26 07:35:26 base-installer: Ign:3 http://192.168.254.254/buster_debian_installer buster Release.gpg Sep 26 07:35:26 base-installer: Reading package lists... Sep 26 07:35:26 base-installer: Sep 26 07:35:26 base-installer: E: The repository 'http://192.168.254.254/buster_debian_installer buster Release' is not signed. Sep 26 07:35:26 base-installer: warning: apt update failed: 100 Sep 26 07:35:26 base-installer: dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename Sep 26 07:35:27 in-target: Reading package lists... Sep 26 07:35:27 in-target: Sep 26 07:35:27 in-target: Building dependency tree... Sep 26 07:35:27 in-target: Package locales is not available, but is referred to by another package. Sep 26 07:35:27 in-target: This may mean that the package is missing, has been obsoleted, or Sep 26 07:35:27 in-target: is only available from another source Sep 26 07:35:27 in-target: Sep 26 07:35:27 in-target: E: Package 'locales' has no installation candidate Sep 26 07:35:27 localechooser: error: the command 'validlocale' is not available Sep 26 07:35:27 base-installer: info: Found kernels '' Sep 26 07:35:27 base-installer: error: exiting on error base-installer/kernel/no-kernels-found Yet, I have in my preseed.txt the following statement : # By default the installer requires that repositories be authenticated # using a known gpg key. This setting can be used to disable that # authentication. Warning: Insecure, not recommended. #d-i debian-installer/allow_unauthenticated boolean true d-i debian-installer/allow_unauthenticated boolean true How can I tell Debian-installer, through the preseed file or another mean, to use my [unsigned] repository ? with regards, Fred.
Re: Avoiding low-memory warning in preseed mode
Hi Fred I do not know the answer, but I can tell you what I would try: d-i lowmem/low boolean true d-i lowmem/insufficient boolean true You can see the sentences in the code here: https://sources.debian.org/src/lowmem/1.47/debian/lowmemcheck.templates/ I showed "true" as an example. But I can't know if you need "true" or "false" because it depends which button in the dialog is the one you want. Also I don't know if you need one, or both lines, because you did not provide the exact text of the message. Please reply to advise if you have success or failure. Hello David, I've tried to add the 2 given lines, with 'true' value, then with 'false' value, without any behaviour change :-( The exact message is : Entering low memory mode : This system has relatively little free memory, so it will enter low memory mode. Among other things, this means that this program will proceed in English. You should setup swap space as soon as possible. and there is an unique button « Continue »... I can't try at now the solution suggested by Samuel, because my install fails later, I'll do another e-mail for this purpose, but I'll try it as soon as I'll fixed this latter problem. Thanks for your help, Fred.
Bug#941300: finish-install: write random seed to correct location for chosen init system
On Wed, 2019-10-02 at 17:59 +0800, Ian Campbell wrote: > If it's going to override/shadow (as opposed to simply working > alongside/in parallel) urandom, probably it ought to also be looking > at/consuming the urandom seed? Perhaps. I'm not sure systemd upstream would be convinced though. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Avoiding low-memory warning in preseed mode
On Wed, 2 Oct 2019 at 22:02, Samuel Thibault wrote: > David, le mer. 02 oct. 2019 21:53:08 +1000, a ecrit: > > On Wed, 2 Oct 2019 at 21:46, Samuel Thibault wrote: > > Thanks for your work on Debian!!! > > Thanks for providing a link this time. > Finding the link took me the time to google for "debian installation > manual", choose the english language, and look for the "Creating a > preconfiguration file" item in the table of contents. Hey, my thank-you was 100% genuine. I noticed that you made an extra effort to find the link for us, it was helpful to me and so I said thank you. It's easy for newbies to get lost in Debian documentation, especially we don't know what has been superceded or current. When a developer recommends something, it's helpful.
Re: Avoiding low-memory warning in preseed mode
David, le mer. 02 oct. 2019 21:53:08 +1000, a ecrit: > On Wed, 2 Oct 2019 at 21:46, Samuel Thibault wrote: > > Which provides the same information as the installation manual > > https://www.debian.org/releases/stable/amd64/apbs03.en.html > > Hi Samuel > > Thanks for your work on Debian!!! > > Thanks for providing a link this time. Finding the link took me the time to google for "debian installation manual", choose the english language, and look for the "Creating a preconfiguration file" item in the table of contents. Samuel
Re: Avoiding low-memory warning in preseed mode
On Wed, 2 Oct 2019 at 21:28, john doe wrote: > Have a look at (1). > 1) https://wiki.debian.org/DebianInstaller/Preseed#Custom_preseed_files I remember reading that document a little while ago when I first got my hands dirty attempting to preseed some VM. Regarding template files discussed in the section: https://wiki.debian.org/DebianInstaller/Preseed#Preseeding_and_the_installer.27s_debconf_templates I find "sed | awk | sed | sed | sed | awk | sed" style approaches completely horrifying and for that purpose it made a lot more sense to me to just do: git clone https://salsa.debian.org/installer-team/d-i.git to get the packages and template files where I can search them locally. But I'm still a newbie in this area so I'm far away from having much understanding what I'm doing or any confidence or ability to recommend ways of doing things.
Re: Avoiding low-memory warning in preseed mode
On Wed, 2 Oct 2019 at 21:46, Samuel Thibault wrote: > john doe, le mer. 02 oct. 2019 13:28:32 +0200, a ecrit: > > On 10/2/2019 1:11 PM, Samuel Thibault wrote: > > > Fred Boiteux, le mar. 01 oct. 2019 16:09:05 +0200, a ecrit: > > >> d-i lowmem/low note > > >> > > >> Does someone can tell me which sentence is supposed to be used in preseed > > >> file to skip this manual validation ? > > > > > > As suggested in the "Creating a preconfiguration file" section of the > > > installation manual, the easiest way is to install by hand in these > > > conditions and then use debconf-get-selections --installer > > > > > > > Have a look at (1). > > > > 1) https://wiki.debian.org/DebianInstaller/Preseed#Custom_preseed_files > > Which provides the same information as the installation manual > https://www.debian.org/releases/stable/amd64/apbs03.en.html Hi Samuel Thanks for your work on Debian!!! Thanks for providing a link this time. You wrote that "the easiest way is to ..." but the link you provided really does not encourage newbies to use that method: """ a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users. """ So it's interesting that you encourage us in that direction, thanks. Now I can choose between "easiest" and "better" :)
Re: Avoiding low-memory warning in preseed mode
john doe, le mer. 02 oct. 2019 13:28:32 +0200, a ecrit: > On 10/2/2019 1:11 PM, Samuel Thibault wrote: > > Hello, > > > > Fred Boiteux, le mar. 01 oct. 2019 16:09:05 +0200, a ecrit: > >> d-i lowmem/low note > >> > >> Does someone can tell me which sentence is supposed to be used in preseed > >> file to skip this manual validation ? > > > > As suggested in the "Creating a preconfiguration file" section of the > > installation manual, the easiest way is to install by hand in these > > conditions and then use debconf-get-selections --installer > > > > Have a look at (1). > > 1) https://wiki.debian.org/DebianInstaller/Preseed#Custom_preseed_files Which provides the same information as the installation manual https://www.debian.org/releases/stable/amd64/apbs03.en.html but with less details. Samuel
Re: Avoiding low-memory warning in preseed mode
On 10/2/2019 1:11 PM, Samuel Thibault wrote: > Hello, > > Fred Boiteux, le mar. 01 oct. 2019 16:09:05 +0200, a ecrit: >> d-i lowmem/low note >> >> Does someone can tell me which sentence is supposed to be used in preseed >> file to skip this manual validation ? > > As suggested in the "Creating a preconfiguration file" section of the > installation manual, the easiest way is to install by hand in these > conditions and then use debconf-get-selections --installer > Have a look at (1). 1) https://wiki.debian.org/DebianInstaller/Preseed#Custom_preseed_files -- John Doe
Re: Avoiding low-memory warning in preseed mode
Hello, Fred Boiteux, le mar. 01 oct. 2019 16:09:05 +0200, a ecrit: > d-i lowmem/low note > > Does someone can tell me which sentence is supposed to be used in preseed > file to skip this manual validation ? As suggested in the "Creating a preconfiguration file" section of the installation manual, the easiest way is to install by hand in these conditions and then use debconf-get-selections --installer Samuel
Re: Avoiding low-memory warning in preseed mode
On Wed, 2 Oct 2019 at 15:56, Fred Boiteux wrote: > When launching the install of a Debian Buster 10.1 on a VM with a small > memory footprint (512Mb), I get a warning from the Debian installer > about entering in low-memory mode. I would like to have a > non-interactive installation using a preseed file, but I didn't found > how to avoid this warning which blocks installation until I manually > validates the message in console. I've digged on Internet, and tried > following preseed paragraph, without success : > > d-i lowmem/low note > > Does someone can tell me which sentence is supposed to be used in > preseed file to skip this manual validation ? Hi Fred I do not know the answer, but I can tell you what I would try: d-i lowmem/low boolean true d-i lowmem/insufficient boolean true You can see the sentences in the code here: https://sources.debian.org/src/lowmem/1.47/debian/lowmemcheck.templates/ I showed "true" as an example. But I can't know if you need "true" or "false" because it depends which button in the dialog is the one you want. Also I don't know if you need one, or both lines, because you did not provide the exact text of the message. Please reply to advise if you have success or failure.
Bug#941300: finish-install: write random seed to correct location for chosen init system
On Wed, 2019-10-02 at 08:59 +0800, Paul Wise wrote: > On Tue, 2019-10-01 at 11:55 +0100, Steve McIntyre wrote: > > > Wouldn't it just be easier to write it one location and replace the > > other with a symlink to it? > > Looks like neither the urandom init script nor systemd-random-seed > unlink the file before writing to it, so this could potentially work > unless that changes at some point. Just writing two different seeds > avoids the need to care about what the implementations will do in the > future so I think it is safer. The original report says: > systemd-random-seed.service overrides the urandom init script > but uses a different location for its random seed file If it's going to override/shadow (as opposed to simply working alongside/in parallel) urandom, probably it ought to also be looking at/consuming the urandom seed? Ian.
Bug#941026: netcfg_gateway_reachable wrongly rejects IPv6 link-local addresses
On 2019-09-23 18:00, Andrew Kanaber wrote: When doing static IP configuration, netcfg will reject a gateway address outside the host's network as defined by the netmask. This is wrong for IPv6 because the gateway can legitimately be a link-local address in fe80::/64 instead of the host's network range. Ubuntu have fixed this bug in their version, see LP#1382295 https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1382295 The relevant function is netcfg_gateway_reachable in netcfg-common.c which simply checks gateway_address & netmask == host_address. It should also allow IPv6 addresses in the link local prefix fe80::/64. Less importantly, the error message it triggers could be a bit clearer, "The gateway address you entered is unreachable" sounds like it might be a network error when it's purely a user-input parsing rejection - if the code had actually tried the link-local address it would've worked. So how does it identify the interface to use in this case? Does the kernel have special support to pick the correct one if there is only one non-loopback interface? Generally link-local addresses do need to be qualified with the interface to be used. Kind regards Philipp Kern
