-----BEGIN PGP SIGNED MESSAGE----- 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? Regards, Jeremiah - -- GnuPG key fingerprint; 798D B834 436A 7BE3 8C97 422D 0DC0 6220 5451 931B -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxLR/AACgkQeFgrT+6R sjkBDAv/fnl1D0QaUP0kdG/PRdQ6A984iWUK73/1Qcp3YqOe+2y+jpiiyrfAH10i 9q2esL08F2u/K6LTTYWpREgFNbw/++4WyUW09sgYjdfscicSpmG5zNkjCdjZ9f+i gyBaFcNvFG/f+gR5LmPz5jAa4heATXa4394trWw4ERbyt/dyVf3qcm3SVfZHKK/Y o5hdwkb9GbKGvpeVVNSpUfw+PRDnrjYLisuQdMINIWLKmE2BwtTF3UcLmJiElu2W VnjMcZA9JF4YLXkjUzpMLYIP4FR0XvOJHvCmOqEEtyPWKOhPq5EKVnuaFUihIcXW LPvgBSpPcaPEk8M8870PKRoHzYcXkQEsrQ/wSnKChJ/fJrYTaX8jtMvcjobjtTae jCz6c/UDCL7MPfQ4nLEXPheDDoWXC3tRhj9alNxxvkRbXDoqn3/4lAUGOF63GETt GS+4IeV52N/6piZryiHBIpptzxd705vR9xmrYGMKnsGDvuCKPy0e4JENux6SfLgv 95AwHnXS =pC+9 -----END PGP SIGNATURE-----
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). 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. If an image is tested, someone from the web team needs to be ping'ed to update the download link on pureos.net/downloads (Francois for example). Cheers, Matthias
-----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-----
Am Fr., 25. Jan. 2019 um 21:02 Uhr schrieb Jeremiah C. Foster <jeremiah.foster@puri.sm>:
[...]
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?
Currently I just hit a button in Laniakea (whenever something important changes, but at least once a month) - long-term I just want to do weekly or daily builds (we don't do those at the moment to save disk space and builder resources. It won't be much effort to set this up though.) FWIW, an updated image should be ready for testing tomorrow, due to the APT security fix landing in green. Cheers, Matthias
On Fri, Jan 25, 2019 at 3:28 PM, Matthias Klumpp <matthias.klumpp@puri.sm> wrote:
Am Fr., 25. Jan. 2019 um 21:02 Uhr schrieb Jeremiah C. Foster <jeremiah.foster@puri.sm>:
[...]
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?
Currently I just hit a button in Laniakea (whenever something important changes, but at least once a month) - long-term I just want to do weekly or daily builds (we don't do those at the moment to save disk space and builder resources. It won't be much effort to set this up though.)
+1
FWIW, an updated image should be ready for testing tomorrow, due to the APT security fix landing in green.
Thanks for the heads up! Do you mean the plasma release? --> https://downloads.puri.sm/live/plasma/2019-01-26/ Cheers, Jeremiah
Am Mo., 28. Jan. 2019 um 21:25 Uhr schrieb Jeremiah C. Foster <jeremiah.foster@puri.sm>:
[...] FWIW, an updated image should be ready for testing tomorrow, due to the APT security fix landing in green.
Thanks for the heads up! Do you mean the plasma release? --> https://downloads.puri.sm/live/plasma/2019-01-26/
There should have been releases for GNOME as well, however the sshfs connection that ties the upload server and archive server together became reeeealy slow for unknown reasons, so slow that a subsequent upload of the live image over the oem image was overriding files with the same name which resulted in a signature verification failure. So, I will ensure that the files have unique names in future, it is kind of silly that that wasn't the case before. New releases should meanwhile be available. Cheers, Matthias
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Mon, 2019-01-28 at 23:16 +0100, Matthias Klumpp wrote:
Am Mo., 28. Jan. 2019 um 21:25 Uhr schrieb Jeremiah C. Foster <jeremiah.foster@puri.sm>:
[...] FWIW, an updated image should be ready for testing tomorrow, due to the APT security fix landing in green.
Thanks for the heads up! Do you mean the plasma release? --> https://downloads.puri.sm/live/plasma/2019-01-26/
There should have been releases for GNOME as well
I tested the GNOME Live image from here; https://downloads.puri.sm/live/gnome/2019-01-28/ Checksums match but it fails to boot. Message is; firmware: failed to load i915/skl_dmc_ver1_27.bin (-2) firmware_class: See https://wiki.debian.org/Firmware for imformation about missing firmware. touch: /root/var/crash/crash.init: No such file or directory rm: can't remove '/root/var/crash/crash.init': No such file or directory Regards, Jeremiah -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxQw/YACgkQeFgrT+6R sjlPsQv+PW5UZymLXzTwqivDu+1sh1u+yFU3Svol0VTN3JlZM/ja4U20xQtIGKXe nv0Dj2oy0eGe1PK2TUv95BjeCFVt2n+1ewO4VDMdt95Gh4+il0drNWbVyWZTSWRF mrhaNYOQgFWHQGYH+CXgHj3FbdYaD9drbqc7H97iOf767gU9HJOSo0VdnXSi4bFC RxNwxZx586ZOHRK+d1NfiHK4XSRwOnJvm7ga6UjouiTqhIzfk460qllkazKBVRWh kafH3pYSGDo8rGC/FLdTGZdd/juvDE3UIZVX574TwxQl1bK3HiuEPHxYedF8kqf9 ye8n1NUdrADEMXkzCPxOshI4eqR8yIPl90coKGLZ8tzdxgfndbkkvaSWnXWEIx+1 t3jFPVJOMHT4Bf6qQRjRRL1lVy4wRe4u8Ucgy+DyfyE0Oh64aAM7z14aMx4ihk91 0dXter8Uq+Tjh6pXQ3G0iyLe7+3QILYHtWVRtOw3O6suf7z5EkJV5TQSX6mX5W1e HgdTfwf9 =p1mv -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Tue, 2019-01-29 at 16:21 -0500, Jeremiah C. Foster wrote:
On Mon, 2019-01-28 at 23:16 +0100, Matthias Klumpp wrote:
Am Mo., 28. Jan. 2019 um 21:25 Uhr schrieb Jeremiah C. Foster <jeremiah.foster@puri.sm>:
[...] FWIW, an updated image should be ready for testing tomorrow, due to the APT security fix landing in green.
Thanks for the heads up! Do you mean the plasma release? --> https://downloads.puri.sm/live/plasma/2019-01-26/
There should have been releases for GNOME as well
I tested the GNOME Live image from here; https://downloads.puri.sm/live/gnome/2019-01-28/
I rebooted and then chose the "failsafe" install and live, that worked. I'm installing PureOS at the moment. Jeremiah -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxQxnMACgkQeFgrT+6R sjmGagv/fm+7qv9GDkOyxTWcLXyJKBjtwsdRMGhdLdXvcUYyHKJtOPtrLfIO94Ox l2zsB1ErK5bLa/aR20t78TZArUfXCq601j8ZCgHCpcZx9epCa/kp6BwY4BSajchE iQnjS8FPdJIlGQaLjMcQ7qd1tp506WG5tvKp2xwrUZrJy1zOI9WDsBpsTTeVQe2Z HYzhtAwhkXkczz/HNI2/ys/HeAsBrzHARgA7O4iLru4b9OZpZaytCkXeuJhGpeRJ XE2HtWsgb08LgbH0B/HSH+bv1aSFzmAXvDasiPd1E0GG2YwN2XDcsnRL9xmy3EQR +1SoUMfli/2Q21baw9iPtst8XOMo3ltalGxkGmDGIjaG0NGQGTxj57rSB7y+enXg r/YOYI2tBhx7Qjl9EfTHa3M6CG8uDMU2ITPgKhn7BBGq+hJejXZXpSIuTklZ5NA5 CzaRqiKQgfDfd9Qo/P6Lb1yDF8dvSsP2sqngFALNKrlgC/OFXV/0Z/b+CtaoIJtP CllRpj7M =zRNv -----END PGP SIGNATURE-----
participants (2)
-
Jeremiah C. Foster -
Matthias Klumpp