Hola Steve Langasek <vorlon@debian.org> el Mon, 8 Nov 2010 12:18:10 -0800 escribiste: > > I try to update to the last version of aptitude: > > > aptitude install aptitude > > This is not the recommended method of upgrading to squeeze. See > <http://www.debian.org/releases/testing/i386/release-notes/ch-upgrading.en.html#upgradingpackages>. Oh, I was googling for this document prior to the upgrade (looking for debain squeeze upgrade) but I din't find it. > > evolution refuses to upgrade because it is already running. > > > [...] > > Could you file a bug report against evolution for this issue? I don't think > this is an appropriate failure mode for such a package. At most, evolution > should prompt the user (via debconf) to close any running evolution > sessions, and only *then* abort if the user continues without doing so. Well, in fact debconf sends an email to root on behalf of evolution, but I didn't see it until later. I have debconf configured for unattended non-interactive runs. The problem is that eolution breaks the unattended upgrade, but I don't know how should this be addressed. ¿Do you already think I should file a bug report about this issue? > > It tries to download iceweasel, but ... > > > [...] > > Heh, I don't think there's much we can do to help you with that; there's > always some point in the install when local services will be unavailable. Well, in fact there are three questions related to apt/aptitude that could be addressed to avoid a lot of probems. First, why apt decides to install iceweassel (I have not requested it) in the middle of the upgrade, and not at the very beginning. I always make a full download before the actual upgrade. Second, apt should not halt when an error occurs. It should try to upgrade as most packages as possible, and finally stop with a list of broken packages due to errors. Third, apt should be more atomic when upgrading packages. It should go to the cycle prepare/unpack/configure for each package in turn. This slows down the process, but avoids problems with "external" dependencies (invisible to apt) like the one with approx (apt doesn't know in my system there is a dependency from all packages to approx). The same have happened to me with VPN software: the upgrade stops the VPN daemon and leaves the system unconnected while other packages are being upgraded. Then, if some other package breaks, the upgrade stops with the remote connection stopped: system isolated. The first issue is a bug. The last two issues should be wish-listed against apt, but i think they are difficult to solve. They affect the very inners of the workings of the apt. > > The only one post-upgrade issue I have find so far is that some > > xserver-xorg-video-* had been removed, and the X server refused to > > start. Installing xserver-xorg-video-ati solved the problem. > > That in particular is of concern. Could you please post a log of this > upgrade (from /var/log/apt/term.log, maybe), so that we can see why these > drivers were removed? I think the old system used the radeon driver. I've been looking at the logs but don't see why the X server broke. I attach the logs. Two more issues related to the upgrade: I use xfce4 as desktop environment. After upgrade the default session is set to Xscript, and gdm says that there is not xfce4 session available. In fact manually selecting the xfce4 session my last session is properly recovered. I used to have the specific-Debian-menu inside the xfce4 menu generated by the menu and menu-xdg packages. It has dissapear and I don't know how to recover. I have menu amd menu-xdg installed. -- Gonzalo Pérez de Olaguer Córdoba <gpoc@iies.es> --- www.gpoc.es PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704
Attachment:
term.log.gz
Description: GNU Zip compressed data
Attachment:
signature.asc
Description: PGP signature