[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bothersome Brother package



On Sat, 2005-04-09 at 21:58 +0200, Osamu Aoki wrote:
> On Sat, Apr 09, 2005 at 04:14:51PM +0100, michael wrote:
> > I couldn't get a .deb from Brother (for printing) to install and now I
> > can't seem to get rid off it whatever I do (see below - it wouldn't
> > in/de-stall since some directories not present so I created them but it
> > doesn't help NB /usr/local has lots of my valuable data too!). I don't
> > need it since I've sorted how to print to the Brother printer without
> > said .deb but with it hanging about it's making present 'apt-get's very
> > messy. All help welcome - couldn't see how to sort this mess out from
> > the man pages.
> 
> 
> Your question is basically how to remove broken package.
> 
> My answe: fix it :-)

Indeed - my first time fixing a broken package and thanks to below it
helped!

> 
> > dpkg - warning: while removing hl5150dlpr, unable to remove directory
> > `/usr/loca l': Device or resource busy - directory may be a mount
> > point ?
> 
> WTF this package is doing???  God thing DPKG prevent this.

yes, I am extremely disappointed with this - Brother claimed to support
Linux for their printers!

> 
> > /var/lib/dpkg/info/hl5150dlpr.postrm: line 3: /etc/init.d/lpd: No such
> > file or d irectory
> > dpkg: error processing hl5150dlpr (--purge):
> >  subprocess post-removal script returned error exit status 127
> > /var/lib/dpkg/info/hl5150dlpr.postinst: line
> > 3: /usr/local/Brother/inf/setupPrin tcap: No such file or directory
> > /var/lib/dpkg/info/hl5150dlpr.postinst: line 4: /etc/init.d/lpd: No such
> > file or  directory
> 
> This is it.  Edit /var/lib/dpkg/info/hl5150dlpr.postinst !
> Read its code and do things which make sense to you by hand.
> Insert "exit 0" at the top and run "sudo apt-get remove --purge
> hl5150dlpr".

I basically commented out all lines (they all pointed to either
something in /usr/local or /etc/init.d/lpd) and then it worked

ta, Michael



Reply to: