Bug#1064617: update password selection advice

On Tuesday, 19 March 2024 12:08:53 CET Holger Wansing wrote: > Apparently we have reached something like a consensus on this topic, > should we merge this then? > > > > Any objections? LGTM :-) possibly `s/rms/debra/` with

Re: Bug#1055016: override: tasksel-data:admin/optional

On Sunday, 29 October 2023 12:54:13 CET Cyril Brulebois wrote: > Daniel Lewart (2023-10-29): > > Package: ftp.debian.org > > Severity: normal > > User: ftp.debian@packages.debian.org > > Usertags: override > > X-Debbugs-Cc: task...@packages.debian.org, debian-boot@lists.debian.org, > >

Bug#1064617: Passwords should not be changed frequently

On Friday, 8 March 2024 19:58:56 CET Philip Hands wrote: > IMO Having the 'password/passphrase' throughout makes it awkward to > read, and actually we've got one place where it still just says > password, and fixing that would make it slightly worse IMO. > > How about dropping the passphrase

Bug#1064617: Passwords should not be changed frequently

On Wednesday, 6 March 2024 13:19:04 CET Justin B Rye wrote: > Maybe instead of saying "use the system's initial user account to > become root" it should say "allow the system's initial user account > to gain administrative privileges"? I'm not sure. Oh, and we might > even want to mention the

Bug#1064617: Passwords should not be changed frequently

On Tuesday, 5 March 2024 19:28:25 CET Cyril Brulebois wrote: > Philip Hands (2024-03-05): > > Cool, in that case I'll fix those two things and then use the result > > for the MR[1], and if the openQA test runs look OK, will merge that. > > Only skimmed over it, but that looks sensible, thanks

Bug#1064617: Passwords should not be changed frequently

On Monday, 4 March 2024 22:30:57 CET Holger Wansing wrote: > > https://wiki.debian.org/Passwords doesn't exist (yet), but it's an easy to > > remember URL and we'd have all the space we need to give proper advise? > > Would need to check if that fits in the relevant screens (I want to avoid >

Bug#1064617: Passwords should not be changed frequently

On Monday, 4 March 2024 10:43:59 CET Holger Wansing wrote: > >Regarding the password advice, I ended up concluding that it's pretty > >unlikely that anything we say at this point will have any effect on > >people's behaviour, but then I'm probably just an old cynic. Also, I > >failed when trying

Bug#1064617: Passwords should not be changed frequently

On Saturday, 2 March 2024 21:07:34 CET Philip Hands wrote: > I don't actually care very much whether we encourage sudo use. A person who I consider very knowledgeable deliberately went for sudo and disabled the root account for security reasons. It was an image provided by him that I ended up

Bug#1064617: Passwords should not be changed frequently

Hi, On Friday, 1 March 2024 20:46:49 CET Holger Wansing wrote: > Philip Hands wrote (Fri, 01 Mar 2024 06:46:27 +0100): > > If you want to make a constructive contribution, how about suggesting a > > wording that reflects the advice that you think would be most useful to > > the people that

Bug#1064617: Passwords should not be changed frequently

Hi Philip, On Friday, 1 March 2024 06:46:27 CET Philip Hands wrote: > Having helped people to install Linux for ~30 years, I'd say that it's > the norm for people to be almost incapable of coming up with a decent > password if they were not expecting the question. I fully agree that most people

Bug#1064617: Passwords should not be changed frequently

On Thursday, 29 February 2024 23:13:55 CET Holger Wansing wrote: > > in which I'm recommending setting no password for root, which then gives > > the initial user 'sudo' membership[1]. > > What about the "Allow login as root?" question (only shown in expert mode), > which is asked directly before

Bug#1058806: HP EliteBook 860 G9 (4C148AV)

On Saturday, 16 December 2023 22:16:32 CET Pascal Hambourg wrote: > According to /usr/share/misc/pci.ids, this device has PCI ID 8086:51f0 > which is listed in bookworm's iwlwifi module aliases. > Can you post the output of the following commands after booting with > kernel 6.1 ? Could it be the

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

