| Summary: | app-office/openoffice-2.3.1 fails to compile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Santiago Gala <sgala> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Santiago Gala
2007-12-09 21:39:58 UTC
Any news on this one? last icu breaks openoffice 2.2, and it has disappeared from portage, so I really need to compile 2.3, which is still giving the same error about a duplicated patch in xmlsec... (In reply to comment #1) > Any news on this one? last icu breaks openoffice 2.2, and it has disappeared > from portage, so I really need to compile 2.3, which is still giving the same > error about a duplicated patch in xmlsec... > Sorry that I didn't answer earlier. But I really can't reproduce this, all the patches apply fine here. Are you sure this is not from some overlay? I'm using plain openoffice-2.3.1.ebuild, the only one in portage: # $Header: /var/cvsroot/gentoo-x86/app-office/openoffice/openoffice-2.3.1.ebuild,v 1.6 2007/12/14 14:11:55 suka Exp $ (yes, it was modified without revision bump a bit after I reported the bug, but I tried again with the same results) Are you sure you are using the same distfiles as the main portage? (In reply to comment #3) > I'm using plain openoffice-2.3.1.ebuild, the only one in portage: > > # $Header: > /var/cvsroot/gentoo-x86/app-office/openoffice/openoffice-2.3.1.ebuild,v 1.6 > 2007/12/14 14:11:55 suka Exp $ > > (yes, it was modified without revision bump a bit after I reported the bug, but > I tried again with the same results) Are you sure you are using the same > distfiles as the main portage? > Yes, surely ;) And also: I honestly doubt this package would have been stabilized on 3 archs without anyone being able to compile it ;) Have you tried to start compilation with the same USE flags I have? In particular odk or java are probably related. (In reply to comment #5) > Have you tried to start compilation with the same USE flags I have? In > particular odk or java are probably related. > Actually I build with nearly exactly the same use flags the same, the only difference is that you also compile kde-support, but this shouldn't be relevant here (and such a basic build break for alle kde-users would have been detected long ago) But you mentioning odk makes me wonder one thing: do you actually build with "odk" enabled? Cause your emerge info doesn't mention this... I'm not sure of the exact dates, but it was turned stable for amd64 the same day I reported this bug (I hope the bug was *after*), and the ebuild was modified a number of times "silently", which means most people might have compiled it either without the java and/or odk USE flags or before those modifications. Is there a cvsview somewhere so that I can track the changes? Google was not helping me. I am completely sure that the /var/tmp/portage/app-office/openoffice-2.3.1/work/ooo/patches/src680/apply file in patches contain a patch (libxmlsec-system-nss.diff) which is already applied in the bundled sources, and causes the build to fail (after it stays waiting for confirmation at the prompt) for my version of portage. how you managed to skip this patch is strange, I guess your build.log can talk about it. I'm not sure if the behavior of the ebuild will be different if there is no stderr where asking for confirmation about the patch,... I just noticed odk and webdav are in package.use, not in make.conf Yeah, we really should f(In reply to comment #8) > I just noticed odk and webdav are in package.use, not in make.conf > Yeah, we really should force people to provide the use flags they tried to build a package with, emerge info becomes more and more useless. Anyway: I've just tried to build with odk and webdav enabled, no problem, patch applies fine: libxmlsec-system-nss.diff: testing...( patch -l -p0 -d /var/tmp/portage/app-of$ patching file libxmlsec/xmlsec1-1.2.6.patch ( patch -l -p0 -d /var/tmp/portage/app-office/openoffice-2.3.1/work/ooo/build/$ done. copy libxmlsec-system-nss.diff -> /var/tmp/portage/app-office/openoffice-2.3.1/$ forget about the bug: I was pretty sure I had removed my bashrc from portage, but I managed to do it in different buggy forms 4-5 times :( I have been able to emerge it. The reason why it complained about already applied patch is that I was patching on the fly the same issues (--as-needed). |
