A52q, date of the source code used to build eOS

[luca102]

Hi,
is there a way to figure out when the source to make a dev build has been taken from the original Lineage for microg and then from Lineage?

https://images.ecloud.global/dev/a52q/e-1.15-t-20230917331436-dev-a52q.zip

For instance, here it was build on 2023 Sep 17 by murena, but when the source from LineageOS has been downloaded?

Thanks
Luca

[aibd]

The standard build routine ensures that all the projects involved, that will include the required LineageOS repos, are synced at time of build, when the date stamp is created.

One is able to cherry pick back to certain points in one or more repos, thus certain repos might be non current. The process is expected to follow continuous integration and continuous delivery CI/CD principles from both /e/OS and LineageOS, except:

Week 43, Development and Testing Updates

Using the Lineage partitions should work since the source, kernel and blobs are the same as /e/OS is a fork of LOS. Technically, there should not be any issues in flashing the partitions from LOS. The only exception would be if in a particular device there is a big difference on the LOS side or if the dtbo files have been changed. Both cases do not happen in normal circumstances. To explain why we keep shifting the version number of the fix is approximately every 2 weeks we freeze the code and …

For a52q I have no specific knowledge.

[piero]

@luca102

e-1.15-t was build on 2023 Sep 17 by murena

e-1.15-t → android security bulletin from 2023.08.05

Security fixes

This /e/OS v1.15 includes the Android security patches available until August.

.

but e-1.16-t-20231018342574-dev-a52q is out now :

.

e-1.16-t → android security bulletin from 2023.09.05

Security fixes

This /e/OS v1.16 includes the Android security patches available until September.