i386
|
Size: 1523
Comment:
|
Size: 1777
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Partial-port == | |
| Line 3: | Line 4: |
| == No boot support == | |
| Line 5: | Line 7: |
| == Self-hosted, natively built == | |
| Line 7: | Line 10: |
| Launchpad has a white-list of packages that build for i386, which are based on a seed. This was scoped through the community process. However, sometimes as part of an ABI transition `src:foo(N+1)` needs to be build on i386 to eventually replace `src:fooN`, for example boost1.71, gcc-11, etc. When such a need arises, one should contact an Archive Admin to: 1. add new source package to newSet in `update-i386-whitelist` script in ubuntu-archive-tools 1. run it to update laucnhpad's whitelist |
== How to transition src:foo1 to src:foo2 == Launchpad has a white-list of packages that build for i386, which are based on a seed. This was scoped through the community process. However, sometimes as part of an ABI transition `src:foo(N+1)` needs to be build on i386 to eventually replace `src:fooN`, for example boost1.71, gcc-11, etc. When such a need arises, one should: 1. ask Archive Admin to add a new versioned abi-source package to newSet in `update-i386-whitelist` script in ubuntu-archive-tools 1. ask Archive Admin to run it to update laucnhpad's whitelist 1. Then one can upload/sync/no-change rebuild 1src:foo(N+1)` and it will be built for i386. |
| Line 11: | Line 16: |
| After that is done, one can upload/sync/no-change `rebuild src:foo(N+1)` and it will be built for i386. | == ProposedMigration requested i386 test result, which does not exist == |
| Line 15: | Line 20: |
| == How to expand i386 port scope == |
Partial-port
i386 is a partial-port of Ubuntu, which is supported as a multi-arch supplementary architecture.
No boot support
There is no kernel, installers, bootloaders for i386, thus it cannot be booted as pure i386.
Self-hosted, natively built
All package building is self-hosting, and is built in a i386 chroot on an amd64 host.
How to transition src:foo1 to src:foo2
Launchpad has a white-list of packages that build for i386, which are based on a seed. This was scoped through the community process. However, sometimes as part of an ABI transition src:foo(N+1) needs to be build on i386 to eventually replace src:fooN, for example boost1.71, gcc-11, etc. When such a need arises, one should:
ask Archive Admin to add a new versioned abi-source package to newSet in update-i386-whitelist script in ubuntu-archive-tools
- ask Archive Admin to run it to update laucnhpad's whitelist
- Then one can upload/sync/no-change rebuild 1src:foo(N+1)` and it will be built for i386.
ProposedMigration requested i386 test result, which does not exist
Sometimes, britney requests test results for i386, despite a source package not building for i386 at all. In such a case please contact Ubuntu Release Team to update the britney hint to badtest the i386 result. These usually clear on subsequent uploads, and thus only happen once per source package.
How to expand i386 port scope
If you genuinely need to increase the scope of the i386 port (i.e. 3rd party app now needs this i386 library), then community process must be used to nominate and get a library added to the i386 seed as the supported target package. Post to https://discourse.ubuntu.com/t/community-process-for-32-bit-compatibility/12598.
i386 (last edited 2024-02-17 14:01:38 by tsimonq2)