Bug#919883: libreoffice arch all FTBFS, javadoc: error - The code being documented uses modules but the packages defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module.
Package: libreoffice Version: 1:6.1.4-1 Severity: serious The arch all build for libreoffice 1:6.1.5~rc1-1 ( https://buildd.debian.org/status/fetch.php?pkg=libreoffice=all=1%3A6.1.5%7Erc1-1=1547977527=0 ) failed with javadoc: error - The code being documented uses modules but the packages defined inhttp://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. According to the reproducible builds site ( https://tests.reproducible-builds.org/debian/rbuild/buster/amd64/libreoffice_6.1.4-4.rbuild.log.gz ) this also affects the existing version in testing 1:6.1.4-1
sys/mount.h not C++ clean on kfreebsd
Libreoffice failed to build on kfreebsd-i386 and kfreebsd-amd64 with the following error. Compiling: sal/osl/unx/file_volume.cxx In file included from /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:77:0: /usr/include/x86_64-kfreebsd-gnu/sys/mount.h: In function 'int getvfsbyname(const char*, xvfsconf*)': /usr/include/x86_64-kfreebsd-gnu/sys/mount.h:398:23: error: invalid conversion from 'void*' to 'xvfsconf*' [-fpermissive] /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx: At global scope: /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:1153:17: warning: unused parameter 'pszPath' [-Wunused-parameter] /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:1153:17: warning: unused parameter 'pItem' [-Wunused-parameter] /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:1160:17: warning: unused parameter 'pDevice' [-Wunused-parameter] /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:555:35: warning: 'oslVolumeDeviceHandleImpl* osl_newVolumeDeviceHandleImpl()' defined but not used [-Wunused-function] /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:579:13: warning: 'void osl_freeVolumeDeviceHandleImpl(oslVolumeDeviceHandleImpl*)' defined but not used [-Wunused-function] /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:1153:17: warning: 'sal_Bool osl_getFloppyMountEntry(const sal_Char*, oslVolumeDeviceHandleImpl*)' defined but not used [-Wunused-function] /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx/file_volume.cxx:1160:17: warning: 'sal_Bool osl_isFloppyMounted(oslVolumeDeviceHandleImpl*)' defined but not used [-Wunused-function] dmake: Error code 1, while making '../../unxkfgx6.pro/obj/file_volume.obj' Retrying /build/buildd-libreoffice_3.4.5-3-kfreebsd-amd64-ukEv52/libreoffice-3.4.5/libreoffice-build/build/libreoffice-3.4.5.2/sal/osl/unx A simple test program including the header (and with an empty main function) compiles fine when built as C but fails when built as C++. So it looks like this is a case of the header not being C++ clean (implicit conversion from void* to other pointer types is allowed in C but not in C++). Presumablly the fix is to add an explicit typecast. I would file a bug report but packages.debian.org doesn't seem to want to tell me what package sys/mount.h is in. -- To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f48d24d.60...@p10link.net
Re: libreoffice, mingw-w64, gcc-mingw-w64 and gnat-4.6 on armhf
Luke Kenneth Casson Leighton wrote: i686-w64-mingw32-g++ is called. that's different from mingw-w64, then. No it's *part of* mingw-w64. Mnigw-w64 is a fork of mingw32 and provides toolchains targetting both 32-bit and 64-bit windows. These toolchains (at least in debian, not sure about upstream) have triplets i686-w64-mingw32 and x86_64-w64-mingw32 . To be fair, that all is inherited from OOo. And it's a non-issue now that we *do* have mingw-w64 on armhf. hurrah! Yeah, I provided the gcc-mingw-w64 maintainers with a patch that disabled gnat support on armhf allowing the rest of the package to be built and the libreoffice build to be tried. Thanks to everyone who helped get libreoffice into armhf unstable. -- To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f49688e.6040...@p10link.net
libreoffice, mingw-w64, gcc-mingw-w64 and gnat-4.6 on armhf
Libreoffice hasn't yet been built on armhf. I consider libreoffice to be a reasonablly important package and one that we need to get in before we can claim we have a reasonablly complete port. The reason libreoffice isn't built is because mingw-w64 is not installable. The reason mingw-w64 is not installable is because gcc-mingw-w64 isn't built. The reason gcc-mingw-w64 isn't built is because gnat-4.6 is not built My understanding from a previous reply Konstantinos sent me is that gnat-4.6 is not built on armhf because it needs porting followed by manual boostrapping. This (build-)dependency chain leaves me with a few questions 1: what is the current status of gnat-4.6 on armhf? does an upload look likely any time soon? 2: why does libreoffice need mingw-w64 in the first place? 3: why are we building an ada cross compiler for windows? is it just for completeness or was/is there an identified requirement? 4: if we can't get an ada compiler on armhf in the near future would anyone consider it unreasonable to build gcc-mingw-w64 without ada suport on armhf so that libreoffice can be built? -- To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f2b4821.8040...@p10link.net
Bug#620137: openoffice.org-writer: Saving in docx format destroys, the entire file content
Is there anything I can do to ensure that this gets looked at for the OOo package in squeeze? Not really, debian stable releases are all about keeping changes to a minimum. If someone made a minimal patch to fix this issue it MIGHT be accepted but I can't see that happening unless you do the work yourself. OK, understood. So what should I do? My advice to you would be to try using the libreoffice packages from squeeze-backports and see if they provide an acceptable soloution for a squeeze deployment in your environment. Also while I understand that you don't want to deploy testing widely I would strongly reccomend testing it in your environment. The earlier in the release cycle you spot an issue the easier it is likely to be to get it sorted. P.S. i'm just a guy looking through debian rc bugs. I have no relationship to the debian openoffice guys but I do have a pretty good idea of how debian works. -- To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eab5853.2060...@p10link.net
