You are not logged in.
Pages: 1
hi,
i wonder why the software in the staging repo is so old.
staging [################] 100% 20K 129.7K/s 00:00:00
:: gxine: local version (0.4.5-2) is newer than repo version (0.4.1-s1)
:: skype: local version (1.1.0.13-1) is newer than repo version (0.92.0.12-s1)
:: smb4k: local version (0.6.0-1) is newer than repo version (0.4.1a-s1)There are many other packages in that repo that needs an update. Updates are available in the AUR!
Are there plans to delete this repo?
THX!!
cu matsche
Offline
All TURs, including staging, seem to be obsolete by now. I guess it's not even worth keeping 'em in pacman.conf.
Offline
Yup, take them out
Offline
hmm... bad. So plz move all pkgs to extra repo! Without that i have to look after the updates by myself in the AUR. But with pacman i get updates automatically with pacman -Syu! :-)
THX!!
cu matsche
Offline
have you heard of the community repository in AUR?
Dusty
Offline
hmm... bad. So plz move all pkgs to extra repo! Without that i have to look after the updates by myself in the AUR. But with pacman i get updates automatically with pacman -Syu! :-)
uncomment the "[community]" section in pacman.conf - if there's packages you want in binary form, you need to vote for them in the AUR ( http://aur.archlinux.org ) - the TUs do not build every AUR package, because there's too many to deal with and they may be a waste of space - but we try to build all packages with high votes.
Offline
So anyone can take packages from staging, update them if needed, and add them to AUR. Is that correct? Logically, I would have thought that, due to their status, the packages in staging would bypass the voting system and be directly added to extra or community. :?
Offline
ok. so i haven't read some information! now i read everything in the "holy" newsletter. We learn: We need more newsletter! :-)
THX!!
cu matsche
Offline
Pages: 1