debian-cd_3.1.26_source.changes ACCEPTED into unstable

2019-08-10 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Aug 2019 11:50:47 +0200
Source: debian-cd
Architecture: source
Version: 3.1.26
Distribution: unstable
Urgency: medium
Maintainer: Debian CD Group 
Changed-By: Holger Levsen 
Changes:
 debian-cd (3.1.26) unstable; urgency=medium
 .
   [ Steve McIntyre ]
   * Start bullseye development, copy the buster dirs to bullseye as a
 start.
   * Stop producing MD5SUMS and SHA1SUMS files by default.
   * Add shim-signed and grub-efi-arm64-signed to the arm64 package
 list.
   * Change a load of http URLs to use https instead.
 .
   [ Holger Levsen ]
   * d/control:
 - bump standards version to 4.4.0, no changes needed.
 - bump debhelper-compat to 12.
Checksums-Sha1:
 61e36fa708a226b6fbbb3d2b30466a3d87bd4cce 1741 debian-cd_3.1.26.dsc
 d9c065096ee26f85afb4e0872c3a3413c0a412fe 1164552 debian-cd_3.1.26.tar.xz
 4cfe3f8139cf216af0875be9ef4ffdbbfb05052d 5188 debian-cd_3.1.26_source.buildinfo
Checksums-Sha256:
 de7404fabf912c8d2a74065881c2a3e6fad653702e1ca7f32ba95c53be27b1bd 1741 
debian-cd_3.1.26.dsc
 54563b082544c9a7f919b9f95a63e25da2eebfdbc34d95f57a2093578abe6083 1164552 
debian-cd_3.1.26.tar.xz
 62c1fa54a35cb51bbd0a2f94219b69621bd09c324620837f4f83e970ed5c21ef 5188 
debian-cd_3.1.26_source.buildinfo
Files:
 f6ad66477f8198ac4e984ac8d57a44d9 1741 admin optional debian-cd_3.1.26.dsc
 aacd3c35a46bdcbb283122cdb63b1002 1164552 admin optional debian-cd_3.1.26.tar.xz
 390fc33f4168e61421d597b784bdc01a 5188 admin optional 
debian-cd_3.1.26_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAl1Ok+oACgkQCRq4Vgaa
qhzc9Q//bJMVvKlJCPv2dfkIDNNPqppO8EX2H8OWsJScVO9kRTtDfFQUoC9guIvy
AnSFRS0r/8pZV1UNo5Vz2vDSQH82xFh5QwNhf8yrNN1vtAKzzCQ/rPjtGsGCfDs8
cwEHiwyr45my2E46zQrmHoUbZEdxcZ/QHSFoFeP/xOX1yzJWYNMkuTgUtqolLRc6
GCr3qrSBYGcxhbbFZeA7rNJS/OFjnSYQQAZnIUhOK6+pBtr3xZC52wkJ1ERkp57R
gFI1OLTTnkprVWg3rTmmqfCRrAqYIv3Rzlu9/0llX6KjNvK1dOj3RxoaHEPnYc0a
yg+AmlgOoXuETrLa2Uv+iIXMrRFPX65li1ICNV94rWDX9ifAwABm9mdYNhge+Z+S
I85UDxEsqGeyR6Zar2LLZiN4A9WkWmZLaQIDobYslvPJhD5yk+Xr64YQcvPc+CDc
Oo8TczzVuO9+vZeyqF2J2O2uhnVt/gTaHq7+mfYrhtvRsggt4lGovE2qv8+5iIgH
KAyhyiT1F/06KfYdRwUqzpTCHoOXmT/lDBCFZNtiH+4xTgi6cM6nhr4qKsMR4UH2
SvsqiWKZg+4ARgie3E2M/PlT6sWWHUSdMzEQF7OGtUs6yYmzpQkg0Ruy+6c6dbug
Qu7Ii57p2luC0pz/ryCFFY6GtYln8ZAX00zCBTjrnPHOOLY05b8=
=wr6B
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Processing of debian-cd_3.1.26_source.changes

2019-08-10 Thread Debian FTP Masters
debian-cd_3.1.26_source.changes uploaded successfully to localhost
along with the files:
  debian-cd_3.1.26.dsc
  debian-cd_3.1.26.tar.xz
  debian-cd_3.1.26_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#934218: cdrom: grub-install fails with "failed to get%0A canonical path of /dev/nvme0np1"

