You are not logged in.
Pages: 1
I've made a "Syu" 5 hours ago, and upgraded initscripts. See what a Qi shows now:
XXXXX$ pacman -Qi initscripts
Name : initscripts
Version : 0.8-6
But, searching in the repos (all, includind inestable and testing), the last is 0.8-5.
I use current, extra and community with these servers:
What has happened?
Dienadel
Offline
Looks like the package list on archlinux.org is not entirely uptodate.
The cvs entry shows pkgbuild for initscripts 0.8-6 , just like your mirror, ftp.archlinux.org and belnet.be to name a few.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I've made a "Syu" 5 hours ago, and upgraded initscripts. See what a Qi shows now:
XXXXX$ pacman -Qi initscripts
Name : initscripts
Version : 0.8-6But, searching in the repos (all, includind inestable and testing), the last is 0.8-5.
I use current, extra and community with these servers:
What has happened?
Dienadel
Yeah, the same thing and same package upgrade happened to me last night.
Today, a newer version of bzip2 showed to be available by pacman, but the newer version is not showing in the current repo. I really don't know what's going on with it.
Oh, and the only mirrors I use are the Current and Extra for ftp.archlinux.org
Last edited by ozar (2007-01-30 23:02:00)
oz
Offline
We had a minor administrative glitch which left the website out of sync with the repos. It has now been rectified, so everything will be back to normal shortly.
Offline
Thanks for the reply, tomk!
Something still doesn't seem right with this because the initscripts and bzip2 packages on my box are both later versions than what is currently showing in the current repo. It would seem that if it were simply a sync issue, the current packages listing would be corrected by now.
Here's what is showing on my system with pacman:
$ pacman -Qi initscripts
Name : initscripts
Version : 0.8-6
$ pacman -Qi bzip2
Name : bzip2
Version : 1.0.4-1
...while current is still showing older packages.
Maybe I'm not understanding the situation correctly?
Last edited by ozar (2007-01-31 18:19:45)
oz
Offline
It's not an automatic fix - the glitch has been rectified, but the maintainers of the affected packages have to resubmit them. I'll give them a nudge.
Offline
ok, thanks again for the explanation.
oz
Offline
Pages: 1