Package Details: oh-my-zsh-git r6192.be4a95297-1

Git Clone URL: (read-only, click to copy)
Package Base: oh-my-zsh-git
Description: A community-driven framework for managing your zsh configuration. Includes 180+ optional plugins and over 120 themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community
Upstream URL:
Licenses: MIT
Submitter: phoenixlzx
Maintainer: MarcinWieczorek
Last Packager: MarcinWieczorek
Votes: 442
Popularity: 1.56
First Submitted: 2012-10-24 12:04 (UTC)
Last Updated: 2021-10-05 05:52 (UTC)

Latest Comments

MarcinWieczorek commented on 2022-02-03 07:36 (UTC)

patch is in base-devel. Is it required at runtime or only buildtime?

uint2048_t commented on 2022-02-03 03:18 (UTC)

PKGBUILD needs patch as a dependency

krs commented on 2021-10-04 12:27 (UTC) (edited on 2021-10-04 12:41 (UTC) by krs)

It's because the format of disabling automatic updates in the zshrc file has apparently changed, so the patch doesn't work anymore.

Here's an updated patch:

--- a/zshrc 2021-10-04 14:06:44.858883829 +0200
+++ b/zshrc 2021-10-04 14:09:17.198891675 +0200
@@ -2,7 +2,7 @@
 # export PATH=$HOME/bin:/usr/local/bin:$PATH

 # Path to your oh-my-zsh installation.
-export ZSH=$HOME/.oh-my-zsh

 # Set name of the theme to load --- if set to "random", it will
 # load a random theme each time oh-my-zsh is loaded, in which case,
@@ -24,7 +24,7 @@

 # Uncomment the following lines to change the auto-update behavior
-# zstyle ':omz:update' mode disabled  # disable automatic updates
+zstyle ':omz:update' mode disabled  # disable automatic updates
 # zstyle ':omz:update' mode auto      # update automatically without asking
 # zstyle ':omz:update' mode reminder  # just remind me to update when it's time

@@ -72,8 +72,6 @@
 # Add wisely, as too many plugins slow down shell startup.

-source $ZSH/
 # User configuration

 # export MANPATH="/usr/local/man:$MANPATH"
@@ -99,3 +97,10 @@
 # Example aliases
 # alias zshconfig="mate ~/.zshrc"
 # alias ohmyzsh="mate ~/.oh-my-zsh"
+if [[ ! -d $ZSH_CACHE_DIR ]]; then
+  mkdir $ZSH_CACHE_DIR
+source $ZSH/

pkr commented on 2021-10-04 11:11 (UTC) (edited on 2021-10-04 11:12 (UTC) by pkr)

Seeing this when installing.

==> Starting prepare()... patching file zshrc Hunk #1 succeeded at 4 with fuzz 2 (offset 3 lines). Hunk #2 FAILED at 15. Hunk #3 succeeded at 72 with fuzz 2 (offset 16 lines). Hunk #4 succeeded at 98 (offset 17 lines). 1 out of 4 hunks FAILED -- saving rejects to file zshrc.rej ==> ERROR: A failure occurred in prepare(). Aborting...

Appreciate any help.

MarcinWieczorek commented on 2020-11-11 20:03 (UTC)

This is not a support channel. If you have your oh-my-zsh in $HOME, then it's probably not this package's fault as files are installed in /usr/share. Try a fresh install or check git status/git diff if you cloned the repository to ~/.oh-my-zsh

glitxh commented on 2020-11-11 19:59 (UTC)

I'm recently getting this error on launch. Any help? /home/username/.oh-my-zsh/lib/misc.zsh:21: command not found: env_default /home/username/.oh-my-zsh/lib/misc.zsh:22: command not found: env_default

jiahuiz commented on 2020-10-13 23:33 (UTC)

@ryankh @csts The correct way is run: cp /usr/share/oh-my-zsh/zshrc ~/.zshrc

csts commented on 2020-07-17 21:12 (UTC)

@ryankh I just installed it and ran:

EgidioCaprino commented on 2020-06-09 08:39 (UTC)

I guess it's because you're supposed to upgrade it through AUR

eh8 commented on 2020-06-09 02:59 (UTC)

Why is upgrade_oh_my_zsh disabled as a command?

ryankh commented on 2020-06-08 02:49 (UTC)

