- 1 Reasoning for Existence of Page
- 2 Detail missing
- 3 No RTFM or personal opinions
- 4 Official name?
- 5 New merge
- 6 Pacman refuses to delete corrupted package, because it is corrupted...
- 7 proposed addition to package cache cleaning...
- 8 Changes with pacman 3.4
- 9 Troubleshooting: manually reinstall pacman
- 10 Outdated Mirrors
- 11 Package format
- 12 testdb
Reasoning for Existence of Page
We already have --help for a quick description of commands, and the man page for a detailed description. So what does this wiki page achieve exactly? shining 16:45, 27 April 2008 (EDT)
- After last cleanup from toofishes which removed a bunch of flags, and linked to --help and man page instead, I think it is now clearer.
- This page should just be a quick overview of the most frequently used pacman commands, not an exhaustive enumeration of every single flag. shining 07:50, 12 June 2008 (EDT)
- Good points. Additionally, after the article refers users to the pacman.conf man page for configuration instructions, it goes on to discuss it! It would be more appropriate to remove all configuration settings as it implied, and stick with pacman and its commands.
- To make matters worse, the article doesn't even discuss all about pacman; leaving out huge and important chunks of information regarding the databases, their relationships, program lists, the backend application, etc. etc. (See following section.) Perhaps someone more knowledgable could flesh it out a little, starting with the basics. It would be greatly appreciated. - KitchM 12:52, 5 November 2010 (EDT)
Can someone please add the details of pacman? There is no explanation of how it works. What are the components and their interaction? And how about related dependencies and libraries? Without that basic flow-chart concept in mind, it is very difficult to understand the roll that third-party additions or frontends might play.
- This would be very interesting. libfetch, libalpm, etc. manolo 15:23, 15 November 2009 (EST)
No RTFM or personal opinions
Get rid of any comments that direct people to man pages instead of actually explaining things. That is a very lazy way of doing things. At the very least you can summarize, or you can let someone else do it.
Do not forget that one of the reasons the wiki exists is give the reader something they can understand in simple language. Man pages are the worst example of writing that has ever been written.
Also, don't make claims about how wonderful a program is; rather state the reasons for the way it was created and let the user be the judge of if it is actually wonderful or not. - KitchM
- We are trying to direct to man pages as much as possible in order to avoid duplicated effort.
- We do the best we can at explaining things in man pages. If people find that things are not clear, we would much prefer to get feedback, rather than people duplicating the documentation on the wiki.
- The people working on pacman and its man pages actually also check this wiki page and maintain it occasionally. We would like to avoid having to fix things in both places systematically.
- I hope that is understandable. We do want to explain things. We should just prefer do that in one centralized place. shining 12:10, 1 October 2009 (EDT)
- Thanks, Shining, for your thoughts. I think that centralization has been the intent for many decades, but has never been correctly implemented.
- IMHO, I have found that man pages are written in geek-speak by the programmers who make the software as a quickie way to document themselves to others of their language, and wiki pages are to be written by people whose job it is to communicate with everyone. I am not convinced that there is any duplication of effort in the two, but rather the necessary translation which must be done from one language to another. That is why one should only refer to man pages as an extra reference, but not the main one.
- By the way, one example of problems with man pages is the recent one I ran across for pacman. Man pacman had one little reference to man pacman.conf at the bottom of the text. I had overlooked it for a long time, and only stumbled upon it by accident. Coulda, shoulda, woulda just doesn't have any bearing in this case. Poorly written, poorly formated and poorly cross-referenced is the best to which man pages can attain. There are many non-personal reasons for this, but suffice it to say, that's the way it is. Worse yet, even between the two there were still many important questions left unanswered.
- I maintain that we should fully explain as we go so that mistakes like this do not occur, else the wiki is incomplete. - KitchM 11:33, 4 October 2009 (EDT)
- You seem very negative and biased against man pages. You didn't even try to have them improved. We would really like to receive more detailed feedback on them before giving up. Please join email@example.com to discuss this. That way, more people could also contribute to this discussion. Mails are also a much better way to discuss than a wiki page.
- Did you try the web version of the man pages ? This seems well formatted and cross-referenced to me : pacman.8.html. shining 12:22, 5 October 2009 (EDT)
- Could it be that the bias is on your part? I plainly wrote that as a person with experience in this area, I recognize the frustration of the billions of people who suffer from the terse and odd language of the traditional man pages. I also wrote that I have always stood ready to assist in any way to translate these things into useful common English and that few take me up on that.
- I do not think that your erasure of my comments should justify contrary statements on subjects I have already addressed. Why do that?
- In any case, this is the place to make comment about the problems in the wiki writing found on the referenced page. Please keep that in mind as I point out that man pages should have no place in a wiki setting as a substitute for doing proper wiki writing. I would hope that we can all agree to that, and repair the wiki page in question.
- (As to the issue of helping with the man pages, as I have twice stated, all you had to do was ask. I will gladly meet you there.) KitchM 14:35, 5 October 2009 (EDT)
- shining wrote: We would really like to receive more detailed feedback on them before giving up. Please join firstname.lastname@example.org to discuss this.
- KitchM wrote: all you had to do was ask. I will gladly meet you there.
- Seems we are going around in circles... Allan
- I don't think that is completely accurate. Sure, I was forced to restate some points, but we got thru it. And the good thing was that I got asked to help. (Which I did, by the way.) So that's real progress. And very cool. I hope my suggestions got to the right parties and were appreciated. KitchM 19:53, 6 October 2009 (EDT)
~Also, what is pacman's official name? i.e., pacman or Pacman?manolo 00:42, 13 November 2009 (EST)
- It appears as "pacman" on both the man page and the home page. -- pointone 12:35, 13 November 2009 (EST)
I think the new article merged by pointone is perfect, but I predict some people are going to think it's too verbose :) manolo 13:32, 16 November 2009 (EST)
I just had a look at the merge, I find it perfectly fine. I think that giving this information to users is very important. I am still a big wiki noob, but I used to be pissed off many times by stupid edit of wiki pages, adding useless or wrong information. I have to say I am impressed by all the amazing work done by manolo and pointone so far on various wiki pages, both in contents and style. Please keep up the good work :) --shining 18:19, 16 November 2009 (EST)
Pacman refuses to delete corrupted package, because it is corrupted...
I had this issue today with two packages (icu-4.4-2-x86_64.pkg.tar.xz and ttf-bitstream-vera-1.10-7-any.pkg.tar.xz). Got asked "<X> is corrupted. Do you want to delete it? [Y/n]" and then told "failed to commit transaction - <x> is invalid or corrupted". Some nice person should add in "Troubleshooting" that in this case one can delete said package manually as root in /var/cache/pacman/pkg. -- Misc 20:17, 17 April 2010 (EDT)
- I'm glad someone asked this. And thanks for the pointer. One of the most annoying things that I've found users have ever had to deal with in the last couple decades has been this sort of problem with automated package management methods, regardless of the OS used. I have noticed, however, that the download process usually weeds out the corrupted downloads before committing them to the install process. It might be that dumping a bad package might be something that is automated by the pacman routine in a better manner than it does now, but downloading again, and overwriting the bad one, should fix the problem without further effort. - KitchM 23:01, 18 April 2010 (EDT)
proposed addition to package cache cleaning...
Comment: I think people will find value if the following was added to the page. Might be good to insert it between the pacman -Sc and pacman -Scc descriptions. What do others think?
Alternatively, the [CacheClean] python script can be used to manage one's pacman cache. Functionally, the script acts like the "pacman -Sc" command with a key difference: the user can select how many old versions (generations) of his/her packages to keep. For example, the following command will keep two versions of the cached packages, deleting everything else in the /var/cache/pacman/pkg directory.
# cacheclean.py 2
- graysky 16:18, 28 May 2010 (EDT)
- Disagree; I think we should keep these kinds of unsupported tools, etc. in pacman Tips. -- pointone 18:07, 2 September 2010 (EDT)
Changes with pacman 3.4
In the Installing and/or Upgrading sections, we could mention the new possibility of: pacman -Syu <package> D garbage 06:26, 27 June 2010 (EDT)
Troubleshooting: manually reinstall pacman
There is a great sticky in the forums explaining how to manually reinstall pacman. We could add something along these lines to the Troubleshooting section (sorry, I'm not good at this - but as a start):
- Added (slightly modified). Thanks! -- pointone 21:47, 27 July 2010 (EDT)
Recently, some people had problems with mirrors that went completely out of sync due the new tier1/2-scheme. maybe we could add a sentence & link to the related troubleshooting section:
"pacman mirrors are not synced immediately. It may take over 24 hours before an update is available to you. The only options are be patient or use another mirror. If you have not received any updates for a long time, check MirrorStatus for a properly syncing mirror."
Hokasch 06:48, 2 September 2010 (EDT)
- Implemented (simplified). -- pointone 18:04, 2 September 2010 (EDT)
"It uses the .tar.gz package format, and is currently migrating to the .tar.xz (LZMA2) format."
Isn't the migration complete?
Jasonwryan 02:49, 22 October 2010 (EDT)
- Updated. -- pointone 10:39, 22 October 2010 (EDT)