On Saturday, 25 November 2023 08:37:09 CET Cyril Brulebois wrote: > Hard to tell without any logs. The output of `lsmod` and `dmesg` from both Ubuntu and Debian may also help to figure out why it's working in one but not the other. signature.asc Description: This is a digitally signed message

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

On Wednesday, 11 October 2023 20:05:43 CEST Emanuele Rocca wrote: > To triple-check that the needed module is in there: > > zstdcat /initrd.img | cpio -itv | grep qnoc-sc8280xp.ko ICYDK: there's also an `lsinitramfs` command signature.asc Description: This is a digitally signed message part.

Bug#1043226: debian-installer: Please consider moving root user setup to expert install, or change text

On Monday, 7 August 2023 18:25:07 CEST Jonathan Carter wrote: > Source: debian-installer > Version: 20230607+deb12u1 > > Firstly, the instructions start off with "You need to set a password for > 'root'", followed by seemingly uninteresting text about what a good password > should be, which makes

Re: Default network configuration system (was Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie)

On Tuesday, 20 June 2023 13:11:14 CEST Diederik de Haas wrote: > The 'old world' Please ignore me. signature.asc Description: This is a digitally signed message part.

Re: Default network configuration system (was Re: proposal: dhcpcd-base as standard DHCP client starting with Trixie)

On Tuesday, 20 June 2023 11:19:08 CEST Lukas Maerdian wrote: > IMHO ifupdown{2,-ng} is the "old world" The 'old world' and 'not of this time (anymore)' are the absolute worst arguments against something, typically used when no substantive arguments can be made. > potentially in combination

Re: Bug#1029843: Missing symlinks for RPi 4 (to brcmfmac43455-sdio.raspberrypi,4-model-b.txt)

On Monday, 8 May 2023 14:08:14 CEST James Addison wrote: > On Mon, 1 May 2023 11:18:03 +0100, James Addison wrote: > > > Diederik de Haas (2023-04-30): > > > > And that's exactly what happens or will happen. Even though the RPi4 > > > > filename doesn

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

On Friday, 5 May 2023 17:45:34 CEST Fabian Greffrath wrote: > Today I attempted to install Debian bookworm on a brand new Lenovo > IdeaPad 5 14IAL7 with an i5-1235U CPU, 16GB RAM and 512GB SDD. > > The installation failed to proceed at the network card detection > stage. Apparently, the machine

Re: Bug#1029843: brcmfmac: requested firmware filename inconsistent with linux-firmware.git on non-devicetree systems

Control: block -1 1035505 On Thursday, 4 May 2023 01:41:12 CEST Cyril Brulebois wrote: > Diederik de Haas (2023-05-04): > > And that makes it a firmware-brcm80211 issue and now it all does make > > sense as it now all does tie together :-) > > Great, that's what it lo

Re: Bug#1035392: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters

