Re: apt-get failure: no script in the new version of the package
OK, I fixed it. I manually downloaded an earlier, more robust version of esound-common from ftp.debian.org and did a dpkg -i. After that I ran apt-get -f install and now it's whistling clean: [EMAIL PROTECTED]:~# dpkg -i esound-common_0.2.35-2_all.deb dpkg - warning: downgrading esound-common from 0.2.35-2.1 to 0.2.35-2. (Reading database ... 358586 files and directories currently installed.) Preparing to replace esound-common 0.2.35-2.1 (using esound-common_0.2.35-2_all.deb) ... error: empty control file at /usr/sbin/install-docs line 621. dpkg: warning - old pre-removal script returned error exit status 21 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. Unpacking replacement esound-common ... Setting up esound-common (0.2.35-2) ... [EMAIL PROTECTED]:~# apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: esound-common The following packages will be REMOVED: libwine libwine-print libwine-twain wine wine-utils winetools The following packages will be upgraded: esound-common 1 upgraded, 0 newly installed, 6 to remove and 1892 not upgraded. 8 not fully installed or removed. Need to get 0B/38.2kB of archives. After unpacking 11.2MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 358586 files and directories currently installed.) Preparing to replace esound-common 0.2.35-2 (using .../esound-common_0.2.36-3_all.deb) ... Unpacking replacement esound-common ... (Reading database ... 358542 files and directories currently installed.) Removing libwine-twain ... Removing wine-utils ... Removing winetools ... Removing libwine-print ... Removing wine ... Removing libwine ... Setting up esound-common (0.2.36-3) ... Setting up libesd0 (0.2.36-3) ... Setting up esound (0.2.36-3) ... Setting up libgnome2-0 (2.10.1-1) ... Setting up gnome-about (2.10.2-1) ... Setting up libgnome-desktop-2 (2.10.2-1) ... Setting up libpanel-applet2-0 (2.10.2-1) ... Setting up gnome-panel (2.10.2-1) ... Setting up libesd0-dev (0.2.36-3) ... [EMAIL PROTECTED]:~# I'm not under the impression that anyone is listening; this is kind of for my own notes at this point, but if you are listening, honk if you love the Flying Spaghetti Monster. Ron Hale-Evans [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get failure: no script in the new version of the package
On 28 Jan 2006 00:18:28 -0800 Ron Hale-Evans [EMAIL PROTECTED] wrote: OK, I fixed it. I manually downloaded an earlier, more robust version of esound-common from ftp.debian.org and did a dpkg -i. After that I ran apt-get -f install and now it's whistling clean: [EMAIL PROTECTED]:~# dpkg -i esound-common_0.2.35-2_all.deb dpkg - warning: downgrading esound-common from 0.2.35-2.1 to 0.2.35-2. (Reading database ... 358586 files and directories currently installed.) Preparing to replace esound-common 0.2.35-2.1 (using esound-common_0.2.35-2_all.deb) ... error: empty control file at /usr/sbin/install-docs line 621. dpkg: warning - old pre-removal script returned error exit status 21 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. Unpacking replacement esound-common ... Setting up esound-common (0.2.35-2) ... [EMAIL PROTECTED]:~# apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: esound-common The following packages will be REMOVED: libwine libwine-print libwine-twain wine wine-utils winetools The following packages will be upgraded: esound-common 1 upgraded, 0 newly installed, 6 to remove and 1892 not upgraded. 8 not fully installed or removed. Need to get 0B/38.2kB of archives. After unpacking 11.2MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 358586 files and directories currently installed.) Preparing to replace esound-common 0.2.35-2 (using .../esound-common_0.2.36-3_all.deb) ... Unpacking replacement esound-common ... (Reading database ... 358542 files and directories currently installed.) Removing libwine-twain ... Removing wine-utils ... Removing winetools ... Removing libwine-print ... Removing wine ... Removing libwine ... Setting up esound-common (0.2.36-3) ... Setting up libesd0 (0.2.36-3) ... Setting up esound (0.2.36-3) ... Setting up libgnome2-0 (2.10.1-1) ... Setting up gnome-about (2.10.2-1) ... Setting up libgnome-desktop-2 (2.10.2-1) ... Setting up libpanel-applet2-0 (2.10.2-1) ... Setting up gnome-panel (2.10.2-1) ... Setting up libesd0-dev (0.2.36-3) ... [EMAIL PROTECTED]:~# I'm not under the impression that anyone is listening; this is kind of for my own notes at this point, but if you are listening, honk if you love the Flying Spaghetti Monster. just saw your thread and you solved it before I could suggest trying an earlier version. really! may his noodly appendage guide you. Ramen. A Ron Hale-Evans [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] pgph8K8knHqn2.pgp Description: PGP signature
Re: apt-get failure: no script in the new version of the package
Still no luck. I've discovered that dpkg --configure -a is my friend -- it seemed to uncork things a bit, but it only helped so much. A broken esound-common install still seems to be the crux of the problem, but the error messages I'm getting are a deep mystery. What am I doing wrong? I would be grateful for _any_ help, even if I have to muck about inside /var/lib/dpkg/info, putting right what once went wrong, and hoping that each tweak will be the tweak home. [EMAIL PROTECTED]:~# apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: esound-common The following packages will be REMOVED: libwine libwine-print libwine-twain wine wine-utils winetools The following packages will be upgraded: esound-common 1 upgraded, 0 newly installed, 6 to remove and 1892 not upgraded. 8 not fully installed or removed. Need to get 0B/38.2kB of archives. After unpacking 11.2MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 358586 files and directories currently installed.) Preparing to replace esound-common 0.2.35-2.1 (using .../esound-common_0.2.36-3_all.deb) ... /usr/share/doc-base/esound-common: cannot open control file for reading: No such file or directory dpkg: warning - old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: error processing /var/cache/apt/archives/esound-common_0.2.36-3_all.deb (--unpack): there is no script in the new version of the package - giving up Errors were encountered while processing: /var/cache/apt/archives/esound-common_0.2.36-3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED]:~# Ron Hale-Evans [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
apt-get failure: no script in the new version of the package
I'm running a Knoppix 4.0 DVD distro installed to hard drive, and recently apt has refused to update or install _anything_. I seem to have some packages halfway installed, or perhaps installed twice (as it appears in synaptic), notably esound-common (I was tweaking my sound packages a few weeks back). Here is the script of a recent attempt: [EMAIL PROTECTED]:~# apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: esound-common The following packages will be REMOVED: libwine libwine-print libwine-twain wine wine-utils winetools The following packages will be upgraded: esound-common 1 upgraded, 0 newly installed, 6 to remove and 1894 not upgraded. 3 not fully installed or removed. Need to get 0B/38.2kB of archives. After unpacking 11.2MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 358458 files and directories currently installed.) Preparing to replace esound-common 0.2.35-2.1 (using .../esound-common_0.2.36-3_all.deb) ... /usr/share/doc-base/esound-common: cannot open control file for reading: No such file or directory dpkg: warning - old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: error processing /var/cache/apt/archives/esound-common_0.2.36-3_all.deb (--unpack): there is no script in the new version of the package - giving up Errors were encountered while processing: /var/cache/apt/archives/esound-common_0.2.36-3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I've tried a lot of things, including plenty of Googling, but it all boils down to this. FWIW, fsck notices a few errors it can't fix on my HD; I'll get to those soon by booting from the original Knoppix DVD. The errors don't seem to be in /etc/apt or anything. I'm almost at the point of reinstalling, but I really don't want to do that. Any other ideas? Thanks, Ron Hale-Evans [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing .v. unstable .v. sarge (WAS Re: apt-get Failure)
Brian Nelson wrote: First of all, the sarge security autobuilders are still not yet functional, which is the biggest thing holding back the release. But until we have released, those autobuilders would not be used for security updates for sarge anyway. Security fixes are currently reaching sarge in the usual way. Based on data I've seen, testing typically has around 50-100 open security vulnerabilities at any time. That number is a little lower now because we're so close to release, but there are still around 30. What data do you base the figure of 100 on? The mail you refered to contained duplicates in its lists between CANs and DSAs. Of course counting security holes is an iffy business anyway, since a given CAN may stand in for one or a dozen holes, or a set of several CANs might cover some holes that are closely related and all fixed in the same upload to debian. And of course the mail you referred to represents an effort to back-check over two years of security holes against sarge. Since this has, AFAIK, never been done for a previous Debian release, there's no data for comparison. -- see shy jo signature.asc Description: Digital signature
Re: apt-get Failure
Michael Spang wrote: Sed's postinst contains this line, which fails: sudo install-info --quiet --section General commands General commands /usr/share/info/sed.info The bug is apparently resolved so a fix should be on the way. Robert Tilley wrote: The sed package causes apt-get upgrade to stop. [EMAIL PROTECTED]:~# apt-get -f upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back: libqt3-compat-headers libqt3-headers libqt3-mt-dev libqt3c102-mt qt3-dev-tools The following packages will be upgraded: console-data inkscape kernel-image-2.6.9-1-686 kvim-perl libexif10 mozilla-stumbleupon python-gnome2 python2.3-gnome2 qt3-assistant qt3-doc qt3-qtconfig valgrind vim vim-common vim-doc 15 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 1 not fully installed or removed. Need to get 0B/35.8MB of archives. After unpacking 1061kB disk space will be freed. Do you want to continue? [Y/n] Reading changelogs... Preconfiguring packages ... Setting up sed (4.1.2-2) ... No `START-INFO-DIR-ENTRY' and no `This file documents'. install-info(/usr/share/info/sed.info): unable to determine description for `dir' entry - giving up dpkg: error processing sed (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: sed E: Sub-process /usr/bin/dpkg returned an error code (1) Can someone with more knowledge than myself provide some insight into this problem? Bob so what do I do meantime? I'm in the middle of switching from stable to unstable when it hit the `sed` issue aborted the dist-upgrade. I guess i have to wait for the bug-fix to get into unstable and then try again? (BTW followed the link in another email but it didn't really help me) michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get Failure
On Wed, Nov 17, 2004 at 09:13:12AM +, michael wrote: Michael Spang wrote: Sed's postinst contains this line, which fails: sudo install-info --quiet --section General commands General commands /usr/share/info/sed.info The bug is apparently resolved so a fix should be on the way. so what do I do meantime? I'm in the middle of switching from stable to unstable when it hit the `sed` issue aborted the dist-upgrade. I guess i have to wait for the bug-fix to get into unstable and then try again? (BTW followed the link in another email but it didn't really help me) Either grab the new version from incoming.debian.org that presumably fixes that bug, or grab an older version from snapshot.debian.net. -- For every sprinkle I find, I shall kill you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get Failure
On Wed, 17 Nov 2004 09:13:12 +, michael [EMAIL PROTECTED] wrote: Michael Spang wrote: so what do I do meantime? I'm in the middle of switching from stable to unstable when it hit the `sed` issue aborted the dist-upgrade. I guess i have to wait for the bug-fix to get into unstable and then try again? (BTW followed the link in another email but it didn't really help me) Sit tight - welcome to the world of unstable! Better get used to it ;) -- Jon Dowland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
testing .v. unstable .v. sarge (WAS Re: apt-get Failure)
On Wed, 17 Nov 2004 09:13:12 +, michael [EMAIL PROTECTED] wrote: Michael Spang wrote: so what do I do meantime? I'm in the middle of switching from stable to unstable when it hit the `sed` issue aborted the dist-upgrade. I guess i have to wait for the bug-fix to get into unstable and then try again? (BTW followed the link in another email but it didn't really help me) Sit tight - welcome to the world of unstable! Better get used to it ;) Inspired by the above and not being able to find anything recent in the mailing lists, may I ask people's views on which flavour (is that the correct term?) of Debian out of testing unstable is currently recommended for a workstation (which will be used for running scientific codes, should not crashing for months on end, is secure from hackers and able to handle things like Fortran C (running with MPI), Intel compilers (don't flame me!) and, probably, NFS mounts with other boxes in the locality) I initially went for 'stable' (woody) but it was too out of date for my Ethernet card hard drive. I've now installed 'testing' (sarge) and have followed recommendations in the Securing Debian Manual. However, I've been warned that there are no security updates for 'testing'. I also see hints on this list that 'sarge' is about to be the new 'stable' (although I'm unsure how when!) from which I infer that there will soon be security updates for 'sarge'. Therefore, I think I'm as well staying with 'sarge' rather than moving to 'unstable' (sid), particularly in light of the above ''sed'' problem (as an example). For those with eagle eyes, yes I am talking now about a different system to the initial (apt-get failure) case! Many thanks to all! Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing .v. unstable .v. sarge (WAS Re: apt-get Failure)
On Wed, Nov 17, 2004 at 01:22:44PM -, michael wrote: Inspired by the above and not being able to find anything recent in the mailing lists, may I ask people's views on which flavour (is that the correct term?) of Debian out of testing unstable is currently recommended for a workstation (which will be used for running scientific codes, should not crashing for months on end, is secure from hackers and able to handle things like Fortran C (running with MPI), Intel compilers (don't flame me!) and, probably, NFS mounts with other boxes in the locality) Woody. Sorry. Sarge has been very stable lately, but there are no guarantees and random packages will sometimes break. I initially went for 'stable' (woody) but it was too out of date for my Ethernet card hard drive. I've now installed 'testing' (sarge) and have followed recommendations in the Securing Debian Manual. However, I've been warned that there are no security updates for 'testing'. I also see hints on this list that 'sarge' is about to be the new 'stable' (although I'm unsure how when!) from which I infer that there will soon be security updates for 'sarge'. Therefore, I think I'm as well staying with 'sarge' rather than moving to 'unstable' (sid), particularly in light of the above ''sed'' problem (as an example). Nobody knows when Sarge goes stable. Speculation was December. I'd bet on March, if I were a betting man. It's all guesswork, though, even the release manager can't (and shouldn't) give a date now. I recommend Sarge over Sid, but it's based on only one person's experience with a couple of computers, so don't take it too seriously. Because it's nearly-stable, Sarge is getting security updates in a very timely fashion just now. If you go with anything but stable, do your apt-get upgrades when you're physically present, then immediately test everything critical in case you have to revert. -- Carl Fink [EMAIL PROTECTED] Jabootu's Minister of Proofreading http://www.jabootu.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get Failure
Brian Nelson wrote: On Wed, Nov 17, 2004 at 09:13:12AM +, michael wrote: Michael Spang wrote: Sed's postinst contains this line, which fails: sudo install-info --quiet --section General commands General commands /usr/share/info/sed.info The bug is apparently resolved so a fix should be on the way. so what do I do meantime? I'm in the middle of switching from stable to unstable when it hit the `sed` issue aborted the dist-upgrade. I guess i have to wait for the bug-fix to get into unstable and then try again? (BTW followed the link in another email but it didn't really help me) Either grab the new version from incoming.debian.org that presumably fixes that bug, or grab an older version from snapshot.debian.net. Or just temporarily comment out the line in ths postinst to pacify dpkg, as follows. Not installing the info shouldn't have serious consequences. The newer version seems to have appeared in my mirror's package list within the last hour, however. /var/lib/dpkg/info/sed.postinst: #! /bin/sh -e pkg=sed if [ ! $1 = configure ]; then exit 0 fi #install-info --quiet --section General commands General commands \ #/usr/share/info/sed.info BTW, is there an easy way to make reply in Thunderbird send to the mailing list list instead of the author of the message? I find it a pain to change the address each time. Michael Spang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing .v. unstable .v. sarge (WAS Re: apt-get Failure)
On Wed, Nov 17, 2004 at 03:45:43PM -0500, Carl Fink wrote: On Wed, Nov 17, 2004 at 01:22:44PM -, michael wrote: I initially went for 'stable' (woody) but it was too out of date for my Ethernet card hard drive. I've now installed 'testing' (sarge) and have followed recommendations in the Securing Debian Manual. However, I've been warned that there are no security updates for 'testing'. I also see hints on this list that 'sarge' is about to be the new 'stable' (although I'm unsure how when!) from which I infer that there will soon be security updates for 'sarge'. Therefore, I think I'm as well staying with 'sarge' rather than moving to 'unstable' (sid), particularly in light of the above ''sed'' problem (as an example). Nobody knows when Sarge goes stable. Speculation was December. I'd bet on March, if I were a betting man. It's all guesswork, though, even the release manager can't (and shouldn't) give a date now. I recommend Sarge over Sid, but it's based on only one person's experience with a couple of computers, so don't take it too seriously. Because it's nearly-stable, Sarge is getting security updates in a very timely fashion just now. Why would you think that? First of all, the sarge security autobuilders are still not yet functional, which is the biggest thing holding back the release. Second of all, there are still many open security holes in testing: http://lists.alioth.debian.org/pipermail/secure-testing-team/2004-November/00.html Based on data I've seen, testing typically has around 50-100 open security vulnerabilities at any time. That number is a little lower now because we're so close to release, but there are still around 30. -- For every sprinkle I find, I shall kill you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
apt-get Failure
The sed package causes apt-get upgrade to stop. [EMAIL PROTECTED]:~# apt-get -f upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back: libqt3-compat-headers libqt3-headers libqt3-mt-dev libqt3c102-mt qt3-dev-tools The following packages will be upgraded: console-data inkscape kernel-image-2.6.9-1-686 kvim-perl libexif10 mozilla-stumbleupon python-gnome2 python2.3-gnome2 qt3-assistant qt3-doc qt3-qtconfig valgrind vim vim-common vim-doc 15 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 1 not fully installed or removed. Need to get 0B/35.8MB of archives. After unpacking 1061kB disk space will be freed. Do you want to continue? [Y/n] Reading changelogs... Preconfiguring packages ... Setting up sed (4.1.2-2) ... No `START-INFO-DIR-ENTRY' and no `This file documents'. install-info(/usr/share/info/sed.info): unable to determine description for `dir' entry - giving up dpkg: error processing sed (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: sed E: Sub-process /usr/bin/dpkg returned an error code (1) Can someone with more knowledge than myself provide some insight into this problem? Bob -- She said, `I know you ... you cannot sing'. I said, `That's nothing, you should hear me play piano.' -- Morrisey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get Failure
Sed's postinst contains this line, which fails: sudo install-info --quiet --section General commands General commands /usr/share/info/sed.info The bug is apparently resolved so a fix should be on the way. Robert Tilley wrote: The sed package causes apt-get upgrade to stop. [EMAIL PROTECTED]:~# apt-get -f upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back: libqt3-compat-headers libqt3-headers libqt3-mt-dev libqt3c102-mt qt3-dev-tools The following packages will be upgraded: console-data inkscape kernel-image-2.6.9-1-686 kvim-perl libexif10 mozilla-stumbleupon python-gnome2 python2.3-gnome2 qt3-assistant qt3-doc qt3-qtconfig valgrind vim vim-common vim-doc 15 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 1 not fully installed or removed. Need to get 0B/35.8MB of archives. After unpacking 1061kB disk space will be freed. Do you want to continue? [Y/n] Reading changelogs... Preconfiguring packages ... Setting up sed (4.1.2-2) ... No `START-INFO-DIR-ENTRY' and no `This file documents'. install-info(/usr/share/info/sed.info): unable to determine description for `dir' entry - giving up dpkg: error processing sed (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: sed E: Sub-process /usr/bin/dpkg returned an error code (1) Can someone with more knowledge than myself provide some insight into this problem? Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get Failure
As Thomas previously suggested: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281601 bye Robert Tilley wrote: The sed package causes apt-get upgrade to stop. [EMAIL PROTECTED]:~# apt-get -f upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back: libqt3-compat-headers libqt3-headers libqt3-mt-dev libqt3c102-mt qt3-dev-tools The following packages will be upgraded: console-data inkscape kernel-image-2.6.9-1-686 kvim-perl libexif10 mozilla-stumbleupon python-gnome2 python2.3-gnome2 qt3-assistant qt3-doc qt3-qtconfig valgrind vim vim-common vim-doc 15 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 1 not fully installed or removed. Need to get 0B/35.8MB of archives. After unpacking 1061kB disk space will be freed. Do you want to continue? [Y/n] Reading changelogs... Preconfiguring packages ... Setting up sed (4.1.2-2) ... No `START-INFO-DIR-ENTRY' and no `This file documents'. install-info(/usr/share/info/sed.info): unable to determine description for `dir' entry - giving up dpkg: error processing sed (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: sed E: Sub-process /usr/bin/dpkg returned an error code (1) Can someone with more knowledge than myself provide some insight into this problem? Bob -- - Riccardo Tortorici - Linux Registered User #365170 Count yourself @ http://counter.li.org/ ! Proudly Running Debian GNU/Linux Sid - Linux Kernel 2.6.9 -- HTML email can be dangerous, is not always readable, wastes bandwidth and is simply not necessary please don't send them to me! If you don't know what I'm talking about please read this: http://www.georgedillon.com/web/netiquette.shtml -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Prestiti Online. Scopri subito se sei finanziabile. in 24 ore senza spese né anticipi, clicca qui * Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2908d=17-11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
apt-get failure
I have a cron job that runs every morning that includes: apt-get -q update apt-get -q -s dist-upgrade Today it produced the following error message: Fetched 6713kB in 28s (238kB/s) Reading Package Lists... E: Dynamic MMap ran out of room E: Error occured while processing aspell (NewVersion1) E: Problem with MergeList /var/lib/dpkg/status E: The package lists or status file could not be parsed or opened. My last upgrade was January 15, and this cron job ran successfully on the 16th and 17th, so I doubt if it is a bug in a newly upgraded package. /var/lib/dpkg/status looks normal, and has the following permissions: -rw-r--r--1 root root 718493 Jan 18 10:36 /var/lib/dpkg/status I don't know if Dynamic MMap ran out of room refers to memory, but I have plenty available: total used free sharedbuffers cached Mem: 1030220 876292 153928 0 128236 488572 -/+ buffers/cache: 259484 770736 Swap: 2096624 02096624 What is the probable cause of this failure? Regards Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get failure
This one time, at band camp, Bob Hilliard said: Fetched 6713kB in 28s (238kB/s) Reading Package Lists... E: Dynamic MMap ran out of room E: Error occured while processing aspell (NewVersion1) E: Problem with MergeList /var/lib/dpkg/status E: The package lists or status file could not be parsed or opened. This is now a FAQ - it comes up every day or so at least once. Please check the archives available at lists.debian.org. You can search this list, most recent quarter, for MMap, and get about a zillion hits. I am not trying to be rude, here, but the same question coming up over and over means no one is doing any homework before writingoff to the list, and it's getting old. I am sorry to pick on you - you're just getting the brunt of it. -- -- | Stephen Gran | Always look over your shoulder because | | [EMAIL PROTECTED] | everyone is watching and plotting | | http://www.lobefin.net/~steve | against you.| -- msg24817/pgp0.pgp Description: PGP signature
apt-get failure on perl
i hope someone can point me to a solution on this. i've been chasing it for days with no luck. i have a machine running woody. i hadn't updated it in a while, so a few days ago, i did an apt-get update, apt-get upgrade on it. here's the results. any suggestions will be /greatly/ appreciated. firestarter:/home/stephen# apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done You might want to run `apt-get -f install' to correct these. Sorry, but the following packages have unmet dependencies: perl: Depends: perl-modules (= 5.6.1-4) but 5.6.1-5 is installed E: Unmet dependencies. Try using -f. firestarter:/home/stephen# apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: perl perl-base 2 packages upgraded, 0 newly installed, 0 to remove and 374 not upgraded. 2 packages not fully installed or removed. Need to get 0B/1637kB of archives. After unpacking 0B will be used. Do you want to continue? [Y/n] Y (Reading database ... 63582 files and directories currently installed.) Preparing to replace perl 5.6.1-4 (using .../archives/perl_5.6.1-5_i386.deb) ... Unpacking replacement perl ... dpkg: error processing /var/cache/apt/archives/perl_5.6.1-5_i386.deb (--unpack): trying to overwrite directory `/usr/share/doc/perl' in package perl-base with nondirectory dpkg-deb: subprocess paste killed by signal (Broken pipe) Preparing to replace perl-base 5.6.1-4 (using .../perl-base_5.6.1-5_i386.deb) ... Unpacking replacement perl-base ... dpkg: error processing /var/cache/apt/archives/perl-base_5.6.1-5_i386.deb (--unpack): trying to overwrite directory `/usr/share/doc/perl' in package perl with nondirectory dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/perl_5.6.1-5_i386.deb /var/cache/apt/archives/perl-base_5.6.1-5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- ) ,_) (-(__ -|- __ ) | (/_\/(/_ ( ___ | http://www.exitwound.org : hard to find music | ___ | Entreprenuer, n.: A high-rolling risk taker | | who would rather be a spectacular failure | | than a dismal success.| ___
apt-get failure
i hope someone can point me to a solution on this. i've been chasing it for days with no luck. i have a machine running woody. i hadn't updated it in a while, so a few days ago, i did an apt-get update, apt-get upgrade on it. here's the results. any suggestions will be /greatly/ appreciated. firestarter:/home/stephen# apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done You might want to run `apt-get -f install' to correct these. Sorry, but the following packages have unmet dependencies: perl: Depends: perl-modules (= 5.6.1-4) but 5.6.1-5 is installed E: Unmet dependencies. Try using -f. firestarter:/home/stephen# apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: perl perl-base 2 packages upgraded, 0 newly installed, 0 to remove and 374 not upgraded. 2 packages not fully installed or removed. Need to get 0B/1637kB of archives. After unpacking 0B will be used. Do you want to continue? [Y/n] Y (Reading database ... 63582 files and directories currently installed.) Preparing to replace perl 5.6.1-4 (using .../archives/perl_5.6.1-5_i386.deb) ... Unpacking replacement perl ... dpkg: error processing /var/cache/apt/archives/perl_5.6.1-5_i386.deb (--unpack): trying to overwrite directory `/usr/share/doc/perl' in package perl-base with nondirectory dpkg-deb: subprocess paste killed by signal (Broken pipe) Preparing to replace perl-base 5.6.1-4 (using .../perl-base_5.6.1-5_i386.deb) ... Unpacking replacement perl-base ... dpkg: error processing /var/cache/apt/archives/perl-base_5.6.1-5_i386.deb (--unpack): trying to overwrite directory `/usr/share/doc/perl' in package perl with nondirectory dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/perl_5.6.1-5_i386.deb /var/cache/apt/archives/perl-base_5.6.1-5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- ) ,_) (-(__ -|- __ ) | (/_\/(/_ ( ___ | http://www.exitwound.org : hard to find | ___ | If a thing's worth having, it's worth | | cheating for. -- W.C. Fields | ___
