It has this in it:
if [ -x /usr/bin/rebuild-gcj-db ]; then
/usr/bin/rebuild-gcj-db
fi
--
[Hardy-updates] openoffice.org-gcj dpkg error - should use dh_nativejava
https://bugs.launchpad.net/bugs/299229
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Doh, this is hardcoded into the postrm.in :(
No cookie for me.
** Summary changed:
- [Hardy-updates] openoffice.org-gcj dpkg error
+ [Hardy-updates] openoffice.org-gcj dpkg error - should use dh_nativejava
--
[Hardy-updates] openoffice.org-gcj dpkg error - should use dh_nativejava
** Summary changed:
- [Hardy-updates] openoffice.org-gcj dpkg error - should use dh_nativejava
+ [Hardy-updates] openoffice.org-gcj dpkg error - snippet out of date
** Changed in: java-gcj-compat (Ubuntu)
Status: Incomplete = Invalid
** Changed in: openoffice.org (Ubuntu)
Assignee:
it is fixed:
if [ -x /usr/bin/rebuild-gcj-db ]; then
/usr/bin/rebuild-gcj-db || true
fi
how does the openoffice.org-gcj postrm look like?
** Changed in: java-gcj-compat (Ubuntu)
Status: New = Incomplete
** Also affects: openoffice.org (Ubuntu)
Importance: Undecided
This looks like bug 64395 but that was closed as fixed, the problem with
the generated snippet that Tollef mentioned still appears to be
occurring even in Jaunty.
** Changed in: java-gcj-compat (Ubuntu)
Sourcepackagename: openoffice.org = java-gcj-compat
--
[Hardy-updates] openoffice.org-gcj
Workaround for this packaging bug:
Rename /usr/bin/rebuild-gcj-db; reinstall openoffice.org-gcj; purge
openoffice.org-gcj.
Clue found in bug #64395
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/64395/comments/11
--
[Hardy-updates] openoffice.org-gcj dpkg error