Bug#655198: live-installer does not remove live packages in the installed system
Hello,
I ran into this issue last year making a derivative (BunsenLabs) live
iso with live-build, and patched live-installer (53) to honour
/cdrom/live/filesystem.packages-remove and enable the functionality
described in Live-Manual 8.2.7 [1]
Just for reference, here's what we did:
1) I added finish-install.d/14copy-pkg-lists, which runs just before
15cdrom-detect, and copies
/cdrom/live/filesystem.packages-{remove,install} to
/var/cache/live-installer/ (arbitary choice of directory).
2) finish-install.d/60remove-live-packages now looks at
/var/cache/live-installer/filesystem.packages-remove for packages to remove.
3) Awk seems not to be available to the d-i hook scripts. I got "not
found" errors when trying to use the existing code in
60remove-live-packages, and likewise in a TTY shell during installation.
No other d-i hooks invoke awk.
I did note, however, that live-installer's postinst script calls it on
line 153 with no apparent ill-effects. (Maybe when install_live_system
() is called the cdrom has already been unmounted, so the absence
of/cdrom/live/filesystem.packages-install masks the unsupported awk?)
Anyway, to separate the first word on a line is a trivial task that can
be done by 'read', which I substituted thus (now adding the forgotten
read -r option):
# Remove packages as specified in specific package removal list
for list in /var/cache/live-installer/filesystem.packages-remove; do
if [ -e $list ]; then
while read -r package otherstuff; do
if [ -f /target/var/lib/dpkg/info/${package}.list ];
then
packages="$packages $package"
do_initrd=true
fi
done < "$list"
fi
done
4) Instead of purging packages individually I collected them all into a
list for a single run of
in-target apt-get --yes purge
NOTE) Users of live-build might want to add a binary hook script to make
sure that any live-only packages that have been provided as local .deb
files get added to filesystem.packages-remove. Otherwise they are left
off because local debs are installed in the first run of
chroot_install-packages.
FWIW I'm attaching the patch on live-installer 53.
[1]
https://live-team.pages.debian.net/live-manual/html/live-manual/customizing-package-installation.en.html#429
--
John
Description: Remove packages in /cdrom/live/filesystem.packages-remove.
Packages listed in /cdrom/live/filesystem.packages-remove
will be uninstalled at the finish-install phase of debian-installer.
Intended to enable correct functionality of Live-Manual 8.2.7,
raised and partly patched in Debian bug #655198.
Author: John Crawley
Last-Update: 2018-03-25
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- /dev/null
+++ b/README
@@ -0,0 +1,12 @@
+Warning: This udeb package is for building debian-installer images only.
+Do not install it on a normal Debian system.
+
+This is a patched version of live-installer-54
+to make live-build's package.list.chroot_{install,live} syntax work.
+
+Packages listed in /cdrom/live/filesystem.packages-remove
+will be uninstalled at the finish-install phase of debian-installer.
+
+A binary hook needs to be added to live-build's config/hooks/normal
+to ensure that local debs are also added to filesystem.packages-remove
+if they are in *.list.chroot_live
--- /dev/null
+++ b/finish-install.d/14copy-pkg-lists
@@ -0,0 +1,15 @@
+#!/bin/sh -e
+
+# Copy package install/remove lists from cdrom before it's unmounted.
+
+lists='/cdrom/live/filesystem.packages-remove
/cdrom/live/filesystem.packages-install'
+cachedir='/var/cache/live-installer'
+
+for list in $lists
+do
+ if [ -e "$list" ]
+ then
+ mkdir -p "$cachedir"
+ cp "$list" "$cachedir"
+ fi
+done
--- a/finish-install.d/60remove-live-packages
+++ b/finish-install.d/60remove-live-packages
@@ -1,20 +1,18 @@
#!/bin/sh -e
do_manual_removal=true
+packages=
# Remove packages as specified in specific package removal list
-for list in /cdrom/live/filesystem.packages-remove; do
+for list in /var/cache/live-installer/filesystem.packages-remove; do
if [ -e $list ]; then
- do_manual_removal=
+ while read package otherstuff; do
+ if [ -f /target/var/lib/dpkg/info/${package}.list ];
then
+ packages="$packages $package"
do_initrd=true
- for package in $(awk '{ print $1 }' $list); do
- if [ -f /target/var/lib/dpkg/info/$package.list ]; then
- packages="$packages $package"
fi
- done
-
- in-target apt-get --yes purge $packages
+ done < "$list"
fi
done
@@ -25,12 +23,16 @@ done
if [ $do_manual_removal ]; then
for package in live-boot live
Bug#920498: os-prober generates jessy entry with bad UUID
Package: os-prober
Version: 1.76~deb9u1
Severity: important
Dear Maintainer,
os-prober generates an incorrect entry for old debian (jessie) partition.
UUID 28cc... is OK
UUID d4c0... is bad - with blkid there is no such UUID on my system
menuentry 'Debian GNU/Linux 8 (jessie) (auf /dev/sdb4)' --class debian --class
gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-
simple-28cc3074-3d74-4a0f-87b6-e0898d2a1e15' {
insmod part_gpt
insmod ext2
set root='hd1,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-
efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4 --hint='hd1,gpt4'
28cc3074-3d74-4a0f-87b6-e0898d2a1e15
else
search --no-floppy --fs-uuid --set=root
28cc3074-3d74-4a0f-87b6-e0898d2a1e15
fi
linux /boot/vmlinuz-3.16.0-4-amd64
root=UUID=d4c01c5a-d679-4725-bde1-bd56bc592d0e ro quiet
initrd /boot/initrd.img-3.16.0-4-amd64
}
I run update-grub some times with always the same result.
If I change the UUID in the linux line to 28cc.. then I can boot.
Thank You
Joachim
-- System Information:
Debian Release: 9.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/3 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages os-prober depends on:
ii grub-common 2.02~beta3-5+deb9u1
ii libc62.24-11+deb9u3
os-prober recommends no packages.
os-prober suggests no packages.
-- no debconf information
Bug#919982: apt-setup: preseeded installation hangs at "Use a network mirror?"
Hi Steve, On Fri, Jan 25, 2019 at 11:58:08PM +, Steve McIntyre wrote: > So I've been looking through this code again, and the corresponding > code in apt-setup that uses these values. Last time I played with > apt-setup, I added a table to describe what d-i will do based on the > information in cd_type, to explain exactly what d-i expects: > > # Various different image types look different here: > # > # Image Type cd_type > ### > # netinst "not_complete" > # full CD sets (default desktop) "full_cd" > # desktop-specific CD images "full_cd/single" > # DVD "dvd" > # bluray "bluray" > # multi-arch CD/DVD"not_complete" > # live "live" Thanks for checking the code and providing this table. The Debian Edu BD image (bluray) is generated using COMPLETE=0, see: https://salsa.debian.org/images-team/setup/blob/master/buster/cronjob.weekly#L268 because otherwise it turned out to be too big (~21 GiB). This image is intended for offline installations, no mirror useable. With this setting the Edu image differs from the stock BD/DLBD ones where COMPLETE=0 is missing and the default (COMPLETE=1) takes effect, see: https://salsa.debian.org/images-team/setup/blob/master/buster/cronjob.weekly#L169 > The changes you've imported from the debian-edu fork of debian-cd > clearly don't match up with these, and that's a problem. Agreed; sorry for that. > We'll come back to this again shortly. To help with that, could you > describe exactly what debian-edu is expecting here please, i.e. what > the settings in cd_type mean for the debian-edu installer? I tried to understand the code that is used to write the content, see: https://salsa.debian.org/images-team/debian-cd/blob/master/tools/start_new_disc#L179 If I understood correctly, for all cases with COMPLETE=0 the content of cd_type is 'not_complete'. If the EDU BD image has 'blueray/not_complete' then this content matches the blueray*) case in apt-setup, see: https://sources.debian.org/src/apt-setup/1:0.145/generators/50mirror/#L104 and the image is usable for offline installation. This is the only change that is actually needed for the Edu BD image. Commit https://salsa.debian.org/images-team/debian-cd/commit/15b482d49e642e21e983dba27a47b4fc2d8b90b4 incorrectly altered the setting 'not_complete' to 'cd/not_complete' for netinst, causing this bug. Sorry for not noticing it. > I'm worried that we may not have a clear solution here that can match > the current expectations of both d-i and and the debian-edu setup. Hopefully I managed to clarify the Edu setup intention. Wolfgang signature.asc Description: PGP signature
apt-setup: Please refer to deb.debian.org over ftp.debian.org in commented-out examples
> Chris Lamb wrote: > > > apt-setup: Please refer to httpredir.debian.org over > > ftp.debian.org in commented-out examples > > I find httpredir too unreliable these days, so an updated patch > is attached that uses http://deb.debian.org instead. This has been fixed in https://tracker.debian.org/news/844054/accepted-apt-setup-10127-source-all-i386-into-unstable/ So closing this (forgotten) bug. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#798996: marked as done (Please refer to deb.debian.org over ftp.debian.org in commented-out examples)
Your message dated Sat, 26 Jan 2019 17:42:17 +0100
with message-id <20190126174217.f5e0a017bf392bb093213...@mailbox.org>
and subject line apt-setup: Please refer to deb.debian.org over ftp.debian.org
in commented-out examples
has caused the Debian Bug report #798996,
regarding Please refer to deb.debian.org over ftp.debian.org in commented-out
examples
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 ow...@bugs.debian.org
immediately.)
--
798996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-setup
Version: 1:0.102
Severity: wishlist
Tags: patch
Hi,
Now that httpredir is under debian.org, it makes sense to refer to
httpredir.debian.org over ftp.debian.org in the (NB.) commented-out
example entries.
Patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/generators/92updates b/generators/92updates
index d68ca89..982be73 100755
--- a/generators/92updates
+++ b/generators/92updates
@@ -47,7 +47,7 @@ else
echo "# are provided as examples, but you should amend them as
appropriate" >> $file
echo "# for your mirror of choice." >> $file
echo "#" >> $file
- echo "# deb http://ftp.debian.org/debian/ ${codename}-updates $dists"
>> $file
+ echo "# deb http://httpredir.debian.org/debian/ ${codename}-updates
$dists" >> $file
fi
if db_get netcfg/dhcp_options && \
[ "$RET" = "Do not configure the network at this time" ]; then
@@ -72,7 +72,7 @@ fi
if [ -n "$protocol" ] && [ -n "$host" ]; then
echo "deb-src $protocol://${host}${directory} ${codename}-updates
$dists" >> $file
else
- echo "# deb-src http://ftp.debian.org/debian/ ${codename}-updates
$dists" >> $file
+ echo "# deb-src http://httpredir.debian.org/debian/ ${codename}-updates
$dists" >> $file
fi
exit $CODE
diff --git a/generators/93backports b/generators/93backports
index 1021d5f..11b12ff 100755
--- a/generators/93backports
+++ b/generators/93backports
@@ -47,7 +47,7 @@ else
echo "# are provided as examples, but you should amend them as
appropriate" >> $file
echo "# for your mirror of choice." >> $file
echo "#" >> $file
- echo "# deb http://ftp.debian.org/debian/ ${codename}-backports $dists"
>> $file
+ echo "# deb http://httpredir.debian.org/debian/ ${codename}-backports
$dists" >> $file
fi
if db_get netcfg/dhcp_options && \
[ "$RET" = "Do not configure the network at this time" ]; then
@@ -72,7 +72,7 @@ fi
if [ -n "$protocol" ] && [ -n "$host" ]; then
echo "deb-src $protocol://${host}${directory} ${codename}-backports
$dists" >> $file
else
- echo "# deb-src http://ftp.debian.org/debian/ ${codename}-backports
$dists" >> $file
+ echo "# deb-src http://httpredir.debian.org/debian/
${codename}-backports $dists" >> $file
fi
exit $CODE
--- End Message ---
--- Begin Message ---
> Chris Lamb wrote:
>
> > apt-setup: Please refer to httpredir.debian.org over
> > ftp.debian.org in commented-out examples
>
> I find httpredir too unreliable these days, so an updated patch
> is attached that uses http://deb.debian.org instead.
This has been fixed in
https://tracker.debian.org/news/844054/accepted-apt-setup-10127-source-all-i386-into-unstable/
So closing this (forgotten) bug.
Holger
--
Holger Wansing
PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076--- End Message ---
Bug#920498: os-prober generates jessy entry with bad UUID
On Sat, 2019-01-26 at 11:21 +0100, Joachim Schmidt wrote:
> Package: os-prober
> Version: 1.76~deb9u1
> Severity: important
>
> Dear Maintainer,
>
> os-prober generates an incorrect entry for old debian (jessie) partition.
> UUID 28cc... is OK
> UUID d4c0... is bad - with blkid there is no such UUID on my system
>
> menuentry 'Debian GNU/Linux 8 (jessie) (auf /dev/sdb4)' --class debian --class
> gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-
> simple-28cc3074-3d74-4a0f-87b6-e0898d2a1e15' {
> insmod part_gpt
> insmod ext2
> set root='hd1,gpt4'
> if [ x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-
> efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4 --hint='hd1,gpt4'
> 28cc3074-3d74-4a0f-87b6-e0898d2a1e15
> else
> search --no-floppy --fs-uuid --set=root
> 28cc3074-3d74-4a0f-87b6-e0898d2a1e15
> fi
> linux /boot/vmlinuz-3.16.0-4-amd64
> root=UUID=d4c01c5a-d679-4725-bde1-bd56bc592d0e ro quiet
> initrd /boot/initrd.img-3.16.0-4-amd64
> }
>
> I run update-grub some times with always the same result.
> If I change the UUID in the linux line to 28cc.. then I can boot.
[...]
In the jessie installation, what does /etc/fstab say is the root
device?
Ben.
--
Ben Hutchings
I'm not a reverse psychological virus.
Please don't copy me into your signature.
signature.asc
Description: This is a digitally signed message part
Re: debian-installer: punjabi installation broken
Holger Levsen wrote: > > http://jenkins.debian.net/job/g-i-installation_debian_sid_daily_rescue_punjabi/8/ > > shows that there is a problem with the rescue mode in Punjabi and thus very > probably also with normal installations. Since the last build was successful, I'm closing this (5 years old) bug. (The build artefacts from those days are no longer available, so there is no way to debug that build problems anyway.) If new build problems on jenkins occur, feel free to file a new bug. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#727043: marked as done (punjabi installation broken)
Your message dated Sat, 26 Jan 2019 18:03:13 +0100 with message-id <20190126180313.f6719c01a11163a754f54...@mailbox.org> and subject line Re: debian-installer: punjabi installation broken has caused the Debian Bug report #727043, regarding punjabi installation broken 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 ow...@bugs.debian.org immediately.) -- 727043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: debian-installer version: 20131014 severity: important Hi, http://jenkins.debian.net/job/g-i-installation_debian_sid_daily_rescue_punjabi/8/ shows that there is a problem with the rescue mode in Punjabi and thus very probably also with normal installations. h01ger: not sure about that particular language, but I know there were regression for asian languages. not sure if that's a different or similar bug. feel free to file a bug against src:debian-installer for now (along with the version I uploaded if you can reproduce it with it) Build 8 was triggered manually after #7 showed these symtons, and I've now triggered #9 as well. cheers, Holger signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Holger Levsen wrote: > > http://jenkins.debian.net/job/g-i-installation_debian_sid_daily_rescue_punjabi/8/ > > shows that there is a problem with the rescue mode in Punjabi and thus very > probably also with normal installations. Since the last build was successful, I'm closing this (5 years old) bug. (The build artefacts from those days are no longer available, so there is no way to debug that build problems anyway.) If new build problems on jenkins occur, feel free to file a new bug. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076--- End Message ---
Bug#744863: marked as done (punjabi installation broken (or at least rescue mode))
Your message dated Sat, 26 Jan 2019 18:03:13 +0100 with message-id <20190126180313.f6719c01a11163a754f54...@mailbox.org> and subject line Re: debian-installer: punjabi installation broken has caused the Debian Bug report #727043, regarding punjabi installation broken (or at least rescue mode) 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 ow...@bugs.debian.org immediately.) -- 727043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: debian-installer [16:47] < h01ger> | there seems to be a problem with punjabi which other languages dont show: https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_rescue_punjabi/ [17:37] < KiBi> it seems to loop on the keyboard options screen here [17:37] < KiBi> maybe setxkbmap/console-setup failing, and making it loop [17:37] < KiBi> (no traces in syslog afaict) cheers, Holger signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Holger Levsen wrote: > > http://jenkins.debian.net/job/g-i-installation_debian_sid_daily_rescue_punjabi/8/ > > shows that there is a problem with the rescue mode in Punjabi and thus very > probably also with normal installations. Since the last build was successful, I'm closing this (5 years old) bug. (The build artefacts from those days are no longer available, so there is no way to debug that build problems anyway.) If new build problems on jenkins occur, feel free to file a new bug. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076--- End Message ---
Bug#920498: [Fwd: Re: Bug#920498: os-prober generates jessy entry with bad UUID]
Forwarded Message From: Joachim Schmidt To: Ben Hutchings Subject: Re: Bug#920498: os-prober generates jessy entry with bad UUID Date: Sat, 26 Jan 2019 18:42:29 +0100 Message-Id: <2f9387ca-3fa6-63ae-9353-2d18be286...@arcor.de> Hi Ben, > In the jessie installation, what does /etc/fstab say is the root > device? here it is: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # proc/proc procdefaults0 0 # / was on /dev/sda5 during installation #UUID=d4c01c5a-d679-4725-bde1-bd56bc592d0e / ext4 errors=remount-ro 0 1 UUID=28cc3074-3d74-4a0f-87b6-e0898d2a1e15 /ext4errors=remount-ro 0 1 #/dev/sdb6 / ext3errors=remount-ro 0 1 # /home was on /dev/sda7 during installation UUID=105c5810-518e-4a69-a6f4-bba8a978a327/home ext4defaults 0 2 # swap was on /dev/sda6 during installation #UUID=519b5df4-8fa9-46e9-8fab-2470193bbbd1 none swapsw00 LABEL=swap noneswapsw 0 0 # #UUID=F2B48F68B48F2E63 /media/System ntfs-3g defaults,locale=de_DE.UTF-8,umask=000 0 0 LABEL=System/media/System ntfs-3g defaults,locale=de_DE.UTF-8,umask=000 0 0 #UUID=58E098AFE09894BA /media/Datenntfs-3g defaults,locale=de_DE.UTF-8 0 0 LABEL=Daten /media/Daten ntfs-3g defaults,locale=de_DE.UTF-8 0 0 LABEL=arch_home /media/arch_homeext4defaults0 2 #UUID=75d3cc98-3d8b-4030-86df-d5552f055fa7 /media/w-test ext4 defaults0 2 #/dev/sdc0 /media/cdrom0 udf,iso9660 user,noauto 0 0 I saved the jessie partition to update to stretch and after that I changed the UUID of jessie partition to a new one. os-prober still uses this old no more existing UUID. Joachim -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your signature.
Processed: severity of 879130 is normal
Processing commands for cont...@bugs.debian.org: > severity 879130 normal Bug #879130 [choose-mirror] empty mirror list on non released architectures Severity set to 'normal' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 879130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 879130 918428
Processing commands for cont...@bugs.debian.org: > merge 879130 918428 Bug #879130 [choose-mirror] empty mirror list on non released architectures Unable to merge bugs because: package of #918428 is 'src:choose-mirror' not 'choose-mirror' Failed to merge 879130: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 879130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879130 918428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 879130 918428
Processing commands for cont...@bugs.debian.org: > merge 879130 918428 Bug #879130 [choose-mirror] empty mirror list on non released architectures Unable to merge bugs because: package of #918428 is 'src:choose-mirror' not 'choose-mirror' Failed to merge 879130: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 879130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879130 918428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 879130 to src:choose-mirror
Processing commands for cont...@bugs.debian.org: > reassign 879130 src:choose-mirror Bug #879130 [choose-mirror] empty mirror list on non released architectures Bug reassigned from package 'choose-mirror' to 'src:choose-mirror'. No longer marked as found in versions choose-mirror/2.82. Ignoring request to alter fixed versions of bug #879130 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 879130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840400: Issue seems in nls_ascii module not available
I was hitting this exact error message during installation. I switched to another VT and did: mkfs.fat /dev/sda1 Then I switched back to the installer VT, and had it try again from "finalize the partition layout". Now it's proceeding with no error. I took the idea from this Ubuntu discussion: https://askubuntu.com/questions/502307/ It looks to me like the installer doesn't ensure the EFI partition contains a filesystem before trying to mount it. -- Aaron Bugher
LUKS bugreports to be closed (house-cleaning)
Hi, since LUKS is no longer supported by d-i, all LUKS related bugreports against d-i packages can be closed, right? That would be https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723729 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801769 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781290 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849400 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873923 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621791 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484263 I will closed them shortly, if noone objects. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Some fonts are missing in the default install (verdana, ...)
Control: reassign -1 gnome Florent Le Saout wrote: >* What led up to the situation? I installed basic Debian testing from > netinstall > Then I installed gnome3, icedove and iceweasel and others. On some pages > or email > some text are replaced by square, for instance on gitlab. (I have screen > capture if needed) >* What exactly did you do (or not do) that was effective (or > ineffective)? I installed fonts-arkpandora which contains font > replacement for verdana, arial, etc.. >* What was the outcome of this action? It fixes the issue >* What outcome did you expect instead? >* Fix proposal : I propose that this package package or similar becomes a > dependency of any window manager Re-assigning to gnome, since those people might know which fonts are installed or needed for Gnome, and which not. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: Some fonts are missing in the default install (verdana, ...)
Processing control commands: > reassign -1 gnome Bug #810068 [installation-reports] 11: Some fonts are missing in the default install (verdana, ...) Bug reassigned from package 'installation-reports' to 'gnome'. Ignoring request to alter found versions of bug #810068 to the same values previously set Ignoring request to alter fixed versions of bug #810068 to the same values previously set -- 810068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#870448: hw-detect - stop using modprobe -l
Control: tags -1 + pending
Holger Wansing wrote:
> Hi,
>
> Vincent McIntyre wrote:
> > On Wed, Aug 02, 2017 at 07:58:05PM +0100, Ben Hutchings wrote:
> > > On Wed, 2017-08-02 at 12:26 +1000, Vincent McIntyre wrote:
> > > > Package: hw-detect
> > > > Version: 1.124
> > > > Severity: normal
> > > > Tags: patch
> > > >
> > > > I keep seeing this in installer logs, back to jessie.
> > > >
> > > > Aug 2 01:52:11 main-menu[193]: (process:224): modprobe: invalid option
> > > > -- 'l'
> > > >
> > > >
> > > > I rated this normal rather than minor because the way it is working
> > > > now the is_available() function always returns 1 (failure)
> > > >
> > > > My suggestion is to use modinfo instead.
> > > > This will return multiline output inside the quotes but
> > > > a couple of tests suggests that is ok.
> > > > It does fail with some modules (nvidia), not sure if we care.
> > > >
> > > > diff --git a/hw-detect.sh b/hw-detect.sh
> > > > index 7977814..d8196c1 100755
> > > > --- a/hw-detect.sh
> > > > +++ b/hw-detect.sh
> > > > @@ -43,7 +43,7 @@ is_not_loaded() {
> > > > }
> > > >
> > > > is_available () {
> > > > - [ "$(modprobe -l $1)" ] || return 1
> > > > + [ "$(modinfo $1)" ] || return 1
> > > > }
> > >
> > > But this still prints error messages for missing modules. I think the
> > > function should be implemented as:
> > >
> > > is_available () {
> > > modprobe -qn "$1"
> > > }
> > >
> >
> > That seems much better, can someone please apply Ben's version?
> > Thanks for tickling this Holger.
>
> Any objections against this?
I've just committed this.
Tagging this bug as pending.
Holger
--
Holger Wansing
PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: Re: Bug#870448: hw-detect - stop using modprobe -l
Processing control commands: > tags -1 + pending Bug #870448 [hw-detect] hw-detect - stop using modprobe -l Added tag(s) pending. -- 870448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[jessie RC1] wireless LAN card not usable, problem with loading/using firmware
Holger Wansing wrote: > I have a laptop here which needs firmware for the wireless LAN card > Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter (PCI-ID: 8086:1043). > > It seems the process of requesting, loading and using firmware is not fully > functional: > When it comes to the d-i step "Detecting network hardware", there is lot of > output on the 4th console regarding > "BUG: unable to handle kernel paging request at ce8ec00c" > and > "Oops: 0002 [#1] > and > "Call Trace:" > " ? ipw2100_down+0x9e/ox10 [ipw2100] > and the like. > > I have attached a syslog of this installation try. > > But I am able to proceed with the installation steps, d-i requests firmware > file, so I plug in my usbstick, the relevant firmware package is installed > (the firmware files end up in /lib/firmware), but the device is not able > to operate. It is not shown in the list of available network devices in the > d-i UI. > > > To investigate this, I started the installation again, but before the step > "Detect network hardware" is started, I mount my usbstick, copy the needed > firmware file into /lib/firmware by hand and then start the step > "Detect network hardware". And now the device is working, it is shown as > available nework device, it scans and shows available WLANs, so the hardware > seems to work. > So it calms down to the firmware not being available, when the module is > loaded. I no longer have access to this notebook, so I am unable to test if installation still fails on this device. So closing this (jessie) bug. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: merging 879130 918428
Processing commands for cont...@bugs.debian.org: > merge 879130 918428 Bug #879130 [src:choose-mirror] empty mirror list on non released architectures Bug #918428 [src:choose-mirror] choose-mirror: mirror list generation broken for all ports architectures Added tag(s) patch. Bug #879130 [src:choose-mirror] empty mirror list on non released architectures Marked as found in versions choose-mirror/2.96. Merged 879130 918428 > thanks Stopping processing here. Please contact me if you need assistance. -- 879130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879130 918428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[kfreebsd] Graphical DE task don't install any DE
Baptiste Jammet > Testing debian-jessie-DI-b2-kfreebsd-amd64-netinst.iso under qemu-kvm, > if I only choose "Graphical desktop environment", d-i doesn't install any > DE, just something like desktop-base. It seems that I have to choose > explicitly. Since there are no kfreebsd installation images currently, there is no way to test the actual status, so closing this (pre-jessie) bug for now. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#764277: marked as done (Graphical DE task don't install any DE)
Your message dated Sun, 27 Jan 2019 00:35:38 +0100 with message-id <20190127003538.c22921770d206109eb54d...@mailbox.org> and subject line [kfreebsd] Graphical DE task don't install any DE has caused the Debian Bug report #764277, regarding Graphical DE task don't install any DE 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 ow...@bugs.debian.org immediately.) -- 764277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Version: 2.57 Severity: important Dear Maintainer, Testing debian-jessie-DI-b2-kfreebsd-amd64-netinst.iso under qemu-kvm, if I only choose "Graphical desktop environment", d-i doesn't install any DE, just something like desktop-base. It seems that I have to choose explicitly. (Tested 2 times) Attached is the output of dpkg --get-selections just after the first reboot, and /var/log/installer/syslog. -- Package-specific info: Boot method: CD Image version: debian-jessie-DI-b2-kfreebsd-amd64-netinst.iso Date: 06 oct 2014 Machine: qemu-kvm on a DELL 780 host Partitions: All in one partition Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] No more 757986 nor 957987 Install base system:[O] Install tasks: [E] Install boot loader:[O] Overall install:[O] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/kFreeBSD installer" DISTRIB_RELEASE="8 (jessie) - installer build 20141002" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: GNU/kFreeBSD debian 10.0-1-amd64 #0 Tue, 20 May 2014 12:47:21 +0100 x86_64 GNU/Linux lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -nn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -nn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] lspci -nn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) lspci -nn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] lspci -nn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 20) usb-list: Error: directory /sys/bus does not exist; is sysfs mounted? kldstat: Id Refs AddressSize Name kldstat: 1 16 0x8020 1142000 kfreebsd-10.gz kldstat: 21 0x86012000 dc18 ext2fs.ko kldstat: 31 0x8602 140df9 zfs.ko kldstat: 41 0x86161000 2d61 opensolaris.ko kldstat: 51 0x86164000 2374 nullfs.ko kldstat: 61 0x86167000 88e3 fuse.ko df: Filesystem 1K-blocks Used Available Use% Mounted on df: /dev/md0 72959 23515 49444 32% / df: devfs1 1 0 100% /dev df: devfs1 1 0 100% /dev df: fdescfs 1 1 0 100% /dev/fd df: linprocfs4 4 0 100% /proc df: /sys 4 4 0 100% /sys df: tmpfs 528600 140528460 0% /var/cache/anna df: tmpfs 550504 22044528460 4% /var/lib/cdebconf df: /dev/ada0s14813468 1424936 3003456 32% /target df: devfs1 1 0 100% /target/dev free: /usr/bin/report-hw: line 63: free: not found /proc/cmdline: BOOT_IMAGE=/kernel ro root=302 /proc/cpuinfo: processor: 0 /proc/cpuinfo: vendor_id: GenuineIntel /proc/cpuinfo: cpu family : 6 /proc/cpuinfo: model: 2 /proc/cpuinfo: model name : QEMU Virtual CPU version 1.1.2 /proc/cpuinfo: stepping : 3 /proc/cpuinfo: /proc/cpuinfo: processor: 1 /proc/cpuinfo: vendor_id: GenuineIntel /proc/cpuinfo: cpu family : 6 /proc/cpuinfo: model: 2 /proc/cpuinfo: model name : QEMU Virtual CPU version 1.1.2 /proc/cpuinfo: stepping : 3 /proc/cpuinfo: /proc/cpuinfo: fla
Re: Daily build d-i + lenny + GRUB2: "Unable to install GRUB in /dev/sda"
"Daniel Richard G." wrote: > I am attempting to install lenny with GRUB2 using a daily build of d-i. > After being prompted whether or not to install to the MBR, I get a red- > screen error as follows: > > [!!] Configuring grub-pc > > Unable to install GRUB in /dev/sda > Executing 'grub-install /dev/sda' failed. Installing grub to a single /dev/sda used to be no problem these days, so this is most probably an old report from times where grub2 had several problems. Closing this bug (from 2010). -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#592770: marked as done (Daily build d-i + lenny + GRUB2: "Unable to install GRUB in /dev/sda")
Your message dated Sun, 27 Jan 2019 00:52:13 +0100 with message-id <20190127005213.1434b8cbb147d6325d4a1...@mailbox.org> and subject line Re: Daily build d-i + lenny + GRUB2: "Unable to install GRUB in /dev/sda" has caused the Debian Bug report #592770, regarding Daily build d-i + lenny + GRUB2: "Unable to install GRUB in /dev/sda" 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 ow...@bugs.debian.org immediately.) -- 592770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: 20100805-15:58 Severity: important I am attempting to install lenny with GRUB2 using a daily build of d-i. After being prompted whether or not to install to the MBR, I get a red- screen error as follows: [!!] Configuring grub-pc Unable to install GRUB in /dev/sda Executing 'grub-install /dev/sda' failed. This is a fatal error. Looking at the log on tty4, I see what appears to be the output of "grub- install --help", and then error: Running 'grub-install --no-floppy --force "/dev/sda"' failed. The only instance of "grub-install" that I can find is under /target, and if I invoke that as shown in the log, I get Unrecognized option `--force' If I drop the --force option, I get /target/usr/sbin/grub-install: .: line 121: can't open '/usr/lib/grub/update-grub_lib' --- End Message --- --- Begin Message --- "Daniel Richard G." wrote: > I am attempting to install lenny with GRUB2 using a daily build of d-i. > After being prompted whether or not to install to the MBR, I get a red- > screen error as follows: > > [!!] Configuring grub-pc > > Unable to install GRUB in /dev/sda > Executing 'grub-install /dev/sda' failed. Installing grub to a single /dev/sda used to be no problem these days, so this is most probably an old report from times where grub2 had several problems. Closing this bug (from 2010). -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076--- End Message ---
Re: LUKS bugreports to be closed (house-cleaning)
On Sat, 2019-01-26 at 22:35 +0100, Holger Wansing wrote: > Hi, > > since LUKS is no longer supported by d-i, all LUKS related bugreports against > d-i packages can be closed, right? I don't know what makes you think that. LUKS is precisely what is used for disk encryption. Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your signature. signature.asc Description: This is a digitally signed message part