I couldn't figure out how to make this work. None of the instructions on the oh-my-zsh readme from GitHub seemed to work with this AUR version. It was faster and easier just to follow the instructions from the readme and manually install it in my home folder.

francoism90 commented on 2020-04-18 15:26 (UTC)

yay -Scc

EgidioCaprino commented on 2020-04-18 12:49 (UTC)

Isn't yay -Sc supposed to do that?

francoism90 commented on 2020-04-18 09:32 (UTC)

@EgidioCaprino you need to remove the yay cache and reinstall.

EgidioCaprino commented on 2020-04-18 09:30 (UTC) (edited on 2020-04-18 09:31 (UTC) by EgidioCaprino)

I have this problem while installing latest update with yay:

==> ERROR: /home/egidio/.cache/yay/oh-my-zsh-git/oh-my-zsh-git is not a clone of

I already tried clearing the cache with yay -Sc, but it doesn't solve the issue.

Anty0 commented on 2020-04-17 14:41 (UTC)

@Feresey According to the image you have patch installed as dependency.

You probably had it installed before installing base-devel group. Since grups in Arch Linux are just lists of packages to by installed, pacman skipped already installed patch and left it installed as dependency. You can easily fix that by setting him as explicitly installed. :)

Feresey commented on 2020-04-17 14:01 (UTC)


Anty0 commented on 2020-04-17 13:51 (UTC)

@Feresey I don't see, how it could be possible... :/

Package patch is in the base-devel.

You can see here:

Feresey commented on 2020-04-17 13:16 (UTC)

@MarcinWieczorek, as you can see, I don't have the patch command when the base-devel group is installed

MarcinWieczorek commented on 2020-04-17 11:42 (UTC)

Patch is in base-devel which is assumed to be installed when building packages from AUR.

Feresey commented on 2020-04-17 11:26 (UTC)

add patch to make deps

MarcinWieczorek commented on 2020-04-16 17:51 (UTC)

I got in touch with ohmyzsh team and we will work on improving the package. In the meantime I'm updating the url and changing schema git git+https.

trekdev commented on 2020-04-16 13:38 (UTC)

I had an issue as my firewall was blocking pulling the source specified as a git endpoint

Changing the source from ...${pkgname}::git+git:// to ...${pkgname}::git+ fixed the issue for me. Can it be swapped to https as it is less likely to be blocked?

MarcinWieczorek commented on 2020-03-15 17:03 (UTC)

What is your reasoning on those changes? I'll be happy to merge them. Also if you could just post a patch.

shaybox commented on 2020-03-15 16:48 (UTC)

I fixed the package for you.

MarcinWieczorek commented on 2020-03-03 14:41 (UTC)

@pkr When using -git packages from AUR you're supposed to update them yourself. This package prevents oh-my-zsh from updating itself, because it would cause a difference in package version and real version of the program. Some maintainers update their -git packages, but that's rare.

pkr commented on 2020-03-02 17:11 (UTC)


just a short question. I used to use this addon on Ubuntu and installed it the way the repository documentation stated it (curl and save in ~). The addon asked notified and asked me about updates from then on and it is still doing it on my other machine. I don't see any notifications nor updates here. Can someone explain to me how to update this when using this AUR? Do I understand this correctly that normally this AUR should be updated ideally every time any changes are pushed upstream on the oh-my-zsh repository?

Thanks in advance! Have a great evening!

rek2 commented on 2020-03-02 15:43 (UTC) (edited on 2020-03-02 15:44 (UTC) by rek2)

This is prob the worse package I ever encounter on the AUR in 12 years... no /bin/:/usr/bin/:/usr/local/bin install so is not on my PATH

So have to search the system for the actual directory

oh-my-zsh]$ pwd

then path is all screw up

zsh: can't open input file: /tools/
./ línea 23: autoload: orden no encontrada
./ línea 41: error sintáctico cerca del elemento inesperado `('
./ línea 41: `for plugin ($plugins); do'

/tools/ ??? really? thought you are installing this on /usr/share/oh-my-zsh not /


MarcinWieczorek commented on 2020-02-29 11:40 (UTC)

this is unable to work

Builds fine for me. @nguyenl95, could you please explain your issue?

francoism90 commented on 2020-02-29 09:24 (UTC)

This has been flagged because?

grawlinson commented on 2019-08-31 17:38 (UTC)

