manifest, branch replicant-6.0-0004-rc6

Override external/proguard

2021-08-26T01:34:19+00:00

Some binaries jar files were found in external/proguard and it
seems we can build Replicant 6.0 on Trisquel 9 (etiona) without
them.

Signed-off-by: Denis 'GNUtoo' Carikli

Override art

2021-08-26T01:33:45+00:00

When building Replicant 6.0 on Trisquel 9, the host version of
libbacktrace failed to compile due to headers incompatibility
between Replicant 6 and Trisquel 9.

So instead of trying to fix we we simply disabled building
libbacktrace in art.

Signed-off-by: Denis 'GNUtoo' Carikli

Override external/libcxx to fix the build on Trisquel 9

2021-08-26T01:33:31+00:00

This is to add a small patch to external/libcxx to fix building
Replicant 6.0 on Trisquel 9.

Signed-off-by: Denis 'GNUtoo' Carikli

Add the wipe utility

2021-03-08T15:38:29+00:00

Wipe comes from wipe 2.3.1 from http://wipe.sourceforge.net/.

As there doesn't seem to be any git repository, the tarball
was imported in git the subsequent commit added support for
Android.

Wipe is strongly needed as without it it's not very convenient
to securely delete files from the internal storage.

Without wipe, one would have to port GNU/Linux to the device
if it's not already done, or reuse the Replicant 11 kernel
otherwise, and run a distribution like Parabola to securely
erase files.

Signed-off-by: Denis 'GNUtoo' Carikli

F-Droid-mirror: Rename to mirrors/F-Droid

2021-01-09T22:44:26+00:00

To release a Replicant 6 version, we need to tag all the
repositories.

For some time, the LineageOS mirrors have been moved in
mirrors/LineageOS. We have redirections in place to continue
being able to fetch old revisions of Replicant.

We have HTTP and HTTPS redirection (it's done with Apache),
but no redirection for git:// or ssh.

Because of that, when we removed the symlinks to make the
setup more robust, git:// or ssh weren't redirected anymore.

This removal doesn't affect the ability to fetch old revisions
as people are expected to use HTTP or HTTPS to fetch the full
Replicant source code.

However it broke the release process: The releasetag.sh script
(which is in the vendor_replicant-release-scripts repository)
was using the git remote URL to reconstruct the URI to which to
push the tag to.

To fix that the best way is update the manifest to make sure
that the address to which to push correspond to the one that
is used to download the repositories.

Signed-off-by: Denis 'GNUtoo' Carikli

AOSP-mirror: Rename to mirrors/AOSP

2021-01-09T22:44:25+00:00

To release a Replicant 6 version, we need to tag all the
repositories.

For some time, the LineageOS mirrors have been moved in
mirrors/LineageOS. We have redirections in place to continue
being able to fetch old revisions of Replicant.

We have HTTP and HTTPS redirection (it's done with Apache),
but no redirection for git:// or ssh.

Because of that, when we removed the symlinks to make the
setup more robust, git:// or ssh weren't redirected anymore.

This removal doesn't affect the ability to fetch old revisions
as people are expected to use HTTP or HTTPS to fetch the full
Replicant source code.

However it broke the release process: The releasetag.sh script
(which is in the vendor_replicant-release-scripts repository)
was using the git remote URL to reconstruct the URI to which to
push the tag to.

To fix that the best way is update the manifest to make sure
that the address to which to push correspond to the one that
is used to download the repositories.

Signed-off-by: Denis 'GNUtoo' Carikli

LineageOS-mirror: Rename to mirrors/LineageOS

2021-01-09T22:44:21+00:00

To release a Replicant 6 version, we need to tag all the
repositories.

For some time, the LineageOS mirrors have been moved in
mirrors/LineageOS. We have redirections in place to continue
being able to fetch old revisions of Replicant.

We have HTTP and HTTPS redirection (it's done with Apache),
but no redirection for git:// or ssh.

Because of that, when we removed the symlinks to make the
setup more robust, git:// or ssh weren't redirected anymore.

This removal doesn't affect the ability to fetch old revisions
as people are expected to use HTTP or HTTPS to fetch the full
Replicant source code.

However it broke the release process: The releasetag.sh script
(which is in the vendor_replicant-release-scripts repository)
was using the git remote URL to reconstruct the URI to which to
push the tag to.

To fix that the best way is update the manifest to make sure
that the address to which to push correspond to the one that
is used to download the repositories.

Signed-off-by: Denis 'GNUtoo' Carikli

Override packages/apps/Messaging to remove ambientsdk

2020-12-03T16:09:30+00:00

The patch serie by belgin to remove the nonfree ambientsdk
also came with instructions to tag this repository to revert
Replicant 6.0 to the revision just before the inclusion of
the ambient SDK.

Signed-off-by: Denis 'GNUtoo' Carikli

Override packages/apps/Contacts to remove ambientsdk

2020-12-01T01:43:55+00:00

The patch serie by belgin to remove the nonfree ambientsdk
also came with instructions to tag this repository to revert
Replicant 6.0 to the revision just before the inclusion of
the ambient SDK.

Signed-off-by: Denis 'GNUtoo' Carikli

Override packages/apps/ContactsCommon to remove ambientsdk

2020-12-01T01:11:59+00:00

The patch serie by belgin to remove the nonfree ambientsdk
also came with instructions to tag this repository to revert
Replicant 6.0 to the revision just before the inclusion of
the ambient SDK.

Signed-off-by: Denis 'GNUtoo' Carikli