<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear all,<br>
I just had problems with a FAI-installation.<br>
Everything went ok until "task_repository". <br>
But then the "apt-get update" failed:<br>
<br>
<font size="-1">Calling task_updatebase<br>
Updating base<br>
Ign file: KUP/ InRelease<br>
Get:1 file: KUP/ Release.gpg [490 B]<br>
Get:2 file: KUP/ Release [844 B]<br>
Ign file: KUP/ Translation-en<br>
Ign <a class="moz-txt-link-freetext" href="http://mirror.switch.ch">http://mirror.switch.ch</a> jessie InRelease<br>
Ign <a class="moz-txt-link-freetext" href="http://stat.ethz.ch">http://stat.ethz.ch</a> jessie-cran3/ InRelease<br>
Get:3 <a class="moz-txt-link-freetext" href="http://mirror.switch.ch">http://mirror.switch.ch</a> jessie-updates InRelease [145 kB]<br>
...<br>
Get:14 <a class="moz-txt-link-freetext" href="http://www.deb-multimedia.org">http://www.deb-multimedia.org</a> jessie/main amd64 Packages
[125 kB]<br>
Get:15 <a class="moz-txt-link-freetext" href="http://fai-project.org">http://fai-project.org</a> jessie Release [6747 B]<br>
E: The method driver /usr/lib/apt/methods/https could not be
found.</font><br>
<br>
Seemingly, apt tries to contact a package source over https - but
all my sources in sources.list(.d) are just http-addresses.<br>
I could solve the problem by removing one of my additional package
sources from my apt-repository (which seems to link to a
https-page), but this is only a workaround, not a real solution.<br>
<br>
Generally, https apt-sources seem to make problems only during
fai-installations, but not during fai-softupdates.<br>
Googleing indicated that the package "apt-transport-https" is needed
to be able to use https-sources. This package is installed on my
FAI-system by default - hence its no problem for softupdates.<br>
<br>
However, its only installed during "task_instsoft", but it needs
already to be present before "task_updatebase" to get it to work
during fai-installations.<br>
<br>
I thought I could get this by adding it to the nfsroot, but I still
got the same apt error during the FAI-installation ...<br>
I found the following lines in "fai-make-nfsroot.log", maybe thats
why it still doesn't work:<br>
<font size="-1">...<br>
<code></code>Setting up dracut (044+241-1~bpo8+1) ...<br>
dracut: Generating /boot/initrd.img-3.16.0-4-amd64<br>
dracut: Couldn't find SSL CA cert bundle; HTTPS won't work.<br>
dracut-install: ERROR: installing 'cryptsetup'<br>
dracut: FAILED: /usr/lib/dracut/dracut-install -D
/var/tmp/dracut.JnLbCQ/initramfs -a cryptsetup rmdir readlink
umount<br>
Setting up linux-image-3.16.0-4-amd64 (3.16.43-2+deb8u2) ...<br>
dracut: Couldn't find SSL CA cert bundle; HTTPS won't work.<br>
dracut-install: ERROR: installing 'cryptsetup'<br>
dracut: FAILED: /usr/lib/dracut/dracut-install -D
/var/tmp/dracut.59612o/initramfs -a cryptsetup rmdir readlink
umount<br>
...</font><br>
<br>
<br>
=> does someone have a FAI-setup where apt-https is working
during installations?<br>
=> is the nfsroot even the right place to add packages which
should already be installed before "task_softupdate" - like
"apt-transport-https"? It just came into my mind that I eventually
made an error in reasoning and I should maybe better add the package
to the basefile...<br>
<br>
Regards<br>
René<br>
<br>
</body>
</html>