From ArchWiki
Revision as of 15:15, 24 June 2012 by Pointone (talk | contribs) (Interlanguage links: close)
Jump to: navigation, search

Is the wiki missing documentation for a popular software package or coverage of an important topic? Or, is existing content in need of correction, updating, or expansion? Write your requests below and share your ideas...

See ArchWiki:Reports to report questionable contributions. Please sign your edits and feel free to comment on others' requests.

General requests

Pages flagged with Template:Accuracy, indicating inaccurate content.
Special:WhatLinksHere/Template:Out of date
Pages flagged with Template:Out of date, indicating outdated content.
Pages flagged with Template:Deletion, indicating irrelevant or unhelpful content.
Pages flagged with Template:Expansion, indicating incomplete content.
Special:WhatLinksHere/Template:Poor writing
Pages flagged with Template:Poor writing, indicating poorly-written content.
Pages flagged with Template:Merge, suggesting duplicate effort or overlapping scope.
Pages flagged with Template:Moveto, suggesting misleading names.
Special:WhatLinksHere/Template:Bad translation
Pages flagged with Template:Bad translation, indicating poor translations.
Pages flagged with Template:Translateme, indicating incomplete translations. See also ArchWiki Translation Team.
Pages flagged with Template:Stub, indicating incomplete content.
Pages flagged with Template:Linkrot, indicating dead or broken links which should be repaired or replaced.
Pages automatically flagged with Template:Error, indicating the presence of a template with an undefined parameter.
Special:WhatLinksHere/Template:Unexplained Status Template
Pages automatically flagged with Template:Unexplained Status Template, indicating the unexplained presence of an article status template.

Problem redirects

Note: Redirects should not point to other sites and ones that do sometimes erroneously show up on these pages.

Creation requests

Here, list requests for topics that you think should be covered on ArchWiki. If not obvious, explain why ArchWiki coverage is justified (rather than existing Wikipedia articles or other documentation). Furthermore, please consider researching and creating the initial article yourself (see Help:Editing for content creation help).


How to configure SAMBA PDC + LDAP in Arch Linux? (Moved from another page. Hokstein 19:57, 16 September 2007 (EDT))


Finding information on the install of this program already requires a bit of searching around the net, and then a variety of modifications to get it running correctly. It would be nice to have a good HowTo about the install and setup of Tripwire on Arch. The package is availabe in community.

It has since been removed from [community], it's in the AUR now. -- Karol 21:52, 29 August 2011 (EDT)

Modification requests

Here, list requests for correction or other modification of existing articles. Only systemic modifications that affect multiple articles should be included here. If a specific page needs modification, use that page's discussion or talk page instead and one of the #General requests templates.

net-tools -> iproute2

It's not really a big deal, but we should start changing commands like netstat and ifconfig to the equivalent iproute2 command. net-tools is dead upstream, and Arch has switched to using iproute2 for initscripts. net-tools isn't a dependency of anything in base, and isn't in the base group itself - we shouldn't assume it is installed anymore.

The new networking syntax in initscripts also only allows you to configure 1 interface. People have to use netcfg or another solution for complex situations, which might require further changes on the wiki.

thestinger 11:32, 8 June 2011 (EDT)

New Official ISO

Coming soon. We need some brave souls that will edit the Beginner's Guide etc. according to what will be on the ISO. -- Karol 11:28, 19 August 2011 (EDT)

