[Replicant] vendor_replicant-release-scripts: Add basic support for Replicant 11

Denis 'GNUtoo' Carikli GNUtoo at cyberdimension.org
Fri Oct 8 13:48:56 UTC 2021


Hi,

With theses patches I managed to build Replicant 6.0 and Replicant 11
images.

On top of theses patches several modifications were still needed:
- The RELEASE and RELEASE_KEY variables needed to be set.
  For RELEASE_KEY you can use any GPG key. For RELEAS you need to set
  it to something that starts either with 6.0- or 11- because now take
  into account the major Replicant version.
- For Replicant 6 I needed to remove all the devices with an OMAP SOC
  as with Trisquel 9 they don't build yet, and the devices with exynos
  probably don't manage to boot because of the exact same cause
  (missing libraries).
- For Replicant 11 I followed the official guide[1] to generate the
  signing  keys, and I didn't look if it was relevant or even if the
  images were  signed.

Here's an example of diff:
--- a/releasevars.sh
+++ b/releasevars.sh
@@ -16,7 +16,7 @@
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
 . common.sh
 
-RELEASE=""
+RELEASE="6.0-test1"
 
 if [ -z "${RELEASE}" ] ; then
        echo "You need to define the"\
@@ -34,12 +34,9 @@ if [ -z "${RELEASE}" ] ; then
 fi
 
 RELEASE_DEVICES_REPLICANT_6="\
-       espresso3g \
-       espressowifi \
        i9100 \
        i9300 \
        i9305 \
-       maguro \
        n5100 \
        n5110 \
        n7000 \
@@ -64,7 +61,7 @@ for device in ${RELEASE_DEVICES} ; do
        RELEASE_IMAGES="${RELEASE_IMAGES} replicant-${RELEASE}-${device}"
 done
 
-RELEASE_KEY=""
+RELEASE_KEY="FB31DBA3AB8DB76A4157329F7651568F80374459"
 if [ -z "${RELEASE_KEY}" ] ; then
     echo "You need to"\
         "define the RELEASE_KEY variable in the releasevars.sh script."


In addition to the patches that will follow in a response to
this mail, here's an URL to the see the patches in a web interface:
https://git.replicant.us/contrib/GNUtoo/vendor_replicant-release-scripts/commit/?id=7f79e78b277019dfbcf3cea20705801c6fcf0a80
https://git.replicant.us/contrib/GNUtoo/vendor_replicant-release-scripts/commit/?id=9c1b9dbb886c4999012785ee4276c953eb92d13b
https://git.replicant.us/contrib/GNUtoo/vendor_replicant-release-scripts/commit/?id=10c741bd9ff53e86e6a5035f09af159f7116b6c8
https://git.replicant.us/contrib/GNUtoo/vendor_replicant-release-scripts/commit/?id=b14f958fd463d485a7e455b4ab10c6f7815c5e07
https://git.replicant.us/contrib/GNUtoo/vendor_replicant-release-scripts/commit/?id=006b09e25c688667cd4fd5ebaeeebf06ec349914
https://git.replicant.us/contrib/GNUtoo/vendor_replicant-release-scripts/commit/?id=9176a9ed181fb5dee238fc2bb777895339357bad

And here's how to get them in a git repository:
git clone https://git.replicant.us/GNUtoo/vendor_replicant-release-scripts
cd vendor_replicant-release-scripts
git show 7f79e78b277019dfbcf3cea20705801c6fcf0a80
git show 9c1b9dbb886c4999012785ee4276c953eb92d13b
git show 10c741bd9ff53e86e6a5035f09af159f7116b6c8
git show b14f958fd463d485a7e455b4ab10c6f7815c5e07
git show 006b09e25c688667cd4fd5ebaeeebf06ec349914
git show 9176a9ed181fb5dee238fc2bb777895339357bad

References:
-----------
[1]https://source.android.com/devices/tech/ota/sign_builds

Denis.



More information about the Replicant mailing list