MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Rebuilding_Spins_Packages",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "53460": {
                "pageid": 53460,
                "ns": 0,
                "title": "RebasingLLVM",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Running collection of notes about how to do LLVM rebases in Fedora, and in particular, how to verify them.  This page currently covers F20's 3.3->3.4 rebase; presumably future updates will need more detail as more things grow LLVM dependencies.\n\n= Strategy =\n\nFirst, get test results from the existing version of llvm.  (XXX links to previous rebase results would be useful...)\n\nNext, get it all building.  Once you've got the new version of llvm building, mockchain it, then mockchain the rest of the affected packages into the same root.\n\nOnce you've done that you can <code>rpm -Fvh</code> from the mockchain repo to update your running system to the new version of llvm, and then re-do the tests against the new llvm version to see what broke.\n\n= Testing =\n\n== llvm itself ==\n\nRun the testsuite. It runs out of <code>%check</code>, you probably need to enable it on some of the non-PC arches though.\n\n== dragonegg ==\n\n<code>make check</code> from the built source, in theory, but that doesn't actually work at the moment; <code>llvm-config --src-root</code> points into space, and the bits it would point to aren't packaged anyway.  Hmm.\n\n== eclipse-cdt ==\n\n== gambas3 ==\n\nNo testsuite.  But the IDE is self-hosting.\n\n== gedit-code-assistance ==\n\n== ghc ==\n\nYou don't actually need to rebuild ghc, I don't think.  The llvm backend for ghc calls <code>/usr/bin/llc</code> so as long as it continues to emit valid code...\n\nEdit <code>ghc.spec</code> to do <code>%define cabal_configure_options --ghc-option=-fllvm</code> to force the llvm code generator (XXX: is this enough?). Testsuite is run by doing <code>make test</code> or <code>make fulltest</code> from the top-level source directory; the former ought to pass completely, but on non-arm it probably does have failures since the llvm generator is not the default elsewhere.\n\n== kate-plugin-cpphelper ==\n\n== mesa ==\n\nSomewhat tricky to test, if you're not used to doing piglit runs, but piglit against Xvfb will exercise llvmpipe.  The r600 and radeonsi drivers also use llvm (XXX more detail on which cards here, please) and I think that's true of the corresponding vdpau drivers too (XXX how to test vdpau).\n\n== OpenGTL ==\n\n<code>make check</code>, which is already done for you in <code>%check</code>, so the mockchain build logs already have this.\n\n== pocl ==\n\n<code>make check</code> from the built source.  Works, but there seem to be a lot of skipped tests (TCE, samples, ViennaCL, Rodinia, Parboil, AMD app SDK, VexCL, piglit).  Needs more investigation.\n\n== pure ==\n\n<code>make check</code>, which is already done for you in <code>%check</code>, so the mockchain build logs already have this.\n\n== python-llvmpy ==\n\n<code>make check</code>, which is already done for you in <code>%check</code>, so the mockchain build logs already have this.\n\n== syntastic ==\n\n== xorg-x11-drv-vmware =="
                    }
                ]
            },
            "54951": {
                "pageid": 54951,
                "ns": 0,
                "title": "RebasingXserver",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Historically Fedora has not updated the X server in ABI-incompatible ways within a single release stream.  Starting with F21, we are moving to a model more like the kernel update process, where stable server releases will turn into stack backports to existing Fedora releases.  This has implications for testing and external repositories; this page is an attempt to document the process.\n\n=== Current versions and update schedule ===\n\n* Rawhide: 1.16.2\n* Fedora 21: 1.16.1 (1.16.2 in testing)\n\nRawhide will stay on 1.16.x until F21 is released, and then move to the 1.17.x stream.\n\n=== How to communicate ===\n\n=== How to test ===\n\n=== Per-release trivia ===\n\n==== xserver 1.17 ====\n\nThe {{package|xorg-x11-drv-modesetting}} driver has been folded into the server; the separate driver package should be retired."
                    }
                ]
            }
        }
    }
}