Debian Bug report logs - #468202
subprocess post-installation script returned error exit status 1

Package: openoffice.org-writer2latex; Maintainer for openoffice.org-writer2latex is Debian LibreOffice Maintainers <debian-openoffice@lists.debian.org>; Source for openoffice.org-writer2latex is src:openoffice.org (PTS, buildd, popcon).

Reported by: Steffen Moeller <steffen_moeller@gmx.de>

Date: Wed, 27 Feb 2008 16:51:01 UTC

Severity: grave

Found in version writer2latex/0.5-5

Fixed in version writer2latex/0.5-6

Done: Rene Engelhard <rene@debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to debian-bugs-dist@lists.debian.org, Debian OpenOffice Team <debian-openoffice@lists.debian.org>:
Bug#468202; Package openoffice.org-writer2latex. (full text, mbox, link).

Acknowledgement sent to Steffen Moeller <steffen_moeller@gmx.de>:
New Bug report received and forwarded. Copy sent to Debian OpenOffice Team <debian-openoffice@lists.debian.org>. (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

Package: openoffice.org-writer2latex
Version: 0.5-5
Severity: grave

There was nothing that I had done except for 
apt-get -u dist-upgrade
in Debian Sid

SM

Setting up openoffice.org-writer2latex (0.5-5) ...
Adding extension
/usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
unopkg failed.
dpkg: error processing openoffice.org-writer2latex (--configure):
 subprocess post-installation script returned error exit status 1
 Errors were encountered while processing:
  openoffice.org-writer2latex
  E: Sub-process /usr/bin/dpkg returned an error code (1)



-- Package-specific info:
Identifier: org.openoffice.legacy.writer2latex.uno.pkg
  URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/i9DLiP_/writer2latex.uno.pkg
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: Extension
  bundled Packages: {
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/i9DLiP_/writer2latex.uno.pkg/writer2latex.jar
      is registered: yes
      Media-Type: application/vnd.sun.star.uno-component;type=Java
      Description: UNO Java Component
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/i9DLiP_/writer2latex.uno.pkg/w2l_types.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/i9DLiP_/writer2latex.uno.pkg/w2l_filters.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
  }

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages openoffice.org-writer2latex depends on:
ii  openoffice.org-core        1:2.4.0~rc1-2 OpenOffice.org office suite archit
ii  openoffice.org-java-common 1:2.4.0~rc1-3 OpenOffice.org office suite Java s

openoffice.org-writer2latex recommends no packages.

-- no debconf information

Information forwarded to debian-bugs-dist@lists.debian.org, Debian OpenOffice Team <debian-openoffice@lists.debian.org>:
Bug#468202; Package openoffice.org-writer2latex. (full text, mbox, link).

Acknowledgement sent to Rene Engelhard <rene@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian OpenOffice Team <debian-openoffice@lists.debian.org>. (full text, mbox, link).

Message #10 received at 468202@bugs.debian.org (full text, mbox, reply):

tag 468202 + unreproducible
thanks

Hi,

Steffen Moeller wrote:
> Setting up openoffice.org-writer2latex (0.5-5) ...
> Adding extension
> /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
> unopkg failed.
> dpkg: error processing openoffice.org-writer2latex (--configure):
>  subprocess post-installation script returned error exit status 1
>  Errors were encountered while processing:
>   openoffice.org-writer2latex
>   E: Sub-process /usr/bin/dpkg returned an error code (1)

Sigh. unopkgs not-existing error handling strikes again.

That said, a dpkg -i worked for me, but indeed on my ppc a dist-upgrade fails...

Regards,

Rene

Tags added: unreproducible Request was from Rene Engelhard <rene@debian.org> to control@bugs.debian.org. (Wed, 27 Feb 2008 20:24:12 GMT) (full text, mbox, link).

Message #17 received at 468202@bugs.debian.org (full text, mbox, reply):

tag 468202 - unreproducible
thanks

Rene Engelhard wrote:
> tag 468202 + unreproducible

Ooops, sorry, left that in acctdentially.

> Sigh. unopkgs not-existing error handling strikes again.
> 
> That said, a dpkg -i worked for me, but indeed on my ppc a dist-upgrade fails...

And a dpkg -P openoffice.org-writer2latex with an aptitude install
openoffice.org-writer2latex after it makes the install work :/

Regards,
 
Rene

Tags removed: unreproducible Request was from Rene Engelhard <rene@debian.org> to control@bugs.debian.org. (Wed, 27 Feb 2008 20:33:05 GMT) (full text, mbox, link).

Acknowledgement sent to Amit Gurdasani <amitg@alumni.cmu.edu>:
Extra info received and forwarded to list. Copy sent to Debian OpenOffice Team <debian-openoffice@lists.debian.org>. (full text, mbox, link).

Message #24 received at 468202@bugs.debian.org (full text, mbox, reply):

I hit the same issue here. A purge and reinstall did not help. Then I 
noticed that the purge seemed to be spitting out


amitg@athena. sudo dpkg --force-depends --purge openoffice.org-writer2latex
dpkg: openoffice.org-writer2latex: dependency problems, but removing anyway 
as you request:
 openoffice.org-writer depends on openoffice.org-writer2latex.
(Reading database ... 240675 files and directories currently installed.)
Removing openoffice.org-writer2latex ...

ERROR: Lock file indicates that a concurrent Office process is running!

unopkg failed.

ERROR: Lock file indicates that a concurrent Office process is running!

unopkg failed.



and indeed, I had a ${HOME}/.openoffice.org2/.lock (but no OpenOffice.org 
process running, confirmed with "fuser"). Once I deleted that, I was able to 
purge and install successfully.

It sounds like unopkg needs a lesson in manners. It should check for active 
users of the lockfile before dying abruptly, and why can't it do its work 
when OpenOffice.org is running, anyway?

Amit

Message #29 received at 468202@bugs.debian.org (full text, mbox, reply):

On Thu, 28 Feb 2008, Amit Gurdasani wrote:

:It sounds like unopkg needs a lesson in manners. It should check for active
:users of the lockfile before dying abruptly, and why can't it do its work when
:OpenOffice.org is running, anyway?

And what appears to be a related upstream bug report:

http://www.openoffice.org/issues/show_bug.cgi?id=86080

Amit

Message #34 received at 468202@bugs.debian.org (full text, mbox, reply):

Amit Gurdasani wrote:
> amitg@athena. sudo dpkg --force-depends --purge openoffice.org-writer2latex
> dpkg: openoffice.org-writer2latex: dependency problems, but removing 
> anyway as you request:
>  openoffice.org-writer depends on openoffice.org-writer2latex.
> (Reading database ... 240675 files and directories currently installed.)
> Removing openoffice.org-writer2latex ...
>
> ERROR: Lock file indicates that a concurrent Office process is running!
>
> unopkg failed.
>
> ERROR: Lock file indicates that a concurrent Office process is running!
>
> unopkg failed.
>
>
>
> and indeed, I had a ${HOME}/.openoffice.org2/.lock (but no OpenOffice.org 
> process running, confirmed with "fuser"). Once I deleted that, I was able 
> to purge and install successfully.

qed. Thanks.

> It sounds like unopkg needs a lesson in manners. It should check for 
> active users of the lockfile before dying abruptly, and why can't it do 

Yes, as I said, unopkg is far from optimal.

Regards,

Rene

Acknowledgement sent to Julien BLACHE <jblache@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian OpenOffice Team <debian-openoffice@lists.debian.org>. (full text, mbox, link).

Message #39 received at 468202@bugs.debian.org (full text, mbox, reply):

Package: openoffice.org-writer2latex
Version: 0.5-5
Followup-For: Bug #468202

Hi,

Here the postinst barfs, the purge barfs too, I have no lockfile around
(contrary to what unopkg claims during the purge), purging and reinstalling
does not work.

strace on the postinst script reveals that unopkg does most (if not all)
of its job but still fails (I can see it opening various XML and other OOo
files).

The upgrade worked on other machines of mine.

I'd happily remove writer2latex which I do not need, if only it wasn't a
Depends. Please demote it to a Recommends.

JB.

-- Package-specific info:
Identifier: org.openoffice.legacy.writer2latex.uno.pkg
  URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/DOhT12_/writer2latex.uno.pkg
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: Extension
  bundled Packages: {
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/DOhT12_/writer2latex.uno.pkg/writer2latex.jar
      is registered: yes
      Media-Type: application/vnd.sun.star.uno-component;type=Java
      Description: UNO Java Component
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/DOhT12_/writer2latex.uno.pkg/w2l_types.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/DOhT12_/writer2latex.uno.pkg/w2l_filters.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
  }

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24.2
Locale: LANG=C, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages openoffice.org-writer2latex depends on:
ii  openoffice.org-core        1:2.4.0~rc1-3 OpenOffice.org office suite archit
ii  openoffice.org-java-common 1:2.4.0~rc1-3 OpenOffice.org office suite Java s

openoffice.org-writer2latex recommends no packages.

-- no debconf information

Message #44 received at 468202@bugs.debian.org (full text, mbox, reply):

Julien BLACHE wrote:
> I'd happily remove writer2latex which I do not need, if only it wasn't a
> Depends. Please demote it to a Recommends.

It is.

rene@frodo:~$ apt-cache show openoffice.org-writer | grep writer2latex
Recommends: java-gcj-compat | icedtea-java7-jre | sun-java5-jre |
sun-java6-jre | java2-runtime, openoffice.org-filter-binfilter,
openoffice.org-java-common (>> 2.2.0-4), openoffice.org-writer2latex

Of course, the "openoffice.org" dummy package depends on it because
writer2latex is shipped since 2.0.4 within OOo and people might wonder
where the functionality is now...

(See #466170)

Regards,

Rene

Message #49 received at 468202@bugs.debian.org (full text, mbox, reply):

Hi,

Amit Gurdasani wrote:
> On Thu, 28 Feb 2008, Amit Gurdasani wrote:
> 
> :It sounds like unopkg needs a lesson in manners. It should check for active
> :users of the lockfile before dying abruptly, and why can't it do its work when
> :OpenOffice.org is running, anyway?
> 
> And what appears to be a related upstream bug report:
> 
> http://www.openoffice.org/issues/show_bug.cgi?id=86080

Yeah, that's known. But OpenOffice.orgs and writer2latexs maintainer
scripts already set those -env options.

Hmm. That said, the prerm of openoffice.org-writer2latex missed the
-env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1...

I do not have much hope this alone fixes it but we'll see..

Regards,

Rene

Message #54 received at 468202@bugs.debian.org (full text, mbox, reply):

Rene Engelhard <rene@debian.org> wrote:

Hi,

> Of course, the "openoffice.org" dummy package depends on it because
> writer2latex is shipped since 2.0.4 within OOo and people might wonder
> where the functionality is now...

OK, and what about fixing that !@#$% bug ? I can reproduce it at will
and none of the workarounds seem to work.

JB.

-- 
 Julien BLACHE <jblache@debian.org>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer        |       <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169

Message #59 received at 468202@bugs.debian.org (full text, mbox, reply):

Hi,

Julien BLACHE wrote:
> > Of course, the "openoffice.org" dummy package depends on it because
> > writer2latex is shipped since 2.0.4 within OOo and people might wonder
> > where the functionality is now...
> 
> OK, and what about fixing that !@#$% bug ? I can reproduce it at will

What do you think I am trying to do with asking those questions? If
people like you would not come up with issues fixed long ago (the
Depends:), I need to explain them...

That said, notice my last comment to the bug. I'll upload a package with
that line added, we'll see.

If you know what causes it please help, otherwise please shut up with
useless comments like this - thanks.

Regards,

Rene

Message #64 received at 468202@bugs.debian.org (full text, mbox, reply):

Julien BLACHE wrote:
> strace on the postinst script reveals that unopkg does most (if not all)
> of its job but still fails (I can see it opening various XML and other OOo
> files).

Have the strace, please? It doesn't really make sense talking about an
strace but then not attaching it, especially as I said that it works on
my both machines now...

> The upgrade worked on other machines of mine.

Yeah. Some unopkg suckage again :/

Regards,

Rene

Reply sent to Rene Engelhard <rene@debian.org>:
You have taken responsibility. (full text, mbox, link).

Notification sent to Steffen Moeller <steffen_moeller@gmx.de>:
Bug acknowledged by developer. (full text, mbox, link).

Message #69 received at 468202-close@bugs.debian.org (full text, mbox, reply):

Source: writer2latex
Source-Version: 0.5-6

We believe that the bug you reported is fixed in the latest version of
writer2latex, which is due to be installed in the Debian FTP archive:

libwriter2latex-java-doc_0.5-6_all.deb
  to pool/main/w/writer2latex/libwriter2latex-java-doc_0.5-6_all.deb
libwriter2latex-java_0.5-6_all.deb
  to pool/main/w/writer2latex/libwriter2latex-java_0.5-6_all.deb
openoffice.org-writer2latex_0.5-6_all.deb
  to pool/main/w/writer2latex/openoffice.org-writer2latex_0.5-6_all.deb
writer2latex-manual_0.5-6_all.deb
  to pool/main/w/writer2latex/writer2latex-manual_0.5-6_all.deb
writer2latex_0.5-6.diff.gz
  to pool/main/w/writer2latex/writer2latex_0.5-6.diff.gz
writer2latex_0.5-6.dsc
  to pool/main/w/writer2latex/writer2latex_0.5-6.dsc
writer2latex_0.5-6_all.deb
  to pool/main/w/writer2latex/writer2latex_0.5-6_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 468202@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard <rene@debian.org> (supplier of updated writer2latex package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 28 Feb 2008 14:11:44 +0100
Source: writer2latex
Binary: writer2latex writer2latex-manual libwriter2latex-java-doc libwriter2latex-java openoffice.org-writer2latex
Architecture: source all
Version: 0.5-6
Distribution: unstable
Urgency: low
Maintainer: Debian OpenOffice Team <debian-openoffice@lists.debian.org>
Changed-By: Rene Engelhard <rene@debian.org>
Description: 
 libwriter2latex-java - OpenOffice.org Writer/Calc to LaTeX/XHTML converter -- library
 libwriter2latex-java-doc - OpenOffice.org Writer/Calc to LaTeX/XHTML converter -- javadoc
 openoffice.org-writer2latex - Writer/Calc to LaTeX/XHTML converter extension for OpenOffice.org
 writer2latex - OpenOffice.org Writer/Calc to LaTeX/XHTML converter
 writer2latex-manual - OpenOffice.org Writer/Calc to LaTeX/XHTML converter -- manual
Closes: 468202
Changes: 
 writer2latex (0.5-6) unstable; urgency=low
 .
   * add missing -env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1 to the prerm
     unopkg call, hopefully closes: #468202, please reopen if not
Files: 
 19304b082f7e06bbc48a5f85f7f599a4 928 text optional writer2latex_0.5-6.dsc
 018f922625f469d6f3be824364fd9f0b 25690 text optional writer2latex_0.5-6.diff.gz
 b6e6938dde058b7d1954045062948fba 64084 text optional writer2latex_0.5-6_all.deb
 6ca6cf82c83d6e46836bab43ba82c366 656930 doc optional writer2latex-manual_0.5-6_all.deb
 5656972de23c3df44dad97c9c6158213 286826 doc optional libwriter2latex-java-doc_0.5-6_all.deb
 9404dfd8ad58415d328b3ab2c94b9e85 379900 text optional libwriter2latex-java_0.5-6_all.deb
 d20a5f067b4ee9d7935cf27f5e166510 382898 text optional openoffice.org-writer2latex_0.5-6_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHxrb5+FmQsCSK63MRAoJAAJ0XXT2pSJXQUlp7YTKZJSFhoETOWwCfR+Tc
rhX568/JZFsmornRa4SdZLw=
=sprv
-----END PGP SIGNATURE-----

Acknowledgement sent to Soeren Sonnenburg <bugreports@nn7.de>:
Extra info received and forwarded to list. Copy sent to Debian OpenOffice Team <debian-openoffice@lists.debian.org>. (full text, mbox, link).

Message #74 received at 468202@bugs.debian.org (full text, mbox, reply):

Package: openoffice.org-writer2latex
Version: 0.5-5
Followup-For: Bug #468202

-- Package-specific info:
Identifier: org.openoffice.legacy.writer2latex.uno.pkg
  URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/SODkgx_/writer2latex.uno.pkg
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: Extension
  bundled Packages: {
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/SODkgx_/writer2latex.uno.pkg/writer2latex.jar
      is registered: yes
      Media-Type: application/vnd.sun.star.uno-component;type=Java
      Description: UNO Java Component
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/SODkgx_/writer2latex.uno.pkg/w2l_types.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/SODkgx_/writer2latex.uno.pkg/w2l_filters.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
  }

-- System Information:
Debian Release: lenny/sid
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-sonne (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openoffice.org-writer2latex depends on:
ii  openoffice.org-core        1:2.4.0~rc1-2 OpenOffice.org office suite archit
ii  openoffice.org-java-common 1:2.4.0~rc1-3 OpenOffice.org office suite Java s

openoffice.org-writer2latex recommends no packages.

-- no debconf information

Message #79 received at 468202@bugs.debian.org (full text, mbox, reply):

Rene Engelhard <rene@debian.org> wrote:

Hi,

> If you know what causes it please help, otherwise please shut up with
> useless comments like this - thanks.

I don't know what's causing that, I did not have enough time to spend
on that issue this morning when I sent the followup.

I straced -f the postinst script but that output is very long and it
takes some time to go through it. I may give it a try tonight or
tomorrow, though (was looking for a lockfile to kill).

I tried moving away my ~/.openoffice.org2 entirely and that didn't
help, confirming that at least for the postinst the lockfile isn't the
problem.

In the meantime, your comment about the prerm makes it sound like the
package may not have been unregistered by the prerm, right ? unopkg
list lists no installed extensions, but maybe that needs some options
to be really meaningful ?

Sorry for what should have been a "how do we go about fixing that
bug" earlier.

JB.

-- 
 Julien BLACHE <jblache@debian.org>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer        |       <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169

Message #84 received at 468202@bugs.debian.org (full text, mbox, reply):

Hi,

Julien BLACHE wrote:
> In the meantime, your comment about the prerm makes it sound like the
> package may not have been unregistered by the prerm, right ? unopkg

Or not unregistered correctly, yes.

> list lists no installed extensions, but maybe that needs some options
> to be really meaningful ?

Yes, you want --shared. A simple unopkg list shows just user-installed
extensions.

Regards,

Rene

Message #89 received at 468202@bugs.debian.org (full text, mbox, reply):

Rene Engelhard <rene@debian.org> wrote:

>> In the meantime, your comment about the prerm makes it sound like the
>> package may not have been unregistered by the prerm, right ? unopkg
>
> Or not unregistered correctly, yes.

Ok, unopkg list --shared shows the extension as installed. I guess
this explains it all :)

> Yes, you want --shared. A simple unopkg list shows just user-installed
> extensions.

Gee sorry I missed that in the help text this morning. Gah.

JB.

-- 
 Julien BLACHE <jblache@debian.org>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer        |       <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169

Message #94 received at 468202@bugs.debian.org (full text, mbox, reply):

Rene Engelhard <rene@debian.org> wrote:

> Have the strace, please? It doesn't really make sense talking about an
> strace but then not attaching it, especially as I said that it works on
> my both machines now...

Wanted to take a look at it before flooding you with a big chunk of
possibly useless data to crawl through.

Given my previous mail, please tell me if it's still needed and I'll
generate it again.

>> The upgrade worked on other machines of mine.
>
> Yeah. Some unopkg suckage again :/

Looks really great, indeed :| I feel your pain...

JB.

-- 
 Julien BLACHE <jblache@debian.org>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer        |       <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169

Acknowledgement sent to Hamish Moffatt <hamish@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian OpenOffice Team <debian-openoffice@lists.debian.org>. (full text, mbox, link).

Message #99 received at 468202@bugs.debian.org (full text, mbox, reply):

Package: openoffice.org-writer2latex
Version: 0.5-6
Followup-For: Bug #468202

Installation of openoffice.org-writer2latex is failing for me.

[10:20AM] hamish@bach:oboe/apps/callexec $ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  icedove icedove-gnome-support linuxprinting.org-ppds
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? 
Setting up openoffice.org-writer2latex (0.5-6) ...
Adding extension /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
unopkg failed.
dpkg: error processing openoffice.org-writer2latex (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 openoffice.org-writer2latex
E: Sub-process /usr/bin/dpkg returned an error code (1)


-- Package-specific info:
Identifier: org.openoffice.legacy.writer2latex.uno.pkg
  URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: Extension
  bundled Packages: {
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/writer2latex.jar
      is registered: yes
      Media-Type: application/vnd.sun.star.uno-component;type=Java
      Description: UNO Java Component
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_types.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_filters.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
  }

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openoffice.org-writer2latex depends on:
ii  openoffice.org-core        1:2.4.0~rc1-3 OpenOffice.org office suite archit
ii  openoffice.org-java-common 1:2.4.0~rc1-3 OpenOffice.org office suite Java s

openoffice.org-writer2latex recommends no packages.

-- no debconf information

Bug marked as found in version 0.5-6 and reopened. Request was from Hamish Moffatt <hamish@debian.org> to control@bugs.debian.org. (Thu, 28 Feb 2008 23:45:07 GMT) (full text, mbox, link).

Message #106 received at 468202@bugs.debian.org (full text, mbox, reply):

Hi,

Hamish Moffatt wrote:
> [10:20AM] hamish@bach:oboe/apps/callexec $ sudo apt-get dist-upgrade
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> Calculating upgrade... Done
> The following packages have been kept back:
>   icedove icedove-gnome-support linuxprinting.org-ppds
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0B of additional disk space will be used.
> Do you want to continue [Y/n]? 
> Setting up openoffice.org-writer2latex (0.5-6) ...
> Adding extension /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
> unopkg failed.
> dpkg: error processing openoffice.org-writer2latex (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  openoffice.org-writer2latex
> E: Sub-process /usr/bin/dpkg returned an error code (1)

And you unregistered the extension manually to have a clean state if it
failed before? Read the buglog...

And of course you should think that the fix we talk about was in the
*prerm*, so it of course doesn't take effect when upgrading *to* 0.5-6
because the old postrm is executed on upgrade...

Regards,

Rene

Message #111 received at 468202@bugs.debian.org (full text, mbox, reply):

On Fri, Feb 29, 2008 at 03:24:19AM +0100, Rene Engelhard wrote:
> And you unregistered the extension manually to have a clean state if it
> failed before? Read the buglog...

How?

[ 5:09PM] hamish@bach $ sudo /usr/lib/openoffice/program/unopkg list --shared
all deployed shared packages:
Identifier: org.openoffice.legacy.writer2latex.uno.pkg
  URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: Extension
  bundled Packages: {
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/writer2latex.jar
      is registered: yes
      Media-Type: application/vnd.sun.star.uno-component;type=Java
      Description: UNO Java Component
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_types.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
      URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/ML7nSq_/writer2latex.uno.pkg/w2l_filters.xcu
      is registered: yes
      Media-Type: application/vnd.sun.star.configuration-data
      Description: Configuration Data
  }
[ 5:10PM] hamish@bach: $ sudo /usr/lib/openoffice/program/unopkg remove org.openoffice.legacy.writer2latex.uno.pkg

ERROR: There is no such extension deployed: org.openoffice.legacy.writer2latex.uno.pkg

unopkg failed.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Message #116 received at 468202@bugs.debian.org (full text, mbox, reply):

On Fri, Feb 29, 2008 at 03:24:19AM +0100, Rene Engelhard wrote:
> Hi,
> 
> Hamish Moffatt wrote:
> > [10:20AM] hamish@bach:oboe/apps/callexec $ sudo apt-get dist-upgrade
> > Reading package lists... Done
> > Building dependency tree       
> > Reading state information... Done
> > Calculating upgrade... Done
> > The following packages have been kept back:
> >   icedove icedove-gnome-support linuxprinting.org-ppds
> > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> > 1 not fully installed or removed.
> > After this operation, 0B of additional disk space will be used.
> > Do you want to continue [Y/n]? 
> > Setting up openoffice.org-writer2latex (0.5-6) ...
> > Adding extension /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
> > unopkg failed.
> > dpkg: error processing openoffice.org-writer2latex (--configure):
> >  subprocess post-installation script returned error exit status 1
> > Errors were encountered while processing:
> >  openoffice.org-writer2latex
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> And you unregistered the extension manually to have a clean state if it
> failed before? Read the buglog...

OK, I removed it (forgot the --shared in the last attempt), and now the
package configures.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Bug marked as fixed in version 0.5-6, send any further explanations to Steffen Moeller <steffen_moeller@gmx.de> Request was from Rene Engelhard <rene@debian.org> to control@bugs.debian.org. (Fri, 29 Feb 2008 07:36:10 GMT) (full text, mbox, link).

Message #123 received at 468202@bugs.debian.org (full text, mbox, reply):

On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote:
> Hamish Moffatt wrote:
> > > And you unregistered the extension manually to have a clean state if it
> > > failed before? Read the buglog...
> > 
> > OK, I removed it (forgot the --shared in the last attempt), and now the
> > package configures.
> 
> Thanks, so I close this again.

Well, it isn't satisfactory that manual intervention is required for
anyone who installed 0.5-5. 

You said the problem is on the old postinst. Therefore, you can fix it
in the new preinst. Either prepare for it, or remove the script, or
whatever. See the policy manual section:
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Message #128 received at 468202@bugs.debian.org (full text, mbox, reply):

Hi,

Hamish Moffatt wrote:
> On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote:
> > Hamish Moffatt wrote:
> > > > And you unregistered the extension manually to have a clean state if it
> > > > failed before? Read the buglog...
> > > 
> > > OK, I removed it (forgot the --shared in the last attempt), and now the
> > > package configures.
> > 
> > Thanks, so I close this again.
> 
> Well, it isn't satisfactory that manual intervention is required for
> anyone who installed 0.5-5. 
> 
> You said the problem is on the old postinst. Therefore, you can fix it

No, I didn't. Read again. I changed the *prerm*.

> http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html

Will have a look again, though.

Regards,

Rene

Message #133 received at 468202@bugs.debian.org (full text, mbox, reply):

On Fri, Feb 29, 2008 at 12:24:36PM +0100, Rene Engelhard wrote:
> Hamish Moffatt wrote:
> > On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote:
> > > Hamish Moffatt wrote:
> > > > > And you unregistered the extension manually to have a clean state if it
> > > > > failed before? Read the buglog...
> > > > 
> > > > OK, I removed it (forgot the --shared in the last attempt), and now the
> > > > package configures.
> > > 
> > > Thanks, so I close this again.
> > 
> > Well, it isn't satisfactory that manual intervention is required for
> > anyone who installed 0.5-5. 
> > 
> > You said the problem is on the old postinst. Therefore, you can fix it
> 
> No, I didn't. Read again. I changed the *prerm*.

Sorry, my fault. 

> > http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
> 
> Will have a look again, though.

Thanks. The manual says that if the old prerm fails, dpkg should try the
same operation with the new prerm, which you said is fixed. I didn't see
it try to do this.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Message #138 received at 468202@bugs.debian.org (full text, mbox, reply):

Hi,

Hamish Moffatt wrote:
> Thanks. The manual says that if the old prerm fails, dpkg should try the
> same operation with the new prerm, which you said is fixed. I didn't see
> it try to do this.

The problem here might be that the prerm didn't actually fail in
the sense that it returned an exitcode != 0... But it failed to do its
job.

unopkg often returns 0 even if it failed..

Regards,

Rene

> 
> 
> Hamish
> -- 
> Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-openoffice-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Message #143 received at 468202@bugs.debian.org (full text, mbox, reply):

On Fri, Feb 29, 2008 at 08:00:58PM +0100, Rene Engelhard wrote:
> Hi,
> 
> Hamish Moffatt wrote:
> > Thanks. The manual says that if the old prerm fails, dpkg should try the
> > same operation with the new prerm, which you said is fixed. I didn't see
> > it try to do this.
> 
> The problem here might be that the prerm didn't actually fail in
> the sense that it returned an exitcode != 0... But it failed to do its
> job.
> 
> unopkg often returns 0 even if it failed..

So, the new postinst fails because the old prerm failed to do its work
(although it returned success)? In that case can't you simply deal with
this in the new postinst?


Thanks,
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Tue, 08 Apr 2008 07:26:20 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Wed Jan 10 21:27:43 2018; Machine Name: beach

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Debian Bug report logs - #468202 subprocess post-installation script returned error exit status 1

Debian Bug report logs - #468202
subprocess post-installation script returned error exit status 1