On Wednesday, 3 May 2023 17:18:42 CEST James Addison wrote: > The system's dmesg includes this line: > > DMI: Raspberry Pi Foundation Raspberry Pi 400/Raspberry Pi 400, BIOS > UEFI Firmware v1.34 1 2/16/2022 > > As Cyril said though.. this can't (shouldn't) be genuine DMI. So > what's going

Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters

On Wednesday, 3 May 2023 03:41:05 CEST James Addison wrote: > I think that the vendor name is coming from a DMI fallback: > > https://sources.debian.org/src/linux/6.1.25-1/drivers/net/wireless/broadcom/ > brcm80211/brcmfmac/common.c/?hl=487#L487 > > Whether the model name is from DMI or from the

Re: RFC: android-style boot image support for flash-kernel

On Sunday, 30 April 2023 23:28:23 CEST Roger Shimizu wrote: > Currently, the dev-board is supported by Linaro [2][3], and most > kernel device-tree, patches and firmware are already upstreamed. > I confirmed that with simple snippet below, generated boot.img can be > used to boot the RB3 / DB845c

Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters

On Sunday, 30 April 2023 20:25:50 CEST James Addison wrote: > Do we _need_ to retain the vendor name and model name in the firmware > filename? > > My guess (without being too familiar with the firmware loading process yet) > is that it'd be easier to ship a concisely-named file that omit the

Re: netboot's kernel version does not match linux-image-amd64

On Tuesday, 25 April 2023 18:09:59 CEST Emanuele Rocca wrote: > On 2023-04-25 06:02, Roland Clobus wrote: > > On 25/04/2023 17:38, ign...@tuta.io wrote: > > > Package: debian-installer-12-netboot-amd64 > > > Version: 20230217 > > > > That's an old image. For Bookworm (Debian 12) the kernel is

Bug#1033985: debian-installer: Installer sets grub up without existing Windows boot choice

On Wednesday, 5 April 2023 22:04:57 CEST Cyril Brulebois wrote: > you should be able to activate os-prober via some configuration > file under /etc (probably /etc/default/grub). Correct, the setting is GRUB_DISABLE_OS_PROBER=false /me wonders why that default changed ... signature.asc

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

On Saturday, 25 February 2023 08:46:21 CET Bastian Bittorf wrote: > There was an argument by steve: > "waste hundreds of gigabytes on swap space." > > => If a computer has "hundreds of gigabytes" of RAM > (and so swap), you do not care - you have enough resources anyway. The use-case which was

Re: Bug#1031289: linux: Missing sound drivers (and speakup) in d-i on arm64

On Monday, 20 February 2023 01:07:29 CET Samuel Thibault wrote: > Diederik de Haas, le lun. 20 févr. 2023 00:38:28 +0100, a ecrit: > > On Monday, 20 February 2023 00:27:57 CET Samuel Thibault wrote: > > > Diederik de Haas, le lun. 20 févr. 2023 00:14:19 +0100, a ecrit: >

Re: Bug#1031289: linux: Missing sound drivers (and speakup) in d-i on arm64

Control: tag -1 -moreinfo On Monday, 20 February 2023 00:38:28 CET Diederik de Haas wrote: > On Monday, 20 February 2023 00:27:57 CET Samuel Thibault wrote: > > Diederik de Haas, le lun. 20 févr. 2023 00:14:19 +0100, a ecrit: > > > On Tuesday, 14 February 2023 18:10:11 CET Sam

Re: Bug#1031289: linux: Missing sound drivers (and speakup) in d-i on arm64

On Monday, 20 February 2023 00:27:57 CET Samuel Thibault wrote: > Diederik de Haas, le lun. 20 févr. 2023 00:14:19 +0100, a ecrit: > > On Tuesday, 14 February 2023 18:10:11 CET Samuel Thibault wrote: > > > Some people on debian-accessibility wanted to install debian in arm64 &

Re: Bug#1031289: linux: Missing sound drivers (and speakup) in d-i on arm64

Control: tag -1 +moreinfo On Tuesday, 14 February 2023 18:10:11 CET Samuel Thibault wrote: > Some people on debian-accessibility wanted to install debian in arm64 > under the utm wrapped qemu on Macos. The current installation images > however do not include sound drivers and speakup. Currently

Re: Bug#1029543: hw-detect: clarify use cases about searching for firmware packages on external media

On Wednesday, 25 January 2023 23:01:01 CET Diederik de Haas wrote: > This sounds like a nice solution for the SD card images. > I myself always use a wired connection, but I saw yesterday that someone > tried to use d-i for RockPro64 but didn't get any output on screen and then > tried

Re: Bug#1029543: hw-detect: clarify use cases about searching for firmware packages on external media

On Wednesday, 25 January 2023 20:22:33 CET Cyril Brulebois wrote: > # SD card images (might also be applicable to the upcoming ChromeOS images) > ... > All of this assuming that the end results can be appended as the third > part of the + + combination! This sounds like a nice solution for the

Bug#1027692: installation-reports: successful with some wifi and encrypted /boot difficulties

On Monday, 2 January 2023 07:03:10 CET Vagrant Cascadian wrote: > Also wifi related, on first boot, there was no wifi device configured, > and I did not happen to install anything that pulled in > network-manager or something similar. I am not sure I even did an > install using wifi before, so

Bug#1025892: Installation at Ryzen 7000 not fully successfully

On Sunday, 11 December 2022 14:16:04 CET Bernhard wrote: > igc :04:00.0 eno1: PCIe link lost, device now detached https://lore.kernel.org/all/20221031170535.77be0...@kernel.org/ looks relevant signature.asc Description: This is a digitally signed message part.

Bug#1009014: installation-reports: Successful install on Pine64 Rock64 using serial console

On Thursday, 14 April 2022 18:56:40 CET Vagrant Cascadian wrote: > > I should see if it works via HDMI sometime... > > HDMI support required tracking down two modules already enabled in the > linux kernel but not present in the udebs used by debian-installer. This > should be fixed in the next

Re: Bug#1022900: grub-install, efibootmgr etc. not working with new kernel

Control: found -1 6.0.5-1 On Friday, 28 October 2022 23:09:00 CEST Stephan Verbücheln wrote: > I have now compiled and booted vanilla kernel 6.0.5. “efibootmgr -o” is > not working. > > I double-checked that with kernel 5.19.11 (Debian), it is working fine. Thanks for testing and reporting

Bug#678694: preseed_fetch fails with relative url

Hi Josch, On Friday, 13 May 2022 13:02:51 CEST Johannes Schauer Marin Rodrigues wrote: > You probably already saw Phils reply to #1010878 but if anybody else is > reading this I also wanted to quickly record what I did to avoid the > problem. It appears that Phil send it to you directly (and not

Bug#1010878: installation-reports: preseeding passwords doesn't work on mips64el under qemu

On Friday, 13 May 2022 09:35:49 CEST Johannes Schauer Marin Rodrigues wrote: > If I understand the docs of preseed_fetch correctly, then this should fetch > the setup-testbed script from a path relative to where it got the preseed > file from. > > Unfortunately this results in the following: > >

Re: ifupdown/dhcp

On Sunday, 8 May 2022 21:34:39 CEST Michael Tokarev wrote: > What's up with ISC dhclient? "ISC DHCP Client and Relay End of Maintenance" @ https://www.isc.org/blogs/dhcp-client-relay-eom/ Couple of quotes: "ISC plans to end maintenance of the ISC DHCP client and relay by the end of Q1, 2022."

Bug#1009670: installation-reports: Mostly working installation on rockpro64

On Thursday, 14 April 2022 05:02:26 CEST Vagrant Cascadian wrote: > On 2022-04-13, Vagrant Cascadian wrote: > > I will admit I used a tained image that added a couple modules for > > HDMI output on another platform (rock64); I'll check without the extra > > modules and report back if they're

Bug#999567: busybox: CVE-2021-42373 through CVE-2021-42386 (fixed in 1.34)

Control: tag -1 pending On 12 Nov 2021 16:54:06 +0100 Diederik de Haas wrote: > Package: busybox > Version: 1:1.30.1-7+b1 > Severity: important > Tags: security upstream fixed-upstream The new upstream version fixing these CVEs (and others) have been ready in salsa for several mon

Bug#1003973: Should we pull in fwupd by default for most systems?

On Tuesday, 18 January 2022 20:13:14 CET Steve McIntyre wrote: > At the moment, fwupd will only be installed by default on systems > installed to use a Gnome desktop (checked for Buster, Bullseye and > Sid). On Gnome, yes, but not other DE or systems where no DE is installed: $ apt-cache rdepends

Bug#881626: busybox: enable telnetd

On Tuesday, 18 January 2022 01:17:38 CET Jonathan Rubenstein wrote: > Maybe this is an indication that busybox-static needs to be audited, or > that all 3 configurations should be audited to make sure something isn't > missing that has no reason to be. IIUC, that is planned:

Bug#877953: busybox: FTBFS on hurd-any and kfreebsd-any

Hi James, On Sat, 7 Oct 2017 22:41:41 +0100 James Clarke wrote: > Forwarded: http://lists.busybox.net/pipermail/busybox/2017-October/ 085870.html > > Currently busybox FTBFS on the Hurd and GNU/kFreeBSD. I have submitted > the above patch series upstream to fix this. Of the 7 patches you

Bug#896902: Bug #896902 in busybox marked as pending

Control: tag -1 -pending On Sun, 29 Jul 2018 08:36:41 + Nobuhiro Iwamatsu wrote: > Control: tag -1 pending > > Bug #896902 in busybox reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below, and you can check the diff of the

Bug#985674: Fixed upstream in 1.33.1 and 1.34.0

Control: tag -1 fix-upstream The mentioned commit is fixed in upstream version 1.33.1 and 1.34.0. signature.asc Description: This is a digitally signed message part.

Bug#999567: busybox: CVE-2021-42373 through CVE-2021-42386 (fixed in 1.34)

Package: busybox Version: 1:1.30.1-7+b1 Severity: important Tags: security upstream fixed-upstream X-Debbugs-Cc: Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 https://security-tracker.debian.org/tracker/source-package/busybox already shows them. I learned it through

Bug#998803: busybox: Debian’s busybox’ tr violates POSIX

On Sun, 07 Nov 2021 23:25:11 +0100 Christoph Anton Mitterer wrote: > Package: busybox > Version: 1:1.30.1-7+b1 > > Unlike mandated by POSIX: > https://pubs.opengroup.org/onlinepubs/9699919799/utilities/tr.html > > busybox' tr in Debian doesn't seem to understand any of the character >

Bug#971946: Unlinking bug with MR

Control: notforwarded -1

Bug#971946: Linking bug with MR

Control: tag -1 patch Control: forwarded -1 https://salsa.debian.org/installer-team/libdebian-installer/-/merge_requests/2 signature.asc Description: This is a digitally signed message part.

Bug#928603: libdebian-installer - parser_rfc822: remove limitation on line length

On Tue, 7 May 2019 12:07:31 + Asbjørn Sloth Tønnesen wrote: > Package: libdebian-installer > Severity: wishlist > > As debated in #55 and #904699, the READSIZE limit is arbitrary, > parser_rfc822 should be rewritten to remove READSIZE, so that it > does't have to be increased again. +1

Bug#971946: libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment

Control: severity -1 grave On Sat, 10 Oct 2020 14:57:28 +0400 Jonathan Stanley wrote: > Package: libdebian-installer > Version: 0.119 > > When using cdebootstrap from within buster/stable to create a rootfs for > sid/unstable, it will fail with: > > W: parser_rfc822: Iek! Don't find end of

Same issue as already reported, and partially fixed

Control: severity -1 serious Hi, This is the same issue as https://bugs.debian.org/904699, which is actually an issue in libdebian-installer (https://bugs.debian.org/55). The fix has actually been made. But the problem is that it needs an unblock ack from the d-i team

Bug#554444: Rebuild for cdebootstrap-static?

Thanks for upping the limit in libdebian-installer :) But doesn't it require a rebuild for cdebootstrap-static to pick up this change? If so, could you do or request it? TIA, Diederik signature.asc Description: This is a digitally signed message part.

