Your message dated Fri, 19 Mar 2021 12:31:49 +0100 with message-id <942ab566-1842-e40c-b313-19926eec719f@rclobus.nl> and subject line Re: Bug#970689: live-build: fails when lilo can't be installed, even if unused has caused the Debian Bug report #970689, regarding live-build: fails when lilo can't be installed, even if unused to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 970689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970689 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: live-build: fails when lilo can't be installed, even if unused
- From: Witold Baryluk <witold.baryluk@gmail.com>
- Date: Mon, 21 Sep 2020 16:28:08 +0000
- Message-id: <160070568823.489146.12063875443777829030.reportbug@localhost>
Package: live-build Version: 1:20191221 Severity: important X-Debbugs-Cc: witold.baryluk@gmail.com Dear Maintainer, I am using lb this way:L sudo --preserve-env=DEBIAN_FRONTEND,APT_LISTCHANGES,NEEDRESTART_MODE,NEEDRESTART_SUSPEND,DEBIAN_FRONT \ lb config \ --apt-recommends true \ --archive-areas "main non-free contrib" \ --binary-images iso-hybrid \ --backports false \ --bootloaders syslinux \ --debconf-priority critical \ --debian-installer live \ --debian-installer-gui true \ --distribution bullseye \ --security false \ --zsync false \ --bootappend-live "intel_iommu=on iommu=pt radeon.si_support=0 amdgpu.si_support=1 amdgpu.ppfeaturemask=0xffffffff boot=live components locales=en_US.UTF-8" Yet, `lb build` fails because it tries to install package lilo, which is at the moment not available in Debian testing (removed due to ftbfs with gcc-10). I don't need lilo in this build, so lb build shouldn't even attempt to install it. I am building iso image image, so I need to use syslinux (which is a default for iso-hybrid anyway). I don't think grub-efi would work on iso? I don't know why lb build is trying to install (and then remove) lilo. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages live-build depends on: ii debootstrap 1.0.123 Versions of packages live-build recommends: ii apt-utils 2.1.7 ii bzip2 1.0.8-3 ii cpio 2.13+dfsg-2 ii file 1:5.38-5 ii live-boot-doc 1:20190614 ii live-config-doc 11.0.1 ii live-manual-html [live-manual] 2:20151217.1 ii wget 1.20.3-1+b3 ii xz-utils 5.2.4-1+b1 Versions of packages live-build suggests: ii e2fsprogs 1.45.6-1 ii mtd-utils 1:2.1.1-1.1 ii parted 3.3-4 -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 970689-done@bugs.debian.org
- Subject: Re: Bug#970689: live-build: fails when lilo can't be installed, even if unused
- From: Roland Clobus <rclobus@rclobus.nl>
- Date: Fri, 19 Mar 2021 12:31:49 +0100
- Message-id: <942ab566-1842-e40c-b313-19926eec719f@rclobus.nl>
- In-reply-to: <YCTvW7tFhq2O/eou@t14-buxy.home.ouaza.com>
- References: <160070568823.489146.12063875443777829030.reportbug@localhost> <MT4I8fc--3-2@tutanota.com> <160070568823.489146.12063875443777829030.reportbug@localhost> <76e59a7d-dd0a-5784-2614-bce17c5a046d@rclobus.nl> <YCTvW7tFhq2O/eou@t14-buxy.home.ouaza.com>
Version: 1:20210216 thanks This bug was fixed in 1:20210216. On 11/02/2021 09:48, Raphael Hertzog wrote: > On Wed, 10 Feb 2021, Roland Clobus wrote: >> If you want to use >> Bullseye, you'll need the daily installer >> (--parent-debian-installer-distribution daily), otherwise you'll get a >> warning that no kernel modules are found (because the installer is based >> on the current Debian Stable). > > That statements seems wrong. bullseye has its own installer images, they > might not be in sync with testing right now (I haven't checked) but > those images certainly do not use stable. Indeed. You're right. Bullseye has its own installer images, but they are not (yet) in sync. I've requested a rebuild [1]. With kind regards, Roland Clobus [1] https://lists.debian.org/debian-boot/2021/03/msg00166.htmlAttachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---