Issue #2224
openShip sources tarball along with the images and verify if we can fetch all the releases at the time
Added by Denis 'GNUtoo' Carikli about 3 years ago. Updated about 3 years ago.
0%
Updated by Denis 'GNUtoo' Carikli about 3 years ago
- Subject changed from Ship sources tarball along with the images to Ship sources tarball along with the images and verify if we can fetch all the releases at the time
We probably need to ship the source code along with the binaries as per GPLv2 as:
Because:If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
- We host our releases at OSUOSL
- We host our source code inside our VM
So I'm not sure that both counts as "the same place".
Updated by Denis 'GNUtoo' Carikli about 3 years ago
Status:
| Release | Fetches | Tarball | Uploaded |
| Replicant 6.0 0004 RC4 | Yes | DONE | DONE |
| Replicant 6.0 0004 RC3 | Yes | DONE | DONE |
| Replicant 6.0 0004 RC2 | Yes | DONE | DONE |
| Replicant 6.0 0004 RC1 | Yes | DONE | DONE |
| Replicant 6.0 0003 | Yes | DONE | DONE |
| Replicant 6.0 0002 | Yes | DONE | DONE |
| Replicant 6.0 0001 | Yes | DONE | DONE |
| Replicant 4.2 0004 | With patch1 | DONE | DONE |
| Replicant 4.2 0003 | No2 | Should be removed? | |
| Replicant 4.2 0002 | No2 | Should be removed? | |
| Replicant 4.2 0001 | No2 | Should be removed? | |
| Replicant 4.0 0005 | no tags | ||
| Replicant 4.0 0004 | no tags | ||
| Replicant 4.0 0003 | no tags | ||
| Replicant 4.0 0002 | no tags | ||
| Replicant 4.0 0001 | no tags | ||
| Replicant 2.3 0005 | no tags | ||
| Replicant 2.3 0004 | no tags | ||
| Replicant 2.3 0003 | no tags | ||
| Replicant 2.3 0002 | no tags | ||
| Replicant 2.3 0001 | no tags | ||
| Replicant 2.2 0009 | no tags | ||
| Replicant 2.2 0008 | no tags | ||
| Replicant 2.2 0007 | no tags | ||
| Replicant 2.2 0006 | no tags | ||
| Replicant 2.2 0005 | no tags | ||
| Replicant 2.2 0004 | no tags | ||
| Replicant 2.2 0003 | no tags | ||
| Replicant 2.2 0002 | no tags | ||
| Replicant 2.2 0001 | no tags | ||
1 make_source_tarball.sh: add support for git:// for Replicant <= 4.2-0004
2 During the fetch we have:
CyanogenMod/android_external_svox: remote: Repository unavailable due to DMCA takedown. remote: See the takedown notice for more details: remote: https://github.com/github/dmca/blob/master/2014/2014-12-22-Cambridge-Mobile.md. fatal: Authentication failed for 'https://github.com/CyanogenMod/android_external_svox/'In addition, there is more details in the [Q] Repository unavailable due to DMCA takedown. Doing Repo sync cm11 forum thread, but beside that we have no way of verifying that DMCA claim ourselves. Older versions:
- Replicant 2.3 and 4.0 have the infos necessary to make tarballs in infos/git_versions.txt and in infos/manifest_version.txt
- In Replicant 2.2 they are directly with the images in git_versions.txt and manifest_versions.txt
So we could simply make a script to checkout theses versions.
Then we'd retrospectively tag the tree with the release scripts and then use the same tool to release tarballs.
PS: Note that this post is constantly updated.
Updated by Denis 'GNUtoo' Carikli about 3 years ago
- Type of work Any programming languages (scripts, C, etc), System administration added
- programming for the script that reconstruct Replicant < 6.0 source code
- sysadmin for people needing access to the infrastructure to upload the result
Updated by Denis 'GNUtoo' Carikli about 3 years ago
- Device Not device specific added
- Device deleted (
Unknown)
Updated by Denis 'GNUtoo' Carikli about 3 years ago
- Category changed from Freedom to Legal
Updated by Denis 'GNUtoo' Carikli about 3 years ago
In the Replicant 4.2 0004 Manifest we have the following issue:
<remote name="replicant"
fetch="git://git.replicant.us/" />
We have git redirects in place but they only work for http...