search

lavabit / robox

The tools needed to robotically create/configure/provision a large number of operating systems, for a variety of hypervisors, using packer.
620 stars 139 forks source link

add FreeBSD 13.1 support #241

Closed yjqg6666 closed 2 years ago

yjqg6666 commented 2 years ago

These files are generated by:

./res/scripts/add.sh freebsd13 freebsd13.1 \
https://download.freebsd.org/ftp/releases/ISO-IMAGES/13.1/FreeBSD-13.1-RELEASE-amd64-disc1.iso \
 697d81653fa246b921ddfcf1d15562c55249cc727b11fa3e47f470e2cf2b6a40

When i ran this command, got the following output:

Bareword "http" not allowed while "strict subs" in use at line 1, in: http/generic.freebsd13

The credentials file is missing, so the validation is being skipped.

Reference: https://github.com/lavabit/robox/issues/9#issuecomment-439504969

ladar commented 2 years ago

@yjqg6666 I updated the freebsd13 to use the 13.1 install media. So it should get updated when I push out the 4.0.0 boxes.

As for the error you mentioned, The credentials file warning should be that important. A template is used to create .credentialsrc the first time you run the robox.sh script.

As for the other error, the only thing I can think of as being a culprit, is using a period in the box name is what caused the error. That may have broken the sed commands used to replace the old box name wth the new.

yjqg6666 commented 2 years ago

@ladar When could we expect the 4.0.0 boxes pushed out?

ladar commented 2 years ago

@yjqg6666 I kicked off the build last week, but unfortunately, with the hardware I have, and the size of the project, a build takes aorund 60 hours.

I checked on it Tues, but there were a few failures (FreeBSD 11 removed there package repos was one issue). Anyways, I fixed the various failures and pushed out boxes late last night/early this morning depending on your time zone. And "released" the new files a few hours later, once all the boxes finished uploading.

I've already started the 4.0.2 build, since Alpine 3.16 and Alma 9 just came out. And because some of the configs which broke need testing/fixing still.