[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

"aptitude update/upgrade" not syncing properly for a squeeze upgrade



Hi,

I'm posting to both lists since it seems to be relevant to both. The problem that I'm experiencing only seems to be happening on my armel (nslu2) systems. Squeeze upgrades to the i386 systems seem to be working properly. However, since aptitude is not (afaict) particularly an app targeted for one architecture, I thought the general debian community might be appropriate.

Anyway, in a nutshell, I'm upgrading from a reprepro local repository that is currently up to date with the debian repositories. I mirror the architectures that are used for production work here, armel and i386 being two. After having upgraded four i386 systems with no "major" problems, I tried upgrading one of my NAS nslu2 systems. It upgraded partially and is in a working state, but I have not gone any further until I solve the problem I am having.

From a pure lenny system, I do a "aptitude update" and it updates okay. Checking the lists in /v/l/apt/lists confirm that they are correct. When I do an "aptitude install aptitude", it says that there is nothing to do. If I run aptitude in curses mode and search for aptitude it shows only the installed version 0.4.11 of aptitude and not the newer (not installed) version 0.6.3. Doing everything with "apt-get" produces the same results. I did do a "safe-upgrade" on one slug and it did upgrade some packages and consequently something is registering from squeeze in the Package updates but not the complete upgrade. It still runs okay.

Doing a squeeze update and attempted aptitude install aptitude on another lenny slug also produces the same behavior, i.e. nothing to install.

I did a bit of a web search but did not find anything relevant. I also looked at the man pages to see if there was any reset functionality in apt-get or aptitude. Removing the lists in /v/l/apt/lists didn't fix it. Nothing in /etc/apt/apt.conf.d seems to be the issue (no /etc/apt/apt.conf). And so I'm not sure (or remember) which file is screwing things up. My choice now is diving into the code, which I'm sure would be very educational, or forcing the aptitude upgrade via dpkg, supplying all of the dependencies that I noticed from the i386 upgrades in the process.

However, I suspect someone out "there" knows what is happening well enough to short circuit this process and provide a quicker solution. Thanks for any help.

-jeff


Reply to: