RE: Help! Stuck in apt-get
Hi Sebastion,
Why not open up "dselect", go to "Select" and then press "/" to search
for "gs-common" and go up one line, then press "_" to purge the file.
Repeat the search and re-install "gs-aladdin" (do not forget that
gs-common must remain selected, it's just easier to search for gs-common
than for gs alone). Note that the action of uninstalling gs will
probably reveal what package depends on it. Next, Hit "enter" then
select "install" to install/remove the needed packages -- that should
get you back up and running. If problem persists, purge gs and use
"remove" then go back and re-install gs-aladin. I'm sorry that I do not
know the cli commands for apt as yet :<
HTH,
Sam Stern
Bethesda, MD, USA
> -----Original Message-----
> From: Sebastian Canagaratna [mailto:scanagar@canax2.onu.edu]
> On Behalf Of Sebastian Canagaratna
> Sent: Tuesday, March 12, 2002 03:01 PM
> To: debian-user@lists.debian.org
> Subject: Help! Stuck in apt-get
>
>
> I have woody installed and just a few days ago I thought I would
> replace gs-aladdin with gs. This has got me into trouble
> where I can't
> proceed any further.
>
> I get
>
> gs: Depends: gs-common(>=0.2) but it is not installed
> E: unmet dependencies. Try using -f.
>
>
> When I try apt-get -f install
>
> I get
>
> dpkg: error processing /var/cache/.... gs-common
> trying to overwrite '/usr/bin/bdftops' which is also in
> package ghostscript'
>
> I don't seem to be able to get past this. Fortunately , the system
> is still working. There is no package called ghostscript, so
> I do not
> know what package is being referred to. Though gs-aladdin is
> reported as being uninstalled, I presume, since the system is working
> and gs has not been installed, that the ghostscript part of aladdin
> has not been completely removed. The problem is: How do I get it to
> instll gs-common so that it can then install gs ?
>
> Thanks for any suggestions.
>
> Sebastian.
> --
> Sebastian Canagaratna
> Department of Chemistry
> Ohio Northern University
> s-canagaratna@onu.edu
>
Reply to: