Abuse filter log

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search
Details for log entry 2,564

12:57, 25 February 2020: Zlogene (talk | contribs) triggered filter 13, performing the action "edit" on Project:ARM64. Actions taken: Tag; Filter description: New Project Member (examine)

Changes made in edit

 
|Developer=User:Blueness
 
|Developer=User:Blueness
 
|Role=catalyst builds for systemd and musl
 
|Role=catalyst builds for systemd and musl
 +
|IsLead=No
 +
}}{{Project Member
 +
|Developer=User:Zlogene
 +
|Role=Minor Minion
 
|IsLead=No
 
|IsLead=No
 
}}
 
}}

Action parameters

VariableValue
Whether or not the edit is marked as minor (no longer in use) (minor_edit)
false
Edit count of the user (user_editcount)
163
Name of the user account (user_name)
'Zlogene'
Age of the user account (user_age)
237138938
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)
'add myself as requested by leio'
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 |IRC=#gentoo-arm |ParentProject=Project:Gentoo |PropagatesMembers=No |LeadElectionDate=2019/04/17 |Members={{Project Member |Developer=User:Leio |IsLead=Yes }}{{Project Member |Developer=User:Bman |Role=Lead Minion |IsLead=No }}{{Project Member |Developer=User:Kentnl |Role=Minion |IsLead=No }}{{Project Member |Developer=User:NeddySeagoon |Role=Minion |IsLead=No }}{{Project Member |Developer=User:Blueness |Role=catalyst builds for systemd and musl |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__ == Profiles == Currently no ARM64 profiles are stable, thus it is currently our responsibility to notice where arm64 keywords were dropped or a stable request that didn't include us, while we had an earlier version marked stable. We would kindly ask package maintainers to CC arm64@ on stable and keyword request bugs when appropriate, despite us currently being in the "Unstable arches" list. Our goal is to fix the existing dependency tree and stabilize a set of profiles and become a first class architecture for Gentoo. == Keywording == If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording. At this moment we would prefer if these keyword additions are already fully tested by you 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 repoman 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 |repoman -d full --include-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. For now, pinging the project members on {{IRC|gentoo-arm}} might work better than Bugzilla requests. == 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 |IRC=#gentoo-arm |ParentProject=Project:Gentoo |PropagatesMembers=No |LeadElectionDate=2019/04/17 |Members={{Project Member |Developer=User:Leio |IsLead=Yes }}{{Project Member |Developer=User:Bman |Role=Lead Minion |IsLead=No }}{{Project Member |Developer=User:Kentnl |Role=Minion |IsLead=No }}{{Project Member |Developer=User:NeddySeagoon |Role=Minion |IsLead=No }}{{Project Member |Developer=User:Blueness |Role=catalyst builds for systemd and musl |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=Minor Minion |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__ == Profiles == Currently no ARM64 profiles are stable, thus it is currently our responsibility to notice where arm64 keywords were dropped or a stable request that didn't include us, while we had an earlier version marked stable. We would kindly ask package maintainers to CC arm64@ on stable and keyword request bugs when appropriate, despite us currently being in the "Unstable arches" list. Our goal is to fix the existing dependency tree and stabilize a set of profiles and become a first class architecture for Gentoo. == Keywording == If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording. At this moment we would prefer if these keyword additions are already fully tested by you 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 repoman 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 |repoman -d full --include-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. For now, pinging the project members on {{IRC|gentoo-arm}} might work better than Bugzilla requests. == 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,8 @@ |Developer=User:Blueness |Role=catalyst builds for systemd and musl +|IsLead=No +}}{{Project Member +|Developer=User:Zlogene +|Role=Minor Minion |IsLead=No }} '
Old page size (old_size)
2947
Lines added in edit (added_lines)
[ 0 => '|IsLead=No', 1 => '}}{{Project Member', 2 => '|Developer=User:Zlogene', 3 => '|Role=Minor Minion' ]
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 Lead(s) Mart Raudsepp (leio) Last elected: 2019/04/17 Member(s) Anthony G. Basile (blueness)catalyst builds for systemd and muslAaron Bauman (bman)Lead MinionKent Fredric (kentnl)MinionRoy Bamford (NeddySeagoon)Minion Subproject(s)(and inherited member(s)) (none) Parent Project Gentoo 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 Profiles 2 Keywording 3 Hardware list Profiles[edit] Currently no ARM64 profiles are stable, thus it is currently our responsibility to notice where arm64 keywords were dropped or a stable request that didn't include us, while we had an earlier version marked stable. We would kindly ask package maintainers to CC arm64@ on stable and keyword request bugs when appropriate, despite us currently being in the "Unstable arches" list. Our goal is to fix the existing dependency tree and stabilize a set of profiles and become a first class architecture for Gentoo. Keywording[edit] If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording. At this moment we would prefer if these keyword additions are already fully tested by you 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 repoman 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 $repoman -d full --include-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. For now, pinging the project members on #gentoo-arm might work better than Bugzilla requests. Hardware list[edit] 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 a webchat to this project&#39;s Freenode IRC channel.">IRC channel</span> </th> <td><a rel="nofollow" class="external text" href="https://webchat.freenode.net/?channels=gentoo-arm">#gentoo-arm</a> </td></tr> <tr valign="top"> <th>Lead(s) </th> <td><ul><li><a href="/wiki/User:Leio" title="User:Leio">Mart Raudsepp</a> (leio)</li></ul> <br />Last elected: 2019/04/17 </td></tr> <tr valign="top"> <th>Member(s) </th> <td><ul><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:Bman" title="User:Bman">Aaron Bauman</a> (bman)<br /><i>Lead Minion</i></li><li><a href="/wiki/User:Kentnl" title="User:Kentnl">Kent Fredric</a> (kentnl)<br /><i>Minion</i></li><li><a href="/wiki/User:NeddySeagoon" title="User:NeddySeagoon">Roy Bamford</a> (NeddySeagoon)<br /><i>Minion</i></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:Gentoo" title="Project:Gentoo">Gentoo</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"><div class="toctitle" lang="en" dir="ltr"><h2>Contents</h2></div> <ul> <li class="toclevel-1 tocsection-1"><a href="#Profiles"><span class="tocnumber">1</span> <span class="toctext">Profiles</span></a></li> <li class="toclevel-1 tocsection-2"><a href="#Keywording"><span class="tocnumber">2</span> <span class="toctext">Keywording</span></a></li> <li class="toclevel-1 tocsection-3"><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="Profiles">Profiles</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM64&amp;action=edit&amp;section=1" title="Edit section: Profiles">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>Currently no ARM64 profiles are stable, thus it is currently our responsibility to notice where arm64 keywords were dropped or a stable request that didn't include us, while we had an earlier version marked stable. We would kindly ask package maintainers to CC arm64@ on stable and keyword request bugs when appropriate, despite us currently being in the "Unstable arches" list. Our goal is to fix the existing dependency tree and stabilize a set of profiles and become a first class architecture for Gentoo. </p> <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&amp;action=edit&amp;section=2" title="Edit section: Keywording">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording. At this moment we would prefer if these keyword additions are already fully tested by you 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 repoman 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 $</code><span class="tripleclick-separator"></span><code>cd $(portageq get_repo_path / gentoo) </code></div><div><code style="color: #4E9A06; font-weight: bold;">user $</code><span class="tripleclick-separator"></span><code>cd dev-libs/foo </code></div><div><code style="color: #4E9A06; font-weight: bold;">user $</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 $</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 $</code><span class="tripleclick-separator"></span><code>repoman -d full --include-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. If you have a set of packages tested for keywording, we would prefer a list of packages tested together, not separate Bugzilla entries. For now, pinging the project members on <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="irc://irc.gentoo.org/gentoo-arm">#gentoo-arm</a></span> might work better than Bugzilla requests. </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&amp;action=edit&amp;section=3" title="Edit section: Hardware list">edit</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> <!-- NewPP limit report Cached time: 20200225125756 Cache expiry: 86400 Dynamic content: false [SMW] In‐text annotation parser time: 0.006 seconds CPU time usage: 0.104 seconds Real time usage: 0.131 seconds Preprocessor visited node count: 540/1000000 Preprocessor generated node count: 2483/1000000 Post‐expand include size: 8740/2097152 bytes Template argument size: 1612/2097152 bytes Highest expansion depth: 10/40 Expensive parser function count: 0/100 Unstrip recursion depth: 0/20 Unstrip post‐expand size: 0/5000000 bytes --> <!-- Transclusion expansion time report (%,ms,calls,template) 100.00% 104.961 1 -total 91.61% 96.158 1 Template:Project 37.52% 39.378 5 Template:ProjectMemberLine 16.04% 16.841 5 Template:ProjectMemberLineNickname 11.96% 12.557 6 Template:Project_Member 7.22% 7.575 1 Template:Cmd 5.76% 6.049 1 Template:GenericCmd 2.62% 2.748 5 Template:GenericCmd/Line 0.87% 0.910 1 Template:IRC --> </div>'
Unix timestamp of change (timestamp)
1582635476