On Mon, 2011-01-31 at 00:34 +0100, Rene Engelhard wrote:
> tag 611583 + moreinfo
> tag 611583 + unreproducible
> thanks
>
> Hi,
>
> On Sun, Jan 30, 2011 at 02:38:18PM -0800, Ross Boylan wrote:
> > I do not know how severe this problem is; it may be trivial. Since
> > we're getting close to release I thought I'd report it.
>
> Well, lenny only has pheriphical matter on a squeeze release
> (except getting from stable to oldstable) :)
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.
> 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).
>
> > Setting up openoffice.org-report-builder-bin (1:2.4.1+dfsg-1+lenny11) ...
> > Setting up openoffice.org-filter-mobiledev (1:2.4.1+dfsg-1+lenny11) ...
> > Setting up openoffice.org (1:2.4.1+dfsg-1+lenny11) ...
> > Setting up openoffice.org-emailmerge (1:2.4.1+dfsg-1+lenny11) ...
> > Adding extension /usr/lib/openoffice/program/mailmerge.py...
> > unopkg failed.
> > done.
>
> 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.
> 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 said, just did a lenny8 (plain 5.0.8) -> lenny11 upgrade in a clean
> lenny chroot. works.
> I bet it's a local problem...
>
> > May be related to 513300.
>
> Nah, that is a scenario on 2.4.x -> 3.x upgrades (because some paths changed.)
> Which you obviously didn't do :)
>
> > 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.
Thanks.
Ross
>
> Grüße/Regards,
>
> René
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
