Bug#401372: iceape-browser: crashes on startup
aba at not.so.argh.org
Sat Dec 23 10:58:03 CET 2006
* Mike Hommey (mh at glandium.org) [061223 10:56]:
> On Sat, Dec 23, 2006 at 10:37:42AM +0100, Andreas Barth <aba at not.so.argh.org> wrote:
> > > That won't be enough to be sure of the upgrade path.
> > Of course - but I think that are still bugs?
> Yes, they are. I'm fixing checky right now.
Good. For the other packages, I'll open RC bugs then.
> > > 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?
> The files generated by update-iceape-chrome are actually generated by
> iceape itself. Changing the path is not an easy thing to do there.
> That's why we put symlinks in the first place.
> > > 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.
> The files generated by update-iceape-chrome can be safely removed. They
> are actually removed by update-iceape-chrome itself before regenerating
> them with iceape.
How can we check if files are generated by update-iceape-chrome? Or
should we just assume any file is generated by update-iceape-chrome?
More information about the pkg-mozilla-maintainers