Nabble - ArchLinux

[PATCH 1/2] Changing [ to [[ and (( - Part One - Amended to remove quotes

2009-11-12T15:09:23Z

This branch is missing the latest origin/master commit (Merge branch 'maint'). I'm not sure if (1) that is a problem and (2) what I should do about it. (merge origin/master? rebase origin/master?)

After Cedric's reply I cleaned up some quotes left behind and replaced the ones removed in error.

>From 6375a17a0fefbb5cfc55e15c1e940e74f8498d97 Mon Sep 17 00:00:00 2001
From: Isaac Good <pacman@...>
Date: Thu, 12 Nov 2009 15:07:34 -0500
Subject: [PATCH 1/2] Changing [ to [[ and (( - Part One - Amended to remove quotes

First half of makepkg
This replaces any prior patches of mine
Includes stuff like -o to || and -a to && etc
if [ $(type .. were preserved due to a bash bug with [[ and set -e and ERR traps

Signed-off-by: Isaac Good <pacman@...>
---
scripts/makepkg.sh.in | 202 ++++++++++++++++++++++++------------------------
1 files changed, 101 insertions(+), 101 deletions(-)

diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in
index 25fb8d9..f22b0d0 100644
--- a/scripts/makepkg.sh.in
+++ b/scripts/makepkg.sh.in
@@ -112,7 +112,7 @@ error() {
# the fakeroot call, the error message will be printed by the main call.
##
trap_exit() {
- if [ "$INFAKEROOT" -eq 0 ]; then
+ if (( ! INFAKEROOT )); then
echo
error "$@"
fi
@@ -126,21 +126,21 @@ trap_exit() {
clean_up() {
local EXIT_CODE=$?

- if [ "$INFAKEROOT" -eq 1 ]; then
+ if (( INFAKEROOT )); then
# Don't clean up when leaving fakeroot, we're not done yet.
return
fi

- if [ $EXIT_CODE -eq 0 -a "$CLEANUP" -eq 1 ]; then
+ if (( ! EXIT_CODE && CLEANUP )); then
# If it's a clean exit and -c/--clean has been passed...
msg "$(gettext "Cleaning up...")"
rm -rf "$pkgdir" "$srcdir"
- if [ -n "$pkgbase" ]; then
+ if [[ -n $pkgbase ]]; then
# Can't do this unless the BUILDSCRIPT has been sourced.
rm -f "${pkgbase}-${pkgver}-${pkgrel}-${CARCH}-build.log"*
- if [ "$PKGFUNC" -eq 1 ]; then
+ if (( PKGFUNC )); then
rm -f "${pkgbase}-${pkgver}-${pkgrel}-${CARCH}-package.log"*
- elif [ "$SPLITPKG" -eq 1 ]; then
+ elif (( SPLITPKG )); then
for pkg in ${pkgname[@]}; do
rm -f "${pkg}-${pkgver}-${pkgrel}-${CARCH}-package.log"*
done
@@ -190,14 +190,14 @@ get_url() {
##
check_option() {
local ret=$(in_opt_array "$1" ${options[@]})
- if [ "$ret" != '?' ]; then
+ if [[ $ret != '?' ]]; then
echo $ret
return
fi

# fall back to makepkg.conf options
ret=$(in_opt_array "$1" ${OPTIONS[@]})
- if [ "$ret" != '?' ]; then
+ if [[ $ret != '?' ]]; then
echo $ret
return
fi
@@ -231,10 +231,10 @@ in_opt_array() {
local opt
for opt in "$@"; do
opt="${opt,,}"
- if [ "$opt" = "$needle" ]; then
+ if [[ $opt = $needle ]]; then
echo 'y' # Enabled
return
- elif [ "$opt" = "!$needle" ]; then
+ elif [[ $opt = "!$needle" ]]; then
echo 'n' # Disabled
return
fi
@@ -251,10 +251,10 @@ in_opt_array() {
##
in_array() {
local needle=$1; shift
- [ -z "$1" ] && return 1 # Not Found
+ [[ -z $1 ]] && return 1 # Not Found
local item
for item in "$@"; do
- [ "$item" = "$needle" ] && return 0 # Found
+ [[ $item = $needle ]] && return 0 # Found
done
return 1 # Not Found
}
@@ -268,14 +268,14 @@ get_downloadclient() {
local i
for i in "${DLAGENTS[@]}"; do
local handler="${i%%::*}"
- if [ "$proto" = "$handler" ]; then
+ if [[ $proto = $handler ]]; then
agent="${i##*::}"
break
fi
done

# if we didn't find an agent, return an error
- if [ -z "$agent" ]; then
+ if [[ -z $agent ]]; then
error "$(gettext "There is no agent set up to handle %s URLs. Check %s.")" "$proto" "$MAKEPKG_CONF"
plain "$(gettext "Aborting...")"
exit 1 # $E_CONFIG_ERROR
@@ -283,7 +283,7 @@ get_downloadclient() {

# ensure specified program is installed
local program="${agent%% *}"
- if [ ! -x "$program" ]; then
+ if [[ ! -x $program ]]; then
local baseprog=$(basename $program)
error "$(gettext "The download program %s is not installed.")" "$baseprog"
plain "$(gettext "Aborting...")"
@@ -317,25 +317,25 @@ download_file() {

local ret=0
eval "$dlcmd || ret=\$?"
- if [ $ret -gt 0 ]; then
- [ ! -s "$dlfile" ] && rm -f -- "$dlfile"
+ if (( ret )); then
+ [[ ! -s $dlfile ]] && rm -f -- "$dlfile"
return $ret
fi

# rename the temporary download file to the final destination
- if [ "$dlfile" != "$file" ]; then
+ if [[ $dlfile != $file ]]; then
mv -f "$SRCDEST/$dlfile" "$SRCDEST/$file"
fi
}

check_deps() {
- [ $# -gt 0 ] || return
+ (( $# )) || return

pmout=$(pacman $PACMAN_OPTS -T "$@")
ret=$?
- if [ $ret -eq 127 ]; then #unresolved deps
+ if (( ret == 127 )); then #unresolved deps
echo "$pmout"
- elif [ $ret -ne 0 ]; then
+ elif (( ret )); then
error "$(gettext "Pacman returned a fatal error (%i): %s")" "$ret" "$pmout"
exit 1
fi
@@ -345,26 +345,26 @@ handle_deps() {
local R_DEPS_SATISFIED=0
local R_DEPS_MISSING=1

- [ $# -eq 0 ] && return $R_DEPS_SATISFIED
+ (( $# == 0 )) && return $R_DEPS_SATISFIED

local deplist="$*"

- if [ "$DEP_BIN" -eq 0 ]; then
+ if (( ! DEP_BIN )); then
return $R_DEPS_MISSING
fi

- if [ "$DEP_BIN" -eq 1 ]; then
+ if (( DEP_BIN )); then
# install missing deps from binary packages (using pacman -S)
msg "$(gettext "Installing missing dependencies...")"
local ret=0

- if [ "$ASROOT" -eq 0 ]; then
+ if (( ! ASROOT )); then
sudo pacman $PACMAN_OPTS -S --asdeps $deplist || ret=$?
else
pacman $PACMAN_OPTS -S --asdeps $deplist || ret=$?
fi

- if [ $ret -ne 0 ]; then
+ if (( ret )); then
error "$(gettext "Pacman failed to install missing dependencies.")"
exit 1 # TODO: error code
fi
@@ -385,7 +385,7 @@ resolve_deps() {
local R_DEPS_MISSING=1

local deplist="$(check_deps $*)"
- if [ -z "$deplist" ]; then
+ if [[ -z $deplist ]]; then
return $R_DEPS_SATISFIED
fi

@@ -393,8 +393,8 @@ resolve_deps() {
pkgdeps="$pkgdeps $deplist"
# check deps again to make sure they were resolved
deplist="$(check_deps $*)"
- [ -z "$deplist" ] && return $R_DEPS_SATISFIED
- elif [ "$DEP_BIN" -eq 1 ]; then
+ [[ -z $deplist ]] && return $R_DEPS_SATISFIED
+ elif (( DEP_BIN )); then
error "$(gettext "Failed to install all missing dependencies.")"
fi

@@ -410,8 +410,8 @@ resolve_deps() {
# fix flyspray bug #5923
remove_deps() {
# $pkgdeps is a GLOBAL variable, set by resolve_deps()
- [ "$RMDEPS" -eq 0 ] && return
- [ -z "$pkgdeps" ] && return
+ (( ! RMDEPS )) && return
+ [[ -z $pkgdeps ]] && return

local dep depstrip deplist
deplist=""
@@ -422,14 +422,14 @@ remove_deps() {

msg "Removing installed dependencies..."
local ret=0
- if [ "$ASROOT" -eq 0 ]; then
+ if (( ! ASROOT )); then
sudo pacman $PACMAN_OPTS -Rns $deplist || ret=$?
else
pacman $PACMAN_OPTS -Rns $deplist || ret=$?
fi

# Fixes FS#10039 - exit cleanly as package has built successfully
- if [ $ret -ne 0 ]; then
+ if (( ret )); then
warning "$(gettext "Failed to remove installed dependencies.")"
return 0
fi
@@ -438,7 +438,7 @@ remove_deps() {
download_sources() {
msg "$(gettext "Retrieving Sources...")"

- if [ ! -w "$SRCDEST" ] ; then
+ if [[ ! -w $SRCDEST ]] ; then
error "$(gettext "You do not have write permission to store downloads in %s.")" "$SRCDEST"
plain "$(gettext "Aborting...")"
exit 1
@@ -450,12 +450,12 @@ download_sources() {
for netfile in "${source[@]}"; do
local file=$(get_filename "$netfile")
local url=$(get_url "$netfile")
- if [ -f "$startdir/$file" ]; then
+ if [[ -f $startdir/$file ]]; then
msg2 "$(gettext "Found %s in build dir")" "$file"
rm -f "$srcdir/$file"
ln -s "$startdir/$file" "$srcdir/"
continue
- elif [ -f "$SRCDEST/$file" ]; then
+ elif [[ -f $SRCDEST/$file ]]; then
msg2 "$(gettext "Using cached copy of %s")" "$file"
rm -f "$srcdir/$file"
ln -s "$SRCDEST/$file" "$srcdir/"
@@ -463,7 +463,7 @@ download_sources() {
fi

# if we get here, check to make sure it was a URL, else fail
- if [ "$file" = "$url" ]; then
+ if [[ $file = $url ]]; then
error "$(gettext "%s was not found in the build directory and is not a URL.")" "$file"
exit 1 # $E_MISSING_FILE
fi
@@ -475,7 +475,7 @@ download_sources() {
# fix flyspray bug #3289
local ret=0
download_file "$dlclient" "$url" "$file" || ret=$?
- if [ $ret -gt 0 ]; then
+ if (( ret )); then
error "$(gettext "Failure while downloading %s")" "$file"
plain "$(gettext "Aborting...")"
exit 1
@@ -512,7 +512,7 @@ generate_checksums() {

local i=0;
local indent=''
- while [ $i -lt $((${#integ}+6)) ]; do
+ while [[ $i -lt $((${#integ}+6)) ]]; do
indent="$indent "
i=$(($i+1))
done
@@ -521,8 +521,8 @@ generate_checksums() {
for netfile in "${source[@]}"; do
local file="$(get_filename "$netfile")"

- if [ ! -f "$file" ] ; then
- if [ ! -f "$SRCDEST/$file" ] ; then
+ if [[ ! -f $file ]] ; then
+ if [[ ! -f $SRCDEST/$file ]] ; then
error "$(gettext "Unable to find source file %s to generate checksum.")" "$file"
plain "$(gettext "Aborting...")"
exit 1
@@ -533,10 +533,10 @@ generate_checksums() {

local sum="$(openssl dgst -${integ} "$file")"
sum=${sum##* }
- [ $ct -gt 0 ] && echo -n "$indent"
+ (( ct )) && echo -n "$indent"
echo -n "'$sum'"
ct=$(($ct+1))
- [ $ct -lt $numsrc ] && echo
+ (( $ct < $numsrc )) && echo
done

echo ")"
@@ -544,7 +544,7 @@ generate_checksums() {
}

check_checksums() {
- [ ${#source[@]} -eq 0 ] && return 0
+ (( ! ${#source[@]} )) && return 0

if [ ! $(type -p openssl) ]; then
error "$(gettext "Cannot find openssl.")"
@@ -555,7 +555,7 @@ check_checksums() {
local integ required
for integ in md5 sha1 sha256 sha384 sha512; do
local integrity_sums=($(eval echo "\${${integ}sums[@]}"))
- if [ ${#integrity_sums[@]} -eq ${#source[@]} ]; then
+ if (( ${#integrity_sums[@]} == ${#source[@]} )); then
msg "$(gettext "Validating source files with %s...")" "${integ}sums"
correlation=1
local errors=0
@@ -566,8 +566,8 @@ check_checksums() {
file="$(get_filename "$file")"
echo -n " $file ... " >&2

- if [ ! -f "$file" ] ; then
- if [ ! -f "$SRCDEST/$file" ] ; then
+ if [[ ! -f $file ]] ; then
+ if [[ ! -f $SRCDEST/$file ]] ; then
echo "$(gettext "NOT FOUND")" >&2
errors=1
found=0
@@ -576,11 +576,11 @@ check_checksums() {
fi
fi

- if [ $found -gt 0 ] ; then
+ if (( $found )) ; then
local expectedsum="${integrity_sums[$idx],,}"
local realsum="$(openssl dgst -${integ} "$file")"
realsum="${realsum##* }"
- if [ "$expectedsum" = "$realsum" ]; then
+ if [[ $expectedsum = $realsum ]]; then
echo "$(gettext "Passed")" >&2
else
echo "$(gettext "FAILED")" >&2
@@ -591,18 +591,18 @@ check_checksums() {
idx=$((idx + 1))
done

- if [ $errors -gt 0 ]; then
+ if (( errors )); then
error "$(gettext "One or more files did not pass the validity check!")"
exit 1 # TODO: error code
fi
- elif [ ${#integrity_sums[@]} -gt 0 ]; then
+ elif (( ${#integrity_sums[@]} )); then
error "$(gettext "Integrity checks (%s) differ in size from the source array.")" "$integ"
exit 1 # TODO: error code
fi
done

- if [ $correlation -eq 0 ]; then
- if [ $SKIPINTEG -eq 1 ]; then
+ if (( ! correlation )); then
+ if (( SKIPINTEG )); then
warning "$(gettext "Integrity checks are missing.")"
else
error "$(gettext "Integrity checks are missing.")"
@@ -622,8 +622,8 @@ extract_sources() {
continue
fi

- if [ ! -f "$file" ] ; then
- if [ ! -f "$SRCDEST/$file" ] ; then
+ if [[ ! -f $file ]] ; then
+ if [[ ! -f $SRCDEST/$file ]] ; then
error "$(gettext "Unable to find source file %s for extraction.")" "$file"
plain "$(gettext "Aborting...")"
exit 1
@@ -662,31 +662,31 @@ extract_sources() {

local ret=0
msg2 "$(gettext "Extracting %s with %s")" "$file" "$cmd"
- if [ "$cmd" = "bsdtar" ]; then
+ if [[ $cmd = bsdtar ]]; then
$cmd -xf "$file" || ret=?
else
rm -f "${file%.*}"
$cmd -dcf "$file" > "${file%.*}" || ret=?
fi
- if [ $ret -ne 0 ]; then
+ if (( ret )); then
error "$(gettext "Failed to extract %s")" "$file"
plain "$(gettext "Aborting...")"
exit 1
fi
done

- if [ $EUID -eq 0 ]; then
+ if (( EUID == 0 )); then
# change perms of all source files to root user & root group
chown -R 0:0 "$srcdir"
fi
}

error_function() {
- if [ -p "$logpipe" ]; then
+ if [[ -p $logpipe ]]; then
rm "$logpipe"
fi
# first exit all subshells, then print the error
- if [ $BASH_SUBSHELL -eq 0 ]; then
+ if (( ! BASH_SUBSHELL )); then
plain "$(gettext "Aborting...")"
remove_deps
fi
@@ -694,13 +694,13 @@ error_function() {
}

run_function() {
- if [ -z "$1" ]; then
+ if [[ -z $1 ]]; then
return 1
fi
pkgfunc="$1"

# clear user-specified makeflags if requested
- if [ "$(check_option makeflags)" = "n" ]; then
+ if [[ $(check_option makeflags) = "n" ]]; then
MAKEFLAGS=""
fi

@@ -713,12 +713,12 @@ run_function() {
local shellopts=$(shopt -p)

local ret=0
- if [ "$LOGGING" -eq 1 ]; then
+ if (( LOGGING )); then
BUILDLOG="${startdir}/${pkgname}-${pkgver}-${pkgrel}-${CARCH}-$pkgfunc.log"
- if [ -f "$BUILDLOG" ]; then
+ if [[ -f $BUILDLOG ]]; then
local i=1
while true; do
- if [ -f "$BUILDLOG.$i" ]; then
+ if [[ -f $BUILDLOG.$i ]]; then
i=$(($i +1))
else
break
@@ -752,24 +752,24 @@ run_function() {

run_build() {
# use distcc if it is requested (check buildenv and PKGBUILD opts)
- if [ "$(check_buildenv distcc)" = "y" -a "$(check_option distcc)" != "n" ]; then
- [ -d /usr/lib/distcc/bin ] && export PATH="/usr/lib/distcc/bin:$PATH"
+ if [[ $(check_buildenv distcc) = "y" && $(check_option distcc) != "n" ]]; then
+ [[ -d /usr/lib/distcc/bin ]] && export PATH="/usr/lib/distcc/bin:$PATH"
export DISTCC_HOSTS
- elif [ "$(check_option distcc)" = "n" ]; then
+ elif [[ $(check_option distcc) = "n" ]]; then
# if it is not wanted, clear the makeflags too
MAKEFLAGS=""
fi

# use ccache if it is requested (check buildenv and PKGBUILD opts)
- if [ "$(check_buildenv ccache)" = "y" -a "$(check_option ccache)" != "n" ]; then
- [ -d /usr/lib/ccache/bin ] && export PATH="/usr/lib/ccache/bin:$PATH"
+ if [[ $(check_buildenv ccache) = "y" && $(check_option ccache) != "n" ]]; then
+ [[ -d /usr/lib/ccache/bin ]] && export PATH="/usr/lib/ccache/bin:$PATH"
fi

run_function "build"
}

run_package() {
- if [ -z "$1" ]; then
+ if [[ -z $1 ]]; then
pkgfunc="package"
else
pkgfunc="package_$1"
@@ -782,16 +782,16 @@ tidy_install() {
cd "$pkgdir"
msg "$(gettext "Tidying install...")"

- if [ "$(check_option docs)" = "n" -a -n "${DOC_DIRS[*]}" ]; then
+ if [[ $(check_option docs) = "n" && -n ${DOC_DIRS[*]} ]]; then
msg2 "$(gettext "Removing doc files...")"
rm -rf ${DOC_DIRS[@]}
fi

- if [ "$(check_option purge)" = "y" -a -n "${PURGE_TARGETS[*]}" ]; then
+ if [[ $(check_option purge) = "y" && -n ${PURGE_TARGETS[*]} ]]; then
msg2 "$(gettext "Purging other files...")"
local pt
for pt in "${PURGE_TARGETS[@]}"; do
- if [ "${pt}" = "${pt//\/}" ]; then
+ if [[ ${pt} = ${pt//\/} ]]; then
find . -type f -name "${pt}" -exec rm -f -- '{}' \;
else
rm -f ${pt}
@@ -799,16 +799,16 @@ tidy_install() {
done
fi

- if [ "$(check_option zipman)" = "y" -a -n "${MAN_DIRS[*]}" ]; then
+ if [[ $(check_option zipman) = "y" && -n ${MAN_DIRS[*]} ]]; then
msg2 "$(gettext "Compressing man and info pages...")"
local manpage ext file link hardlinks hl
find ${MAN_DIRS[@]} -type f 2>/dev/null |
while read manpage ; do
# check file still exists (potentially compressed with hard link)
- if [ -f ${manpage} ]; then
+ if [[ -f ${manpage} ]]; then
ext="${manpage##*.}"
file="${manpage##*/}"
- if [ "$ext" != "gz" -a "$ext" != "bz2" ]; then
+ if [[ $ext != gz && $ext != bz2 ]]; then
# update symlinks to this manpage
find ${MAN_DIRS[@]} -lname "$file" 2>/dev/null |
while read link ; do
@@ -834,7 +834,7 @@ tidy_install() {
done
fi

- if [ "$(check_option strip)" = "y" -a -n "${STRIP_DIRS[*]}" ]; then
+ if [[ $(check_option strip) = y && -n ${STRIP_DIRS[*]} ]]; then
msg2 "$(gettext "Stripping debugging symbols from binaries and libraries...")"
local binary
find ${STRIP_DIRS[@]} -type f 2>/dev/null | while read binary ; do
@@ -851,12 +851,12 @@ tidy_install() {
done
fi

- if [ "$(check_option libtool)" = "n" ]; then
+ if [[ $(check_option libtool) = "n" ]]; then
msg2 "$(gettext "Removing libtool .la files...")"
find . ! -type d -name "*.la" -exec rm -f -- '{}' \;
fi

- if [ "$(check_option emptydirs)" = "n" ]; then
+ if [[ $(check_option emptydirs) = "n" ]]; then
msg2 "$(gettext "Removing empty directories...")"
find . -depth -type d -empty -delete
fi
@@ -864,7 +864,7 @@ tidy_install() {

write_pkginfo() {
local builddate=$(date -u "+%s")
- if [ -n "$PACKAGER" ]; then
+ if [[ -n $PACKAGER ]]; then
local packager="$PACKAGER"
else
local packager="Unknown Packager"
@@ -874,12 +874,12 @@ write_pkginfo() {

msg2 "$(gettext "Generating .PKGINFO file...")"
echo "# Generated by makepkg $myver" >.PKGINFO
- if [ "$INFAKEROOT" -eq 1 ]; then
+ if (( INFAKEROOT )); then
echo "# using $(fakeroot -v)" >>.PKGINFO
fi
echo "# $(LC_ALL=C date -u)" >>.PKGINFO
echo "pkgname = $1" >>.PKGINFO
- [ "$SPLITPKG" -eq 1 ] && echo "pkgbase = $pkgbase" >>.PKGINFO
+ (( SPLITPKG )) && echo pkgbase = $pkgbase >>.PKGINFO
echo "pkgver = $pkgver-$pkgrel" >>.PKGINFO
echo "pkgdesc = $pkgdesc" >>.PKGINFO
echo "url = $url" >>.PKGINFO
@@ -887,7 +887,7 @@ write_pkginfo() {
echo "packager = $packager" >>.PKGINFO
echo "size = $size" >>.PKGINFO
echo "arch = $PKGARCH" >>.PKGINFO
- if [ "$(check_option force)" = "y" ]; then
+ if [[ $(check_option force) = "y" ]]; then
echo "force = true" >> .PKGINFO
fi

@@ -918,8 +918,8 @@ write_pkginfo() {
done
for it in "${packaging_options[@]}"; do
local ret="$(check_option $it)"
- if [ "$ret" != "?" ]; then
- if [ "$ret" = "y" ]; then
+ if [[ $ret != "?" ]]; then
+ if [[ $ret = y ]]; then
echo "makepkgopt = $it" >>.PKGINFO
else
echo "makepkgopt = !$it" >>.PKGINFO
@@ -929,7 +929,7 @@ write_pkginfo() {

# TODO maybe remove this at some point
# warn if license array is not present or empty
- if [ -z "$license" ]; then
+ if [[ -z $license ]]; then
warning "$(gettext "Please add a license line to your %s!")" "$BUILDSCRIPT"
plain "$(gettext "Example for GPL\'ed software: license=('GPL').")"
fi
@@ -941,14 +941,14 @@ check_package() {
# check existence of backup files
local file
for file in "${backup[@]}"; do
- if [ ! -f "$file" ]; then
+ if [[ ! -f $file ]]; then
warning "$(gettext "Invalid backup entry : %s")" "$file"
fi
done
}

create_package() {
- if [ ! -d "$pkgdir" ]; then
+ if [[ ! -d $pkgdir ]]; then
error "$(gettext "Missing pkg/ directory.")"
plain "$(gettext "Aborting...")"
exit 1 # $E_MISSING_PKGDIR
@@ -959,13 +959,13 @@ create_package() {
cd "$pkgdir"
msg "$(gettext "Creating package...")"

- if [ -z "$1" ]; then
+ if [[ -z $1 ]]; then
nameofpkg="$pkgname"
else
nameofpkg="$1"
fi

- if [ "$arch" = "any" ]; then
+ if [[ $arch = "any" ]]; then
PKGARCH="any"
else
PKGARCH=$CARCH
@@ -976,14 +976,14 @@ create_package() {
local comp_files=".PKGINFO"

# check for an install script
- if [ -n "$install" ]; then
+ if [[ -n $install ]]; then
msg2 "$(gettext "Adding install script...")"
cp "$startdir/$install" .INSTALL
comp_files="$comp_files .INSTALL"
fi

# do we have a changelog?
- if [ -n "$changelog" ]; then
+ if [[ -n $changelog ]]; then
msg2 "$(gettext "Adding package changelog...")"
cp "$startdir/$changelog" .CHANGELOG
comp_files="$comp_files .CHANGELOG"
@@ -1009,7 +1009,7 @@ create_package() {
bsdtar -cf - $comp_files * > "$pkg_file" || ret=$?
shopt -u nullglob

- if [ $ret -eq 0 ]; then
+ if (( ! ret )); then
case "$PKGEXT" in
*tar.gz) gzip -f -n "$pkg_file" ;;
*tar.bz2) bzip2 -f "$pkg_file" ;;
@@ -1018,7 +1018,7 @@ create_package() {
ret=$?
fi

- if [ $ret -ne 0 ]; then
+ if (( ret )); then
error "$(gettext "Failed to create package file.")"
exit 1 # TODO: error code
fi
@@ -1042,8 +1042,8 @@ create_srcpackage() {
msg2 "$(gettext "Adding %s...")" "$BUILDSCRIPT"
ln -s "${BUILDFILE}" "${srclinks}/${pkgbase}/${BUILDSCRIPT}"

- if [ -n "$install" ]; then
- if [ -f $install ]; then
+ if [[ -n $install ]]; then
+ if [[ -f $install ]]; then
msg2 "$(gettext "Adding install script...")"
ln -s "${startdir}/$install" "${srclinks}/${pkgbase}/"
else
@@ -1051,8 +1051,8 @@ create_srcpackage() {
fi
fi

- if [ -n "$changelog" ]; then
- if [ -f "$changelog" ]; then
+ if [[ -n $changelog ]]; then
+ if [[ -f $changelog ]]; then
msg2 "$(gettext "Adding package changelog...")"
ln -s "${startdir}/$changelog" "${srclinks}/${pkgbase}/"
else
@@ -1063,10 +1063,10 @@ create_srcpackage() {
local netfile
for netfile in "${source[@]}"; do
local file=$(get_filename "$netfile")
- if [ -f "$netfile" ]; then
+ if [[ -f $netfile ]]; then
msg2 "$(gettext "Adding %s...")" "$netfile"
ln -s "${startdir}/$netfile" "${srclinks}/${pkgbase}"
- elif [ "$SOURCEONLY" -eq 2 -a -f "$SRCDEST/$file" ]; then
+ elif (( SOURCEONLY == 2 )) && [[ -f $SRCDEST/$file ]]; then
msg2 "$(gettext "Adding %s...")" "$file"
ln -s "$SRCDEST/$file" "${srclinks}/${pkgbase}/"
fi
--
1.6.5.2

From forum: pacman-dev

Re: [PATCH 1/2] Changing [ to [[ and ((

2009-11-12T15:07:04Z

Cedric Staniewski wrote:

> Isaac Good wrote:
>>> >From f40b051c1c649889a13f35965fa8f8decd505b47 Mon Sep 17 00:00:00 2001
>> From: Isaac Good <pacman@...>
>> Date: Wed, 11 Nov 2009 16:47:43 -0500
>> Subject: [PATCH 1/2] Changing [ to [[ and ((
>>
>> First half of makepkg
>> This replaces any prior patches of mine
>> Includes stuff like -o to || and -a to && etc
>> if [ $(type .. were preserved due to a bash bug with [[ and set -e and ERR traps
>>
>> Signed-off-by: Isaac Good <pacman@...>
>> ---
>
> I hope your patch do not get lost in this thread.

I have the patches marked so that they will not be lost.

>> @@ -450,12 +450,12 @@ download_sources() {
>> for netfile in "${source[@]}"; do
>> local file=$(get_filename "$netfile")
>> local url=$(get_url "$netfile")
>> - if [ -f "$startdir/$file" ]; then
>> + if [[ -f "$startdir/$file" ]]; then
>> msg2 "$(gettext "Found %s in build dir")" "$file"
>> rm -f "$srcdir/$file"
>> ln -s "$startdir/$file" "$srcdir/"
>> continue
>> - elif [ -f "$SRCDEST/$file" ]; then
>> + elif [[ -f "$SRCDEST/$file" ]]; then
>> msg2 "$(gettext "Using cached copy of %s")" "$file"
>> rm -f "$srcdir/$file"
>> ln -s "$SRCDEST/$file" "$srcdir/"
>
> We could remove the quotes here, too.
>

Hmmm... can we. I know we can when there are spaces in a single
variable, but for some reason I thought quotes were needed when joining
multiple variables like that. I could be wrong...

Allan

From forum: pacman-dev

Re: [PATCH 1/2] Changing [ to [[ and ((

2009-11-12T15:03:08Z

Isaac Good wrote:

> On Thu, Nov 12, 2009 at 07:16:41PM +0000, Cedric Staniewski wrote:
>>> @@ -450,12 +450,12 @@ download_sources() {
>>> for netfile in "${source[@]}"; do
>>> local file=$(get_filename "$netfile")
>>> local url=$(get_url "$netfile")
>>> - if [ -f "$startdir/$file" ]; then
>>> + if [[ -f "$startdir/$file" ]]; then
>>> msg2 "$(gettext "Found %s in build dir")" "$file"
>>> rm -f "$srcdir/$file"
>>> ln -s "$startdir/$file" "$srcdir/"
>>> continue
>>> - elif [ -f "$SRCDEST/$file" ]; then
>>> + elif [[ -f "$SRCDEST/$file" ]]; then
>>> msg2 "$(gettext "Using cached copy of %s")" "$file"
>>> rm -f "$srcdir/$file"
>>> ln -s "$SRCDEST/$file" "$srcdir/"
>
> What about something like this?
>> if [[ "$(check_option makeflags)" = "n" ]]; then
>
> None of the quotes are needed. I'm inclined to replace it with:
>> if [[ $(check_option makeflags) = "n" ]]; then
>
> While the quotes around n are not needed, they highlight that n is a string which appeals to me since it looks like a string as found in other languages. Or would you say to drop all the quotes.
>

Aren't the quotes around the string on the right required if it does
contain spaces? Anyway, I would prefer all such strings to be quoted so
I am happy with your suggestion.

Allan

From forum: pacman-dev

Re: [PATCH 1/2] Changing [ to [[ and ((

2009-11-12T14:37:31Z

Isaac Good wrote:
> On Thu, Nov 12, 2009 at 07:16:41PM +0000, Cedric Staniewski wrote:
>> I hope your patch do not get lost in this thread.
>
> Erm. Yeah, I hope so too. How does it get threaded?
>

I guess you hit the reply button instead of writing a new mail to
pacman-dev. At least, there is the In-Reply-To header field in your mail
header.

>>> @@ -345,26 +345,26 @@ handle_deps() {
>>> local R_DEPS_SATISFIED=0
>>> local R_DEPS_MISSING=1
>>>
>>> - [ $# -eq 0 ] && return $R_DEPS_SATISFIED
>>> + (( $# == 0 )) && return $R_DEPS_SATISFIED
>>>
>> Is there a reason why you do not use (( ! $# )) here?
>
> Some variables are used as a boolean flag in which case testing if ((VAR)) and if (( ! VAR )) reads well. The $# (and EUID) are used as integer values so it struck me as more understandable or readable in this form.
>

I am fine with that, but would it not makes sense to use (( $# > 0 ))
instead of just (( $# )) then?

>>> @@ -512,7 +512,7 @@ generate_checksums() {
>>>
>>> local i=0;
>>> local indent=''
>>> - while [ $i -lt $((${#integ}+6)) ]; do
>>> + while [[ $i -lt $((${#integ}+6)) ]]; do
>>> indent="$indent "
>>> i=$(($i+1))
>>> done
>> What about "while (( $i < $((${#integ}+6)) )); do"?
>
> I was planning a separate patch switching to a for loop.
> for (( i = 0; i < ${#integ} + 6; i++ ))
>

In this case, I would either get rid of -lt by converting to a for loop
directly or not touch that line at all in this patch.

> Should I implement these changes and resend this patch?
> /me goes looking for git help
>

If you like, but you could also wait for at least Allan's comment. You
can use "git commit --amend" to alter your existing commit in git by the
way.

From forum: pacman-dev

Re: [PATCH 1/2] Changing [ to [[ and ((

2009-11-12T14:02:21Z

On Thu, Nov 12, 2009 at 07:16:41PM +0000, Cedric Staniewski wrote:

> > @@ -450,12 +450,12 @@ download_sources() {
> > for netfile in "${source[@]}"; do
> > local file=$(get_filename "$netfile")
> > local url=$(get_url "$netfile")
> > - if [ -f "$startdir/$file" ]; then
> > + if [[ -f "$startdir/$file" ]]; then
> > msg2 "$(gettext "Found %s in build dir")" "$file"
> > rm -f "$srcdir/$file"
> > ln -s "$startdir/$file" "$srcdir/"
> > continue
> > - elif [ -f "$SRCDEST/$file" ]; then
> > + elif [[ -f "$SRCDEST/$file" ]]; then
> > msg2 "$(gettext "Using cached copy of %s")" "$file"
> > rm -f "$srcdir/$file"
> > ln -s "$SRCDEST/$file" "$srcdir/"

What about something like this?
> if [[ "$(check_option makeflags)" = "n" ]]; then

None of the quotes are needed. I'm inclined to replace it with:
> if [[ $(check_option makeflags) = "n" ]]; then

While the quotes around n are not needed, they highlight that n is a string which appeals to me since it looks like a string as found in other languages. Or would you say to drop all the quotes.

Maybe some style guidelines are needed for the bash language...

- Isaac

From forum: pacman-dev

Re: C++ problem with conflicting declarations

2009-11-12T12:55:03Z

On Thu, Nov 12, 2009 at 2:21 PM, Stefan Husmann
<stefan-husmann@...> wrote:

> Hello,
>
> when I try to compile xaralx I get
> In file included from /usr/include/glib-2.0/gio/gio.h:28,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32,
> from ftfonts.cpp:125:
> /usr/include/glib-2.0/gio/giotypes.h:120: error: conflicting declaration
> 'typedef struct _GSocket GSocket'
> /usr/include/wx-2.8/wx/unix/gsockunx.h:41: error: 'class GSocket' has a
> previous declaration as 'class GSocket'
> ftfonts.cpp: In static member function 'static BOOL
> FTFontMan::CacheFontCore(String_64*, BOOL)':
> ftfonts.cpp:262: warning: deprecated conversion from string constant to
> 'char*'
> ftfonts.cpp:262: warning: deprecated conversion from string constant to
> 'TCHAR*'
> ftfonts.cpp:288: warning: deprecated conversion from string constant to
> 'char*'
> ftfonts.cpp:288: warning: deprecated conversion from string constant to
> 'TCHAR*'
> ftfonts.cpp: In static member function 'static FTFont*
> FTFontMan::CreateNewFont(String_64*, FontClass)':
> ftfonts.cpp:703: warning: deprecated conversion from string constant to
> 'char*'
> ftfonts.cpp:703: warning: deprecated conversion from string constant to
> 'TCHAR*'
> make[2]: *** [libwxOil_a-ftfonts.o] Error 1
> make[2]: Leaving directory
> `/home/haawda/paketierung/maintained_by_me/xaralx/src/XaraLX-0.7r1785/wxOil'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory
> `/home/haawda/paketierung/maintained_by_me/xaralx/src/XaraLX-0.7r1785/wxOil'
> make: *** [all-recursive] Error 1
>
> /usr/include/glib-2.0/gio/giotypes.h is included in glib2,
> /usr/include/wx-2.8/wx/unix/gsockunx.h is included in wxgtk.
> What is to do in such cases? Is this a bug in glib2 or in wxgtk?
> Regards Stefan
>

wxgtk 2.8.10.1-5 is supposed to be patched for that. Is your system up-to-date?

From forum: tur-users

Re: perl-libwww duplicates

2009-11-12T12:41:18Z

On Thu, Nov 12, 2009 at 15:16, Xyne <xyne@...> wrote:
> What exactly are you removing by hand? If you're actually talking about
> the provides array, you'll be happy to learn that pacpan no longer
> includes standard CPAN names in that array.

You're right, it was the provides array. I need to update my version I
guess, I must be outdated. I'd also suggest looking at makepkg's new
"purge" option if the new version doesn't already.

In any case, thanks for the good tool :)

From forum: tur-users

Re: C++ problem with conflicting declarations

2009-11-12T12:28:26Z

On Thu, Nov 12, 2009 at 11:21 AM, Stefan Husmann <stefan-husmann@...
> wrote:

The problem may be bitrot. The latest Xara Linux package was released 3
years ago, and since then not much has been done to maintain it.

Smartboy

From forum: tur-users

Re: perl-libwww duplicates

2009-11-12T12:16:34Z

Daenyth Blank wrote:

> Personally I've always found the current behavior very annoying. Why
> not just generate the arch standard names for the depends array and
> let the packager work it out if that isn't correct? Defaulting to the
> standard seems better than defaulting to print everything, most of
> which gets removed by hand. It's the single biggest peeve I have with
> pacpan. (Not to say that I don't find it useful.)

I don't understand what you mean. Pacpan is quite good at detecting
dependencies. It checks if necessary CPAN modules are already installed
and if they are it determines which pacman package they belong to. If
the dependency isn't already installed, it checks pacman's database for
a package which provides the dependency. The only way it produces a
dependency list which is superfluous is if either the metadata on CPAN
is incorrect, which is the module author's fault, or if existing
packages fail to correctly list all of the packages/modules which they
provide, which is then the packager's fault.

The only case in which this might be an issue would be when recursively
building packages to satisfy dependencies. It can't know a priori if
two packages specified in CPAN's metadata are actually provided by the
same package if that package doesn't yet exist. That's not really an
issue though because once that package exists, it will provide both of
the required packages and thus satisfy the dependencies.

What exactly are you removing by hand? If you're actually talking about
the provides array, you'll be happy to learn that pacpan no longer
includes standard CPAN names in that array. I had originally included
them because I had seen other perl packages which did so and I didn't
think it would hurt to be thorough.

Sorry if this doesn't address your issue, but in the context of
the "depends array" I really don't know what you mean by "defaulting to
print everything".

Regards,
Xyne

From forum: tur-users

Re: [PATCH 1/2] Changing [ to [[ and ((

2009-11-12T11:47:03Z

On Thu, Nov 12, 2009 at 07:16:41PM +0000, Cedric Staniewski wrote:
> I hope your patch do not get lost in this thread.

Erm. Yeah, I hope so too. How does it get threaded?

>
> > @@ -345,26 +345,26 @@ handle_deps() {
> > local R_DEPS_SATISFIED=0
> > local R_DEPS_MISSING=1
> >
> > - [ $# -eq 0 ] && return $R_DEPS_SATISFIED
> > + (( $# == 0 )) && return $R_DEPS_SATISFIED
> >
>
> Is there a reason why you do not use (( ! $# )) here?

Some variables are used as a boolean flag in which case testing if ((VAR)) and if (( ! VAR )) reads well. The $# (and EUID) are used as integer values so it struck me as more understandable or readable in this form.

> > @@ -450,12 +450,12 @@ download_sources() {
> > for netfile in "${source[@]}"; do
> > local file=$(get_filename "$netfile")
> > local url=$(get_url "$netfile")
> > - if [ -f "$startdir/$file" ]; then
> > + if [[ -f "$startdir/$file" ]]; then
> > msg2 "$(gettext "Found %s in build dir")" "$file"
> > rm -f "$srcdir/$file"
> > ln -s "$startdir/$file" "$srcdir/"
> > continue
> > - elif [ -f "$SRCDEST/$file" ]; then
> > + elif [[ -f "$SRCDEST/$file" ]]; then
> > msg2 "$(gettext "Using cached copy of %s")" "$file"
> > rm -f "$srcdir/$file"
> > ln -s "$SRCDEST/$file" "$srcdir/"
>
> We could remove the quotes here, too.

I was lax with some of the quotes when doing concatenation and parameter expansion...

> > @@ -512,7 +512,7 @@ generate_checksums() {
> >
> > local i=0;
> > local indent=''
> > - while [ $i -lt $((${#integ}+6)) ]; do
> > + while [[ $i -lt $((${#integ}+6)) ]]; do
> > indent="$indent "
> > i=$(($i+1))
> > done
>
> What about "while (( $i < $((${#integ}+6)) )); do"?

I was planning a separate patch switching to a for loop.
for (( i = 0; i < ${#integ} + 6; i++ ))

> > @@ -521,8 +521,8 @@ generate_checksums() {
> > for netfile in "${source[@]}"; do
> > local file="$(get_filename "$netfile")"
> >
> > - if [ ! -f "$file" ] ; then
> > - if [ ! -f "$SRCDEST/$file" ] ; then
> > + if [[ ! -f $file ]] ; then
> > + if [[ ! -f "$SRCDEST/$file" ]] ; then
> > error "$(gettext "Unable to find source file %s to generate checksum.")" "$file"
> > plain "$(gettext "Aborting...")"
> > exit 1
>
> Same as above. Quotes are not necessary.
>
> > @@ -533,10 +533,10 @@ generate_checksums() {
> >
> > local sum="$(openssl dgst -${integ} "$file")"
> > sum=${sum##* }
> > - [ $ct -gt 0 ] && echo -n "$indent"
> > + (( ct )) && echo -n $indent
> > echo -n "'$sum'"
>
> I do not think we want to remove the quotes here.
>
> $ indent=" "
> $ echo -n $indent; echo asdf
> asdf
> $ echo -n "$indent"; echo asdf
> asdf
> $

That'd be a careless use of s/"// in a macro on my behalf. Thanks for catching.

> > @@ -566,8 +566,8 @@ check_checksums() {
> > file="$(get_filename "$file")"
> > echo -n " $file ... " >&2
> >
> > - if [ ! -f "$file" ] ; then
> > - if [ ! -f "$SRCDEST/$file" ] ; then
> > + if [[ ! -f $file ]] ; then
> > + if [[ ! -f "$SRCDEST/$file" ]] ; then
> > echo "$(gettext "NOT FOUND")" >&2
> > errors=1
> > found=0
> > @@ -622,8 +622,8 @@ extract_sources() {
> > continue
> > fi
> >
> > - if [ ! -f "$file" ] ; then
> > - if [ ! -f "$SRCDEST/$file" ] ; then
> > + if [[ ! -f $file ]] ; then
> > + if [[ ! -f "$SRCDEST/$file" ]] ; then
> > error "$(gettext "Unable to find source file %s for extraction.")" "$file"
> > plain "$(gettext "Aborting...")"
> > exit 1
>
> Quotes are not necessary.
>
> > @@ -662,31 +662,31 @@ extract_sources() {
> > ...
> > fi
> > done
> >
> > - if [ $EUID -eq 0 ]; then
> > + if (( EUID == 0 )); then
> > # change perms of all source files to root user & root group
> > chown -R 0:0 "$srcdir"
> > fi
> > }
> >
> > ...
>
> (( ! EUID )) ?

As above

>
> > @@ -713,12 +713,12 @@ run_function() {
> > ...
> > local i=1
> > while true; do
> > - if [ -f "$BUILDLOG.$i" ]; then
> > + if [[ -f "$BUILDLOG.$i" ]]; then
> > i=$(($i +1))
> > else
> > break
>
> Quotes again? There are several other places where quotes or the dollar
> signs (in e.g. (( $found )) ) are not needed. Maybe you want to remove
> them, maybe not.
>
> Cedric
>
>

Should I implement these changes and resend this patch?
/me goes looking for git help

Thanks for the feedback!
- Isaac

From forum: pacman-dev

C++ problem with conflicting declarations

2009-11-12T11:21:44Z

Hello,

when I try to compile xaralx I get

In file included from /usr/include/glib-2.0/gio/gio.h:28,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from ftfonts.cpp:125:
/usr/include/glib-2.0/gio/giotypes.h:120: error: conflicting declaration 'typedef struct _GSocket GSocket'
/usr/include/wx-2.8/wx/unix/gsockunx.h:41: error: 'class GSocket' has a previous declaration as 'class GSocket'
ftfonts.cpp: In static member function 'static BOOL FTFontMan::CacheFontCore(String_64*, BOOL)':
ftfonts.cpp:262: warning: deprecated conversion from string constant to 'char*'
ftfonts.cpp:262: warning: deprecated conversion from string constant to 'TCHAR*'
ftfonts.cpp:288: warning: deprecated conversion from string constant to 'char*'
ftfonts.cpp:288: warning: deprecated conversion from string constant to 'TCHAR*'
ftfonts.cpp: In static member function 'static FTFont* FTFontMan::CreateNewFont(String_64*, FontClass)':
ftfonts.cpp:703: warning: deprecated conversion from string constant to 'char*'
ftfonts.cpp:703: warning: deprecated conversion from string constant to 'TCHAR*'
make[2]: *** [libwxOil_a-ftfonts.o] Error 1
make[2]: Leaving directory `/home/haawda/paketierung/maintained_by_me/xaralx/src/XaraLX-0.7r1785/wxOil'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/haawda/paketierung/maintained_by_me/xaralx/src/XaraLX-0.7r1785/wxOil'
make: *** [all-recursive] Error 1

/usr/include/glib-2.0/gio/giotypes.h is included in glib2, /usr/include/wx-2.8/wx/unix/gsockunx.h is included in wxgtk.

What is to do in such cases? Is this a bug in glib2 or in wxgtk?

Regards Stefan

From forum: tur-users

Re: (groff+)ghostscript/us letter/paper size problems

2009-11-12T11:19:07Z

On Thu, Nov 12, 2009 at 09:49:13AM -0500, Louis Guillaume wrote:
> Mike Bishop wrote:
<snip>

> >
> >The problem is that recent versions of ghostscript will (often)
> >assume a4 paper size, regardless of /etc/paper. This applies
> >after ghostscript 8.64-5 but I am not sure which version (8.70 has
> >the problem).
>
> I don't know much about how this is "supposed" to work with
> /etc/paper or /etc/papersize. I always thought those were
> ghostscript or grops things.
>
> If you need to explicitly define a paper size for groff to use (that
> isn't the default) I think you need: `-dpaper=letter' in addition to
> `-P-pletter'. The latter is for grops.
>
> Louis
>

Actually, I screwed up. The file on Arch at
/usr/share/groff/1.20.1/font/devps/DESC
has "papersize a4" while a more usual entry is
"papersize /etc/papersize a4" ... so my
settings in /etc/papersize were ignored.

I looked for a complicated answer and found it!

Rgds,
--
Mike Bishop
Willow, Alaska

From forum: arch general

Re: [PATCH 1/2] Changing [ to [[ and ((

2009-11-12T11:16:41Z

Isaac Good wrote:

>> >From f40b051c1c649889a13f35965fa8f8decd505b47 Mon Sep 17 00:00:00 2001
> From: Isaac Good <pacman@...>
> Date: Wed, 11 Nov 2009 16:47:43 -0500
> Subject: [PATCH 1/2] Changing [ to [[ and ((
>
> First half of makepkg
> This replaces any prior patches of mine
> Includes stuff like -o to || and -a to && etc
> if [ $(type .. were preserved due to a bash bug with [[ and set -e and ERR traps
>
> Signed-off-by: Isaac Good <pacman@...>
> ---

I hope your patch do not get lost in this thread.

> @@ -345,26 +345,26 @@ handle_deps() {
> local R_DEPS_SATISFIED=0
> local R_DEPS_MISSING=1
>
> - [ $# -eq 0 ] && return $R_DEPS_SATISFIED
> + (( $# == 0 )) && return $R_DEPS_SATISFIED
>

Is there a reason why you do not use (( ! $# )) here?

> @@ -450,12 +450,12 @@ download_sources() {
> for netfile in "${source[@]}"; do
> local file=$(get_filename "$netfile")
> local url=$(get_url "$netfile")
> - if [ -f "$startdir/$file" ]; then
> + if [[ -f "$startdir/$file" ]]; then
> msg2 "$(gettext "Found %s in build dir")" "$file"
> rm -f "$srcdir/$file"
> ln -s "$startdir/$file" "$srcdir/"
> continue
> - elif [ -f "$SRCDEST/$file" ]; then
> + elif [[ -f "$SRCDEST/$file" ]]; then
> msg2 "$(gettext "Using cached copy of %s")" "$file"
> rm -f "$srcdir/$file"
> ln -s "$SRCDEST/$file" "$srcdir/"

We could remove the quotes here, too.

> @@ -512,7 +512,7 @@ generate_checksums() {
>
> local i=0;
> local indent=''
> - while [ $i -lt $((${#integ}+6)) ]; do
> + while [[ $i -lt $((${#integ}+6)) ]]; do
> indent="$indent "
> i=$(($i+1))
> done

What about "while (( $i < $((${#integ}+6)) )); do"?

> @@ -521,8 +521,8 @@ generate_checksums() {
> for netfile in "${source[@]}"; do
> local file="$(get_filename "$netfile")"
>
> - if [ ! -f "$file" ] ; then
> - if [ ! -f "$SRCDEST/$file" ] ; then
> + if [[ ! -f $file ]] ; then
> + if [[ ! -f "$SRCDEST/$file" ]] ; then
> error "$(gettext "Unable to find source file %s to generate checksum.")" "$file"
> plain "$(gettext "Aborting...")"
> exit 1

Same as above. Quotes are not necessary.

> @@ -533,10 +533,10 @@ generate_checksums() {
>
> local sum="$(openssl dgst -${integ} "$file")"
> sum=${sum##* }
> - [ $ct -gt 0 ] && echo -n "$indent"
> + (( ct )) && echo -n $indent
> echo -n "'$sum'"

I do not think we want to remove the quotes here.

$ indent=" "
$ echo -n $indent; echo asdf
asdf
$ echo -n "$indent"; echo asdf
asdf
$

> @@ -566,8 +566,8 @@ check_checksums() {
> file="$(get_filename "$file")"
> echo -n " $file ... " >&2
>
> - if [ ! -f "$file" ] ; then
> - if [ ! -f "$SRCDEST/$file" ] ; then
> + if [[ ! -f $file ]] ; then
> + if [[ ! -f "$SRCDEST/$file" ]] ; then
> echo "$(gettext "NOT FOUND")" >&2
> errors=1
> found=0
> @@ -622,8 +622,8 @@ extract_sources() {
> continue
> fi
>
> - if [ ! -f "$file" ] ; then
> - if [ ! -f "$SRCDEST/$file" ] ; then
> + if [[ ! -f $file ]] ; then
> + if [[ ! -f "$SRCDEST/$file" ]] ; then
> error "$(gettext "Unable to find source file %s for extraction.")" "$file"
> plain "$(gettext "Aborting...")"
> exit 1

Quotes are not necessary.

> @@ -662,31 +662,31 @@ extract_sources() {
> ...
> fi
> done
>
> - if [ $EUID -eq 0 ]; then
> + if (( EUID == 0 )); then
> # change perms of all source files to root user & root group
> chown -R 0:0 "$srcdir"
> fi
> }
>
> ...

(( ! EUID )) ?

> @@ -713,12 +713,12 @@ run_function() {
> ...
> local i=1
> while true; do
> - if [ -f "$BUILDLOG.$i" ]; then
> + if [[ -f "$BUILDLOG.$i" ]]; then
> i=$(($i +1))
> else
> break

Quotes again? There are several other places where quotes or the dollar
signs (in e.g. (( $found )) ) are not needed. Maybe you want to remove
them, maybe not.

Cedric

From forum: pacman-dev

Re: аrch x86_64 and i686 performance comparison

2009-11-12T10:34:41Z

I find the 64 bit version to be on par with the 32 bit version. I do think
64 bit is faster when using it for GIS with large datasets. I have been
using 64 bit for years without remorse. Now, no 64 bit Windows OS has ever
been worth using.

On Nov 11, 2009 11:19 PM, "Sergey Manucharian" <sergeym@...> wrote:

Excerpts from Smith Dhumbumroong's message of Thursday 12-Nov-09
10:49am:

> Better to install both Arch 32-bit and 64-bit on the same machine > (dual
boot) and run the tests...
I've already did it.

> from my personal experience certain operations, such as video/music >
encoding, is a _lot_ faster...
Well, in my ThinkPad R61 (Core2 Duo CPU T9300 @ 2.50GHz) I got 1.1
times difference (in favour of 64-bit) with couple of videofiles
encoded. (By the way, it means that VM performs almost 1.5 worse then
the real HW).

Thanks,
Sergey

From forum: arch general

Re: Deletion request for mumble-11x-git

2009-11-12T10:27:55Z

On Thu, Nov 12, 2009 at 8:21 PM, Lauri Niskanen <ape@...> wrote:

> The AUR package for mumble-11x-git [1] provides a compatibility client
> for older mumble versions, but uses new code from git. However, it is
> currently fully obsoleted by mumble-git [2] that provides the latest
> git version of the application (1.2.0-git) and the compatibility
> client. The 11x-client part in mumble-git is exactly the same as in
> mumble-11x-git.
>
> I think mumble-11x-git should be removed as obsoleted.
>
> [1] http://aur.archlinux.org/packages.php?ID=30578
> [2] http://aur.archlinux.org/packages.php?ID=26865
>
> -- Ape <Lauri Niskanen>

mumble-11x-git is no more. :)

From forum: tur-users

Deletion request for mumble-11x-git

2009-11-12T10:21:36Z

The AUR package for mumble-11x-git [1] provides a compatibility client
for older mumble versions, but uses new code from git. However, it is
currently fully obsoleted by mumble-git [2] that provides the latest
git version of the application (1.2.0-git) and the compatibility
client. The 11x-client part in mumble-git is exactly the same as in
mumble-11x-git.

I think mumble-11x-git should be removed as obsoleted.

[1] http://aur.archlinux.org/packages.php?ID=30578
[2] http://aur.archlinux.org/packages.php?ID=26865

-- Ape <Lauri Niskanen>

From forum: tur-users

Re: perl-libwww duplicates

2009-11-12T10:06:51Z

On Thu, Nov 12, 2009 at 12:54, Xyne <xyne@...> wrote:
> Pacpan generates a comprehensive "provides" list by cross-referencing all the
> names and sources and thus includes all alternative names which rely on
> the same source files. The user has to select the "main" module though
> and include the comprehensive provides string to avoid overlap, which
> is why I've sent the full "provides" array for Bundle::LWP to the
> perl-libwww packager (which should be named perl-bundle-lwp).

Personally I've always found the current behavior very annoying. Why
not just generate the arch standard names for the depends array and
let the packager work it out if that isn't correct? Defaulting to the
standard seems better than defaulting to print everything, most of
which gets removed by hand. It's the single biggest peeve I have with
pacpan. (Not to say that I don't find it useful.)

From forum: tur-users

Re: perl-libwww duplicates

2009-11-12T09:54:52Z

Cedric Staniewski wrote:

> Thanks. I thought about that again and am curious if there is a name
> convention for CPAN source files. It might make sense to set pkgname to
> 'perl-' the name of the source file (lowercase and without version and
> suffix, of course) by default in pacpan generated PKGBUILDs, even though
> libwww is an exception again.
>
> They should definitely look at the PKGBUILD before uploading them. I
> have seen provide arrays with items like 'modulename=undef' and there is
> a new license introduced by these PKGBUILDs called '~'. But that is the
> drawback of such tools; they make it so easy to generate PKGBUILDs and
> thus you get quantity but often less quality.

There is a naming convention but the problem is that several modules on
CPAN use the same source and install the same component modules. Pacpan
generates a comprehensive "provides" list by cross-referencing all the
names and sources and thus includes all alternative names which rely on
the same source files. The user has to select the "main" module though
and include the comprehensive provides string to avoid overlap, which
is why I've sent the full "provides" array for Bundle::LWP to the
perl-libwww packager (which should be named perl-bundle-lwp).

The inclusion of "undef" was due to a bug in pacpan where I had used a
simplified version check, which I've now fixed. Even so, you're right
that pacpan is incapable of always producing perfect PKGBUILDs and it
was never intended to be used without inspection of the results. It
relies on correct and complete meta information on CPAN (some module
authors don't bother) and a standard build function. In most cases
it works as expected and in others it usuallyl provides a good starting
point, but sometimes it's assumptions are horribly wrong and it fails
miserably.

Regards,
Xyne

From forum: tur-users

Re: apt-get style information for users in pacman

2009-11-12T09:41:25Z

2009/11/12 Xavier <shiningxc@...>:

> On Thu, Nov 12, 2009 at 7:31 AM, Allan McRae <allan@...> wrote:
>>
>> An an FYI, there is a really old bug report requesting this:
>> http://bugs.archlinux.org/task/833
>>
>
> 1 got lost !
>
> http://bugs.archlinux.org/task/8331
>
>

yes it did.. and I figured it out by searching.. =)

--
Bhargav Prasanna
http://muftmukt.wordpress.com/

From forum: pacman-dev

Re: Frustrated with Crappy looking Firefox and OpenOffice GTK & QT themes?

2009-11-12T08:42:22Z

On Thu, Nov 12, 2009 at 01:08:04AM -0600, David C. Rankin wrote:
> After mucking around trying to get firefox and openoffice to look right, I
> thought I would pass on a few tips. For those of you that know already, just
> hit delete.
>
> The dull boxy appearance of both GTK and some Qt apps left me scratching my
> head for the right tools to fix the look. The normal qtconfig and gtk2_prefs
> just didn't do it for all applications (like basket and other kde3 now sort of
> kde4 apps) Trial and error and google helped. The main tools are:
>

i faced a similar problem (gtk application looking horrible in kde) and
applied this fix [1]. Now gtk apps look nice in kde.

[1] http://wiki.archlinux.org/index.php/Kde#KDE_4_Theme_Integration_with_GTK_Applications

From forum: arch general

Re: [PATCH 1/2] makepkg: move pacman calls to a function

2009-11-12T06:13:11Z

Xavier wrote:

> On Thu, Nov 12, 2009 at 2:51 PM, Dan McGee <dpmcgee@...> wrote:
>> Doesn't look undocumented to me:
>> -T, --deptest
>> Check dependencies; this is useful in scripts such as makepkg to
>> check installed packages. This operation will check each dependency
>> specified and return a list of those which are not currently
>> satisfied on the system. This operation accepts no other options.
>> Example usage: pacman -T qt "bash>=3.2".
>>
>>
>
> Ahah ok. Well I am still not sure what a wrapper could add to that
> functionality, besides breaking it. But if everyone is against me,
> then I will shut up :) It is not a big deal.

It would be possible to get rid of -T and depend on vercmp for the
installed dependency check. I am not sure if this is any better though
(probably rather worse).

From forum: pacman-dev

Re: [PATCH 1/2] makepkg: move pacman calls to a function

2009-11-12T06:00:01Z

Xavier wrote:

> On Thu, Nov 12, 2009 at 2:08 PM, Cedric Staniewski <cedric@...> wrote:
>>> I have been thinking about this and its companion patch. I like the
>>> refactoring of the pacman call into the function but dislike not
>>> replacing the "pacman -T" call with it.
>>>
>>> If there is a config option for setting the "pacman" binary, and I have
>>> program that replaces pacman (e.g. the one based on the python alpm
>>> wrapper should work), then I should not need pacman on my system at all.
>>>
>>> So I prefer the original version where the "pacman -T" call was replaced
>>> too.
>>>
>> And leave it to the pacman wrapper authors to fix their programs? Sounds
>> good. :)
>> I also prefer the original patch, mainly because it seems 'cleaner' to
>> me, but being able to replace pacman completely on a system is a valid
>> reason, too.
>>
>>
>
> Well, I am still not convinced.
> Why would any wrapper have to care about pacman -T ?
> This is a hidden / undocumented / internal argument just for the usage
> of makepkg.
>
> In the best case, a wrapper will just forward it correctly. In the
> worst case, it will break it.

Since pacman 3.3 it is not that hidden anymore[1].

[1]
http://projects.archlinux.org/pacman.git/commit/?id=9af9c0f328094228fa363d842ddc9b2a605f0d22

From forum: pacman-dev

Re: [PATCH 1/2] makepkg: move pacman calls to a function

2009-11-12T05:56:52Z

On Thu, Nov 12, 2009 at 2:51 PM, Dan McGee <dpmcgee@...> wrote:

>
> Doesn't look undocumented to me:
> -T, --deptest
> Check dependencies; this is useful in scripts such as makepkg to
> check installed packages. This operation will check each dependency
> specified and return a list of those which are not currently
> satisfied on the system. This operation accepts no other options.
> Example usage: pacman -T qt "bash>=3.2".
>
>

Ahah ok. Well I am still not sure what a wrapper could add to that
functionality, besides breaking it. But if everyone is against me,
then I will shut up :) It is not a big deal.

From forum: pacman-dev

Re: [PATCH 1/2] makepkg: move pacman calls to a function

2009-11-12T05:51:30Z

On Thu, Nov 12, 2009 at 7:48 AM, Xavier <shiningxc@...> wrote:

> On Thu, Nov 12, 2009 at 2:08 PM, Cedric Staniewski <cedric@...> wrote:
>>>
>>> I have been thinking about this and its companion patch. I like the
>>> refactoring of the pacman call into the function but dislike not
>>> replacing the "pacman -T" call with it.
>>>
>>> If there is a config option for setting the "pacman" binary, and I have
>>> program that replaces pacman (e.g. the one based on the python alpm
>>> wrapper should work), then I should not need pacman on my system at all.
>>>
>>> So I prefer the original version where the "pacman -T" call was replaced
>>> too.
>>>
>>
>> And leave it to the pacman wrapper authors to fix their programs? Sounds
>> good. :)
>> I also prefer the original patch, mainly because it seems 'cleaner' to
>> me, but being able to replace pacman completely on a system is a valid
>> reason, too.
>>
>>
>
> Well, I am still not convinced.
> Why would any wrapper have to care about pacman -T ?
> This is a hidden / undocumented / internal argument just for the usage
> of makepkg.

Doesn't look undocumented to me:
-T, --deptest
Check dependencies; this is useful in scripts such as makepkg to
check installed packages. This operation will check each dependency
specified and return a list of those which are not currently
satisfied on the system. This operation accepts no other options.
Example usage: pacman -T qt "bash>=3.2".

> In the best case, a wrapper will just forward it correctly. In the
> worst case, it will break it.

From forum: pacman-dev

Re: [PATCH 1/2] makepkg: move pacman calls to a function

2009-11-12T05:48:22Z

On Thu, Nov 12, 2009 at 2:08 PM, Cedric Staniewski <cedric@...> wrote:

>>
>> I have been thinking about this and its companion patch. I like the
>> refactoring of the pacman call into the function but dislike not
>> replacing the "pacman -T" call with it.
>>
>> If there is a config option for setting the "pacman" binary, and I have
>> program that replaces pacman (e.g. the one based on the python alpm
>> wrapper should work), then I should not need pacman on my system at all.
>>
>> So I prefer the original version where the "pacman -T" call was replaced
>> too.
>>
>
> And leave it to the pacman wrapper authors to fix their programs? Sounds
> good. :)
> I also prefer the original patch, mainly because it seems 'cleaner' to
> me, but being able to replace pacman completely on a system is a valid
> reason, too.
>
>

Well, I am still not convinced.
Why would any wrapper have to care about pacman -T ?
This is a hidden / undocumented / internal argument just for the usage
of makepkg.

In the best case, a wrapper will just forward it correctly. In the
worst case, it will break it.

From forum: pacman-dev

Re: [PATCH 1/2] makepkg: move pacman calls to a function

2009-11-12T05:08:12Z

Allan McRae wrote:

> Dan McGee wrote:
>> On Fri, Nov 6, 2009 at 2:20 PM, Cedric Staniewski <cedric@...> wrote:
>>> Signed-off-by: Cedric Staniewski <cedric@...>
>>> ---
>>
>> Seems pretty reasonable to me; Allan, is this OK?
>>
>
> I have been thinking about this and its companion patch. I like the
> refactoring of the pacman call into the function but dislike not
> replacing the "pacman -T" call with it.
>
> If there is a config option for setting the "pacman" binary, and I have
> program that replaces pacman (e.g. the one based on the python alpm
> wrapper should work), then I should not need pacman on my system at all.
>
> So I prefer the original version where the "pacman -T" call was replaced
> too.
>

And leave it to the pacman wrapper authors to fix their programs? Sounds
good. :)
I also prefer the original patch, mainly because it seems 'cleaner' to
me, but being able to replace pacman completely on a system is a valid
reason, too.

From forum: pacman-dev

Re: [PATCH 2/2] makepkg: add a config file option for the pacman binary to be used

2009-11-12T04:57:03Z

Dan McGee wrote:

> On Tue, Nov 10, 2009 at 4:36 PM, Allan McRae <allan@...> wrote:
>> Cedric Staniewski wrote:
>>> Dan McGee wrote:
>>>> On Fri, Nov 6, 2009 at 2:51 PM, Cedric Staniewski <cedric@...> wrote:
>>>>> Implements FS#13028.
>>>>>
>>>>> Signed-off-by: Cedric Staniewski <cedric@...>
>>>>> ---
>>>>> Oops... forgot to adjust the documentation. -T support is not required
>>>>> anymore for the pacman wrappers.
>>>> I think I'd rather see this as an environment variable- wouldn't that
>>>> make more sense, as we wouldn't require it to be specified by the vast
>>>> majority of people that just want to use the default?
>>>>
>>>> PACMAN=${PACMAN:-pacman} or whatever it is.
>>>>
>>>> -Dan
>>> Sorry Dan, but I do not get your point. This patch makes it possible to
>>> specify a pacman command in one of the makepkg.conf files, but it is not
>>> mandatory because of the reason you mentioned. I already use your line in my
>>> patch:
>>>
>>> +# set pacman command if not defined in config files
>>> +PACMAN=${PACMAN:-pacman}
>>> +
>>>
>>> It is, however, not possible to provide a pacman command via environment
>>> variable, because I think it makes more sense to store it in a config file.
>>> So do you mean it should be possible to use an environment variable as
>>> well?
>> I think Dan wants it to only be available through and environmental variable
>> and not in the makepkg.conf. That should already be possible with your
>> patch (as you point out, the line Dan suggested is already there).
>>
>> I have no real preference but am leaning towards it not being included in
>> pacman.conf given the usage is expected to be low. If we are wrong and it
>> becomes very popular to use some wrapper, then we can always add the config
>> option later.
>
> My suggestion was as Allan says; only do it in the environment. Of
> course, since makepkg.conf is just sourced anyway, then to each his
> own, but I'd rather not advertise it there at all.
>
> Why? Things like $BROWSER, $EDITOR, etc. are pretty standard and
> accepted variables. There is no reason that on an Arch system, $PACMAN
> shouldn't join that list. This would address other things, such as
> people always wanting to have it run with a certain command line flag,
> or perhaps always use a pacman.static binary, or anything like that.
> Maybe I'm making orange juice out of bananas, but yeah.
>
> -Dan
>

I'm fine with your approach and it would definitely have some
advantages, however I prefer documenting it somewhere. My worry is that
we run into side-effects when someone has set this variable to something
weird for some obscure reasons, but perhaps I am a bit too pessimistic here.

From forum: pacman-dev

Re: perl-libwww duplicates

2009-11-12T04:45:41Z

Xyne wrote:

> On Tue, 10 Nov 2009 17:19:08 -0500
> Daenyth Blank <daenyth+arch@...> wrote:
>
>> On Tue, Nov 10, 2009 at 14:36, Cedric Staniewski <cedric@...> wrote:
>>> Hi,
>>> There are several packages in the AUR which provides exactly the same package as perl-libwww from extra does. Apparently, it is a pacpan related issue and therefore these packages are required by other ones. Deleting them is likely no solution as they will get uploaded again by another pacpan user.
>>>
>>> Cedric
>>>
>>>
>>> => perl-http-headers
>>> http://aur.archlinux.org/packages.php?ID=25730
>>>
>>> => perl-http-request
>>> http://aur.archlinux.org/packages.php?ID=25736
>>>
>>> => perl-http-response
>>> http://aur.archlinux.org/packages.php?ID=25735
>>>
>>> => perl-lwp-simple
>>> http://aur.archlinux.org/packages.php?ID=27566
>>>
>>> => perl-lwp-useragent
>>> http://aur.archlinux.org/packages.php?ID=25734
>>>
>> I'm going to cc this to xyne
>
>
> Thanks.
>
>
> This is because perl-libwww only provides libwww-perl in the PKGBUILD
> when in it actually provides over 50 modules/packages. I'll open a
> ticket on the bug tracker and then take care of the listed pacakges in
> the AUR.
>
> I'll post any updates here.
>

Thanks. I thought about that again and am curious if there is a name
convention for CPAN source files. It might make sense to set pkgname to
'perl-' the name of the source file (lowercase and without version and
suffix, of course) by default in pacpan generated PKGBUILDs, even though
libwww is an exception again.

>
> Perhaps this would be a good opportunity to ask everyone packaging CPAN
> modules to at least look at the provides string generated by pacpan. It
> cross-references all names with their associated source files to
> generate a comprehensive list.
>

They should definitely look at the PKGBUILD before uploading them. I
have seen provide arrays with items like 'modulename=undef' and there is
a new license introduced by these PKGBUILDs called '~'. But that is the
drawback of such tools; they make it so easy to generate PKGBUILDs and
thus you get quantity but often less quality.

>
> Regards,
> Xyne

From forum: tur-users

Re: Deletion request: gdata-provider

2009-11-12T03:36:05Z

Dave wrote:
> My package, will create a new one. Thanks!
>
> http://aur.archlinux.org/packages.php?ID=31305

Done.

From forum: tur-users

Re: No sound after hal update

2009-11-12T03:28:22Z

On Wed, Nov 11, 2009 at 8:40 AM, Magnus Therning <magnus@...> wrote:
> On Tue, Nov 10, 2009 at 5:11 PM, Christopher Daley <crdaley@...> wrote:
>> Have you tried running pulseaudio as a daemon? e.g. "/etc/rc.d/pulseaudio
>> start'
>> This would likely be a fix for now...
[..]
> I noticed there's a new HAL package available, I'll upgrade to see if
> things improve.

Seems to have been fixed with the recent set of updates... thanks!

/M

--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe

From forum: arch general

Re: No sound after hal update

2009-11-12T03:25:03Z

Magnus Therning wrote:

> On Tue, Nov 10, 2009 at 5:11 PM, Christopher Daley <crdaley@...> wrote:
>> Have you tried running pulseaudio as a daemon? e.g. "/etc/rc.d/pulseaudio
>> start'
>> This would likely be a fix for now...
>
> First, it's not recommended to run pulseaudio in system mode. Second it fails:
>
> Nov 11 08:35:27 bryma pulseaudio[19871]: main.c: Running in system
> mode, but --disallow-exit not set!
> Nov 11 08:35:27 bryma pulseaudio[19871]: main.c: Running in system
> mode, but --disallow-module-loading not set!
> Nov 11 08:35:27 bryma pulseaudio[19871]: main.c: Running in system
> mode, forcibly disabling SHM mode!
> Nov 11 08:35:27 bryma pulseaudio[19871]: main.c: Running in system
> mode, forcibly disabling exit idle time!
> Nov 11 08:35:28 bryma pulseaudio[19872]: main.c: OK, so you are
> running PA in system mode. Please note that you most likely shouldn't
> be doing that.
> Nov 11 08:35:28 bryma pulseaudio[19872]: main.c: If you do it
> nonetheless then it's your own fault if things don't work as expected.
> Nov 11 08:35:28 bryma pulseaudio[19872]: main.c: Please read
> http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an
> explanation why system mode is usually a bad idea.
> Nov 11 08:35:28 bryma pulseaudio[19872]: module.c: module-hal-detect
> is deprecated: Please use module-udev-detect instead of
> module-hal-detect!
> Nov 11 08:35:28 bryma pulseaudio[19872]: module.c:
> module-volume-restore is deprecated: Please use module-stream-restore
> instead of module-volume-restore!
> Nov 11 08:35:28 bryma pulseaudio[19872]: module-volume-restore.c: We
> will now load module-stream-restore. Please make sure to remove
> module-volume-restore from your configuration.
>
> I noticed there's a new HAL package available, I'll upgrade to see if
> things improve.
>
> /M
>

Hello,

my sound card did not work after hal update. I added the user to the
audio group and now it works.

Thanks for the help!

Bye
Lars

From forum: arch general

Deletion request: gdata-provider

2009-11-12T03:14:14Z

My package, will create a new one. Thanks!

http://aur.archlinux.org/packages.php?ID=31305

From forum: tur-users

Re: apt-get style information for users in pacman

2009-11-12T02:00:13Z

On Thu, Nov 12, 2009 at 7:31 AM, Allan McRae <allan@...> wrote:
>
> An an FYI, there is a really old bug report requesting this:
> http://bugs.archlinux.org/task/833
>

1 got lost !

http://bugs.archlinux.org/task/8331

From forum: pacman-dev

Re: Reset password of AUR account?

2009-11-12T01:39:32Z

On Thu, Nov 12, 2009 at 11:37 AM, Evangelos Foutras <foutrelis@...> wrote:
> On Thu, Nov 12, 2009 at 11:21 AM, Magnus Therning <magnus@...> wrote:
>> I seem to have lost my AUR account password. Looking at the site
>> there's no obvious way to get it back, or reset it. What do I do?
>>
>> Username: magus
>>
>> /M
>
> Laszlo is correct. You'll be receiving a new password t shortly. :)

* You'll be receiving a new password via email from me shortly.

From forum: tur-users

Re: Reset password of AUR account?

2009-11-12T01:39:29Z

On Thu, Nov 12, 2009 at 9:37 AM, Evangelos Foutras <foutrelis@...> wrote:
> On Thu, Nov 12, 2009 at 11:21 AM, Magnus Therning <magnus@...> wrote:
>> I seem to have lost my AUR account password. Looking at the site
>> there's no obvious way to get it back, or reset it. What do I do?
>>
>> Username: magus
>>
>> /M
>
> Laszlo is correct. You'll be receiving a new password t shortly. :)

Thanks. I'll try to take better care of this one, to avoid having to
bother you again with this :-)

/M

--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe

From forum: tur-users