Bug#925582: Allow telling installer about local deb and Package list locations

[積丹尼 Dan Jacobson]

Package: debian-installer

User has a USB drive, loaded with
$ mount
/dev/sdg2 on /var/cache/apt/archives type ext4
/dev/sdg1 on /var/lib/apt/lists type ext4

He takes this drive, along with another drive,
containing a Debian installation ISO, to a remote mountain (offline)
computer, intending to install Debian on it.

Alas, while running the ISO there is no way to tell it about the other
stick where those the .debs are.
Thus making an offline
https://haydenjames.io/direct-install-debian-sid-rolling-release-using-mini-iso-w-screenshots/
not possible.

See also
https://wiki.debian.org/SourcesList#CD-ROM
https://www.debian.org/releases/stretch/amd64/ch06s03.html.en#di-install-software
"/etc/apt/sources.list. You can examine and edit this file to your liking 
**after** the installation is complete."

Anyway the user would like to offline, have a way to say to the
installer:

This  is the location of a lot of *.debs.
and
This ... is a Packages file I made from them.
and
This ... is a list of packages I want you to install from it.

Sure, "just do that all later after you get Debain installed".

But that is very wasteful.

Bug#925556: UEFI or not, can't mount /dev

[積丹尼 Dan Jacobson]

LS> Clearly the initramfs was able to mount /dev and run fsck, but mounting
LS> it to /root/dev to transfer to the real rootfs failed due to a missing
LS> directory.

So it booted, meaning it is not a
https://www.debian.org/releases/stretch/amd64/ch03s06.html.en#UEFI
problem...

Bug#925580: Never leave the user staring at an empty screen, even for a second

[積丹尼 Dan Jacobson]

Package: debian-installer

Here the user is left staring at an empty screen. (Many look that way
for a while at the beginning. Even with the latest fastest hardware.)

Not for long you might say.

But long enough for the user to scratch his head, and then casually get
out his cellphone and take a picture, then wonder some more.

Please for every screen, add a "Please wait..." first.

Bug#925579: User could have just as easily clicked the UEFI or non-UEFI...

[積丹尼 Dan Jacobson]

Package: debian-installer

In https://wiki.debian.org/UEFI
We read

"debian-installer's support for UEFI is mostly contained in two modules.
 First comes the partman-efi module, and this will be loaded
 automatically if d-i recognises it has been booted in UEFI mode."

The problem here is that on e.g., ASUS, there is a 50% chance that a
user could have picked the plain JetFlash (where the d-i ISO is),
or the same ISO, but with the UEFI: prefix...