A bit overdue, but I've gone through the installer in qemu and made a fair number of changes to the preface and installation sections, and just started out on post-installation. I started a couple of discussions on Talk:Beginners' Guide and Talk:Beginners' Guide/Post-Installation.
My review wasn't exhaustive because I didn't have the necessary manpower to follow and document all paths through the installer, and I'm far from infallible, so it would still be good for anyone to give it a quick glance for obvious blunders. | Emiralle 10:36, 13 October 2011 (EDT)
I've finally found the time to go through your changes, it looks a very good job ;)
Just to do some nitpicking, this edit is maybe too i686-centric, and the first link duplicates the one the was already there: does somebody have a good idea on rewording that text to include x86_64 references and remove the duplicate link?
About your discussions, I've replied to those in Talk:Beginners' Guide, but I still have to think of something for Talk:Beginners' Guide/Post-Installation#/etc/pacman.conf.
-- Kynikos 14:22, 20 October 2011 (EDT)
I agree about the i686 centric-ness (I am an x86_64 user after all!). I do like having those links since it clearly and reliably shows what the user is getting into. I guess I picked i686 since for many people it is still "standard", while x86_64 is a sort of optional thing. I'll try thinking of a decent way of making it more neutral without cluttering things up. Emiralle 15:28, 20 October 2011 (EDT)
I took a first stab at cleaning up the i686/x86_64 balance issue in Beginners'_Guide#Select_packages. I added a link to Official Repositories core section, which might be useful and gets rid of the duplicate link. Then I modified the package database and group links to show both i686 and x86_64. I just realized I have no idea how easy this stuff is to follow for people using the Dual Architecture ISO since I've never tried it. Emiralle 19:22, 20 October 2011 (EDT)
Looks good, I've just tried improving the formatting a bit. -- Kynikos 09:01, 21 October 2011 (EDT)
We may have a 2012 iso coming up. I currently have no way to test these images and we should make sure that the official installation info is correct this time. -- Karol (talk) 20:09, 7 May 2012 (UTC)
I don't have the time to test the new images either, not even talking of maintaining the official guide in git, however it may be interesting to propose using pandocAUR (AUR) to convert the original text (in Markdown) to MediaWiki syntax instead of the current shell script. -- Kynikos (talk) 16:15, 13 May 2012 (UTC)
Posted in arch-releng. -- Kynikos (talk) 21:35, 14 May 2012 (UTC)
By the way, I'm pasting also here the link to the new guide in the development branch: That is the file that must be checked, not the current Official Installation Guide. -- Kynikos (talk) 21:38, 14 May 2012 (UTC)
Bug report: FS#30045. -- Kynikos (talk) 13:49, 28 May 2012 (UTC)

Openbox 3.5

There are some leftovers that e.g. refer to, instead of autostart. -- Karol 04:08, 21 August 2011 (EDT)

All reference is removed. Closing. -- Fengchao (talk) 05:38, 11 May 2012 (UTC)
Reopening, searching for "" still gives some results :) -- Kynikos (talk) 15:42, 13 May 2012 (UTC)

AUR went https

The 'Package AUR' template is already using https, but there are tons of links that need to be fixed. -- Karol 22:36, 29 August 2011 (EDT)

This bug got fixed so it's a lot better now. -- Karol 13:53, 7 September 2011 (EDT)
Help:Style will deprecate direct links to aur packages in favour of Template:AUR, do we keep this request open? -- Kynikos 14:28, 20 October 2011 (EDT)
I think we should close requests when they're done i.e. when all the links to the AUR use https. Will there be some kind of automagick conversion from direct links to the new template? -- Karol 14:48, 20 October 2011 (EDT)
A bot and regexp substitutions may be able to do the trick.
Do you want to reopen also the other discussions I've just closed on this page for more or less the same reason? (Just look at the history for reference, I'm too lazy to link them here).
-- Kynikos 16:06, 20 October 2011 (EDT)
I think we should keep the requests open until the changes are done, just having the tools is not enough if they're not used in the wiki. -- Karol 21:03, 20 October 2011 (EDT)
Reopened all. -- Kynikos 08:50, 21 October 2011 (EDT)
Is there any easy way to search the entire wiki for every instance of ``? -- Jstjohn 20:23, 4 March 2012 (EST)
I don't remember if Special:LinkSearch is available to normal users: if it's not and you're interested I can paste the search results somewhere (as of today I get 1853 results, not all of them are package queries). However a bot could easily check for that string and change it safely to https, unless you intend to replace package queries with Template:AUR. -- Kynikos 07:05, 5 March 2012 (EST)
Special:LinkSearch works for me! This is a great tool. I wish it was more widely publicized! Having a bot convert all http://* links to their HTTPS equivalents would be amazing. I would still like to get a lot of them updated to the AUR template though. :) -- Jstjohn 12:15, 8 March 2012 (EST)
You know you can find all the available tools in Special:SpecialPages ;)
If you want to get some level of automation, Wiki Monkey provides a very simple way of performing global regexp substitutions directly in editor pages; technically you can perform regexp substitutions also with the bundled bot, but currently only from Special:WhatLinksHere pages.
-- Kynikos 04:53, 9 March 2012 (EST)
All existing http aur links have been changed to https now, however I'd like to leave this request open until I find the time and the right place to list all the operations that should be done periodically with a bot. -- Kynikos 17:25, 24 March 2012 (EDT)
Thanks for all the great work :-) -- Karol 17:28, 24 March 2012 (EDT)

<tt> is deprecated in HTML 5

See this page. It has been suggested we remove this tag and use Template:Codeline instead. -- Karol 00:08, 1 September 2011 (EDT)