You need to install base-devel if you’re using the AUR. That package group includes patch.

noraj commented on 2019-08-31 17:20 (UTC)

/home/noraj/.cache/pikaur/build/oh-my-zsh-git/PKGBUILD: line 38: patch: command not found

Add patch to makedependencies

grawlinson commented on 2019-08-11 20:47 (UTC)

Updates are disabled because this is the AUR, where all packages are managed by the package manager (pacman). If there are updates upstream, then update the package manually.

The package is system wide, whereas the cache is per user.

tonij commented on 2019-08-11 20:24 (UTC) (edited on 2019-08-11 20:24 (UTC) by tonij)

Hi I have two question: Why do you disable auto updates? Why do you make a cache directory?

grawlinson commented on 2019-05-30 19:50 (UTC)

Install the package, then put this near the top of your zshrc

export ZSH=/usr/share/oh-my-zsh

abdulhakeem commented on 2019-05-30 14:13 (UTC)

I can't figure out how to actually use this. Do you still have to run the script on the github page after installing this AUR package?

grawlinson commented on 2019-05-18 16:27 (UTC)

That’s how *-git packages work. Have a look at the wiki regarding SVN packages and the pkgver function.

commented on 2019-05-18 14:16 (UTC)

You can build now package version oh-my-zsh-git-r5119.5aa62461d-1-any.pkg.tar.xz That is why it is flagged out of date.

grawlinson commented on 2019-05-18 03:17 (UTC)

@twwd: Why did you flag this package out of date? The link you've provided doesn't give any detail as to why.

nazarewk commented on 2019-01-17 14:11 (UTC)

Could you please change PKGBUILD's source from git+git to git+https ? It fails to download the repository when SSH ports are blocked.

commented on 2018-11-28 15:48 (UTC)

something does not work with this. when you source .zshrc and have the random theme option on ... it will say it laoded the theme but it doesnt change: EDIT: actually it doesnt load any theme

MarcinWieczorek commented on 2018-09-21 11:51 (UTC)

Xplorer4x4 flagged oh-my-zsh-git out-of-date on 2018-09-20 for the following reason:

    There seem to be newer commits in git and the comments indicate a modified pkg build to include a bug fix patch.

Please do not flag it out-of-date for such reasons. Also, please provide more information on the patches you mentioned. The package builds just fine for me.

MarcinWieczorek commented on 2018-08-06 23:57 (UTC)

As said in the package:

git: most themes use git (highly recommended but still optional)

Make dependencies can be removed after a successful build (everybody has git anyway but that's the rule).

grawlinson commented on 2018-08-04 08:18 (UTC)

Why is git a make dependency and an optional dependency? Shouldn't the optional dependency be removed?

jtmb commented on 2017-11-06 18:14 (UTC) (edited on 2017-11-06 19:13 (UTC) by jtmb)

seconding the patch request from zerophase. edit: you can download the referenced commit as, and if saved as 0002-colored-man-pages.patch, it can be built with this PKGBUILD: # Maintainer: Marcin (CTRL) Wieczorek <> # Contributor: Simon (vodik) Gomizelj <> # Contributor: Eduardo Leggiero <> # Contributor: jyantis <> # Contributor: jcsiv <siviter dot jamie at gmx dot co dot uk> # Contributor: ThinCarrotShrimp <christoph.r.martin+arch at gmail dot com> pkgname=oh-my-zsh-git pkgver=r4349.9edb3fce pkgrel=1 pkgdesc="A community-driven framework for managing your zsh configuration. Includes 180+ optional plugins and over 120 themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community" arch=('any') url='' license=('MIT') depends=('zsh') makedepends=('git') optdepends=('ruby: for some plugin functionality' 'python: for some plugin functionality' 'oh-my-zsh-powerline-theme-git: great theme' 'bullet-train-oh-my-zsh-theme-git: better powerline theme' 'git: most themes use git (highly recommended but still optional)') install=${pkgname}.install source=("${pkgname}::git+git://" '0001-zshrc.patch' '0002-colored-man-pages.patch') sha256sums=('SKIP' '9b77769319944f394a36f07b9abb296d24fe643c03b8eead74e10b7da52002b1' 'fc1d3a72b2c4c90cc930cb2ae122cfb0b988b2900d38a435657c74ce7d433589') # conflicts=('grml-zsh-config' # 'grml-zsh-config-git') pkgver() { cd ${pkgname} printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" } prepare() { cd "${srcdir}/${pkgname}" cp "templates/zshrc.zsh-template" "zshrc" patch -p1 < "${srcdir}/0001-zshrc.patch" patch -p1 < "${srcdir}/0002-colored-man-pages.patch" } package() { cd "${srcdir}/${pkgname}" mkdir -p "${pkgdir}/usr/share/oh-my-zsh" install -D -m644 "LICENSE.txt" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" cp -r * "${pkgdir}/usr/share/oh-my-zsh/" } # vim:set ts=2 sw=2 et:

zerophase commented on 2017-09-25 10:32 (UTC)

Could you add this in as a patch, till the fix gets pulled into master?

zaidan commented on 2017-06-17 12:38 (UTC)

Please remove '/' at end of ZSH=/usr/share/oh-my-zsh/ And also $HOME/.cache/oh-my-zsh +1 :)

