You are not logged in.
Pages: 1
Topic closed
A few days ago I updated arch, all went ok. Below a piece of the log:
........
[2013-06-01 12:39] [PACMAN] Running 'pacman -Syu'
[2013-06-01 12:39] [PACMAN] synchronizing package lists
[2013-06-01 12:40] [PACMAN] starting full system upgrade
[2013-06-01 12:54] [PACMAN] upgraded epiphany (3.8.1-1 -> 3.8.2-1)
[2013-06-01 12:54] [PACMAN] upgraded gnome-nettool (3.8.0-1 -> 3.8.1-1)
[2013-06-01 12:54] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2013-06-01 12:54] [PACMAN] upgraded pacman-mirrorlist (20130323-1 -> 20130601-1)
[2013-06-01 12:54] [PACMAN] upgraded sane (1.0.23-5 -> 1.0.23-6)
[2013-06-02 13:40] [PACMAN] Running 'pacman -Syu'
[2013-06-02 13:40] [PACMAN] synchronizing package lists
[2013-06-02 13:40] [PACMAN] starting full system upgrade
........
[2013-06-12 02:34] [PACMAN] Running 'pacman -Syu'
[2013-06-12 02:34] [PACMAN] synchronizing package lists
[2013-06-12 02:34] [PACMAN] starting full system upgrade
Since [2013-06-02 13:40] to [2013-06-12 02:34] arch is not detecting any packages upgrade. I would like to know if it is normal and there are no really upgrades till now or if something is happening in my system that cause arch not being upgraded.
Offline
Um ... look around the room (metaphorically) a bit.
The date of your last upgrade was right before the big news item (front page news and a vast majority of recent forum posts).
I take it what you are *not* telling us is that you use some ridiculous tool to automate updates[1] (bad idea) and it is not telling you about the errors that are preventing the update from continuing (even worse).
[1] Either that or you just type "pacman -Syu" then walk away ignoring any output.
Last edited by Trilby (2013-06-11 22:56:04)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Um ... look around the room (metaphorically) a bit.
The date of your last upgrade was right before the big news item (front page news and a vast majority of recent forum posts).
I take it what you are *not* telling us is that you use some ridiculous tool to automate updates[1] (bad idea) and it is not telling you about the errors that are preventing the update from continuing (even worse).
[1] Either that or you just type "pacman -Syu" then walk away ignoring any output.
This is the output for pacman -Syu:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
warning: oss: local (4.2_2007-3) is newer than community (4.2_2007-2)
there is nothing to do
Offline
Whisky Tango Foxtrot, over?
You might look here
And most certainly here
Edit: We were posting at the same time. Try a pacman -Syyu
Edit2: Or try a different mirror...
Last edited by ewaller (2013-06-11 23:06:54)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Offline
It is my opening move ....
We will see how that goes....
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Whoa ... Sorry if I jumped to a conclusion - it wasn't much of a jump given the available info, but it may be a faulty conclusion - it's quite a coincidence though that this seemed to happen at exactly the same time as the update requiring intervention. This definitely looks like a database that isn't properly syncing, quite possible from a bad mirror.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I'd guess your mirror is out of date/stopped updating for some reason. Try another one.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Offline
Yes, all of you are right, the problem was the mirrors used in /etc/pacman.d/mirrorlist. I have uncommented some server from other countries, france, portugal, Japan, taiwan etc... In previous mirrrolist I only had United States and Spain.
and now at the end I get below errors (I guess I must follow the steps described in arch home page), right?:
.......
error: failed to commit transaction (conflicting files)
filesystem: /bin exists in filesystem
filesystem: /sbin exists in filesystem
filesystem: /usr/sbin exists in filesystem
Errors occurred, no packages were upgraded.
Offline
Yup.
Offline
Thanks for the link. It is interesting.
Offline
This link is on the front page, like e.g. https://www.archlinux.org/mirrors/status/
I use reflector https://wiki.archlinux.org/index.php/Reflector
Offline
Yes, all of you are right, the problem was the mirrors used in /etc/pacman.d/mirrorlist. I have uncommented some server from other countries, france, portugal, Japan, taiwan etc... In previous mirrrolist I only had United States and Spain.
Remember only the first mirror listed is used (as long as it responds with a valid file) regardless of if it is out of date or not.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
The thread, at this point, changed topic to the file system upgrade. Tail of thread was merged here
Closed
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Pages: 1
Topic closed