Bug#924760: logfiles...
Control: reassign -1 src:grub2 2.02+dfsg1-13 On Sun, Mar 17, 2019 at 11:31:46PM +0100, Samuel Thibault wrote: > Ok. It looks like os-prober finds the sda1 EFI partition fine, and > apparently "dummy" is correct for EFI platforms. Yes. (Actually it's just ignored, but having it there makes grub-installer's code a little simpler.) > But then > > grub-installer: info: Running chroot /target grub-install --force "dummy" > grub-installer: Installing for x86_64-efi platform. > grub-installer: grub-install: error: unknown filesystem. > > so I guess somehow the grub2 package doesn't manage to find its way with > an xfs filesystem for '/', thus Cc-ing grub2 maintainers, just > reassigning to grub-installer for now. Looks very much like the bug fixed upstream here: https://git.savannah.gnu.org/cgit/grub.git/commit/?id=cda0a857dd7a27cd5d621747464bfe71e8727fff I'll cherry-pick that patch. Thanks, -- Colin Watson [cjwat...@debian.org]
Processed: Re: Bug#924760: logfiles...
Processing control commands: > reassign -1 src:grub2 2.02+dfsg1-13 Bug #924760 [grub-installer] Grub is extremely picky in regards to partition Bug reassigned from package 'grub-installer' to 'src:grub2'. Ignoring request to alter found versions of bug #924760 to the same values previously set Ignoring request to alter fixed versions of bug #924760 to the same values previously set Bug #924760 [src:grub2] Grub is extremely picky in regards to partition Marked as found in versions grub2/2.02+dfsg1-13. -- 924760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Feature request: Support for QEMU Virtio driver for CD-ROM
Package: debian-installer Version: debian-testing-amd64-DVD-1.iso, from 2019-03-16 When installing Debian as a guest in KVM/QEMU assigning the ISO to a CD-ROM using Virtio or Virtio-SCSI as the bus type the debian-installer cannot see the CD-ROM drive and ask for drivers. I assume the Virtio drivers are not bundled/loaded in the installer. It would be nice if it was :-) In my benchmark of different bus types for CD-RO I got this read numbers: -ata/ide: 541MB/s -sata: 1,2GBs -Virtio-SCSI: 3,6GB Unfortunately I didn't test Virtio, but it should be at least just as fast as the Virtio-SCSI I've read from RHEL that Virtio is a little faster (at least for HDDs).
Bug#925105: CD-ROM is default repository, not mirror
Package: debian-installer Version: debian-testing-amd64-DVD-1.iso, from 2019-03-16 After a clean installation this in the content of the sources.list: # deb cdrom:[Debian GNU/Linux testing _Buster_ - Official Snapshot amd64 DVD Binary-1 20190311-05:00]/ buster contrib main deb cdrom:[Debian GNU/Linux testing _Buster_ - Official Snapshot amd64 DVD Binary-1 20190311-05:00]/ buster contrib main deb http://deb.debian.org/debian/ buster main deb-src http://deb.debian.org/debian/ buster main deb http://security.debian.org/debian-security buster/updates main contrib deb-src http://security.debian.org/debian-security buster/updates main contrib I guess you can always argue if this is a bug. But I will claim that by far the waste majority of Debian users want to have the selected mirror in the installation to be the primary repository, not the, in many ways, useless CD-ROM. Wouldn't it be more fair that the very few that actually want the CD-ROM to be the primary repositor, are the one who has to modify the sources.list? And not the waste majority of the users. And if they don't, they can just skip selecting a mirror in the installation, and then the CD-ROM should be the repository. install log attached. Debian_install_logs.7z Description: Binary data
Bug#925048: debootstrap: --keyring= Release signed by unknown key (key id EF0F382A1A7B6500)
Package: debootstrap
Version: 1.0.89
Severity: important
Dear Maintainer,
* What led up to the situation?
dpkg-deb -R debian-archive-keyring_2017.5_all.deb /tmp/
ls *.gpg|xargs -I{} debootstrap --download-only --force-check-gpg --keyring={}
--variant minbase --arch amd64 --make-tarball=debian_amd64 stable
/root/dbs_debian_amd64 https://debian.ethz.ch/debian
* What exactly did you do (or not do) that was effective (or
ineffective)?
E: Release signed by unknown key (key id EF0F382A1A7B6500)
but
debootstrap --download-only --force-check-gpg --variant minbase --arch amd64
--make-tarball=debian_amd64 stable /root/dbs_debian_amd64
https://debian.ethz.ch/debian
works
There's a problem with using --keyring=whatever.gpg
-- System Information:
Debian Release: 9.8
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debootstrap depends on:
ii wget 1.18-5+deb9u2
Versions of packages debootstrap recommends:
ii debian-archive-keyring 2017.5
ii gnupg 2.1.18-8~deb9u4
debootstrap suggests no packages.
-- debconf-show failed
Processed: Re: busybox ip --oneline displays nothing
Processing commands for cont...@bugs.debian.org: > severity 924374 serious Bug #924374 [busybox] busybox ip -oneline link show displays nothing Severity set to 'serious' from 'important' > # breaks other packages > End of message, stopping processing here. Please contact me if you need assistance. -- 924374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