eshizhan commented on 2017-04-02 03:18 (UTC)

$HOME/.cache/oh-my-zsh +1

ilpianista commented on 2016-08-25 17:42 (UTC)

Hi, why not using $HOME/.cache/oh-my-zsh as ZSH_CACHE_DIR?

vltr commented on 2016-06-13 12:32 (UTC)

A patch for PKGBUILD, if someone need it for the license file :)

johnramsden commented on 2016-05-15 01:16 (UTC) (edited on 2016-05-15 01:16 (UTC) by johnramsden)

The file MIT-LICENSE.txt no longer exists, needs to be changed in PKGBUILD to LICENSE.txt.

pingplug commented on 2016-05-14 01:06 (UTC)

MIT-LICENSE.txt is renamed to LICENSE.txt

madalin commented on 2016-02-21 14:05 (UTC) (edited on 2016-02-21 14:18 (UTC) by madalin)

To do a proper setup: Copy the contents of /usr/share/oh-my-zsh/zshrc to your ~/.zshrc Modify to your heart's desire.

toketin commented on 2016-01-05 18:53 (UTC)

Ok worked, thanks @luolimao!

luolimao commented on 2016-01-05 03:03 (UTC)

@toketin Try deleting the temp folder and rebuilding; I can't replicate your issue, but googling indicates that your error usually comes up when the .git/ folder is corrupted somehow, so a clean rebuild should pull the proper .git/ from the repository.

toketin commented on 2016-01-02 16:02 (UTC) (edited on 2016-01-02 16:04 (UTC) by toketin)

I can't update it since (with packer -Syu): "fatal: Not a git repository (or any parent up to mount point /tmp) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set)"

manuelschneid3r commented on 2015-10-26 10:47 (UTC)