Bug#554444: Ping?

I just tried to install a Buster system with cdebootstrap(-static) and that fails because this bug is not fixed. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904699#15, increasing READSIZE from 16384 to 65536 'fixes' it. I agree that 65536 is also just a random number, but so

Bug#831513: installation-reports: Install on Asus ZenBook UX305CA largely successful (with a workaround)

Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: usb stick Image version: http://cdimage.debian.org/cdimage/stretch_di_alpha7/amd64/iso-cd/debian-stretch-DI-alpha7-amd64-netinst.iso retrieved on 2016-07-15 Date: 2016-07-15 05:22 Machine: Asus

Bug#694068: Still present with debian-stretch-DI-alpha7-amd64-netinst.iso

I bumped into this issue when I recently installed Debian on my new laptop. I only installed the "Standard system utilities", thus no network-manager and while wpasupplicant was installed the wireless connection config I used during installation wasn't written to a/the wpa_supplicant.conf file

Re: Bug#771208: unblock: busybox/1:1.22.0-14

On Thursday 11 December 2014 08:52:05 Ivo De Decker wrote: #768876 is tagged jessie-ignore so I'm really unconvinced by the debian/rules changes. It is jessie-ignore just to be non-RC. The fun with static linking and bugs it discovered shows that proper Built-Using field is really

