-----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
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
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 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