Listmates, I'm building a local repo for boxes to update via the lan instead of redownloading. I have my repo on my local server as: arch/ x86/ x86_64/ I have moved all files for my two x86_64 boxes to the arch/x86_64 dir and I am filtering with a script to eliminate dups by moving the lesser numbered packages to arch/x86_64/oldpkgs. Testing the script before the actual move of packages, I ran across this anomaly in some filenames: (script output) [1] <snip> ttf-isabella-1.003-3.pkg.tar.gz -> oldpkgs ttf-isabella-1.003-4-x86_64.pkg.tar.gz tunepimp-0.5.3-5.pkg.tar.gz -> oldpkgs tunepimp-0.5.3-6-x86_64.pkg.tar.gz tzdata-2009f-1-x86_64.pkg.tar.gz -> oldpkgs tzdata-2009g-1-x86_64.pkg.tar.gz unrar-3.8.5-2-x86_64.pkg.tar.gz -> oldpkgs unrar-3.9.1-1-x86_64.pkg.tar.gz <snip> As shown above, there are multiple packages where the earlier version did *not* contain the x86_64 designation where the current package now does. Are these the same packages? If so why did earlier packages not have the x86_64 and when was the architecture added? Are all packages now going to have the architecture specified? Footnotes: [1] Filtering done by a simple look ahead and the output created as follows: PKGFILES=( $(ls -1 /home/backup/archlinux/x86_64) ) for ((i=0;i<${#PKGFILES[@]}-1;i++)); do if [[ ${PKGFILES[$i]%%-[[:digit:]]*} == ${PKGFILES[$i+1]%%-[[:digit:]]*} ]]; then echo -e "${PKGFILES[$i]} -> oldpkgs\n${PKGFILES[$i+1]}\n" fi -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com