If only there was somebody who could configure a bot for these kind of jobs... This wiki is all about computers, and programming, and many more abstruse things, and we're still performing these jobs by hand, like our fathers used to do in the old days? XD (EDIT: see Wikipedia:Wikipedia:Bot_requests and related) -- Kynikos 06:14, 3 September 2011 (EDT)
A bot would be godsend. Let me see: "Dear Santa ..."
In the past you had to retype the whole thing on the typewriter, you couldn't just do hundreds small changes every now and then ;P -- Karol 11:22, 3 September 2011 (EDT)
Eheh, but, more seriously (and I don't know if it's worth to start a separate discussion for this), what if we really made a proper section (or an article) where users can request bot operations, and where other users can provide PHP, Python... scripts (I don't know what language wiki bots speak) so that wiki admins just have to feed the bot with it and let it go? For example, in this situation we could write a PHP function that takes a multiline text, replaces <tt> with Codeline using regexp substitutions, and returns the new text: I'm quite sure that what would remain to do would be calling that function from the bot, which of course has the ability of getting every article text and writing it back. -- Kynikos 12:28, 3 September 2011 (EDT)
EDIT: Bot info now at User:Strcat.
I'm going to try out a few things on my user page like tagging dead links with a template, replacing <tt> with codeline, etc.
thestinger 22:04, 3 September 2011 (EDT)
Ran it on a few articles and it works fine (tt -> codeline), going to ask for a bot tag before doing more though. thestinger 23:01, 3 September 2011 (EDT)
It needs to be smart enough to escape strings containing = or | with <nowiki></nowiki> tags. See PHP James Eder 23:23, 3 September 2011 (EDT)
Escaping those will work most of the time but there are a bunch of cases where templates or markup like [[link|text]] are used inside <tt>. The bot can show a diff and ask for confirmation each time, so I'll just check for stuff like that each time and fix the few articles doing crazy stuff like this manually (rather than trying to use regex to parse Wiki markup :P). thestinger 23:46, 3 September 2011 (EDT)
Another alternative is using {{Subst:Codeline|text}} when = or | appear in the text, but that's not ideal. thestinger 23:58, 3 September 2011 (EDT)
Perhaps you can make it automatic at least for for the trivial cases that lack craziness. Anyway, keep up the good work. James Eder 00:58, 4 September 2011 (EDT)
Good job Thestinger, you could also consider using {{Ic|1=text}} to escape = and | (EDIT: works only with =, but I think pipes are less frequent than equals; another alternative is replacing them with html entities). -- Kynikos 07:40, 4 September 2011 (EDT)
1= turns out to be the only viable solution in some situations. For example, it seems to be the only way to have the following template usage parsed correctly by the wiki software:
Note: A note with a URL containing an equal sign:
You cannot use <nowiki> tags without also breaking the link behavior. We should probably document this in our Wiki help pages somewhere. It is easy enough to run into but not necessarily obvious to fix. James Eder 14:54, 6 September 2011 (EDT)
Found it documented here: Help:Template. I wonder if it should be mentioned in other pages as well. James Eder 15:28, 6 September 2011 (EDT)
1= works great! I just have the bot recheck the pages for '{{{' now after changing them for so I can manually fix any breakage. thestinger 16:34, 6 September 2011 (EDT)

This is now finished for every category on this page (should be all the english content categories). thestinger 17:30, 6 September 2011 (EDT)

Are you going to periodically unleash the bot to fix e.g. this or should we fix such edits manually as they appear? -- Karol 11:11, 1 October 2011 (EDT)
The bot can watch the recent changes list, so I'll set that up at some point. I ran it recursively over Category:English, and there were a lot of uncategorized pages/categories (mostly fixed now) so some pages were missed on that run anyway. -- thestinger 22:12, 1 October 2011 (EDT)
What's the status of this? -- Karol (talk) 20:59, 7 May 2012 (UTC)
Except for the fact that this request has been closed for months, now <tt> is styled exactly the same as <code> and Template:ic (well, not exactly but it doesn't matter), so I don't know if thestinger has something to say, but I'd remove this section. -- Kynikos (talk) 17:35, 10 May 2012 (UTC)


Many pages are out of date and I can't even flag them out of date. Should users be warned that pages in this "category" may be really old and abandoned? -- Karol 09:19, 8 October 2011 (EDT)

Perhaps we can create a special template to be included at the top of every article in that category? -- Kynikos 13:41, 8 October 2011 (EDT)

Remove -f short option for --force

It's not live yet [1] but will force some changes - is it bot-able or do we have to comb the wiki by hand? -- Karol 14:13, 19 October 2011 (EDT)

Uh I see, well, searching "pacman -Sf" and "pacman -Uf" doesn't give many results, however a regexp'd bot search with something like "pacman -[A-Za-z]*f" would catch more complex combinations and also possible existing mistakes. -- Kynikos 19:23, 19 October 2011 (EDT)

ck-launch-session dbus-launch and friends

Help:Style#Hypertext_metaphor taken to extreme: while searching for some hints on the exec ck-launch-session dbus-launch yourwm thing, I found myself tracking a piece of referenced info that has fallen victim to some daisy-chain mania.

Fluxbox tells you to check Xinitrc: "See Xinitrc for more details." Once there you learn that it has something to do with Policykit ... or Xfce, as you're told to "See also the notes of Xfce#Manually for more details.". Let's see what's on PolicyKit's page first. "Please note: to correct issues with automount and shutdown, please check the ConsoleKit page."" ConsoleKit was a disappointment for me, seems the princess is in another castle. Let's see that Xfce article mentioned earlier. Indeed, Xfce#Manually seems to have the most info about the issue, but not by much.

Unfortunately we don't have tools to see such "double-redirects" and lacking expertise in this particular issue is definitely a factor. Can someone please untangle this mess? -- Karol 16:37, 19 October 2011 (EDT)

AUR changing paths to PKGBUILDs

We recently hit the 32k subdirectories limit due to great number of packages in the AUR and it has been decided that the packages are going to be divided according to the first two letters of their name e.g. Xlayout goes to 'xl' subdirectory and the path to its PKGBUILD will change to This move caused the old links to go 404 and now they appear on our ArchWiki:Linkrot page. I think instead of fixing the links we should generally remove sections like this one. -- Karol 15:43, 20 October 2011 (EDT)

udev update

[2] says that "The long deprecated keys: SYSFS=, ID=, BUS= have been removed." (among other changes). Many wiki articles use them in the udev rules.

MediaWiki Visual Editor

References to the Visual editor sandbox should me made on the Wiki and BBS, especially where new users will easily come across it. ~ Filam 16:12, 16 December 2011 (EST)

Packages dropped to AUR

There have been many packages dropped to AUR during the Christmas Cleanup. The list can help us with updating the templates [3] etc. -- Karol 13:04, 18 December 2011 (EST)

alsaconf removed from alsa-utils

FS#28631 There are many mentions of 'alsaconf' in the wiki. I have no idea whether to just remove them or suggest using some other tool instead. -- Karol 17:16, 8 March 2012 (EST)

Interesting, I think most of the mentions are on the out-of-date laptop pages and I'm not too worried about trying to maintain those. thestinger 00:32, 11 April 2012 (EDT)

Move/Merge articles to external wikis

Although French, Swedish and Finnish have their own wikis, we're still hosting some articles in those languages:

Some users of those wikis should probably be contacted in order to complete the move/merge, replacing those articles with interlanguage links at least on the respective English pages.

-- Kynikos (talk) 16:34, 10 May 2012 (UTC)

New dependencies for pacman

[moved from [4] -- Kynikos (talk) 09:30, 2 June 2012 (UTC)]

Some parts of the wiki may need updating, e.g. [5] (the last one in the faq). -- Karol 08:39, 20 January 2012 (EST)

This sounds more like a request, I'd move it under Requests#pacman_4_in_.5Bcore.5D, as a subdiscussion, agreed? -- Kynikos 07:57, 21 January 2012 (EST)
There are actually quite a few dependencies that aren't mentioned, since a broken dependency of pacman would also break pacman (can see them all with pactree -l pacman | sort -u | cut -f 1 -d ' '). The packages that would need to be downloaded and extracted would vary depending on which partial upgrade was done. thestinger 15:19, 21 February 2012 (EST)


Instead of flagging all articles still using the old kernel image naming out of date, can we do some mass-renaming? -- Karol 20:55, 20 October 2011 (EDT)

Last week, I found at one article that was using vmlinuz26 in an example for users of non-recent kernel versions. I'm not sure if we would want to keep such an example around, but we may want to decide that before doing a mass rename. And for what it's worth, I don't think it is necessary to keep such antiquated examples around. -- Jstjohn (talk) 20:53, 4 June 2012 (UTC)
Of course I don't know what article you're referring to, but doing a mass-renaming with a bot sounds a bit dangerous, because as you've pointed out there may be exceptions where the old kernel names are still ok. I'm moving this discussion out of Bot requests. -- Kynikos (talk) 14:57, 5 June 2012 (UTC)

Bot requests

Here, list requests for repetitive, systemic modifications to a series of existing articles to be performed by a wiki bot.

Moving pages

Can we have a bot that will move non-English pages and fix i18n links when the English page gets moved/renamed? SSH -> Secure Shell and Cpufrequtils -> CPU Frequency Scaling and the recent examples. -- Karol 10:47, 8 September 2011 (EDT)

Interlanguage links

[moved from Help talk:Style#i18n links -- Kynikos 18:35, 22 September 2011 (EDT)]

Should we add links to external wikis just to the English article or to every one: Arch_User_Repository_(Српски) has the link to the French wiki, Thestinger also started adding such links to non-English articles. -- Karol 19:25, 1 September 2011 (EDT)

Of course adding external links to all articles would be the ideal situation, but it would take quite a lot of bravery, to check every translation of every article... Maybe it would be the perfect work for a learned bot. -- Kynikos 04:48, 2 September 2011 (EDT)
Adding the interwiki links to articles on other wikis is easy and there's already a script for it (for example, if the English wiki has links to German and French and neither of those wikis have interlanguage links, it can add English and German links to the French article, etc.). Dealing with i18n pages here seems like it should be easy (just need to add all the potential language tags to the end of the English article title to look for the pages) so I'll try editing the script later to get it to work with our i18n conventions. thestinger 18:45, 3 October 2011 (EDT)
How does it handle the (very rare) cases where, for example, the article "A (aa)" (title is "A", language is "aa") has an interlanguage link "[[cc:title1]]", and the article "A (bb)" has an interlanguage link "[[cc:title2]]" (same language but different article)? An experiment could be interesting :) -- Kynikos 05:14, 4 October 2011 (EDT)
There are actually a lot of weird things going on with the i18n stuff (English pages actually being redirects to a different language etc.) so I'll hold off on this for now. thestinger 19:27, 20 October 2011 (EDT)
Closing request. See Help talk:i18n#"Dummy" interlanguage links and deprecation of Template:i18n. -- pointone (talk) 15:15, 24 June 2012 (UTC)

Updating templates

It would be really useful if a bot would crawl the entire wiki and update the old templates to the new ones. Just doing a search and replace of {{Filename| to {{ic| would be amazing. The templates that I believe should be able to safely be converted are the following:

The above templates are the most widely used, so just replacing them would be a godsend. Template:Cli and Template:Command could probably be handled manually. :P

Additionally, it would probably be safe to batch convert <pre> to {{bc|<nowiki> and </pre> to </>}}, and similarly for <code> and <tt> being changed to Template:ic. -- Jstjohn 15:54, 10 December 2011 (EST)

If you're interested I've created a GreaseMonkey script, Wiki Monkey, which I've been using quite successfully in the last weeks. Currently it just replaces the templates and removes multiple line breaks, but it could do much much more. If you have some knowledge of javascript and regular expressions you may also contribute to the project and create new user functions! :) -- Kynikos 08:47, 11 December 2011 (EST)
I started on the basic conversions (where stuff already redirects). A GreaseMonkey script would definitely be better than pywikipediabot when stuff might require intervention (there's a horrible tkinter editor that pywikipediabot uses...). thestinger 11:39, 11 December 2011 (EST)
I'd like to spend some more words on Wiki Monkey, to try and attract some contributors, because I'm sure that despite the need for some development work at the beginning, it has the potential to alleviate wiki maintenance efforts quite a lot in the future: the main script is a greasemonkey file which just requires (includes from "upstream", i.e. my github repo) the most up-to-date version of the "core" script, which in turn provides a high-level API which can then be used to write quite simple JS functions to perform automatic actions in the wiki. User functions can be created separately and just "required" in the main script in the same way the "core" script is required.
But there's more: GreaseMonkey provides some functions that let store some values persistently throughout page changes or reloads, so, by exploiting that feature, it may be possible to make the script perform real bot operations by making it collect lists of articles and perform a series of actions on them automatically or even semi-automatically, which means it would be perfectly able to show the user a preview in the browser for every action to be taken.
All this can be implemented with some Javascript and MediaWiki API knowledge.
-- Kynikos 16:30, 12 December 2011 (EST)
I've struck the reference to Template:File in the list above because the named arguments are not the main problem for its conversion! The biggest problem is the fact that File is based on <div>, <code> and <pre>, while Hc is based only on <pre>, and this can make the internal string to be processed differently by MediaWiki.
Also note that Wiki Monkey now handles the named argument translation quite smartly.
Finally, a link to the place where this discussion was started: Help talk:Style/Migration_to_new_Code_formatting_templates#Migration strategy.
-- Kynikos 08:39, 18 December 2011 (EST)

Use internal links

[6] and [7] list all the full links that should be turned into internal links. -- Kynikos 06:03, 23 March 2012 (EDT)