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

Bug#611583: openoffice.org-emailmerge: unopkg failed



Hi,

On Mon, Jan 31, 2011 at 10:09:32PM -0800, Ross Boylan wrote:
> The lenny->squeeze upgrade path might hit this, and the bug might be
> present in squeeze (if it's a bug, and not just a warning message).  Or,
> as you say, it might be specific to my setup.

Or not. At least I never saw it on my test dist-upgrades. Then again
lenny->squeeze has some possible other pitfalls...

> > And the version you report the bug against is the version from
> > lenny-security/lenny-proposed-updates.
> > 
> > > On a recent update to a lenny system
> > 
> > *to* a lenny? From what? etch? Now??
> lenny.  That is, I have a stable/lenny system and did an aptitude "U"
> upgrade (i.e., security fixes).

OK.

> > Hmm. And what happens if you run unopkg using -v manually? See
> > /var/lib/dpkg/info/openoffice.org-emailmerge.postinst for the exact command
> > line used. 
> Assuming this is the relevant section
> add_extension() {
>   echo -n "Adding extension $1..."
>   INSTDIR=`mktemp -d`
>   /usr/lib/openoffice/program/unopkg add --shared $1 \
>     "-env:UserInstallation=file:///$INSTDIR" \
>     '-env:UNO_JAVA_JFW_INSTALL_DATA=$ORIGIN/../share/config/javasettingsunopkginstall.xml' \
>     "-env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1"
>   if [ -n $INSTDIR ]; then rm -rf $INSTDIR; fi
>   echo " done."
> }
> , I don't know what $ORIGIN is.

You don't need to, it's evaluated by OOo itself.

> > Did you have OOo running while you ran the upgrade?
> Not that I was aware of.  My mail client probably had used it to view
> some MS Word attachments earlier. If that leaves something hanging
> around, it's possible OO was still running.

That's possible, yes...
Was/is there a soffice.bin process running?

> > >  APT policy: (990, 'stable'), (50, 'unstable')
> > 
> > Do you have packages from unstable installed? Which?
> How do I check?  I'm pretty sure I have some packages pulled in from the
> testing or unstable, but I don't recall which.  Unstable packages I
> probably built from source. apt-cacher and samba have had  some of that.

apt-show-versions can help you.

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70



Reply to: