diff options
| -rwxr-xr-x | maint/release.in | 2 | ||||
| -rw-r--r-- | share/rcm.sh.in | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/maint/release.in b/maint/release.in index 1df9f97..e29e059 100755 --- a/maint/release.in +++ b/maint/release.in @@ -87,7 +87,7 @@ release_build_deb() { cp -R debian deb-build/${PACKAGE}-${PACKAGE_VERSION} && \ cd deb-build/${PACKAGE}-${PACKAGE_VERSION} && \ dch -d "New upstream release" && dch -r "" && \ - debuild --prepend-path=/usr/local/bin -e USER -F && \ + debuild --prepend-path=/usr/local/bin -F && \ cd ${abs_top_builddir} && \ ([ -d gh-pages ] || git clone --branch gh-pages ${ORIGIN_URL} gh-pages) && \ ([ -d gh-pages/debs ] || mkdir gh-pages/debs) && \ diff --git a/share/rcm.sh.in b/share/rcm.sh.in index c7a3dfb..ed5d6f9 100644 --- a/share/rcm.sh.in +++ b/share/rcm.sh.in @@ -130,7 +130,7 @@ run_hooks() { # The former is however a bit better when it comes to security. On the other hand # running these hooks imply some level of trust; surely one doesn't clone somebody # else's dotfiles repository without reviewing the hooks before doing an `rcup`? - find "$hook_file" -type f \( \( -user $USER -perm -100 \) -o -perm -001 \) \ + find "$hook_file" -type f \( \( -user $LOGNAME -perm -100 \) -o -perm -001 \) \ -exec \ sh -c 'cd "`dirname $1`" && ./"`basename $1`"' arg0 '{}' \ \; |