Aaron Griffin schrieb:
Here we go. I was about to move pacman 3 to current last night and realized there is a minor show-stopper in the upgrade path.
The way pacman 2.X works, when it finds an upgrade for itself, it removes _ALL_ additional targets from the list and adds pacman. At this point, deps have already been resolved.
So, the new pacman depends on libdownload and libarchive. Clearing out the target list also removes these. So pacman will download pacman3, then try to install it, and fail because dependencies are missing.
I knew that :) I thought you knew, too.
The use case will go as follows: pacman -Syu "New pacman is available, upgrade? [Y/n]" Y ...download pacman 3... Whoops, cannot find dependencies "libdownload" or "libarchive", failing "Hmmm, wtf?" pacman -S libdownload libarchive pacman -Syu
There was the suggestion of pushing a fixed pacman2 out there. I hate it. pacman2 is so buggy with dependencies and just pushing out a new release to make the update smoother appears stupid. And it will confuse people. And it will be a waste of time to change the pacman2 codebase again. We need pacman3 now and I suggest we just move it. If we post a news item, an item in the Announcements forum and add a repeated irc message, people will pick it up.