| Variable | Value |
|---|
Edit count of the user (user_editcount) | 95 |
Name of the user account (user_name) | 'Flow' |
Age of the user account (user_age) | 387252820 |
Page ID (page_id) | 223166 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'ARM64' |
Full page title (page_prefixedtitle) | 'Project:ARM64' |
Action (action) | 'edit' |
Edit summary/reason (summary) | '' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=ARM64 Development
|Description=The ARM64 project is devoted to getting and keeping Gentoo in good shape on the ARM AArch64 architecture.
|Email=arm64@gentoo.org
|Bug assignment=No
|Packages=No
|IRC=#gentoo-arm
|ParentProject=Project:ARM
|PropagatesMembers=Yes
|LeadElectionDate=2020-08-24
|Members={{Project Member
|Developer=User:Leio
|IsLead=No
}}{{Project Member
|Developer=User:NeddySeagoon
|IsLead=No
}}{{Project Member
|Developer=User:Blueness
|Role=Catalyst builds for systemd and musl
|IsLead=No
}}{{Project Member
|Developer=User:Sam
|IsLead=Yes
}}{{Project Member
|Developer=User:Arthurzam
|Role=arm64 keywording/stabilization
|IsLead=No
}}
}}
The ARM64 project works on getting the AArch64 architecture in 64-bit mode into a stable state (stable profiles, stable keywords coverage) and maintain its support long-term.
__TOC__
== Key facts ==
TODO: list our current hardware
* ARM64 is 64-bit.
* ''Some'', but not all, ARM64 CPUs can run 32-bit ARM programs (e.g. chrooting into an armv7a stage3).
* ARM64 is primarily little-endian (we don't really talk about big-endian for arm[64] -- nor does anybody else).
** ... but we do actually have an arm64 big-endian profile at least!
== Keywording ==
{{Note|Users do '''not''' have to test themselves with FEATURES{{=}}test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!}}
{{Tip|We want both stable <code>arm64</code> '''and''' keywording <code>~arm64</code> requests. File them! See [[Stable_request|Stable request]].}}
If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording (see [[Knowledge_Base:Missing_keywords_and_keyword_requests#Fixing_it_for_everybody]]).
=== Going further ===
If possible, it'd be nice (but not required) if you can fully test request and covers all the dependencies - even those that you don't need yourself (from extra USE flags). To test for that, mark it locally and run {{c|pkgcheck scan}} as such (dev-libs/foo-1.2-r3 is what we try to keyword as an example):
{{Cmd
|cd $(portageq get_repo_path / gentoo)
|cd dev-libs/foo
|ekeyword ~arm64 foo-1.2-r3.ebuild
|ebuild foo-1.2-r3.ebuild manifest
|pkgcheck scan --arches arm64
}}
If you notice any arm64 dependency issues, then you should test and keyword those as well. If this ends up with too much, or that isn't too applicable to arm64, then at least state the USE flags that didn't get tested due to extra dependencies, for the purpose of at least knowing to package.use.mask'ing them for now to avoid introducing new keyword issues. Once done, don't forget to clean up your local changes - if this was in a rsync tree, then that will happen automatically on next sync.
If you have a set of packages tested for keywording, we would prefer a list of packages tested together, not separate Bugzilla entries.
Ping our project members on {{IRC|gentoo-arm}} if you need any help!
== Hardware list ==
Feel free to add yourself with your IRC handle to our [[Embedded systems/ARM hardware list|ARM hardware list]] here on the wiki. It contains both 32-bit and AArch64 hardware. It is always nice to know what gadgets are out there!' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=ARM64 Development
|Description=The ARM64 project is devoted to getting and keeping Gentoo in good shape on the ARM AArch64 architecture.
|Email=arm64@gentoo.org
|Bug assignment=No
|Packages=No
|IRC=#gentoo-arm
|ParentProject=Project:ARM
|PropagatesMembers=Yes
|LeadElectionDate=2020-08-24
|Members={{Project Member
|Developer=User:Leio
|IsLead=No
}}{{Project Member
|Developer=User:NeddySeagoon
|IsLead=No
}}{{Project Member
|Developer=User:Blueness
|Role=Catalyst builds for systemd and musl
|IsLead=No
}}{{Project Member
|Developer=User:Sam
|IsLead=Yes
}}{{Project Member
|Developer=User:Arthurzam
|Role=arm64 keywording/stabilization
|IsLead=No
}}{{Project Member
|IsLead=No
}}
}}
The ARM64 project works on getting the AArch64 architecture in 64-bit mode into a stable state (stable profiles, stable keywords coverage) and maintain its support long-term.
__TOC__
== Key facts ==
TODO: list our current hardware
* ARM64 is 64-bit.
* ''Some'', but not all, ARM64 CPUs can run 32-bit ARM programs (e.g. chrooting into an armv7a stage3).
* ARM64 is primarily little-endian (we don't really talk about big-endian for arm[64] -- nor does anybody else).
** ... but we do actually have an arm64 big-endian profile at least!
== Keywording ==
{{Note|Users do '''not''' have to test themselves with FEATURES{{=}}test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!}}
{{Tip|We want both stable <code>arm64</code> '''and''' keywording <code>~arm64</code> requests. File them! See [[Stable_request|Stable request]].}}
If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording (see [[Knowledge_Base:Missing_keywords_and_keyword_requests#Fixing_it_for_everybody]]).
=== Going further ===
If possible, it'd be nice (but not required) if you can fully test request and covers all the dependencies - even those that you don't need yourself (from extra USE flags). To test for that, mark it locally and run {{c|pkgcheck scan}} as such (dev-libs/foo-1.2-r3 is what we try to keyword as an example):
{{Cmd
|cd $(portageq get_repo_path / gentoo)
|cd dev-libs/foo
|ekeyword ~arm64 foo-1.2-r3.ebuild
|ebuild foo-1.2-r3.ebuild manifest
|pkgcheck scan --arches arm64
}}
If you notice any arm64 dependency issues, then you should test and keyword those as well. If this ends up with too much, or that isn't too applicable to arm64, then at least state the USE flags that didn't get tested due to extra dependencies, for the purpose of at least knowing to package.use.mask'ing them for now to avoid introducing new keyword issues. Once done, don't forget to clean up your local changes - if this was in a rsync tree, then that will happen automatically on next sync.
If you have a set of packages tested for keywording, we would prefer a list of packages tested together, not separate Bugzilla entries.
Ping our project members on {{IRC|gentoo-arm}} if you need any help!
== Hardware list ==
Feel free to add yourself with your IRC handle to our [[Embedded systems/ARM hardware list|ARM hardware list]] here on the wiki. It contains both 32-bit and AArch64 hardware. It is always nice to know what gadgets are out there!' |
Unified diff of changes made by edit (edit_diff) | '@@ -25,4 +25,6 @@
|Developer=User:Arthurzam
|Role=arm64 keywording/stabilization
+|IsLead=No
+}}{{Project Member
|IsLead=No
}}
' |
Old page size (old_size) | 3248 |
Lines added in edit (added_lines) | [
0 => '|IsLead=No',
1 => '}}{{Project Member'
] |
Lines removed in edit (removed_lines) | [] |
New page text, stripped of any markup (new_text) | '
ARM64 Development
Description
The ARM64 project is devoted to getting and keeping Gentoo in good shape on the ARM AArch64 architecture.
Project email
arm64@gentoo.org
IRC channel
#gentoo-arm (webchat)
Lead(s)
Sam James
(sam) Last elected: 2020-08-24
Member(s)
Arthur Zamarin
(arthurzam)arm64 keywording/stabilizationAnthony G. Basile
(blueness)Catalyst builds for systemd and muslMart Raudsepp
(leio)Roy Bamford
(NeddySeagoon)
Subproject(s)(and inherited member(s))
(none)
Parent Project
ARM Development
Project listing
The ARM64 project works on getting the AArch64 architecture in 64-bit mode into a stable state (stable profiles, stable keywords coverage) and maintain its support long-term.
Contents
1 Key facts
2 Keywording
2.1 Going further
3 Hardware list
Key facts[edit | edit source]
TODO: list our current hardware
ARM64 is 64-bit.
Some, but not all, ARM64 CPUs can run 32-bit ARM programs (e.g. chrooting into an armv7a stage3).
ARM64 is primarily little-endian (we don't really talk about big-endian for arm[64] -- nor does anybody else).
... but we do actually have an arm64 big-endian profile at least!
Keywording[edit | edit source]
NoteUsers do not have to test themselves with FEATURES=test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!
TipWe want both stable arm64 and keywording ~arm64 requests. File them! See Stable request.
If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording (see Knowledge_Base:Missing_keywords_and_keyword_requests#Fixing_it_for_everybody).
Going further[edit | edit source]
If possible, it'd be nice (but not required) if you can fully test request and covers all the dependencies - even those that you don't need yourself (from extra USE flags). To test for that, mark it locally and run pkgcheck scan as such (dev-libs/foo-1.2-r3 is what we try to keyword as an example):
user $cd $(portageq get_repo_path / gentoo)
user $cd dev-libs/foo
user $ekeyword ~arm64 foo-1.2-r3.ebuild
user $ebuild foo-1.2-r3.ebuild manifest
user $pkgcheck scan --arches arm64
If you notice any arm64 dependency issues, then you should test and keyword those as well. If this ends up with too much, or that isn't too applicable to arm64, then at least state the USE flags that didn't get tested due to extra dependencies, for the purpose of at least knowing to package.use.mask'ing them for now to avoid introducing new keyword issues. Once done, don't forget to clean up your local changes - if this was in a rsync tree, then that will happen automatically on next sync.
If you have a set of packages tested for keywording, we would prefer a list of packages tested together, not separate Bugzilla entries.
Ping our project members on #gentoo-arm (webchat) if you need any help!
Hardware list[edit | edit source]
Feel free to add yourself with your IRC handle to our ARM hardware list here on the wiki. It contains both 32-bit and AArch64 hardware. It is always nice to know what gadgets are out there!' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tbody><tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>ARM64 Development</big>
</th></tr>
<tr valign="top">
<th>Description
</th>
<td style="text-align: justify;">The ARM64 project is devoted to getting and keeping Gentoo in good shape on the ARM AArch64 architecture.
</td></tr>
<tr>
<th><span title="Mails to member(s) listed below.">Project email</span>
</th>
<td><a rel="nofollow" class="external text" href="mailto:arm64@gentoo.org">arm64@gentoo.org</a>
</td></tr>
<tr>
<th><span title="The link opens an IRC client to libera.chat IRC channel.">IRC channel</span>
</th>
<td><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-arm">#gentoo-arm</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-arm">webchat</a></span>)
</td></tr>
<tr valign="top">
<th>Lead(s)
</th>
<td><ul><li><a href="/wiki/User:Sam" title="User:Sam">Sam James</a>
(sam)</li></ul> <br />Last elected: 2020-08-24
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td><ul><li><a href="/wiki/User:Arthurzam" title="User:Arthurzam">Arthur Zamarin</a>
(arthurzam)<br /><i>arm64 keywording/stabilization</i></li><li><a href="/wiki/User:Blueness" title="User:Blueness">Anthony G. Basile</a>
(blueness)<br /><i>Catalyst builds for systemd and musl</i></li><li><a href="/wiki/User:Leio" title="User:Leio">Mart Raudsepp</a>
(leio)</li><li><a href="/wiki/User:NeddySeagoon" title="User:NeddySeagoon">Roy Bamford</a>
(NeddySeagoon)</li></ul>
</td></tr>
<tr valign="top">
<th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td>(none)
</td></tr>
<tr>
<th>Parent Project
</th>
<td><a href="/wiki/Project:ARM" title="Project:ARM">ARM Development</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></tbody></table>
<p>The ARM64 project works on getting the AArch64 architecture in 64-bit mode into a stable state (stable profiles, stable keywords coverage) and maintain its support long-term.
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Key_facts"><span class="tocnumber">1</span> <span class="toctext">Key facts</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Keywording"><span class="tocnumber">2</span> <span class="toctext">Keywording</span></a>
<ul>
<li class="toclevel-2 tocsection-3"><a href="#Going_further"><span class="tocnumber">2.1</span> <span class="toctext">Going further</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-4"><a href="#Hardware_list"><span class="tocnumber">3</span> <span class="toctext">Hardware list</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="Key_facts">Key facts</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM64&veaction=edit&section=1" class="mw-editsection-visualeditor" title="Edit section: Key facts">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:ARM64&action=edit&section=1" title="Edit section: Key facts">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>TODO: list our current hardware
</p>
<ul><li>ARM64 is 64-bit.</li>
<li><i>Some</i>, but not all, ARM64 CPUs can run 32-bit ARM programs (e.g. chrooting into an armv7a stage3).</li>
<li>ARM64 is primarily little-endian (we don't really talk about big-endian for arm[64] -- nor does anybody else).
<ul><li>... but we do actually have an arm64 big-endian profile at least!</li></ul></li></ul>
<h2><span class="mw-headline" id="Keywording">Keywording</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM64&veaction=edit&section=2" class="mw-editsection-visualeditor" title="Edit section: Keywording">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:ARM64&action=edit&section=2" title="Edit section: Keywording">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div class="alert alert-info gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-sticky-note-o fa-rotate-180"></i> Note</strong><br />Users do <b>not</b> have to test themselves with FEATURES=test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!</div>
<div class="alert alert-success gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-check-circle"></i> Tip</strong><br />We want both stable <code>arm64</code> <b>and</b> keywording <code>~arm64</code> requests. File them! See <a href="/wiki/Stable_request" title="Stable request">Stable request</a>.</div>
<p>If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording (see <a href="/wiki/Knowledge_Base:Missing_keywords_and_keyword_requests#Fixing_it_for_everybody" title="Knowledge Base:Missing keywords and keyword requests">Knowledge_Base:Missing_keywords_and_keyword_requests#Fixing_it_for_everybody</a>).
</p>
<h3><span class="mw-headline" id="Going_further">Going further</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM64&veaction=edit&section=3" class="mw-editsection-visualeditor" title="Edit section: Going further">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:ARM64&action=edit&section=3" title="Edit section: Going further">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>If possible, it'd be nice (but not required) if you can fully test request and covers all the dependencies - even those that you don't need yourself (from extra USE flags). To test for that, mark it locally and run <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">pkgcheck scan</span> as such (dev-libs/foo-1.2-r3 is what we try to keyword as an example):
</p>
<div class="cmd-box"><div><code style="color: #4E9A06; font-weight: bold;">user <span style="color:royalblue;">$</span></code><span class="tripleclick-separator"></span><code>cd $(portageq get_repo_path / gentoo)
</code></div><div><code style="color: #4E9A06; font-weight: bold;">user <span style="color:royalblue;">$</span></code><span class="tripleclick-separator"></span><code>cd dev-libs/foo
</code></div><div><code style="color: #4E9A06; font-weight: bold;">user <span style="color:royalblue;">$</span></code><span class="tripleclick-separator"></span><code>ekeyword ~arm64 foo-1.2-r3.ebuild
</code></div><div><code style="color: #4E9A06; font-weight: bold;">user <span style="color:royalblue;">$</span></code><span class="tripleclick-separator"></span><code>ebuild foo-1.2-r3.ebuild manifest
</code></div><div><code style="color: #4E9A06; font-weight: bold;">user <span style="color:royalblue;">$</span></code><span class="tripleclick-separator"></span><code>pkgcheck scan --arches arm64
</code></div></div>
<p>If you notice any arm64 dependency issues, then you should test and keyword those as well. If this ends up with too much, or that isn't too applicable to arm64, then at least state the USE flags that didn't get tested due to extra dependencies, for the purpose of at least knowing to package.use.mask'ing them for now to avoid introducing new keyword issues. Once done, don't forget to clean up your local changes - if this was in a rsync tree, then that will happen automatically on next sync.
</p><p>If you have a set of packages tested for keywording, we would prefer a list of packages tested together, not separate Bugzilla entries.
</p><p>Ping our project members on <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-arm">#gentoo-arm</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-arm">webchat</a></span>) if you need any help!
</p>
<h2><span class="mw-headline" id="Hardware_list">Hardware list</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM64&veaction=edit&section=4" class="mw-editsection-visualeditor" title="Edit section: Hardware list">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:ARM64&action=edit&section=4" title="Edit section: Hardware list">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Feel free to add yourself with your IRC handle to our <a href="/wiki/Embedded_systems/ARM_hardware_list" title="Embedded systems/ARM hardware list">ARM hardware list</a> here on the wiki. It contains both 32-bit and AArch64 hardware. It is always nice to know what gadgets are out there!
</p>
' |
Unix timestamp of change (timestamp) | 1708272855 |
Wiki