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

Re: Dealing with "forcibly" installed packages



Hi Dan.

Dan H., 10.04.2007 18:06:
> the most recent etch upgrade broke the Opera web browser (I think
> because of new X libs). Googled for a fix and found one, downloaded the
> newest debs (v9.20) from opera.org.

Which one exactly?

> Unfortunately at first the .deb wouldn't install due to an unsatisfied
> dependency on libqt3c102-mt, which doesn't seem to be in etch.

There is no such package in the whole wide Debian world. Which package exactly
were you trying to install? None of the three hotfixes has such a dependency:

> Depends: libc6 (>= 2.1.3), xlib6g (>= 3.3.6) | xlibs | libxmu6, libqt3-mt (>= 3.3.4), libstdc++6

The package "libtqt3-mt" does exist in Etch.

> I
> thought, fuck it, Opera didn't need that package yesterday so it won't
> need it today and forced the installation of opera using dpkg's -f
> option. All went fine and Opera works.

Forcing something should be the last resort. You first should have looked around
in the web and post into the Blog[0] to clear things up.

> Then I wanted to install stuff using aptitude, and upon hitting 'g',
> aptitude dutifully informed me that opera was broken and insisted on its
> removal. Is there a possibility to flag a package to apt as "it works,
> so leave it alone and stop bitching"?

Maybe the following?

# aptitude keep-all


Regards, Mathias

[0] http://my.opera.com/desktopteam/blog/

-- 
debian/rules

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: