2007/4/10, Andrew Fyfe <andrew@neptune-one.net>:
Roman Kyrylych wrote:
2007/4/10, Andrew Fyfe <andrew@neptune-one.net>:
Roman other than repos/servers, what's in your pacman.conf?
I've looked at the filesystem packages and it's got all the backup lines, so it's not a problem with the package itself.
I know, that's why I wonder, especially that old bug (when file was replaced during first update after NoUpgrade removed) shouldn't work now. I don't have access to my server now, but can assure you that there's nothing unusual in pacman.conf. As I said all NoUpgrade was removed since pacman 2.9.8 out so even that old bug shouldn't cause this. Besides .pacnew was created which is right, but WTH file was replaced - that's the point. I will do upgrade at home tomorrow (sure, backing up /etc previously) and will do it with --debug=3 now.
I did the upgrade last night and didn't have any problems, BUT I'm running with an updated copy of libalpm. I did notice that only group.pacnew was created. /etc/issue wasn't updated and there wasn't an issue.pacnew. (etc/issue was the file updated for the new release).
Hm, could you please then diff your version with 3.0.1 in part of backing up files? -- Roman Kyrylych (Роман Кирилич)