[PureOS] Building my own PureOS ISO image?

Jeremiah C. Foster jeremiah.foster at puri.sm
Tue Mar 19 06:22:22 PDT 2019


On Mon, 2019-03-18 at 23:43 +0100, Matthias Klumpp wrote:
> Am Mo., 18. März 2019 um 22:28 Uhr schrieb Jeremiah C. Foster
> <jeremiah.foster at puri.sm>:
> > On Wed, 2019-03-06 at 22:04 +0100, Matthias Klumpp wrote:
> > > Am Mi., 6. März 2019 um 19:56 Uhr schrieb Chris Lamb <
> > > chris.lamb at puri.sm>:
> > > > Hi pureos-project,
> > > > 
> > > > I'm trying to build a PureOS ISO image on my own system but
> > > > can't
> > > > seem to locate a script/repo/documentation
> > > 
> > > That should be pretty easy. The basic process is the following
> > > (see
> > > below for replicating almost 100% of what our builders do):
> > 
> > I've put the instructions here as well:
> > http://tracker.pureos.net/w/howto_build/
> 
> Thanks a lot for doing that!

Thank you for your help with the instructions, much appreciated.

> 
> Am Mo., 18. März 2019 um 22:48 Uhr schrieb Jeremiah C. Foster
> <jeremiah.foster at puri.sm>:
> > On Wed, 2019-03-06 at 22:04 +0100, Matthias Klumpp wrote:
> > > Am Mi., 6. März 2019 um 19:56 Uhr schrieb Chris Lamb <
> > > chris.lamb at puri.sm>:
> > > > Hi pureos-project,
> > > > 
> > > > I'm trying to build a PureOS ISO image on my own system but
> > > > can't
> > > > seem to locate a script/repo/documentation
> > > That should be pretty easy. The basic process is the following
> > > (see
> > > below for replicating almost 100% of what our builders do):
> > 
> > <snip>
> > 
> > > These steps can be sped up a lot and be automated by using
> > > debspawn,
> > > which is used to create the official PureOS images in a
> > > controlled
> > > environment.
> > > In order to use debspawn, just follow these steps:
> > > 1) Run `sudo apt install debspawn`
> > > 2) Then run `debspawn create green`
> > 
> > Running this I get this error;
> > 
> > I: Target architecture can be executed
> > I: Keyring file not available at /usr/share/keyrings/pureos-
> > archive-
> > keyring.gpg; switching to https mirror 
> > https://deb.debian.org/debian
> > I: Retrieving InRelease
> > 
> > The error is easily mitigated by running with the --mirror arg;
> > $ debspawn create green --mirror https://repo.pureos.net/pureos
> > 
> > Should we somehow provide the pureos-archive-keyring or mention it
> > ought to be downloaded?
> 
> We could probably include it in Debian at some point, but for now
> mentioning to download it explicitly makes sense to me, especially
> because that ensures people will get a recent enough version of the
> archive keyring (which reminds me that we should likely refresh the
> keys at some point).

+1

I think I'll add a little blurb to the instructions mentioning the
keys.

Cheers,

Jeremiah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part
URL: <http://lists.puri.sm/pipermail/pureos-project/attachments/20190319/e0d88fcb/attachment-0001.sig>


More information about the Pureos-project mailing list