Bug#929889: debootstrap: Support unconventional PATH on foreign distros

2019-06-03 Thread Tianon Gravi
On Sun, 2 Jun 2019 at 11:12, Vagrant Cascadian  wrote:
> The following patch fixes issues when the hard-coded
> PATH=/sbin:/usr/sbin:/bin:/usr/bin does not contain chroot or other
> commonly used utilities, by changing to PATH=$PATH:/sbin:...

Do you think it would make sense to instead use "/usr/bin/env" inside
the chroot to just explicitly set PATH to a sane value?  Maybe even
with "-i" to ensure we don't leak any other environment variables too?


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4



Re: Debian Jessie net installations broken for last months

2019-06-03 Thread Cyril Brulebois
Hi Floris,

Floris Bos  (2019-06-03):
> We having been having problems with preseeded PXE network installations of
> Debian Jessie for the past months, while it used to work before, and other
> Debian editions do install properly.
> 
> 
> First of all our installation script used to be able to download the network
> installation files (kernel/initrd) from:
> http://ftp.debian.org/debian/dists/jessie/main/installer-amd64/current/
> But that folder disappeared.

This /might/ be a bug on the FTP side, or a deliberate decision on their
side. I suggest getting in touch with them:

  https://wiki.debian.org/Teams/FTPMaster

> Filled a bug report a month ago:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928517.
> But did not receive any response.

The mirrors team deals with the mirror network, while the issue you're
seeing is likely on the contents generation side.

> Then tried the network installation files in the other folder
> "20150422+deb8u" that does still exist: 
> http://ftp.debian.org/debian/dists/jessie/main/installer-amd64/20150422+deb8u5/images/netboot/debian-installer/amd64/
> 
> But that will fail to complete installation on servers do not have full
> Internet access.
> 
> 
> We set a custom mirror with the "d-i mirror/http/hostname" preseed option.
> 
> But it also wants to download repository files from
> http://security.debian.org/ nevertheless, which will fail with a warning.
> 
> It then complains that the (mirrored)
> http://ftp.debian.org/debian/dists/jessie-updates/InRelease file does not
> have the right entries.
> 
> "Unable to find expected entry 'main/binary-amd64/Packages' in Release file
> (Wrong sources.list entry or malformed file)"
> 
> 
> The InRelease file for stretch and buster does have
> main/binary-amd64/Packages entries on the main mirror site.
> 
> Any reason they are no longer there for jessie even while that release is
> not EOL yet?

I think you might find tweaking apt-setup/services-select interesting.


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


signature.asc
Description: PGP signature


Debian Jessie net installations broken for last months

2019-06-03 Thread Floris Bos

Hi,


We having been having problems with preseeded PXE network installations 
of Debian Jessie for the past months, while it used to work before, and 
other Debian editions do install properly.



First of all our installation script used to be able to download the 
network installation files (kernel/initrd) from: 
http://ftp.debian.org/debian/dists/jessie/main/installer-amd64/current/


But that folder disappeared.

Filled a bug report a month ago: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928517.

But did not receive any response.


Then tried the network installation files in the other folder 
"20150422+deb8u" that does still exist: 
http://ftp.debian.org/debian/dists/jessie/main/installer-amd64/20150422+deb8u5/images/netboot/debian-installer/amd64/


But that will fail to complete installation on servers do not have full 
Internet access.



We set a custom mirror with the "d-i mirror/http/hostname" preseed option.

But it also wants to download repository files from 
http://security.debian.org/ nevertheless, which will fail with a warning.


It then complains that the (mirrored) 
http://ftp.debian.org/debian/dists/jessie-updates/InRelease file does 
not have the right entries.


"Unable to find expected entry 'main/binary-amd64/Packages' in Release 
file (Wrong sources.list entry or malformed file)"



The InRelease file for stretch and buster does have 
main/binary-amd64/Packages entries on the main mirror site.


Any reason they are no longer there for jessie even while that release 
is not EOL yet?




Yours sincerely,


Floris Bos



Re: Debian-Installer support for riscv64

2019-06-03 Thread Ian Campbell
On Sun, 2019-06-02 at 22:25 +0200, Karsten Merker wrote:
> Another thing that needs to be tackled in d-i is an annoying
> property of qemu's riscv64 "virt" machine: The "virt" machine
> emulates both a normal serial console (/dev/ttyS0) and a HVC
> console (/dev/ttyhvc0).  Unfortunately in qemu both share the
> same physical console device and systemd starts a getty on both
> /dev/ttyS0 and /dev/ttyhvc0 so that we have two getty instances
> running on the same physical console which wreks havoc.

Can this be fixed on the qemu side? Having two emulated devices
appearing on the same host console is going to cause confusion over and
over again I think.

Is it possible that this behaviour is down to the command line you are
giving qemu? e.g. `-nographic` might (completely guessing) end up with
this behaviour, whereas the UI would put them on separate virtual
consoles.

Ian.