Re: Tips for libreoffice backporting
Hi,
On Mon, Aug 13, 2012 at 09:08:42AM -0500, Félix Arreola Rodríguez wrote:
> Libreoffice 3.5. Is a sad new, because I really need the new version.
Sorry, I don't buy that. You WANT, but that's not NEED. I know 3.4.x
isn't really a good LO release, but it works.
But that said, given that the backport of the last security fix I
received for 3.4 doesn't build at all I think I need to backport 3.5.x
anyway to keep squeeze-backports not vulnarable...)
Because of this I had a look now what'd be needed (see below).
> But, I know that libreoffice is not just *any* package that you just
> could backport, is a huge package. So, before I start I ask for some
> advices for backporting libreoffice. Like what type of dependencies
> should I change, or what is buggy or else.
You obviously haven't even looked at the package, have you?
You'd have seen that there's already loads of stuff for squeeze-backports
there (which just need to be updated).
A dpkg-source -x and look would give you hints (and more
after regenerating control).
- debian/rules relies on /usr/share/dpkg/*.mk which makes it need dpkg-dev
from squeeze-backports (no big deal).
- you need to add a patch to revert the adaptions for new poppler as
there's no support for the old poppler in squeeze anymore afair
(or you use the internal xpdf, which is there right now but I don't believce
this is a very good idea.
more an option is disabling -pdfimport which is a not really
needed extension anyways.)
- root@frodo:/# apt-get install librsvg2-dev gdb junit4 libservlet2.5-java libsampleicc-dev libicc-utils-dev libgtk-3-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libsampleicc-dev
E: Unable to locate package libicc-utils-dev
E: Unable to locate package libgtk-3-dev
Needs to use internal sampleICC (add to the respective filter-out) and
disable gtk3 stuff.
- dpkg-checkbuilddeps: Unmet build dependencies: libservlet2.5-java (<< 1.1.1-9)
is the last thing after the above, which need to be looked at
(BEWARE: flaky get-the-info-from-other-package)
Regards,
Rene
Reply to: