Bug#401372: iceape-browser: crashes on startup

[Andreas Barth]

* Mike Hommey (mh at glandium.org) [061223 10:03]:
> On Fri, Dec 22, 2006 at 07:45:24PM +0100, Andreas Barth <aba at not.so.argh.org> wrote:
> > BTW, these packages currently still contain /usr/lib/iceape/chrome in
> > unstable:
> > usr/lib/iceape/chrome                                       web/iceape-browser
> > usr/lib/iceape/chrome/checky                                web/mozilla-checky
> 
> Dammit, I left one !
> 
> > usr/lib/iceape/chrome/imagezoom.jar                         web/mozilla-imagezoom
> > usr/lib/iceape/chrome/mozgest.jar                           web/mozilla-mozgest
> > usr/lib/iceape/chrome/stumbleupon.jar                       web/mozilla-stumbleupon
> > 
> > I think we should file RC-bugs against all but the first to move their
> > file out.
> 
> That won't be enough to be sure of the upgrade path.

Of course - but I think that are still bugs?

> Moreover, iceape
> itself generates files in usr/lib/iceape/chrome through
> update-iceape-chrome (which are really intended to go in
> usr/share/iceape/chrome).

Can't we change the patch in update-iceape-chrome?

> They would need to be removed before the
> symlink may be created.

Can we safely remove them in all cases? I thought about moving them to
/usr/share/iceape/chrom in case the file doesn't exist there, and
bailing out with a resume instruction in case the file exists in both
places.


Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/