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
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
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
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
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
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.
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.
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
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
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
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
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 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
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]:~#
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
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
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
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.
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.
19 matches
Mail list logo
