Summary: | app-office/libreoffice-4.1.0.4 fails to build with net-libs/neon-0.30.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | New packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ao, arfrever.fta, bugs+gentoo, bugzie, dabbott, derk.tebokkel, dschridde+gentoobugs, eugene.shalygin, ganastasiouGR, gentoo, gentoo, gentoo, giovanni.bobbio, heiko.baums, holger, mail, marcfgrondin, marco, Martin.Jansa, matrix47, mstomich, pageexec, patrakov, rose, spiros, staff, tdalman, tetromino, travisghansen, tuxtor, uzytkownik2, z23, zeekec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Workaround |
Description
Patrick Lauer
2013-08-03 07:37:46 UTC
I have the same issue. Created attachment 355004 [details, diff]
Workaround
The errors are caused by a Windows-specific code. A workaround is to remove this code. Please test this patch.
The patch worked for me. Me too, works fine with the patch, thanks. Thamks. it did it also for me on ~amd64 I can confirm the workaround solves the issue. So, what are the next actions ? Will there be a -r1 ? Is this libreoffice version going to be masked until the issue is solved ? Has the problem been reported to upstream ? *** Bug 480462 has been marked as a duplicate of this bug. *** The patch worked for me too. Downgrading to neon-0.29 works perfectly. neon-0.30 could be masked for libreoffice until the issue is resolved by upstream (reported, anyone ?). Masking of Neon does not make sense. The patch can be safely applied in Gentoo and we can wait for LibreOffice Windows developers finding proper solution. (NE_FEATURE_SSPI is not defined in vanilla Neon <0.30. LibreOffice source code for Windows is written for a fork of older version of Neon, with added SSPI support. SSPI support has been accepted by Neon upstream for Neon 0.30, but in a different form than it was in a fork.) same here and i think what tolga was getting at is it was easier to downgrade, which i did before looking into this, then it is to create and overlay and edit an ebuild etc. nice catch though arfrever (In reply to merwan kashouty from comment #12) > same here and i think what tolga was getting at is it was easier to > downgrade, which i did before looking into this, then it is to create and > overlay and edit an ebuild etc. there's no need for an overlay and all that stuff, just save the patch into /etc/portage/patches/app-office/libreoffice/libreoffice-4.1.0.4.patch . > nice catch though arfrever exactly, and IMHO there's zero reason to force a systemwide downgrade of the library just because one app's windows specific code doesn't compile with it. (In reply to PaX Team from comment #13) > there's no need for an overlay and all that stuff, just save the patch into > /etc/portage/patches/app-office/libreoffice/libreoffice-4.1.0.4.patch . Neither is, in my eyes, a proper solution. > > nice catch though arfrever > > exactly, and IMHO there's zero reason to force a systemwide downgrade of the > library just because one app's windows specific code doesn't compile with it. I disagree. Only if all users of that library (i.e., neon) are compatible with the new version, the upgrade should be performed. The other way round breaks software for people like me. There are two correct approaches: 1. make an -r1 of libreoffice, thus, fixing it until upstream catches up 2. mask neon 0.30. I prefer 1. (In reply to Tolga Dalman from comment #14) Build fixes do not need revision bump. Nice bug guys. Nobody reported this upstream yet so it seems we are first one updating to neon-0.30. Never the less the patch is technically correct the policy for patches is that they should be at minimum submitted to gerrit.libreoffice.org in order to commit them to cvs. (we had few patches in cvs for ages otherwise) I could look to it in ~10 days but if you want it sooner feel free to create the submit (it is pretty trivial). (In reply to Tolga Dalman from comment #14) > (In reply to PaX Team from comment #13) > > there's no need for an overlay and all that stuff, just save the patch into > > /etc/portage/patches/app-office/libreoffice/libreoffice-4.1.0.4.patch . > > Neither is, in my eyes, a proper solution. obviously. but it's also not true that downgrading is easier than applying this patch in the interim which is what #12 was saying. > I disagree. Only if all users of that library (i.e., neon) are compatible > with the new version, the upgrade should be performed. The other way around > breaks software for people like me. you should realize that we're talking about ~arch packages here (both neon and openoffice), so breakage like this is expected. if you want that kind of stability go with the arch versions (0.29.6-r2 and 4.0.4.2, respectively, at the moment). *** Bug 480690 has been marked as a duplicate of this bug. *** + 13 Aug 2013; Patrick Lauer <patrick@gentoo.org> + +files/libreoffice-4.1.0.4-neon-build.patch, libreoffice-4.1.0.4.ebuild: + Build fix for neon-0.30 #479604 I have no idea how this gerrit thing is supposed to be operated (and it lacks documentation), so I'll just leave this bug open instead. Since this bug, I can't emerge libreoffice and I can't emerge libreoffice-bin because of conflict between version of boost and 3 or 4 other libraries. I find libreoffice and libreoffice are becoming a pain to compile and install... But I have successfully unmerge libreoffice and installed openoffice-bin ... Waiting for this @#! to resolve. Regards, BT (In reply to Bernard Tremblay from comment #20) > Since this bug, I can't emerge libreoffice and I can't emerge > libreoffice-bin because of conflict between version of boost and 3 or 4 > other libraries. > > I find libreoffice and libreoffice are becoming a pain to compile and > install... > libreoffice-bin is exclusively for stable arch unless you volunteer to rebuild it for testing all the time, nobody was willing to do that last time I checked. Not sure if this is relevant because of branches mixing, but libreoffice-4.0.4.2 is also affected by this. Downgrading to neon-0.29 solved the problem for me. Fixed properly in 4.1.1.2 and 4.0.5.2. (In reply to Tomáš Chvátal from comment #23) > Fixed properly in 4.1.1.2 and 4.0.5.2. Thanks a lot! I confirm I have compiled openoffice 4.1.1.2 and confirm that it did compiled successfully without any trouble. Keep on the good work and thanks again! Regards, BT |