Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 22593
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Paul de Vrieze <pauldv@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Bernd Wurst <bugzilla-gentoo@bwurst.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 22593 depends on: Show dependency tree
Bug 22593 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-06-10 23:21 0000
There was an upgrade of openoffice1.1 recently. It only was a new ebuild and no
new binary distribution, so this error must be in the ebuild.
The installation/autoclean removed the soffice-binary and the whole "program"
folder inside /opt/OpenOffice1.1_beta/ and so OOo is no longer usable! 
I tried emerge -C openoffice-bin && emerge openoffice-bin but it did not work.

bernd@aragorn bernd $ ls -l /opt/OpenOffice.org1.1_beta/
lrwxrwxrwx    1 root     root           13 2003-06-11 08:00 setup -> program/setup
drwxr-xr-x    3 root     root         4096 2003-06-10 20:02 share
lrwxrwxrwx    1 root     root           15 2003-06-11 08:00 spadmin ->
program/spadmin
drwxr-xr-x   10 root     root         4096 2003-06-11 08:00 user

There is missing something. :-)

If that helps someone:
bernd@aragorn bernd $ emerge info
Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.21-rc7-laptop1 i686 Intel(R) Pentium(R) M processor 1300MHz
GENTOO_MIRRORS="ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo
http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror
http://www.ibiblio.org/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 libg++ mikmod xml2 xv zlib gtkhtml gdbm berkdb slang readline arts svga
guile sdl gpm tcpd pam libwww ssl esd imlib motif opengl plotutils xml gd -3dnow
-apm hbci X ipv6 gtk gnome alsa oss tcltk gtk2 kde aalib acpi apache2 avi bonobo
cdr crypt cups dvd encode fbcon gif jpeg tiff png -java mozilla mmx maildir mbox
ncurses nls cardbus oggvorbis mpeg pdflib perl python qt quicktime samba scanner
spell sse tetex truetype usb xface xmms mysql"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium3 -mcpu=pentium3 -pipe"
CXXFLAGS="-O3 -march=pentium3 -mcpu=pentium3 -pipe"
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
 


Reproducible: Always
Steps to Reproduce:

------- Comment #1 From Paul de Vrieze 2003-06-11 04:43:58 0000 -------
I didn't actually try it out myself, I'll mask the beta again as it is an old
version anyway, and I think it is a nice task for the new maintainer to fix.

------- Comment #2 From Paul de Vrieze 2003-06-11 04:48:22 0000 -------
Oops, I read too fast, it is a source version that is masked. The new ebuild
for the binary version should not touch the program directory at all. Are you
sure that the old 1.1 beta did work. The new version should only fix the kde
links.

------- Comment #3 From Bernd Wurst 2003-06-11 11:53:25 0000 -------
I upgraded OOo via emerge -u world last evening and that did the corruption.
This has happened on two Gentoo-Boxes, both the same problem.

I have autoclean enabled and let emerge upgrade "world" overnight, so I cannot
say what exactly has happened. I just recognized that on those two boxes, OOo
could not be started this morning.

And yes, the old 1.1_beta DID work.

Perhaps you can view something helpful in last night's emerge.log...

aragorn bernd # grep -i openoffice /var/log/emerge.log
1055268040:  >>> emerge (19 of 32) app-office/openoffice-bin-1.1_beta-r1 to /
1055268040:  === (19 of 32) Cleaning
(/usr/portage/app-office/openoffice-bin/openoffice-bin-1.1_beta-r1.ebuild)
1055268041:  === (19 of 32) Compiling/Merging
(/usr/portage/app-office/openoffice-bin/openoffice-bin-1.1_beta-r1.ebuild)
1055268083:  === (19 of 32) Post-Build Cleaning
(/usr/portage/app-office/openoffice-bin/openoffice-bin-1.1_beta-r1.ebuild)
1055268084:  >>> AUTOCLEAN: app-office/openoffice-bin
1055268089: === Unmerging... (app-office/openoffice-bin-1.1_beta)
1055268122:  >>> unmerge success: app-office/openoffice-bin-1.1_beta
1055268122:  ::: completed emerge (19 of 32)
app-office/openoffice-bin-1.1_beta-r1 to /


------- Comment #4 From Bernd Wurst 2003-06-11 11:56:51 0000 -------
...and sorry for the confusion, I really forgot to talk about "openoffice-bin"
and not the source distribution.
As I'm not that curious, I use the precompiled version. Everything I'm talking
about is "openoffice-bin", upgrade from version 1.1_beta to 1.1_beta-r1.

------- Comment #5 From Paul de Vrieze 2003-06-19 14:25:32 0000 -------
I just added an ebuild for beta2 binary version. Please try it out. As far as
your problem is concerned, I found that the openoffice installer installs files
with their modification dates being the original dates. As -r1 does only differ
in one file, many files are found to be "old" by the portage cleanup process,
and removed. Unmerging first and then merging beta1 should work too. I fixed it
in the beta2 ebuild and the beta1-r1 ebuild.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug