Re: debian-installer now available in Ports
I've set up some additional jobs at
http://jenkins.kfreebsd.eu/jenkins/view/cd/
and after much trial-and-error, there are now (untested) sid netinst
images built for:
hurd-i386 kfreebsd-amd64 kfreebsd-i386 powerpc
You can find the .iso images within each job's workspace e.g.:
http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_sid_hurd-i386/ws/build/
It's building on a kfreebsd-amd64 host, in a jessie-kfreebsd chroot,
with current Git master of debian-cd, my patches for #860187 and
#860204 applied, and the attached diff against CONF.sh. I started each
build like this:
$ export CODENAME=sid
$ export ARCHES=hurd-i386
$ CONF.sh && ./build.sh
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/CONF.sh b/CONF.sh
index 99e58ad..08ffbd7 100644
--- a/CONF.sh
+++ b/CONF.sh
@@ -62,11 +62,15 @@ export BASEDIR=`pwd`
# export CDNAME=debian
# Building $codename cd set ...
-export CODENAME=stretch
+#export CODENAME=stretch
# By default use Debian installer packages from $CODENAME
if [ -z "$DI_CODENAME" ]; then
- export DI_CODENAME=$CODENAME
+ if [ "${CODENAME}" = "jessie-kfreebsd" ]; then
+ export DI_CODENAME=${CODENAME}-proposed-updates
+ else
+ export DI_CODENAME=${CODENAME}
+ fi
fi
# If you want backported d-i (e.g. by setting
# DI_CODENAME=jessie-backports, then you'll almost definitely also
@@ -86,7 +90,7 @@ fi
#export DI_WWW_HOME=default
# Version number, "2.2 r0", "2.2 r1" etc.
-export DEBVERSION="9.0"
+export DEBVERSION="unofficial"
# Official or non-official set.
# NOTE: THE "OFFICIAL" DESIGNATION IS ONLY ALLOWED FOR IMAGES AVAILABLE
@@ -119,17 +123,17 @@ fi
# images, however. Also, if you are using an NFS partition for
# some part of this, you must use this option.
# Paths to the mirrors
-export MIRROR=/srv/mirror/debian
+export MIRROR=/srv/ftp.debian.org
# Path of the temporary directory
-export TDIR=/srv/mirror/tmp
+export TDIR=/home/cd/tmp
# Path where the images will be written
-export OUT=/srv/mirror/debian-cd-test
+export OUT=/home/cd/out
# Where we keep the temporary apt stuff.
# This cannot reside on an NFS mount.
-export APTTMP=/srv/mirror/tmp/apt
+export APTTMP=$TDIR/apt
# Do I want to have NONFREE merged in the CD set
# export NONFREE=1
@@ -164,7 +168,9 @@ export CONTRIB=1
# Note that on the CDs it will not be visible where packages came from:
# from the released archive or from proposed updates archive.
# NOTE: intended to be used for pre-release testing, not for publication!
-#export PROPOSED_UPDATES=$CODENAME-proposed-updates
+if [ "${CODENAME}" = "jessie-kfreebsd" ]; then
+ export PROPOSED_UPDATES=$CODENAME-proposed-updates
+fi
# Sparc only : bootdir (location of cd.b and second.b)
# export BOOTDIR=/boot
@@ -175,7 +181,7 @@ export CONTRIB=1
# Use this to force copying the files instead of symlinking or hardlinking
# them. This is useful if your destination directories are on a different
# partition than your source files.
-# export COPYLINK=1
+export COPYLINK=1
# Options
# export MKISOFS=mkisofs
@@ -190,6 +196,12 @@ export CONTRIB=1
#export i386_MKISOFS_OPTS="-as mkisofs -r -checksum_algorithm_iso md5,sha1"
#export amd64_MKISOFS="xorriso"
#export amd64_MKISOFS_OPTS="-as mkisofs -r -checksum_algorithm_iso md5,sha1"
+export hurd_i386_MKISOFS="xorriso"
+export hurd_i386_MKISOFS_OPTS="-as mkisofs -r -checksum_algorithm_iso sha256"
+export kfreebsd_i386_MKISOFS="xorriso"
+export kfreebsd_i386_MKISOFS_OPTS="-as mkisofs -r -checksum_algorithm_iso sha256"
+export kfreebsd_amd64_MKISOFS="xorriso"
+export kfreebsd_amd64_MKISOFS_OPTS="-as mkisofs -r -checksum_algorithm_iso sha256"
# Keyring (defaults):
#ARCHIVE_KEYRING_PACKAGE=debian-archive-keyring
@@ -233,7 +245,7 @@ ATTEMPT_FALLBACK=yes
# STICK4GB: 4GB USB stick or similar
# STICK8GB: 8GB USB stick or similar
# CUSTOM:up to you - specify a size to go with it (in 2K blocks)
-export DISKTYPE=CD
+export DISKTYPE=NETINST
#export DISKTYPE=CUSTOM
#export CUSTOMSIZE=
# If you want to over-ride this choice (e.g. to make a larger version of a given disk),
@@ -242,7 +254,7 @@ export DISKTYPE=CD
# export FORCE_CD_SIZE1= to change the size of disk 1 (only)
# Extra variants to enable. See docs/README.variants for more information.
-export VARIANTS=
+export VARIANTS=light
# We don't want certain packages to take up space on CD1...
#export EXCLUDE1=exclude
@@ -375,8 +387,8 @@ export SNAPURL=Debian=http://snapshot.debian.org/archive/debian/SNAPDATETIME/
# INSTALLER_CD=0: nothing special (default)
# INSTALLER_CD=1: just add debian-installer (use TASK=debian-installer)
# INSTALLER_CD=2: add d-i and base (use TASK=debian-installer+kernel)
-#export INSTALLER_CD=2
-#export TASK=debian-installer+kernel
+export INSTALLER_CD=2
+export TASK=debian-installer+kernel
# Parameters to pass to kernel (or d-i) when the CD boots. Not currently
# supported for all architectures.
@@ -387,7 +399,7 @@ export
Re: debian-installer now available in Ports
On Wed, Apr 12, 2017 at 01:55:08PM +0100, Steven Chamberlain wrote: >John Paul Adrian Glaubitz wrote: >> Thus, I was wondering whether any volunteers would be willing to help >> building >> ISO images for the various architectures. > >I'm already doing this for kfreebsd-amd64, but only the jessie-kfreebsd >suite: >http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_jessie-kfreebsd/lastBuild/console >and I had to patch debian-cd before it worked. (Didn't yet find time to >file bugs or submit those patches). Please post them! >I could probably set up similar jobs for kfreebsd-* sid now. > >> It's not necessary to run debian-cd on the same architecture as the >> target architecture of the ISO images. Exactly. There are sometimes difficulties with the tools needed to set up boot files etc., but they tend to be portable. >I did not even realise that. So I will add kfreebsd-i386 next. > >I expect there might be problems trying to build linux arches from a >kfreebsd host. But we should try to find out, and then maybe fix it. We were happily building kfreebsd-* images from a Linux host, so I'd expect it to work OK. I've offered before: I don't have the time personally to work on building ports images, but I'm more than happy to help other people getting them building on our official infrastructure... -- Steve McIntyre, Cambridge, UK.st...@einval.com Who needs computer imagery when you've got Brian Blessed?
Re: debian-installer now available in Ports
Steven Chamberlain, on mer. 12 avril 2017 13:55:08 +0100, wrote: > I expect there might be problems trying to build linux arches from a > kfreebsd host. But we should try to find out, and then maybe fix it. FWIW, I have been building hurd-i386 images from a linux box for a long time without problems. Samuel
Re: debian-installer now available in Ports
Hello, John Paul Adrian Glaubitz wrote: > Thus, I was wondering whether any volunteers would be willing to help building > ISO images for the various architectures. I'm already doing this for kfreebsd-amd64, but only the jessie-kfreebsd suite: http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_jessie-kfreebsd/lastBuild/console and I had to patch debian-cd before it worked. (Didn't yet find time to file bugs or submit those patches). I could probably set up similar jobs for kfreebsd-* sid now. > It's not necessary to run debian-cd on the same architecture as the > target architecture of the ISO images. I did not even realise that. So I will add kfreebsd-i386 next. I expect there might be problems trying to build linux arches from a kfreebsd host. But we should try to find out, and then maybe fix it. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
debian-installer now available in Ports
Hi! Thanks to the recent efforts within the Debian Ports projects, debian-installer is finally available for the Debian Ports architectures [1]. Previously, the installer images had to be built manually because building on the buildds always required a testing repository to be available for a given architecture. With the latest release of debian-installer, the build falls back to the unstable and unreleased repositories for the required udebs. The generated d-i images for powerpc, kfreebsd-* and hurd-i386 can be found here: > ftp://ftp.debian.org/debian/dists/sid/main/installer-$ARCH For the remaining Ports architectures: > http://ftp.ports.debian.org/debian-ports/pool-$ARCH/main/d/debian-installer/ Now, since the process of building installer images no longer requires manual intervention, the process for building CD images has been simplified as well, still requires some manual work. Thus, I was wondering whether any volunteers would be willing to help building ISO images for the various architectures. A rough guide can be found in [2] from which the the d-i part can be omitted, however, a local mirror available through the filesystem is still necessary (see MIRROR in CONF.sh). So, reprepro needs to be used to set up a local mirror or the remote mirror needs to be mounted with a FUSE module or similar. In order to use the debian-installer images for building CD images, they have to be downloaded and extracted (for the remaining Ports architectures above) and placed into the directory pointed to by DI_DIR in the easy-build.sh script, e.g.: export DI_DIR="/srv/d-i/debian-installer/installer/build/tmp/cdrom/. Would be great if we could get several people work on this and create ISOs for alpha, hppa, powerpc, ppc64 and so on. Please note: It's not necessary to run debian-cd on the same architecture as the target architecture of the ISO images. Hence, using an amd64 host should be fine. Thanks, Adrian > [1] https://buildd.debian.org/status/package.php?p=debian-installer=sid > [2] https://wiki.debian.org/PortsDocs/CreateDebianInstallerImages -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
