Another suggestion.
In
https://redmine.replicant.us/projects/replicant/wiki/ReleaseKey#From-a-key-server-recommended
(I do not have the rights on this page):
change "keys.gnupg.net" by "keys.openpgp.org" as noticed in
https://redmine.replicant.us/boards/15/topics/15110?r=15689#message-15689 2
years ago.
The explanation seems to be SKS server is deprecated
(https://central.sonatype.org/publish/requirements/gpg/#distributing-your-public-key).
You'll find others pages where this server should be fixed in
https://redmine.replicant.us/issues/1719
- Fil Lupin.
------- Original Message -------
On Tuesday, April 18th, 2023 at 2:22 PM, Fil Lupin <fillu...@protonmail.com>
wrote:
> Hi,
> for the links to generic/device installation pages, I reply to myself since I
> noticed that main page
> (https://redmine.replicant.us/projects/replicant/wiki#Replicant-installation-and-update)
> links to generic installation page
> (https://redmine.replicant.us/projects/replicant/wiki/Installation) so I
> understand the links to device installation page should be replaced.
> Do you confirm?
>
> My other questions are still open, I would be glad to get some information or
> answers:)
>
> - Fil Lupin.
>
> ------- Original Message -------
> On Monday, April 17th, 2023 at 8:58 PM, Fil Lupin via Replicant
> <replicant@osuosl.org> wrote:
>
>> I continue giving a try with generated .img and .zip without using signature
>> script.
>> I reboot in download mode and I downloaded recovery.img on the device, the
>> device then reboot on recovery.
>>
>> I noticed that
>> https://redmine.replicant.us/projects/replicant/wiki/GalaxySIIIGTI9300#Replicant-installation
>> section only explains how to make a minor update and not how to install
>> replicant 6.
>> I think there is a missing link to
>> https://redmine.replicant.us/projects/replicant/wiki/Installation on this
>> page, but I would prefer to avoid introducing an error, do you confirm my
>> guess?
>>
>> If we follow the link given in
>> https://redmine.replicant.us/projects/replicant/wiki/GalaxySIIIGTI9300#Replicant-build,
>> we got the page
>> https://redmine.replicant.us/projects/replicant/wiki/GalaxyS3I9300Build
>> which does not explain the signification of the files found in
>> dist/out/[DEVICE] like
>> ```
>> -rw-r--r-- 1 debian debian 6660096 Jan 1 2009 recovery-i9300.img
>> -rw-r--r-- 1 debian debian 277338623 Apr 13 19:40
>> replicant-6.0-0004-i9300.zip
>> -rw-r--r-- 1 debian debian 10889124 Apr 13 19:40
>> signed-img-i9300.zip-rw-r--r-- 1 debian debian 564128147 Apr 13 19:38
>> signed-target_files-i9300.zip
>> ```
>>
>> A search shows that those files are cited into
>> https://redmine.replicant.us/projects/replicant/wiki/GenericReplicant60Build
>> (but their use is not detailed) so I understand:
>>
>> - this generic page is planned to replace all device pages
>> - the file details should be given in this new generic page
>>
>> Do you confirm this guess? Does anyone is able to explain me
>>
>> - Fil Lupin.
>>
>> ------- Forwarded Message -------
>> From: Fil Lupin via Replicant <replicant@osuosl.org>
>> Date: On Sunday, April 16th, 2023 at 7:55 AM
>> Subject: Re: [Replicant] key signing for app
>> To: Replicant <replicant@osuosl.org>
>>
>>> Hello,
>>> does anyone knows what is the page to follow to build replicant 6 with app
>>> signature?
>>> If the doc is not up-to-date, could you tell me how to to this?
>>>
>>> Regards
>>>
>>> - Fil Lupin.
>>>
>>> ------- Original Message -------
>>> On Thursday, April 13th, 2023 at 9:17 PM, Fil Lupin via Replicant
>>> <replicant@osuosl.org> wrote:
>>>
>>>> Hi,
>>>> trying to build replicant-6 image,
>>>> I read
>>>>
>>>> -
>>>> https://redmine.replicant.us/projects/replicant/wiki/AndroidSystemKeyMigration
>>>> (I see that some keys are stored somewhere and need to be updated if one
>>>> want to build replicant-6)
>>>>
>>>> -
>>>> https://redmine.replicant.us/projects/replicant/wiki/Replicant60BuildTips#Signing-keys
>>>> (those keys seems to be stored into vendor/replicant-security)
>>>>
>>>> -
>>>> https://git.replicant.us/replicant/vendor_replicant-scripts/tree/images/gen_key_migration_script/README
>>>>
>>>> -
>>>> https://redmine.replicant.us/projects/replicant/wiki/GenericReplicant60Build
>>>>
>>>> However, following last instructions, it seems
>>>> `./vendor/replicant/build.sh i9300` signs apk with the generated key, but
>>>> since this file has been modified 9/9/2020, I understand the files
>>>> generated bu this script are not usable and need to install
>>>> replicant6-0004 and need to run
>>>> https://git.replicant.us/replicant/vendor_replicant-scripts/tree/images/gen_key_migration_script/README
>>>> instructions.
>>>> However, I probably missed some information in this file: it seemed to me
>>>> `./gen_key_migration_script.py gen-script \
>>>>
>>>> vendor/replicant/prebuilt/common/bin/key-migration.sh \
>>>> vendor/replicant-data/distros/releases/certificates/ \
>>>> vendor/replicant-security/
>>>>
>>>> `
>>>>
>>>> need to be updated for path like this:
>>>> `./gen_key_migration_script.py gen-script \
>>>>
>>>> ../../../../
>>>>
>>>> vendor/replicant/prebuilt/common/bin/key-migration.sh \
>>>>
>>>> ../../../../
>>>>
>>>> vendor/replicant-data/distros/releases/certificates/ \
>>>>
>>>> ../../../../
>>>>
>>>> vendor/replicant-security/
>>>>
>>>> `
>>>>
>>>> In addition, it seemed some additionnal fixes were needed :
>>>>
>>>> - chmod u+x
>>>> ../../../../vendor/replicant/prebuilt/common/bin/key-migration.sh
>>>>
>>>> - the sashbang `!/system/bin/sh` in
>>>> ../../../../vendor/replicant/prebuilt/common/bin/key-migration.sh does not
>>>> work (/bin/sh should work)
>>>>
>>>> But I then got following output (si I probably made missed something):
>>>> ---
>>>> ./gen_key_migration_script.py gen-script ./gen_key_migration_script.py
>>>> gen-script \
>>>>>
>>>> Traceback (most recent call last):
>>>> File "./gen_key_migration_script.py", line 20, in <module>
>>>> import sh
>>>> ImportError: No module named 'sh'
>>>> debian@replicant:~/replicant/replicant-6.0/vendor/replicant-scripts/images/gen_key_migration_script$
>>>> ../../../../vendor/replicant/prebuilt/common/bin/key-migration.sh \
>>>>> ../../../../vendor/replicant-data/distros/releases/certificates/ \
>>>>> ../../../../vendor/replicant-security/
>>>> Cannot migrate keys due to missing /data/system/packages.xml:
>>>> - If /data is not mounted, you might need to mount it
>>>> - If /data is already mounted, maybe the data partition is blank. In this
>>>> case you can skip running this script.
>>>>
>>>> ---
>>>> Someone to help me please?
>>>>
>>>> - Fil Lupin.
_______________________________________________
Replicant mailing list
Replicant@osuosl.org
https://lists.osuosl.org/mailman/listinfo/replicant