2019-08-10 Thread Josep Guerrero
Hi, Steve

Thanks a lot for your answer! I'll try to answer your questions and I'll add 
some new information on the problem.

> When you tried to run grub-install by hand, did you have /dev and
> /sys mounted ok in the chroot?

I'm not sure, I admit I didn't check for that. Just after I received the grub 
error in the installer (the text one, just in case it's important), I switched 
to a second console with Alt-F2, executed: 

tail /var/log/syslog, 

and I saw a line about executing 

chroot /target grub-install --force "dummy"
 
and after that, the error I mentioned in my previous message:

grub-install: error: failed to get canonical path of `/dev/nvme0n1p1`

I did not mount or umount anything by myself, so the chrooted /target was in 
the state the debian installer had left it after failing with the grub 
installation.

> If you could try again and add a "-v"
> to the grub-install command line that will give us more
> information. It *will* be verbose, but only the last few lines are
> likely to matter.

I'll do that (sorry, but I won't have physical access to that system till 
Monday).

> You don't describe the system hardware that you're working with. What
> do you have? This sounds like *potentially* a firmware issue, but it's
> not 100% clear yet.

Sorry, you are completely right. I'm attaching the lshw output for this 
machine

I've been trying more ideas with this system, and I contacted the seller for 
advice (they suggested changing some BIOS setup options, some of them related 
to firmware, most of them related to UEFI settings).

After changing those options (I'm not completely sure if they had any effect, 
but maybe) I reinstalled again with a simpler configuration (just to be 
faster), without RAID or LVM, and just used standard partitions on the NVMe 
disk (all the system partitions were in that disk). This time it failed again 
on the grub installation, but there wasn't an explicit error message on the 
syslog (just that it failed with status 1) and when tried the the grub 
installation manually on a second console using:

chroot /target grub-install "dummy"

the error message was that grub-install was unable to find the

/usr/lib/grub/i386-pc/modinfo.sh

file. At that point, I tried continuing the installation without the boot 
loader (didn't try that before), and the installer asked if I wanted to 
install grub in a (I think, citing from memory) "external removable media". I 
chose "Yes" and when I rebooted, among the options there was a new UEFI one 
but the installer USB UEFI options were missing. Choosing the new option 
brought me to the grub prompt, which was an improvement, but didn't boot the 
system.

After (again citing from memory) issuing some grub commands, I don't remember 
the exact parameters, but they were:

root (hdX,Y)
linux /boot/vmlinux-X root=/dev/nvme0n1p2
initrd /boot/initrd-X
boot

the system booted, as far as I can tell, correctly. I executed 

grub-install /dev/nkvm0n1

on the newly booted system, which ran without errors, removed the installer 
USB and got again a new UEFI option, but still I only got the grub prompt when 
rebooting (I could boot from there with the same set of instructions as 
before). I was planning on trying to find if I could get grub to execute those 
instructions by itself, so the system can boot normally, and write a followup 
to the bug report, but I just saw your message.

Sorry about the length of the message. Hope some of this information is 
useful. 

Regards,

Josep Guerrerokilimanjaro
description: Computer
product: AS -1013S-MTR (To be filled by O.E.M.)
vendor: Supermicro
version: 0123456789
serial: A324200X9405087
width: 64 bits
capabilities: smbios-3.1.1 dmi-3.1.1 smp vsyscall32
configuration: boot=normal family=To be filled by O.E.M. sku=To be filled 
by O.E.M. uuid=----AC1F6B7CCF82
  *-core
   description: Motherboard
   product: H11SSL-i
   vendor: Supermicro
   physical id: 0
   version: 1.01
   serial: ZM18CS600800
   slot: To be filled by O.E.M.
 *-firmware
  description: BIOS
  vendor: American Megatrends Inc.
  physical id: 0
  version: 1.1
  date: 02/15/2019
  size: 64KiB
  capacity: 16MiB
  capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd 
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial 
int17printer acpi usb biosbootspecification uefi
 *-memory
  description: System Memory
  physical id: 21
  slot: System board or motherboard
  size: 32GiB
  capacity: 2TiB
  capabilities: ecc
  configuration: errordetection=multi-bit-ecc
*-bank:0
 description: DIMM DDR4 Synchronous Registered (Buffered) 2667 MHz 
(0.4 ns)
 product: 9ASF1G72PZ-2G6D1
 vendor: Micron Technology
 physical id: 0
 serial: