On Wed, May 09, 2007 at 01:18:32PM -0500, Aaron Griffin wrote:
On 5/9/07, Jason Chu <jason@archlinux.org> wrote:
On Wed, May 09, 2007 at 12:52:31PM -0500, Aaron Griffin wrote:
Jason, can you take this task on? I want to a) figure out a solution to the pacman upgrade issue b) deal with the package cleanup So I don't have huge amounts of time to spare at the moment.
I am also lacking in time. Can you explain the pacman upgrade issue a little better (there was a bug report about it at one point, right?)?
I will make sure something gets done, but I doubt I'll be the one to do it.
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.
Workaround: static-only pacman3 build? Jürgen