Examine individual changes

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

Variable	Value
Edit count of the user `(user_editcount)`	2879
Name of the user account `(user_name)`	'MGorny'
Age of the user account `(user_age)`	418848227
Page ID `(page_id)`	166582
Page namespace `(page_namespace)`	510
Page title (without namespace) `(page_title)`	'Rust'
Full page title `(page_prefixedtitle)`	'Project:Rust'
Action `(action)`	'edit'
Edit summary/reason `(summary)`	'add myself'
Old content model `(old_content_model)`	'wikitext'
New content model `(new_content_model)`	'wikitext'
Old page wikitext, before the edit `(old_wikitext)`	'{{Project \|Name=Rust Project \|Description=The Rust Project maintains the Rust toolchain and its related packages. \|Email=rust@gentoo.org \|Bug assignment=No \|Packages=Yes \|IRC=#gentoo-rust \|ParentProject=Project:Gentoo \|PropagatesMembers=No \|Members={{Project Member \|Developer=User:GYakovlev \|Role=Self-appointed lead \|IsLead=Yes }}{{Project Member \|Developer=User:Arthurzam \|Role=Bootstraping rust-bin \|IsLead=No }} }} The goal of this project is to provide proper packaging of Rust and Cargo for use within the Gentoo ecosystem. The project also maintains {{Path\|cargo.eclass}} for use in ebuilds. There are two tools for writing ebuilds for Rust software: {{Package\|app-portage/pycargoebuild}} (recommended) and {{Package\|dev-util/cargo-ebuild}}. == Bumping Rust and Cargo == * [[User:GYakovlev/Rust_bump]] === Network-less builds === It is important to ensure that users of network-less builds or network sandboxing are able to build Rust and Cargo so you should test your ebuilds with the following: {{FileBox\|filename=[[:/etc/portage/make.conf]]\|title=Adding network-sandbox to FEATURES in Portage\|lang=bash\|1= FEATURES="network-sandbox" }} === Ensure the binary is up to date === When bumping {{Package\|dev-lang/rust}}, please ensure that {{Package\|dev-lang/rust-bin}} is kept at the same release. This avoids issues with people mixing versions that Portage can't reason around (note: add the bug #). == Cargo based projects == This includes Cargo itself (and soon Rust itself). Always use {{Package\|app-portage/pycargoebuild}} [https://github.com/projg2/pycargoebuild/ (github)] or {{Package\|dev-util/cargo-ebuild}} ([https://github.com/gentoo/cargo-ebuild github]) to gather the proper dependencies that need to appear in your ebuild. More than likely, either of these utilities will generate a proper ebuild for you. If the package in question contains a ''Cargo.lock'' file, the dependencies that the tool creates '''MUST''' not be changed because offline installs will be broken. == <code>rust-dev</code> overlay == The <code>rust-dev</code> overlay is a prototype experiment for building crates as individual crate units. This overlay handles each crate similarly to how non-binary programming languages like Perl, Python and Ruby work, by installing (possibly augmented) copies of the extracted crate archives, constructing a local directory registry source as described in [https://doc.rust-lang.org/cargo/reference/source-replacement.html#directory-sources source replacement in the cargo book], while deferring actual binary compilation to the relevant target leaves, leveraging slot-operator deps for automatic rebuilds. But it's currently a very complicated mountain of work and not quite ready for prime-time. * main repo: https://github.com/kentnl-gentoo-rust/rust-dev-overlay * kentnl's work-in-progress: https://github.com/kentfredric/rust-dev-overlay [[Project:Rust/rust-dev\|More details]]'
New page wikitext, after the edit `(new_wikitext)`	'{{Project \|Name=Rust Project \|Description=The Rust Project maintains the Rust toolchain and its related packages. \|Email=rust@gentoo.org \|Bug assignment=No \|Packages=Yes \|IRC=#gentoo-rust \|ParentProject=Project:Gentoo \|PropagatesMembers=No \|Members={{Project Member \|Developer=User:GYakovlev \|Role=Self-appointed lead \|IsLead=Yes }}{{Project Member \|Developer=User:Arthurzam \|Role=Bootstraping rust-bin \|IsLead=No }}{{Project Member \|Role=Forced to maintain one Rust package too many \|IsLead=No }} }} The goal of this project is to provide proper packaging of Rust and Cargo for use within the Gentoo ecosystem. The project also maintains {{Path\|cargo.eclass}} for use in ebuilds. There are two tools for writing ebuilds for Rust software: {{Package\|app-portage/pycargoebuild}} (recommended) and {{Package\|dev-util/cargo-ebuild}}. == Bumping Rust and Cargo == * [[User:GYakovlev/Rust_bump]] === Network-less builds === It is important to ensure that users of network-less builds or network sandboxing are able to build Rust and Cargo so you should test your ebuilds with the following: {{FileBox\|filename=[[:/etc/portage/make.conf]]\|title=Adding network-sandbox to FEATURES in Portage\|lang=bash\|1= FEATURES="network-sandbox" }} === Ensure the binary is up to date === When bumping {{Package\|dev-lang/rust}}, please ensure that {{Package\|dev-lang/rust-bin}} is kept at the same release. This avoids issues with people mixing versions that Portage can't reason around (note: add the bug #). == Cargo based projects == This includes Cargo itself (and soon Rust itself). Always use {{Package\|app-portage/pycargoebuild}} [https://github.com/projg2/pycargoebuild/ (github)] or {{Package\|dev-util/cargo-ebuild}} ([https://github.com/gentoo/cargo-ebuild github]) to gather the proper dependencies that need to appear in your ebuild. More than likely, either of these utilities will generate a proper ebuild for you. If the package in question contains a ''Cargo.lock'' file, the dependencies that the tool creates '''MUST''' not be changed because offline installs will be broken. == <code>rust-dev</code> overlay == The <code>rust-dev</code> overlay is a prototype experiment for building crates as individual crate units. This overlay handles each crate similarly to how non-binary programming languages like Perl, Python and Ruby work, by installing (possibly augmented) copies of the extracted crate archives, constructing a local directory registry source as described in [https://doc.rust-lang.org/cargo/reference/source-replacement.html#directory-sources source replacement in the cargo book], while deferring actual binary compilation to the relevant target leaves, leveraging slot-operator deps for automatic rebuilds. But it's currently a very complicated mountain of work and not quite ready for prime-time. * main repo: https://github.com/kentnl-gentoo-rust/rust-dev-overlay * kentnl's work-in-progress: https://github.com/kentfredric/rust-dev-overlay [[Project:Rust/rust-dev\|More details]]'
Unified diff of changes made by edit `(edit_diff)`	'@@ -15,4 +15,7 @@ \|Developer=User:Arthurzam \|Role=Bootstraping rust-bin +\|IsLead=No +}}{{Project Member +\|Role=Forced to maintain one Rust package too many \|IsLead=No }} '
Old page size `(old_size)`	2932
Lines added in edit `(added_lines)`	[ 0 => '\|IsLead=No', 1 => '}}{{Project Member', 2 => '\|Role=Forced to maintain one Rust package too many' ]
Lines removed in edit `(removed_lines)`	[]
New page text, stripped of any markup `(new_text)`	' Rust Project Description The Rust Project maintains the Rust toolchain and its related packages. Project email rust@gentoo.org Packages p.g.o/rust@gentoo.org IRC channel #gentoo-rust (webchat) Lead(s) Georgy Yakovlev (gyakovlev)Self-appointed lead No lead election date set Member(s) Arthur Zamarin (arthurzam)Bootstraping rust-bin Subproject(s)(and inherited member(s)) (none) Parent Project Gentoo Project listing The goal of this project is to provide proper packaging of Rust and Cargo for use within the Gentoo ecosystem. The project also maintains cargo.eclass for use in ebuilds. There are two tools for writing ebuilds for Rust software: app-portage/pycargoebuild (recommended) and dev-util/cargo-ebuild. Contents 1 Bumping Rust and Cargo 1.1 Network-less builds 1.2 Ensure the binary is up to date 2 Cargo based projects 3 rust-dev overlay Bumping Rust and Cargo[edit] User:GYakovlev/Rust_bump Network-less builds[edit] It is important to ensure that users of network-less builds or network sandboxing are able to build Rust and Cargo so you should test your ebuilds with the following: FILE /etc/portage/make.confAdding network-sandbox to FEATURES in Portage FEATURES="network-sandbox" Ensure the binary is up to date[edit] When bumping dev-lang/rust, please ensure that dev-lang/rust-bin is kept at the same release. This avoids issues with people mixing versions that Portage can't reason around (note: add the bug #). Cargo based projects[edit] This includes Cargo itself (and soon Rust itself). Always use app-portage/pycargoebuild (github) or dev-util/cargo-ebuild (github) to gather the proper dependencies that need to appear in your ebuild. More than likely, either of these utilities will generate a proper ebuild for you. If the package in question contains a Cargo.lock file, the dependencies that the tool creates MUST not be changed because offline installs will be broken. rust-dev overlay[edit] The rust-dev overlay is a prototype experiment for building crates as individual crate units. This overlay handles each crate similarly to how non-binary programming languages like Perl, Python and Ruby work, by installing (possibly augmented) copies of the extracted crate archives, constructing a local directory registry source as described in source replacement in the cargo book, while deferring actual binary compilation to the relevant target leaves, leveraging slot-operator deps for automatic rebuilds. But it's currently a very complicated mountain of work and not quite ready for prime-time. main repo: https://github.com/kentnl-gentoo-rust/rust-dev-overlay kentnl's work-in-progress: https://github.com/kentfredric/rust-dev-overlay More details'
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>Rust Project</big> </th></tr> <tr valign="top"> <th>Description </th> <td style="text-align: justify;">The Rust Project maintains the Rust toolchain and its related packages. </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:rust@gentoo.org">rust@gentoo.org</a> </td></tr> <tr> <th><span title="Link to packages.g.o for ebuilds maintained in gentoo.git.">Packages</span> </th> <td><span class="fa fa-cubes fa-fw"></span> <a rel="nofollow" class="external text" href="https://packages.gentoo.org/maintainer/rust@gentoo.org">p.g.o/rust@gentoo.org</a> <p><br /> </p><p><br /> </p> </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-rust">#gentoo-rust</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-rust">webchat</a></span>) </td></tr> <tr valign="top"> <th>Lead(s) </th> <td><ul><li><a href="/wiki/User:GYakovlev" title="User:GYakovlev">Georgy Yakovlev</a> (gyakovlev)<br /><i>Self-appointed lead</i></li></ul> <br />No lead election date set </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>Bootstraping rust-bin</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 goal of this project is to provide proper packaging of Rust and Cargo for use within the Gentoo ecosystem. The project also maintains <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">cargo.eclass</span> for use in ebuilds. </p><p>There are two tools for writing ebuilds for Rust software: <span style="white-space: nowrap;" class="plainlinks" title="External link to https://packages.gentoo.org for the app-portage/pycargoebuild package."><a rel="nofollow" class="external text" href="https://packages.gentoo.org/packages/app-portage/pycargoebuild"><span style="font-family: monospace; font-size: 95%; color: MidnightBlue;">app-portage/pycargoebuild</span></a><span style="color: grey; margin-left: 0.1em; font-size: 70%;" class="fa fa-hdd-o fa-fw"></span></span> (recommended) and <span style="white-space: nowrap;" class="plainlinks" title="External link to https://packages.gentoo.org for the dev-util/cargo-ebuild package."><a rel="nofollow" class="external text" href="https://packages.gentoo.org/packages/dev-util/cargo-ebuild"><span style="font-family: monospace; font-size: 95%; color: MidnightBlue;">dev-util/cargo-ebuild</span></a><span style="color: grey; margin-left: 0.1em; font-size: 70%;" class="fa fa-hdd-o fa-fw"></span></span>. </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="#Bumping_Rust_and_Cargo"><span class="tocnumber">1</span> <span class="toctext">Bumping Rust and Cargo</span></a> <ul> <li class="toclevel-2 tocsection-2"><a href="#Network-less_builds"><span class="tocnumber">1.1</span> <span class="toctext">Network-less builds</span></a></li> <li class="toclevel-2 tocsection-3"><a href="#Ensure_the_binary_is_up_to_date"><span class="tocnumber">1.2</span> <span class="toctext">Ensure the binary is up to date</span></a></li> </ul> </li> <li class="toclevel-1 tocsection-4"><a href="#Cargo_based_projects"><span class="tocnumber">2</span> <span class="toctext">Cargo based projects</span></a></li> <li class="toclevel-1 tocsection-5"><a href="#rust-dev_overlay"><span class="tocnumber">3</span> <span class="toctext">rust-dev overlay</span></a></li> </ul> </div> <h2><span class="mw-headline" id="Bumping_Rust_and_Cargo">Bumping Rust and Cargo</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Rust&action=edit&section=1" title="Edit section: Bumping Rust and Cargo">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <ul><li><a href="/wiki/User:GYakovlev/Rust_bump" title="User:GYakovlev/Rust bump">User:GYakovlev/Rust_bump</a></li></ul> <h3><span class="mw-headline" id="Network-less_builds">Network-less builds</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Rust&action=edit&section=2" title="Edit section: Network-less builds">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>It is important to ensure that users of network-less builds or network sandboxing are able to build Rust and Cargo so you should test your ebuilds with the following: </p> <div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #54487A">FILE</span> <strong><code style="border: none; background: none; color: #54487A; margin-right: .5em;"><a href="/wiki//etc/portage/make.conf" title="/etc/portage/make.conf">/etc/portage/make.conf</a></code></strong><strong>Adding network-sandbox to FEATURES in Portage</strong></div> <div class="mw-highlight mw-highlight-lang-bash mw-content-ltr" dir="ltr"><pre><span></span><span class="nv">FEATURES</span><span class="o">=</span><span class="s2">"network-sandbox"</span> </pre></div> <h3><span class="mw-headline" id="Ensure_the_binary_is_up_to_date">Ensure the binary is up to date</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Rust&action=edit&section=3" title="Edit section: Ensure the binary is up to date">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>When bumping <span style="white-space: nowrap;" class="plainlinks" title="External link to https://packages.gentoo.org for the dev-lang/rust package."><a rel="nofollow" class="external text" href="https://packages.gentoo.org/packages/dev-lang/rust"><span style="font-family: monospace; font-size: 95%; color: MidnightBlue;">dev-lang/rust</span></a><span style="color: grey; margin-left: 0.1em; font-size: 70%;" class="fa fa-hdd-o fa-fw"></span></span>, please ensure that <span style="white-space: nowrap;" class="plainlinks" title="External link to https://packages.gentoo.org for the dev-lang/rust-bin package."><a rel="nofollow" class="external text" href="https://packages.gentoo.org/packages/dev-lang/rust-bin"><span style="font-family: monospace; font-size: 95%; color: MidnightBlue;">dev-lang/rust-bin</span></a><span style="color: grey; margin-left: 0.1em; font-size: 70%;" class="fa fa-hdd-o fa-fw"></span></span> is kept at the same release. This avoids issues with people mixing versions that Portage can't reason around (note: add the bug #). </p> <h2><span class="mw-headline" id="Cargo_based_projects">Cargo based projects</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Rust&action=edit&section=4" title="Edit section: Cargo based projects">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>This includes Cargo itself (and soon Rust itself). </p><p>Always use <span style="white-space: nowrap;" class="plainlinks" title="External link to https://packages.gentoo.org for the app-portage/pycargoebuild package."><a rel="nofollow" class="external text" href="https://packages.gentoo.org/packages/app-portage/pycargoebuild"><span style="font-family: monospace; font-size: 95%; color: MidnightBlue;">app-portage/pycargoebuild</span></a><span style="color: grey; margin-left: 0.1em; font-size: 70%;" class="fa fa-hdd-o fa-fw"></span></span> <a rel="nofollow" class="external text" href="https://github.com/projg2/pycargoebuild/">(github)</a> or <span style="white-space: nowrap;" class="plainlinks" title="External link to https://packages.gentoo.org for the dev-util/cargo-ebuild package."><a rel="nofollow" class="external text" href="https://packages.gentoo.org/packages/dev-util/cargo-ebuild"><span style="font-family: monospace; font-size: 95%; color: MidnightBlue;">dev-util/cargo-ebuild</span></a><span style="color: grey; margin-left: 0.1em; font-size: 70%;" class="fa fa-hdd-o fa-fw"></span></span> (<a rel="nofollow" class="external text" href="https://github.com/gentoo/cargo-ebuild">github</a>) to gather the proper dependencies that need to appear in your ebuild. </p><p>More than likely, either of these utilities will generate a proper ebuild for you. If the package in question contains a <i>Cargo.lock</i> file, the dependencies that the tool creates <b>MUST</b> not be changed because offline installs will be broken. </p> <h2><span class="mw-headline" id="rust-dev_overlay"><code>rust-dev</code> overlay</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Rust&action=edit&section=5" title="Edit section: rust-dev overlay">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>The <code>rust-dev</code> overlay is a prototype experiment for building crates as individual crate units. </p><p>This overlay handles each crate similarly to how non-binary programming languages like Perl, Python and Ruby work, by installing (possibly augmented) copies of the extracted crate archives, constructing a local directory registry source as described in <a rel="nofollow" class="external text" href="https://doc.rust-lang.org/cargo/reference/source-replacement.html#directory-sources">source replacement in the cargo book</a>, while deferring actual binary compilation to the relevant target leaves, leveraging slot-operator deps for automatic rebuilds. </p><p>But it's currently a very complicated mountain of work and not quite ready for prime-time. </p> <ul><li>main repo: <a rel="nofollow" class="external free" href="https://github.com/kentnl-gentoo-rust/rust-dev-overlay">https://github.com/kentnl-gentoo-rust/rust-dev-overlay</a></li> <li>kentnl's work-in-progress: <a rel="nofollow" class="external free" href="https://github.com/kentfredric/rust-dev-overlay">https://github.com/kentfredric/rust-dev-overlay</a></li></ul> <p><a href="/wiki/Project:Rust/rust-dev" title="Project:Rust/rust-dev">More details</a> </p> '
Unix timestamp of change `(timestamp)`	1737120634