Bug#769190: busybox-static: DNS resolver is broken again with the last upload

Package: busybox-static Version: 1:1.22.0-11 Severity: important This is basically the same error as with bug #757941, but it was reassigned to glibc and fixed there. As Aurelien Jarno correctly stated in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757941#120 it was indeed fixed with

Bug#768876: Wrong bug number fixed?

Bug nr 768926 is filed against qemu-user-static, and was supposedly fixed with busybox version 1.22.0-10 My guess is that that upload was supposed to fix bug nr 768876 and not 768926 -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.

Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7

On Tuesday 12 August 2014 21:46:43 Michael Tokarev wrote: Nope. This is getaddrinfo() function. So it is glibc, not gcc or optimization. getaddrinfo() does not work in jessie glibc when linked statically. It immediately returns Name or service not known (rc=-2) without trying to read

Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7

On Sunday 21 September 2014 17:34:24 Michael Tokarev wrote: This _is_ a glibc problem, and it can be trivially demonstrated by writing a tiny program that calls, say, getaddrinfo() on its argument. When built statically it always returns NOTFOUND, without any attempt to load any nss modules

Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7

Package: busybox-static Version: 1:1.22.0-8 Severity: important When trying to ping an address, like debian.org, with busybox-static you get a ping: bad address 'debian.org' error. I knew that version 1.22.0-6 of busybox-static was working, so I also downloaded version 1.22.0-7 and 1.22.0-8 and

Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7