Please make a wiki entry. I cant get it to work. After following the patches in the comments here I get: no matches found: /lib/*.zsh.

manuelschneid3r commented on 2015-10-26 10:47 (UTC)

Please make a wiki entry. I cant get it to work. After following the patches in the comments here I get: no matches found: /lib/*.zsh.

letik commented on 2015-10-22 10:41 (UTC)

Hi ! Just wanting to give a suggestion for the PKGBUILD. Knowing that if DISABLE_AUTO_UPDATE isn't set to true before the source zsh line, it would be cool to detect if "DISABLE_AUTO_UPDATE" is set to true ( if [[ `cat .zshrc | grep "DISABLE_AUTO_UPDATE" | grep true` ]] ) and if it is set before "source $ZSH/" (don't know how in shell script). If those conditions are false, would be cool to put a warning, are automatically add this line to the .zshrc (if user accept it). What about that ? Would you want me to code it ?

commented on 2015-06-18 23:54 (UTC)

well starting for reduce the description, the package guideliness state that description'll below 80 characters, this description is complete but SO LONG.

gat commented on 2015-06-16 08:16 (UTC)

I'm sorry jyantis, it's all good.

jyantis commented on 2015-06-16 05:45 (UTC)

Gat - I am unsure what needs updating since this is a git based pkgbuild and should auto handle it. Is there something specific you believe needs to be done?

gat commented on 2015-06-16 03:14 (UTC)

Could you please update when you have a minute? is annoying :)

bcc commented on 2015-04-10 10:50 (UTC)

Ah, great. Thank you jyantis.

jswagner commented on 2015-04-03 19:47 (UTC)

@jyantis Yup, thanks!

jyantis commented on 2015-04-03 16:52 (UTC)

Jswagner: This happens because the variable DISABLE_AUTO_UPDATE either doesn't exist in your zshrc or is after the sourcing of /usr/share/oh-my-zsh/ For new installs this is automatically setup for you in the: /usr/share/oh-my-zsh/zshrc file that you copy over to ~/.zshrc This wasn't noticeable before because the old PKGBUILD simply left that file in there so instead of you being alerted of an issue it just ran that bit of code every time. At least this way you know where to properly put the sourcing line. Your .zshrc file should have something that looks like this. In this order. ZSH=/usr/share/oh-my-zsh/ DISABLE_AUTO_UPDATE="true" ZSH_CACHE_DIR=$HOME/.oh-my-zsh-cache if [[ ! -d $ZSH_CACHE_DIR ]]; then mkdir $ZSH_CACHE_DIR fi source $ZSH/

jswagner commented on 2015-04-03 07:46 (UTC)

Getting this message whenever a zsh session starts: zsh: can't open input file: /usr/share/oh-my-zsh/tools/

jyantis commented on 2015-04-02 15:40 (UTC)

Sc0rian - I went ahead and removed the conflict for grml-zsh-config please let me know if you have any issues and I will see if I can find some type of workaround.

bcc commented on 2015-04-02 13:22 (UTC)

its a shame that grml-zsh-config conflicts, I used to enjoy running both.

jyantis commented on 2015-03-25 11:19 (UTC)

The cache issue was fixed. See this thread:

jyantis commented on 2015-03-22 05:30 (UTC)

yochaigal - There are two ways to solve this. 1) set ZSH_CACHE_DIR="/tmp/zsh_cache" or your directory of choosing in your .zshrc file 2) sudo chmod 777 /usr/share/oh-my-zsh I am hesitant about setting such permissive permissions if there is away around it so I opted with a message on the post install that recommends people add this line to their .zshrc: ZSH_CACHE_DIR="/tmp/zsh_cache" I should probably change the template as well but would like some feedback first.

jyantis commented on 2015-03-22 02:40 (UTC)

I saw this was orphaned so I picked it up. chuckdaniels: I added your request on the conflicts.

yochaigal commented on 2015-03-22 02:19 (UTC)

I'm getting this error: _store_cache:46: permission denied: /usr/share/oh-my-zsh//cache//modules-3.19.1-1-ck When I try certain commands as root. I created an issue in oh-my-zsh github, here: Maybe something with the linux-ck modules?

chuckdaniels commented on 2015-03-19 12:17 (UTC)

It seems that there are compatibility problems with "grml-zsh-config" package (changing themes, etc.). Maybe that package could be added in PKGBUILD as conflictive.

Nefelim4ag commented on 2015-02-20 20:37 (UTC)

@tjaart, okay, i've updated package.

tjaart commented on 2015-02-20 19:11 (UTC)

When I tried to install the package, it would not clone the git repository. It would just sort of stall on the clone step and not return. I changed the following line in the PKGBUILD: source=("$_gitname::git://") to source=("git+") I am not sure what the exact purpose is of the original line, but from other PKGBUILD files I have seen, the replacement may be a cleaner solution.

orschiro commented on 2014-12-01 10:03 (UTC)

@vvo This alone does not work for me. Anyone with the same problem?

vvo commented on 2014-12-01 09:25 (UTC)

In the meantime, you can add `unset GREP_OPTIONS` at the end of ~/.zshrc

orschiro commented on 2014-11-27 14:21 (UTC)

@vvo Thanks! Expecting the fix to hit the master repo soon.

vvo commented on 2014-11-27 09:23 (UTC)

@orschiro it seems to have been discussed/ficed/in the work on the github repo:

orschiro commented on 2014-11-26 09:29 (UTC)

Anyone else getting the following error message since the latest update of grep? grep: warning: GREP_OPTIONS is deprecated; please use an alias or script I guess the option is somewhere used within (oh-my)zsh. Does someone know how to fix it?

orschiro commented on 2014-10-01 19:11 (UTC)

@balki Just leave the others where they are. Your zshrc will reference to them as far as I know.

commented on 2014-10-01 12:22 (UTC)

I installed this package. I am confused with the the following files /usr/share/oh-my-zsh/ /usr/share/oh-my-zsh/templates/zshrc.zsh-template /usr/share/oh-my-zsh/zshrc The README file asks to copy the template file as my .zshrc. It is not clear what do we have the other two files. Can someone explain?

commented on 2014-03-30 21:58 (UTC)

Hi @dlh, You should get an update via the regular method (without --devel) which should take you to the latest version of the package. Thanks, Jamie

dlh commented on 2014-03-30 19:23 (UTC)

I cannot upgrade to the latest git version with yaourt -Syua --devel, I am receiving the message the I have the latest version which is not true.

centos commented on 2013-11-03 10:57 (UTC)

Hello, thank you for the info and your effort. Jan

commented on 2013-11-03 08:19 (UTC)

Hello @centos, When I use yaourt with the '--devel' flag, I get all of my git packages updating every time, even when already up to date. Whenever there is a new commit on github for this package, I'll update the pkgver so that it is be updated using the regular 'yaourt -Syua'. Thanks, Jamie

centos commented on 2013-11-02 08:34 (UTC)

Hello jcsiv, oh-my-zsh-git still shows up: ==> upgrading SVN/CVS/HG/GIT package Targets (3): oh-my-zsh-git powerdown-git powerstat-git ==> Proceed with upgrade? [Y/n] BUT, after the change you made it also showed up in 'regular' update (yaourt -Syua) and succesfully updated itself. So maybe using 'yaourt -Syua --devel' is not such a good idea and '--devel' is causing this trouble? Or maybe I totally misunderstood its purpose? Thanks, Jan

commented on 2013-11-01 10:16 (UTC)

Hello @centos, Sorry for the slow reply, I've been away for a few days. I'm going to modify the pkgver to the current version and then upload that pkgbuild. Hopefully that should solve the problem for now. Thanks, Jamie

centos commented on 2013-10-27 14:48 (UTC)

Hi, I tried to change pkgver to 1982.something and ended up with 1975.90c28b7-1 after install, so changing pkgver basically does nothing (looks like you are in this pkbuild trying to do the same thing -- change pkgver to 1949.61e3951-1). Last changes to this git were made two days ago, so maybe this pkbuild is outdated..? Just an assumption, I'm not really familiar with git stuff. I also tried pacaur which installed same version as yaourt. And according to this post yaourt checks pkgver in installed package at every update and compares it with pkgver in pkbuild from AUR. So if the version installed from git (1975.90c28b7-1) differs from the one in pkbuild (currently 1949.61e3951-1), yaourt will try to update that package every time, regardless that installed version is actually more recent. This could be it, don't you think? Thanks, Jan

commented on 2013-10-27 09:53 (UTC)

Hello @centos, I have done the same and now my version is the same as yours. What does modifying the pkgbuild pkgver during installation do? Does using a different AUR helper (i.e. pacaur like elpasi) solve the problem (I'm not suggesting you do that permanently, just to help us diagnose.)? Thanks, Jamie

centos commented on 2013-10-27 09:14 (UTC)

Hello jcsiv, that's weird. I removed oh-my-zsh-git (pacman -R) and installed it again. The problem persists and version installed changed: aur/oh-my-zsh-git 1949.61e3951-1 [installed: 1975.90c28b7-1] (72) When I try to install it once again with yaourt, in pkbuild I see pkgname=oh-my-zsh-git pkgver=1949.61e3951 which is the version that yaourt keeps suggesting me and version that is in the package name and also version that differs from version you have installed. What do you see when "yaourt oh-my"? Thanks.

commented on 2013-10-21 16:41 (UTC)

Hello @centos, I use yaourt myself, but I don't have the same issue. I think we have the same version of the package installed: $ yaourt -Qi oh-my-zsh-git Name : oh-my-zsh-git Version : 1957.c79e5a9-1 Description : A community-driven framework for managing your zsh configuration. Architecture : any URL : Licences : MIT Groups : None Provides : None Depends On : zsh Optional Deps : ruby: for some plugin functionality Required By : None Optional For : None Conflicts With : None Replaces : None Installed Size : 594.00 KiB Packager : Unknown Packager Build Date : Mon 21 Oct 2013 17:19:55 BST Install Date : Mon 21 Oct 2013 17:20:07 BST Install Reason : Explicitly installed Install Script : Yes Validated By : None I have reinstalled the package using the latest PKGBUILD from the AUR but I still cannot replicate your problem. If there are any more developments, please contact me. Thanks, Jamie

centos commented on 2013-10-20 19:48 (UTC)

Hi, I seem to have pkgver problem with yaourt. It keeps telling me in every update that there is new version, but nothing happens after actual update. Even if I try to install it manually I end up with the same version I already had. It looks like yaourt thinks my installed version is newer than the git one and therefore it maybe doesn't make any changes. Can someone explain this to me? % i oh-my 1 aur/oh-my-zsh-git 1949.61e3951-1 [installed: 1957.c79e5a9-1] (71)

commented on 2013-09-27 18:15 (UTC)

Hello @scarpino, I've updated the PKGBUILD now to include your suggested changes. It seems to be working. If there's any issues, tell me and I'll fix them. Thanks, Jamie

ilpianista commented on 2013-09-24 07:50 (UTC)

Could you put $pkgdir between double apixes?

commented on 2013-09-21 08:35 (UTC)

I can confirm the issue's gone when using pacaur, too. Thanks a lot!

commented on 2013-09-20 20:57 (UTC)

Hello, I've updated the PKGBUILD now to include the changes suggested by @elpasi regarding the pkgver() function. Having installed this myself, it seems to be working. Feedback appreciated, any problems and I'll amend as required. Thanks, Jamie

commented on 2013-09-20 20:03 (UTC) I'd suggest changing the pkgver function for the latter Git pkgver() listed there, and then changing the one defined explicitly at the top to match the new format.

commented on 2013-09-20 20:03 (UTC) I'd suggest changing the pkgver for the latter Git pkgver listed there, and then changing the one defined at the top to match the same formatting.

commented on 2013-09-20 19:47 (UTC)

Hi everyone, I've decided to maintain this package, as I use zsh and this tool a lot. Fist I'll get on and fix the pkgver() problems. Feel free to send me an improved pkgbuild. Thanks, Jamie

phoenixlzx commented on 2013-09-20 16:32 (UTC)

Hi @elpasi and @scarpino, I'm sorry for too busy to take care of my packages.. I'm going to disown this package, so if anyone is interesting in maintaining, please go ahead. Thank you guys.

commented on 2013-09-20 15:19 (UTC)

I've really flagged this for the same reason as scarpino's message below. If you update this, you get a weird pkgver inconsistency (20130716_2cc4801-1 v 61e3951-1) which leads to pacaur asking you to update the package every time you run a pacaur -Syua. This doesn't happen with any other VCS package I have that uses pkgver() to change its version partway through.

ilpianista commented on 2013-09-10 06:53 (UTC)

I just updated and the pkgver now is dff966a, could you fix this with a proper pkgver?

ilpianista commented on 2013-07-22 09:32 (UTC)

Please put $pkgdir between double apixes, thank you.

phoenixlzx commented on 2013-04-18 12:24 (UTC)

@ThinCarrotShrimp Thank you for your PKGBUILD. I've added you as contributor, and sorry for my lack of time update these packages.

commented on 2013-04-16 19:13 (UTC)

I modified the PKGBUILD according to Changes: - add git repo to sources - let makepkg handle git clone/fetch - get package version from git - set correct license info - copy license to /usr/share/licenses/oh-my-zsh-git/LICENSE Have a look at Cheers

alphazo commented on 2013-04-08 10:21 (UTC)

Problem comes from the new prompt support in grml 0.8. Solution can be found here When using oh-my-zsh you need to add the line : prompt off in ~/.zshrc

phoenixlzx commented on 2013-04-08 09:05 (UTC)

@alphazo Hi, I dont find any conflict on my own laptop and our community compile machine, you could try install the pre-made package through our community repo: [archlinuxcn] Server =$arch If problem continues, please tell me which files are in conflict. Thank you.

alphazo commented on 2013-04-08 08:47 (UTC)

Sorry to bother you but installing oh-my-zsh-git 20130408-1 didn't fix the conflict with grml-zsh-config. Still have issues with the latest grml-zsh-config 0.8.1-1. I can only get my prompt right after downgrading grml-zsh-config to 0.7.4-1.

phoenixlzx commented on 2013-03-16 14:38 (UTC)

@Mizuchi fixed, thanks for suggestion.

ytj commented on 2013-03-16 14:18 (UTC)

conflict with package "grml-zsh-config" from official repo.