(Don't worry about the highlighted line in that photo.)

Re: Fixing stretch debian-installer on armhf

[Vagrant Cascadian]

On 2019-03-09, Adam D. Barratt wrote:
> On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote:
>> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
>> [...]
>> > > * Rebuild the debian-installer images, pulling in updates from
>> > >   stretch-updates, leaving only armhf netboot targets broken. 
>> > 
>> > Expanding a bit: rebuilding src:debian-installer from the stretch
>> > branch, which has s-p-u enabled, would fetch the fixed kernel and a
>> > couple of its udebs, at build time; the resulting netboot images
>> > wouldn't know about s-p-u though at run time, and would try to load
>> > udebs from stretch.
>> 
>> [...]
>> 
>> Why is that a problem?  The only change made in 4.9.144-3.1 is in the
>> kernel image, and the module udebs don't have versioned dependencies.
>
> However, as an additional data point, the kernel currently sat in NEW
> and destined for stable has an ABI bump. If that's accepted, then I
> assume things will "just work" in the meantime as the old binary
> packages will hang around until they're decrufted, but it's worth
> bearing in mind.

A debian-installer build for stretch-proposed-updates was made, which
may not get merged into stretch before the next point release. For the
time being:

  
https://deb.debian.org/debian/dists/stretch-proposed-updates/main/installer-armhf/

I've successfully tested version "20170615+deb9u5+b3", as well as at
least one other person. It should continue to work until the next point
release, and I'll do at least some minimal testing of the next point
release on armhf before pushing it to stretch so this doesn't happen
again.

More details in:

  https://bugs.debian.org/924129


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#925556: UEFI or not, can't mount /dev

[Lennart Sorensen]

On Tue, Mar 26, 2019 at 07:13:21PM +, Steve McIntyre wrote:
> On Wed, Mar 27, 2019 at 02:58:36AM +0800, 積丹尼 Dan Jacobson wrote:
> >Package: debian-installer
> >
> >Guess what, seen with ASUS X370-A:
> 
> Dan, you know better than this. A useful bug report needs much more
> information. For a start, what image did you use to install with? This
> looks like it *might* be on first boot after installation, but you're
> leaving me to guess at that. How did you partition, etc.? Were there
> any errors reported during installation?
> 
> Please help us to help you...

Well the picture appears to show root is sdb2 on a disk with sdb1 and
sdb2 partitions, and it can't mount /dev apparently because there is no
/dev directory on the root filesystem to mount it on.

At least that's what it looks like in the picture.

Clearly the initramfs was able to mount /dev and run fsck, but mounting
it to /root/dev to transfer to the real rootfs failed due to a missing
directory.

-- 
Len Sorensen

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

[Adam D. Barratt]

On Tue, 2019-03-26 at 10:39 -0700, Vagrant Cascadian wrote:
> On 2019-03-26, Adam D. Barratt wrote:
> > On 2019-03-15 06:44, Adam D. Barratt wrote:
> > > The updated images for armhf have been available in p-u for a
> > > couple of
> > > days now.
> > > 
> > > Feedback would be appreciated, as we would like to be able to
> > > accept
> > > the new kernel upload into p-u, which will block a further
> > > rebuild here
> > > as it brings an ABI bump. (The existing images should continue to
> > > work
> > > until the older packages are decrufted in the next point
> > > release.)
> > 
> > Thanks to Peter for the feedback.
> > 
> > Vagrant (or anyone else) - anything to add?
> 
> Just tested fine on BananaPI:
> 
>   https://cdn-aws.deb.debian.org/debian/dists/stretch-proposed-update
> s/main/installer-
> armhf/20170615+deb9u5+b3/images/netboot/netboot.tar.gz
> 
> Installed to SATA. No surprises or anything unusual.
> 
> I'd say it's ready; please push it into stretch.

Thanks for testing.

As I mentioned on IRC, we can't "push it into stretch" without a point
release, and the whole point of this exercise was to avoid having to
schedule another short-notice point release.

However, assuming KiBi has no objections, it sounds like we can go
ahead with getting the -9 ABI kernel into p-u in preparation for the
9.9 point release in a few weeks time. Assuming I haven't missed
anything, the d-i version in p-u should continue to be suitable for
installing stretch on armhf in the meantime (at least until the p-u
freeze hits, at which point d-i will get rebuilt against the new
kernel).

Regards,

Adam

Bug#925556: UEFI or not, can't mount /dev

[Steve McIntyre]

On Wed, Mar 27, 2019 at 02:58:36AM +0800, 積丹尼 Dan Jacobson wrote:
>Package: debian-installer
>
>Guess what, seen with ASUS X370-A:

Dan, you know better than this. A useful bug report needs much more
information. For a start, what image did you use to install with? This
looks like it *might* be on first boot after installation, but you're
leaving me to guess at that. How did you partition, etc.? Were there
any errors reported during installation?

Please help us to help you...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

[Vagrant Cascadian]

On 2019-03-26, Adam D. Barratt wrote:
> On 2019-03-15 06:44, Adam D. Barratt wrote:
>> The updated images for armhf have been available in p-u for a couple of
>> days now.
>> 
>> Feedback would be appreciated, as we would like to be able to accept
>> the new kernel upload into p-u, which will block a further rebuild here
>> as it brings an ABI bump. (The existing images should continue to work
>> until the older packages are decrufted in the next point release.)
>
> Thanks to Peter for the feedback.
>
> Vagrant (or anyone else) - anything to add?

Just tested fine on BananaPI:

  
https://cdn-aws.deb.debian.org/debian/dists/stretch-proposed-updates/main/installer-armhf/20170615+deb9u5+b3/images/netboot/netboot.tar.gz

Installed to SATA. No surprises or anything unusual.

I'd say it's ready; please push it into stretch.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#925545: udhcpd: support for Runit supervision system

[Dmitry Bogatov]

Package: udhcpd
Version: 1:1.30.1-3
Severity: wishlist
Tags: patch
User: ru...@packages.debian.org
Usertags: runscript

Dear Maintainer,

please consider applying patch, that adds support for Runit supervision
system.

dpkg-source: warning: extracting unsigned source package 
(/home/iu/devel/salsa/debian/busybox_1.30.1-2.dsc)
dpkg-source: warning: extracting unsigned source package 
(/home/iu/devel/salsa/debian/busybox_1.30.1-3.dsc)
diff -Nru busybox-1.30.1/debian/changelog busybox-1.30.1/debian/changelog
--- busybox-1.30.1/debian/changelog 2019-03-02 08:11:13.0 +
+++ busybox-1.30.1/debian/changelog 2019-03-24 11:24:02.0 +
@@ -1,3 +1,9 @@
+busybox (1:1.30.1-3) UNRELEASED; urgency=medium
+
+  * Add runscript for Runit system.
+
+ -- Dmitry Bogatov   Sun, 24 Mar 2019 11:24:02 +
+
 busybox (1:1.30.1-2) unstable; urgency=high
 
   * Complete the fix for [CVE-2018-20679] Closes: #918846
diff -Nru busybox-1.30.1/debian/control busybox-1.30.1/debian/control
--- busybox-1.30.1/debian/control   2019-03-02 07:57:49.0 +
+++ busybox-1.30.1/debian/control   2019-03-24 11:24:02.0 +
@@ -5,7 +5,7 @@
 Uploaders:
  Chris Boot ,
  Christoph Biedl ,
-Build-Depends: debhelper (>= 11~), zip
+Build-Depends: debhelper (>= 11~), zip, dh-runit (>= 2.8.8)
 Standards-Version: 4.1.5
 Vcs-Git: https://salsa.debian.org/installer-team/busybox.git
 Vcs-Browser: https://salsa.debian.org/installer-team/busybox
@@ -123,6 +123,7 @@
  lsb-base,
  ${misc:Depends},
 Provides: dhcpd
+Breaks: ${runit:Breaks}
 Description: Provides the busybox DHCP server implementation
  Busybox contains a very small yet fully function RFC compliant DHCP
  server formerly known as udhcpd.
diff -Nru busybox-1.30.1/debian/rules busybox-1.30.1/debian/rules
--- busybox-1.30.1/debian/rules 2019-03-02 07:57:49.0 +
+++ busybox-1.30.1/debian/rules 2019-03-24 11:19:17.0 +
@@ -47,7 +47,7 @@
 export KCONFIG_NOTIMESTAMP=1
 
 %:
-   dh $@
+   dh $@ --with runit
 
 ##
 
diff -Nru busybox-1.30.1/debian/udhcpd.runit busybox-1.30.1/debian/udhcpd.runit
--- busybox-1.30.1/debian/udhcpd.runit  1970-01-01 00:00:00.0 +
+++ busybox-1.30.1/debian/udhcpd.runit  2019-03-24 11:22:23.0 +
@@ -0,0 +1 @@
+debian/udhcpd.runscript name=udhcpd,logscript,since=1:1.30.1-3
diff -Nru busybox-1.30.1/debian/udhcpd.runscript 
busybox-1.30.1/debian/udhcpd.runscript
--- busybox-1.30.1/debian/udhcpd.runscript  1970-01-01 00:00:00.0 
+
+++ busybox-1.30.1/debian/udhcpd.runscript  2019-03-24 11:23:50.0 
+
@@ -0,0 +1,3 @@
+#!/bin/sh
+exec 2>&1
+exec /usr/sbin/udhcpd -f /etc/udhcpd.conf



pgpOoQgQ98ZCh.pgp
Description: PGP signature

Processed: reassign 925537 to installation-reports

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 925537 installation-reports
Bug #925537 [installation-reports v5.4 cd amd64] Debian Buster test
Warning: Unknown package 'v5.4'
Warning: Unknown package 'cd'
Warning: Unknown package 'amd64'
Bug reassigned from package 'installation-reports v5.4 cd amd64' to 
'installation-reports'.
Ignoring request to alter found versions of bug #925537 to the same values 
previously set
Ignoring request to alter fixed versions of bug #925537 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
925537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#925537: Debian Buster test

[Ken]

Package: installation-reports v5.4 CD amd64

Boot method: CD ISO from USB
Image version:
https://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/
Date: 2019-03-26

Machine: COMPAQ Presario 
Processor: AMD Athlon 64 3800+ x1
Memory: 2Gb
Partitions:  Partition FSMNTSize   USED  UNUSED
FLAGS
 /dev/sda1 ext4  /  27.94 GiB  6.88 GiB  21.06 GiB 
boot
 /dev/sda2 extended 46.56
 /dev/linux-swap /swap  1.4 GiB
 /dev/sda6   /home  45.17 GiB  1.89 GiB  43.29 GiB

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [O]
Load installer modules: [E]
Detect hard drives: [E]
Partition hard drives:  [ ]
Install base system:[E]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [E]
Install boot loader:[O]
Overall install:[E]

Comments/Problems: After initial menu no selection allows install to
complete. Screen goes blank and activity ceases. No cursor and no text.
This is an older 
   machine that does not allow use of ACIP. Debian 9.8
stretch runs fine. 

   I do like how quickly the initial menu comes up. All
of the boot / install process should go that fast as well as the final
boot splash response 
   on boot load. 
   Much more attention should be paid to user feedback
of system activity. Just sitting waiting for the next display is not
enough. Newer machines 
   don't even have a disk activity indicator. It is not
possible to tell what is going on nor if there is a problem. Use the
wait cursor much more 
   and include status message much more where
appropriate.
   Overall I much prefer Debian and LMDE to Ubuntu base
even with Cinnamon. Hoping for same result from 10.

-- 

73 AD5XJ Ken
ad...@arrl.net
ad...@winlink.org subject: //WL2K subject 
ad...@qso.com 

Southern Territory SATERN Net Manager
SATERN International Digi Net Manager
WebMaster satern.org
ARRL Technical Specialist
(985) 746-5110

Bug#925531: Preseeding partman-auto/method causes incorrect display of existing partitions

[Heiko Noordhof]

Package: partman-auto
Version: 20170615+deb9u5

Short description of the bug:

Including this line in the preesed file:

  d-i partman-auto/method string regular

causes the installer (partman) to incorrectly display the partitions
already present on the disk. Some partitions are not shown at all,
incorrect sizes are displayed and flags shown are wrong.

OS: Debian Stretch (stable at the time of writing)
Arch: amd64
Hardware: Lenovo ThinkCentre M910q (also reproduced on vmWare ESX guest)
Harddisks: 1 nvme disk (also reproduced on virtual vmWare ESX disk)

Netboot setup (I use iPXE and dnsmasq):

   kernel: http://ftp.nl.debian.org/debian/dists/stretch/main/installer-
   amd64/current/images/netboot/debian-installer/amd64/linux

   initrd: http://ftp.nl.debian.org/debian/dists/stretch/main/installer-
   amd64/current/images/netboot/debian-installer/amd64/initrd.gz

   arguments:
   initrd=initrd.gz
   vga=normal
   auto=true
   priority=critical
   locale=en_US
   bootable
   ipv6.disable=1
   url=http:preseed.txt

Existing disk label type: msdos (i.e. not gpt)


To reproduce:

(1) Create this simple two-line preseed.txt file:

d-i debian-installer/locale string en_US
d-i keyboard-configuration/xkb-keymap select us

(2) Boot the installer and when asked, enter some root password, some
username and password.

(3) When 'Partition disks' dialog is shown, select "manual" option.

(4) Partition table shown now is correctly. In (one of) my test case(s):

/dev/nvme0n1 - 256.1 GB Ubknown
 #1  primary  100.0 GB  B ext4
 #2  primary8.0 GB F  swap  swap
 #5  logical   48.0 GBext4
 #6  logical   20.0 GBext4
 #4  primary   80.1 GBext4

(5) Now add this line to the preseed.txt file:

d-i partman-auto/method string regular

(6) Without changing any partitions restart installation (e.g. press
ctrl-alt-del).

(7) Arriving at partman's manual partitioning the same way again, the
same partition table is now displayed quite incorrectly:

/dev/nvme0n1 - 256.1 GB Ubknown
 #1  primary  247.6 GB f  ext4
 #5  logical8.5 GB f  ext4

(7) Note this partition information is very different compared to what
was shown (correctly) the first time:

  - flags 'B' and 'F' seem to have gone on #1 and #5.
  - flag  'f' is shown, but not on the same partitions that had 'B'
and 'F' before.
  - Partition #1 now seems to fill the entire disk (size wrong).
  - Partition #5 is now shown as swap with a different size.
  - Partitions #2 #4 and #6 are not shown at all.

(8) The partition are left correctly on disk by the way: after removing
the "partman-auto/method" line from the preseed file and rebooting
the installer, everything is still fine.

Re: Bug#925508: unblock: debian-edu-install/2.10.21

[Cyril Brulebois]

Wolfgang Schweer  (2019-03-25):
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> 
> Please unblock package debian-edu-install
> 
> This is a very tiny change needed to set the right Debian Edu version 
> for the release. Holger Levsen uploaded the package already.
> 
> Full source debdiff against the version in testing attached.
> 
> Cced to debian-boot@ and Cyril Brulebois because an ack is needed due to 
> udebs.
> 
> unblock debian-edu-install/2.10.21

No objections, thanks.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

[Adam D. Barratt]

On 2019-03-15 06:44, Adam D. Barratt wrote:

The updated images for armhf have been available in p-u for a couple of
days now.

Feedback would be appreciated, as we would like to be able to accept
the new kernel upload into p-u, which will block a further rebuild here
as it brings an ABI bump. (The existing images should continue to work
until the older packages are decrufted in the next point release.)


Thanks to Peter for the feedback.

Vagrant (or anyone else) - anything to add?

KiBi - do you have any opinions on us going ahead with accepting the new 
kernel (including the ABI bump) into p-u?


Regards,

Adam