FS#11142 - Repositories' packages.txt files seem out-of-date

Attached to Project: Arch Linux
Opened by Simon Malinge (Tapi) - Thursday, 07 August 2008, 11:16 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 17 October 2008, 20:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dale Blount (dale)
Simo Leone (neotuli)
Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Hi,
Each repository's packages.txt file should list the packages filenames of the current repository, but it seems that several filenames are incorrect, because of out-of-date versions.
I noticed this while trying to install Arch on a dedicated server (thus, without a screen) using a custom bootstrap script which relies on this file ; the script failed to download some required packages, because of 404 errors.
As I run an official mirror which synchronizes directly on rsync.archlinux.org, I launched a sync to find out if this was not a mirroring problem, but when the sync finished the files were still out-of-date.
I wrote a quick and dirty shell script to list out-of-date package versions in the packages.txt file.
The last run of this script gave me more than 1600 out-of-date package versions and vanished packages...
It's awefully slow, you've been warned ;)

# Just run this script at the root of your packages mirror tree
for txt in `find . -name packages.txt | grep -v setup`
do
dirname=`dirname $txt`
for pkg in `sed 's!.*/!!' $txt`
do
if [ "${pkg%.pkg.tar.gz}" != "$pkg" ]; then
if [ ! -f "$dirname/$pkg" ]; then
repo=`echo $dirname | cut -d/ -f2`
arch=`echo $dirname | cut -d/ -f4`
pkg=${pkg%.pkg.tar.gz}
pkg=${pkg%-i686}
pkg=${pkg%-x86_64}
pkgname=${pkg%-*-*}
txtpkgver=${pkg#$pkgname-}
repopkg=$(basename $(echo $dirname/$pkgname-*.pkg.tar.gz | tr ' ' '\n' | head -1))
if [ -f "$dirname/$repopkg" ]; then
repopkg=${repopkg%.pkg.tar.gz}
repopkg=${repopkg%-i686}
repopkg=${repopkg%-x86_64}
repopkgver=${repopkg#$pkgname-}
echo "$repo/$pkgname is out-of-date in packages.txt (txt: $txtpkgver | repo: $repopkgver)"
else
echo "$repo/$pkgname no longer exists for the $arch arch !"
fi
fi
fi
done
done


Additional info:
* This "bug" concerns the 'core' and 'extra' repositories


Steps to reproduce:
Go on your favorite mirror with your web browser (or any other access method), open /core/os/i686/packages.txt, write down the bash version stored in this file, and notice that the version doesn't match the actual version of the bash package in the repository.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 17 October 2008, 20:36 GMT
Reason for closing:  Works for me
Additional comments about closing:  See final comments. packages.txt is no longer used.
Comment by Aaron Griffin (phrakture) - Thursday, 07 August 2008, 16:02 GMT
packages.txt isn't used anymore, and it has been entirely broken since we switched to SVN, and the new installer does not use packages.txt.

Why is your mirror syncing based on that file? It should be using rsync
Comment by Dale Blount (dale) - Thursday, 07 August 2008, 16:04 GMT
If we don't use this file anymore, we really should delete it to avoid confusion. His custom bootstrap script uses this file, not the mirror. If you want, post your bootstrap script and I'll try to give suggestions on how to change it to not use packages.txt.

Comment by Aaron Griffin (phrakture) - Thursday, 07 August 2008, 16:17 GMT
The file was floating around until we made sure the new ISO made the rounds.

You can get the same info from "pacman -Sl core" and "pacman -Sl extra"
Comment by Aaron Griffin (phrakture) - Thursday, 07 August 2008, 16:26 GMT
Files have been removed
Comment by RicardoH (richer) - Friday, 17 October 2008, 18:56 GMT
  • Field changed: Percent Complete (100% → 0%)
Right now when you install using ftp with the current installer 2008.06..it tries to find packages.txt and of course is not found. I read in the comments that this is fixed in next release but is out?. I can't install arch right now
Comment by Aaron Griffin (phrakture) - Friday, 17 October 2008, 18:57 GMT
Can someone confirm that 2008.06 is broken?

I plan on pushing out a new ISO asap (maybe this weekend, or next). Dan & Simo - does the latest installer package still read packages.txt?
Comment by Simo Leone (neotuli) - Friday, 17 October 2008, 20:19 GMT Comment by Dan McGee (toofishes) - Friday, 17 October 2008, 20:21 GMT
Note that the above blob is from the 2008.06 version of the installer, so we do not use it now or back then.

Loading...