Examine individual changes

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search

This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.

Variables generated for this change

VariableValue
Edit count of the user (user_editcount)
61
Name of the user account (user_name)
'Bman'
Age of the user account (user_age)
185741906
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 |IRC=#gentoo-arm |ParentProject=Project:Gentoo |PropagatesMembers=No |LeadElectionDate=2020/08/24 |Members={{Project Member |Developer=User:Leio |IsLead=No }}{{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 }}{{Project Member |Developer=User:Sam |Role=Anything/everything |IsLead=Yes }}{{Project Member |Developer=User:Sultan |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__ == 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=2020/08/24 |Members={{Project Member |Developer=User:Leio |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 }}{{Project Member |Developer=User:Sam |Role=Anything/everything |IsLead=Yes }}{{Project Member |Developer=User:Sultan |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__ == 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)
'@@ -9,8 +9,4 @@ |Members={{Project Member |Developer=User:Leio -|IsLead=No -}}{{Project Member -|Developer=User:Bman -|Role=Lead Minion |IsLead=No }}{{Project Member '
Old page size (old_size)
2642
Lines added in edit (added_lines)
[]
Lines removed in edit (removed_lines)
[ 0 => '|IsLead=No', 1 => '}}{{Project Member', 2 => '|Developer=User:Bman', 3 => '|Role=Lead Minion' ]
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) Sam James (sam)Anything/everything Last elected: 2020/08/24 Member(s) Anthony G. Basile (blueness)catalyst builds for systemd and muslAaron Bauman (bman)Lead MinionKent Fredric (kentnl)MinionMart Raudsepp (leio)Roy Bamford (NeddySeagoon)MinionStephan Hartmann (sultan)Minor MinionMikle Kolyada (Zlogene)Minor 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 Keywording 2 Hardware list Keywording[edit | edit source] 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 | 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 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:Sam" title="User:Sam">Sam James</a> (sam)<br /><i>Anything/everything</i></li></ul> <br />Last elected: 2020/08/24 </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:Leio" title="User:Leio">Mart Raudsepp</a> (leio)</li><li><a href="/wiki/User:NeddySeagoon" title="User:NeddySeagoon">Roy Bamford</a> (NeddySeagoon)<br /><i>Minion</i></li><li><a href="/wiki/User:Sultan" title="User:Sultan">Stephan Hartmann</a> (sultan)<br /><i>Minor Minion</i></li><li><a href="/wiki/User:Zlogene" title="User:Zlogene">Mikle Kolyada</a> (Zlogene)<br /><i>Minor 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" 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="#Keywording"><span class="tocnumber">1</span> <span class="toctext">Keywording</span></a></li> <li class="toclevel-1 tocsection-2"><a href="#Hardware_list"><span class="tocnumber">2</span> <span class="toctext">Hardware list</span></a></li> </ul> </div> <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;veaction=edit&amp;section=1" class="mw-editsection-visualeditor" title="Edit section: Keywording">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:ARM64&amp;action=edit&amp;section=1" title="Edit section: Keywording">edit source</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;veaction=edit&amp;section=2" class="mw-editsection-visualeditor" title="Edit section: Hardware list">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:ARM64&amp;action=edit&amp;section=2" 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)
1610566024