On Tuesday 12 August 2014 21:16:06 Michael Tokarev wrote: Also, it is specific to amd64 arch, it does not happen on i386 (from 2 variants of x86 arches). It's not just limited to amd64, since I encountered the issue on raspbian for the Raspberry Pi, which is somewhere between armel and armhf.

Bug#678694: preseed_fetch fails with relative url

Package: preseed Severity: normal Tags: d-i Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Trying to install Debian Wheezy in a VirtualBox image using preseeding and trying to use the following line: d-i

Bug#678694: Also reported on Launchpad

See https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/909139 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206232126.40925.didi.deb...@cknow.org

Bug#637808: installation-report: Graphical Installer doesn't work properly

If someone has a virtual machine system handy, trying to locate when the problem appeared would be nice, e.g. using the dailies. Images downloaded through http://cdimage.debian.org/cdimage/daily-builds/daily/ Tested with VirtualBox 4.1 on a Debian sid install on amd64. I've used the testing

tasksel 'standard' install gnome

Hello, I'm creating a preseed.cfg to automate installing Debian (in a VirtualBox image). In appendix B of the installation guide I've read We recommend always including the standard task. and I agree. So I've added the following line to my preseed.cfg: d-itasksel/first multiselect

Grub2 fails to boot from menu entry

Hello, I have grub2 as my bootloader with 2 entries for debian (normal + rescue), some entries for memtest and an entry for windows. If I boot and select one of the debian entries, it fails saying File not found (the kernel) and initrd also fails since it needs a kernel. When I go to the grub

Re: Grub2 fails to boot from menu entry

It looks like I was hit with bug #601073, removing /boot from the linux and initrd lines fixed it :) Regards, Diederik On Sunday 24 October 2010 08:41:02 Diederik de Haas wrote: Hello, I have grub2 as my bootloader with 2 entries for debian (normal + rescue), some entries for memtest

Bug#547949: functions: line 1065: sudo: command not found

Package: debootstrap Version: 1.0.16 Severity: grave Justification: renders package unusable debootstrap is called as part of lh_build (from live-helper), but when Unpacking the base system is started, it stops. Last lines: I: Configuring sysvinit... I: Unpacking the base system... P: Begin