-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Fri, 2019-01-25 at 20:22 +0100, Matthias Klumpp wrote:
Am Fr., 25. Jan. 2019 um 18:31 Uhr schrieb Jeremiah C. Foster <jeremiah.foster@puri.sm>:
Hash: SHA512
Hi,
In this PureOS issue; https://tracker.pureos.net/T677 it appears that we have two places to download a PureOS ISO;
- - The PureOS download page (https://pureos.net/download/) - - And downloads (https://downloads.puri.sm/live/gnome/2018-12-10/ )
The downloads page has a more recent release and I wonder if we should move it to the PureOS "download" page? What is the process?
This is actually one place: pureos.net/downloads points to downloads.puri.sm/downloads.pureos.net (that's the same server).
Excellent, thanks!
The download page on pureos.net gets updated whenever we properly tested a new image to point to what live image we want our users to download, the downloads.pureos.net directory contains all built images (even untested ones and flavor we don't officially support!) as well as the OEM install images we use internally for Librems.
Okay, good to know.
If an image is tested,
I'll download and test the 2018-12-10 ISO. I'll see if I can boot it onto my Librem13v3
someone from the web team needs to be ping'ed to update the download link on pureos.net/downloads (Francois for example).
ACK. What is the process for cutting a new image? Do we have an automated nightly build or do we twiddle a bit somewhere to create a new image? Regards, Jeremiah -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxLaxoACgkQeFgrT+6R sjn6GgwAjp3EdloBuM+wfX1oLVuc9/OF2AB3DQ4pe0EBXp8WlrubvUSwTbNB5qd4 CsTJSLQ0Pg9OwTXwTCq537mwO6fhMzd20pFTNtS6Zch54i2ftz6LWql6BwbFH+7G xQRvwAz2BV9xM9GyhBfWJ0WmQ/F+k2KsxjZTgYmhZWPMGsxM0QMZrD/lbAPySxhD 0gSPdObXDd3kYo4TqS3Kb8GHl8oHgtcwoQlGuEz6V6xlOBaFn1J8qNHsepsoytaM tak0+4jHujL1JKpN0qKrhum7Rwoq9rn9ZsOMVos5vajtSyROWQjlpxT0fL5sMn0H m3p2V6rUEQd4clQPccTyPA/npOpEfiPCmwykW8guOgSaRJ8WVSbrpnriqROZTPSW uF5bzfHXRbOYkdLigY/cVdzi29eHfLrlLr7QKrwVYn3T041WZcNmdRyNSZGECDYr +wYjwbN9w7iCC8NqHHqT3wKIdtI3dse529vRha++NsT0F95VDodK2V9Ao8aW58wb yZpY/BVx =EMJz -----END PGP SIGNATURE-----