MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Whiteboard-validation",
        "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": {
            "63": {
                "pageid": 63,
                "ns": 0,
                "title": "Server Administration",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{Fink_Header}}\n\n== Backups ==\n\nBackups are being done with Bacula.  It deserves [[Admin:Backups|its own page]].\n\n== DNS ==\n\nWe are running the default bind9 installation from debian.  Domains are each in a separate file in <code>/etc/bind/</code> named after the top-level domain (finkmirrors.net, finkdeveloper.net, etc.) and are editable by anyone in the <code>bind</code> group (or root).\n\nTo add a finkmirrors.net record, do the following:\n\n# edit /etc/bind/finkmirrors.net\n# change the Serial to today's date\n# add a distfiles.AIRPORT.STATE.CONTINENT record in the \"distfiles (source tarballs) mirrors\" section\n# add a AIRPORT.STATE.CONTINENT record in the \"bindist (.deb package) mirrors\" section\n# save the file\n# restart bind: <code>/etc/init.d/bind9 restart</code>\n\n== Mail ==\n\nWe run a mail server.  It really really needs to be documented.  (In particular, we are running squirrelmail, websieve, and god knows what else.)\n\nIn particular, the following URL's are useful:\n\n<https://www.finkdeveloper.net/squirrelmail/src/login.php>\n\n<https://www.finkdeveloper.net/cgi-bin/websieve.pl>\n\nAuthorized persons can restart the mail server with <code> sudo /etc/init.d/cyrus2.2 restart</code>\n\n== Creating New Users ==\n\n# add the user to LDAP\n#* details go here\n# create their SVN experimental directory\n#* <code>svnadmin create --fs-type fsfs /var/lib/svn/users/'''username'''</code>\n#* <code>chown -R www-data:www-data /var/lib/svn/users/'''username'''</code>\n# create their .users.finkproject.org web site\n#* add to /etc/bind/finkproject.org\n#** <code>2006XXXXXX ; serial</code>\n#** <code>'''username'''.users IN CNAME finch</code>\n#** <code>/etc/init.d/bind restart</code>\n#* add to apache2 config\n#** <code>sed -e 's,@USER@,'''username''',g &lt; /etc/apache2/users/user.template &gt; /etc/apache2/users/'''username'''.user</code>\n#** <code>/etc/init.d/apache2 restart</code>\n\n{{Fink_Header}}\n\n[[Category: Fink|FinkProject]]\n[[Category: Fink Structure|FinkProject]]"
                    }
                ]
            },
            "58": {
                "pageid": 58,
                "ns": 0,
                "title": "Setting MAKEFLAGS in Fink",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{Fink_Header}}\n\n== Building with multiple processors ==\n\nRecent Apple computers come with multiple CPU cores which can greatly decrease the time it takes to build a package from source.  Activating this ability in Fink can make managing large builds (think those that can last several hours) manageable.\n\n=== For end users ===\n\nStarting with fink-0.31.2, the fink tool now builds using multiple processors by default.  Running <code>fink configure</code> will ask for the number of processors that fink can use during a build.  No further actions are needed by end users.\n\n==== Troubleshooting ====\n\nIf you run into a package that fails to build and suspect the failure is due to a multiprocessor build failure, run <code>fink configure</code> and set the number of available processors to 1 and try the build again.  If it then succeeds, let the package maintainer know so that they can fix their package.  You can restore the setting again by running <code>fink configure</code> once more.\n\n=== For package maintainers ===\n\nThe number of processors (N) available to Fink will get set in the field <code>MaxBuildJobs</code> in <code>/sw/etc/fink.conf</code>.  The value N is then appended to the variable MAKEFLAGS (as -jN) during CompileScript and TestScript.  It is '''not''' appended during InstallScript.\n\nThe <code>fink.conf</code> setting can be overriden using the boolean field <code>UseMaxBuildJobs</code> in a .info file.  When absent, empty, or set to 'true', fink will use as many processors as <code>fink.conf</code> declares.  When set to 'false', <code>-j1</code> will be added.  For more information on the use of the <code>UseMaxBuildJobs</code> field, check the [http://www.finkproject.org/doc/packaging/reference.php Packaging Reference].\n\n==== Troubleshooting ====\n\nBuild failures can occur in some packages where the source is not able to deal with multithreaded compiling.  This is often, but not always, manifested by an error about some file not being found.  If your package fails this way, setting <code>MaxBuildJobs: false</code> is the quickest way to diagnose the problem. It should no longer be necessary to set MAKEFLAGS to enable or disable building with multiple processors (other normal uses of MAKEFLAGS are, of course, acceptable).\n\n== Passing Other Values to MAKEFLAGS ==\n\n=== Dire Warnings ===\n\nThis section is not officially supported by Fink.  If you run into any problems, make sure you '''first''' disable it before reporting any errors to maintainers or the mailing lists.  Failure to do so will cause you to be shaved, covered in honey, and set upon by fire ants!  Well, OK, perhaps that's a bit harsh.  But really.  Messing with system wide settings can make funny things happen.  If it breaks in half, the only guarantee is that you get to keep both halves.\n\nThe examples below were originally created for parallel builds (see previous section), but can in theory can be amended for passing other values to MAKEFLAGS.  The same caveats, disclaimers, etc. apply.\n\n=== Getting Started ===\n\nThat said, it is technically possible to make use of distcc (or just multiple CPUs) when building packages from source in Fink, as long as the package(s) you're building support the MAKEFLAGS variable (anything that uses make, and possibly other things as well).\n\nTo do so, edit <code>/sw/lib/perl5/Fink/PkgVersion.pm</code> and look for the comment that says '''''\"# uncomment this to be able to use distcc -- not officially supported!\"'''''  Uncomment the <code>$defaults{'MAKEFLAGS'}</code> line, and fink should no longer erase MAKEFLAGS from the build environment.  Note that every time the <code>fink</code> package gets updated, you will have to do this again.  You'll deal with it, I know you can.  That's what you get for living on the bleeding edge.  ;)\n\nNow, you'll have to make sure that MAKEFLAGS is actually *in* the environment.  To do so, install the <code>distcc-default</code> package (you'll need the latest unstable version), and then edit the MAKEFLAGS= line in <code>/sw/etc/distcc.conf</code> as appropriate.  Alternatively, if you don't care about distcc, you can make a <code>/sw/etc/profile.d/localenvironment.sh</code> file or similar, and set <code>MAKEFLAGS</code> in there.\n\n=== When Issues Arise ===\n\nThe first thing to try is to just set <code>MAKEFLAGS</code> to \"-j1\" in your /sw/etc/distcc.conf or equivalent, and see if it builds.  If it does, mail the maintainer for the package (<code>fink info ''packagename''</code>) to add the following lines to his info file:\n\n  NoSetMAKEFLAGS: true\n  SetMAKEFLAGS: -j1\n\nMany packages that I've personally had problems with build with that.  You don't get a parallel build this way, but you also don't get a dead one.  :)\n\nIf you still have errors, try also setting CCACHE_CPP2=1.  Some stuff bombs because it doesn't like the tricky way ccache runs things through the c preprocessor before getting passed on to the local gcc.  In these cases you generally see an error about adding -fconstant-cfstrings to the command-line, or something similar.  If that doesn't work, try setting DISTCC_HOSTS to an empty string.  \n\n  CompileScript: <<\n    ./configure %c\n    CCACHE_CPP2=1 make\n  <<\n\n...or...\n\n  CompileScript: <<\n    ./configure %c\n    DISTCC_HOSTS=<nowiki>''</nowiki> MAKEFLAGS='-j1' make\n  <<\n\nThat has fixed things in all cases where just MAKEFLAGS has not, other than the less obvious errors of builds completing, but missing files and such.\n\nIf you still have issues, you're on your own.  See the top of this section.  ;)\n\n{{Fink_Header}}\n\n[[Category:Fink]]\n[[Category:Fink Documentation]]\n[[Category:Fink Internals]]"
                    }
                ]
            }
        }
    }
}