Comments on: Upgrade Debian Sarge to Debian Etch

By: Ati

Ati — Fri, 14 Nov 2008 13:02:42 +0000

Hi,

I’m getting the following error when i try to update&&upgrade with aptitute

Preconfiguring packages ... Can't exec "/tmp/linux-image-2.6.18-6-686-bigmem.config.273351": Permission denied at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of /tmp/linux-image-2.6.18-6-686-bigmem.config.273351 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 58 linux-image-2.6.18-6-686-bigmem failed to preconfigure, with exit status 9 Can't exec "/tmp/linux-image-2.6.18-4-686-bigmem.config.273353": Permission denied at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of /tmp/linux-image-2.6.18-4-686-bigmem.config.273353 configure 2.6.18.dfsg.1-12~bpo.2 failed at /usr/share/perl5/Debconf/ConfModule.pm line 58 linux-image-2.6.18-4-686-bigmem failed to preconfigure, with exit status 9 (Reading database ... 52305 files and directories currently installed.) Unpacking linux-image-2.6.18-6-686-bigmem (from .../linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb) ... Done. dpkg: error processing /var/cache/apt/archives/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb (--unpack): failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./lib/modules/2.6.18-6-686-bigmem/kernel/fs/ntfs/ntfs.ko': No space left on device dpkg-deb: subprocess paste killed by signal (Broken pipe) Preparing to replace linux-image-2.6.18-4-686-bigmem 2.6.18.dfsg.1-12~bpo.2 (using .../linux-image-2.6.18-4-686-bigmem_2.6.18.dfsg.1-12etch2_i386.deb) ... The directory /lib/modules/2.6.18-4-686-bigmem still exists. Continuing as directed. Done. Unpacking replacement linux-image-2.6.18-4-686-bigmem ... dpkg: error processing /var/cache/apt/archives/linux-image-2.6.18-4-686-bigmem_2.6.18.dfsg.1-12etch2_i386.deb (--unpack): failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./lib/modules/2.6.18-4-686-bigmem/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko': No space left on device dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb /var/cache/apt/archives/linux-image-2.6.18-4-686-bigmem_2.6.18.dfsg.1-12etch2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

By: Jason

Jason — Mon, 23 Apr 2007 02:02:44 +0000

Why are you recommending using “–with-recommends” ? That has the potential to pull in a HUGE amount of unnecessary packages rather than just upgrading the ones that are installed.

By: Hans Ekbrand

Hans Ekbrand — Sun, 15 Apr 2007 20:35:22 +0000

Azar: see the release notes about the safest way to upgrade.

Admin: 1. using “stable” instead of “etch” in sources.list saves you from having to change sources.list with each new release.
2. Why do recommend using –with-recommends? I think with or without recommends is a personal preference that does not make the upgrade better or worse.
3. The release notes recommends that the upgrade is done in several steps, not a simple aptitude -f dist-upgrade.

By: Admin

Admin — Fri, 13 Apr 2007 07:56:50 +0000

i would suggest use dist-upgrade it will install all the available upgrades

By: Azar

Azar — Fri, 13 Apr 2007 00:51:12 +0000

Burning Question:
Should we dist-upgrade to etch while still using the 2.6.8 kernel from sarge, or after changing the sources.list to “etch” we should first install the 2.6.18 kernel?

Or immediately after dist-upgrade upgrade the kernel to 2.6.18?

What is the safer way to do it?

By: tiyun.de

tiyun.de — Mon, 09 Apr 2007 23:02:45 +0000

ab nach Etch…

Ich werde noch ein bisschen Zeit vergehen lassen bis der Rootie auf Etch gesetzt wird. Sobald genug Leute im Sycp-Forum positive Erfahrung gemacht haben, wird das in Angriff genommen. Vorher gucke ich dann nochmal über diese kleine Checkliste, der Di…