You are not logged in.
I'm upgrading through the python-->python3 change. I have been using a modified version of wicd and that obviously needs to change. I normally do this by syncing abs and then starting from the latest /var/abs/extra/wicd and then making my changes and creating my bespoke package.
However, I find that the abs I'm downloading has a PKGBUILD with
pkgname=wicd
pkgver=1.7.0
pkgrel=4
while the binary packages now appear to be at 1.7.0-6 ;(
Do the ABS sources lag the actual builds?
Offline
ABS syncs once every 24 hours. If it has not done a sync yet, the wicd PKGBUILD you want will be in [testing].
Edit: It appears there was an issue in SVN for that package. Fixed so the change should propagate to ABS soon.
Offline
Maybe your mirror is out of sync?
Offline
Allan, how did you discover about the svn issue? I'm not totally familiar with how the various bits of Arch join up. I looked at the svn trunk & extra-any links for wicd, but they appeared to be in sync.
Not sure what Awebb means, but my abs.conf has
SYNCSERVER="rsync.archlinux.org"
ARCH="x86_64"
MIRRORLIST="/etc/pacman.d/mirrorlist"
and I think a simple abs command uses the sync server.
Offline
There were entries for extra-i686 and extra-x86_64 that I removed. The conversion to an arch=any package was not complete...
Offline
OK and thanks, I guess this means that wicd will now have an 'any' arch which makes sense.
Offline