Entête en cours de reécriture, merci de patienter en lisant la réponse au mail de Adam Williamson, à Dimanche 23 Mars 2003 05:14
> Overall, I can broadly say...it worked. You were lucky, i did the same, and, it was a nightmare. Well, not really a nightmare. Since I was a newbie on upgrade with urpmi, i think i have done something wrong. just added the sources for cooker, and urpmi.update -a ; urpmi --auto-select --auto first problem, wget keep doing a connection for each file, and downloading the long listing. So i updated to use curl. curl wasn't able to work, a proxy problem. So, after having done something ( disabling a old proxy conf in urpmi ), I began the update. After 1 hour, /var is full, urpmi stopped, and I discover that my rpm database is corrupt ! ( well, it may be my fault, since i killed some curl process cause of proxy, I may have done a mistake... ) so, I try to rebuild, no way, and now, I have done a script to reinstall all rpm with urpmf , find and rpm -qf. But the computer still run, and, it runs well. So, is there something I missed for the upgrade ? Why did urpmi insist of downloading all package before installing them ? And, I think that rpm should check before creating rpmnew file, by doing a md5 checksum, to see if the file is not the same. FOr now, it look if the file is in the database and don't touch it if not. -- Mickaël Scherer
