Libpoppler, Qt 4.6 and repos oh, my!
 

I have poked at this problem a few times before and always just figured i'd "wait for PR1.2" before worrying about it. Well, PR1.2 is here and my excuses pretty much used up.

I'm really not very knowledgeable about library versioning, nor how that works with repos, and would really appreciate help getting this issue resolved.

Here it is: i'm trying to use libpoppler-qt in an app and the dependencies are broken. It works okay on my N900 after some apt forcing, but it won't go through autobuilder. There seems to be rather a mess with libpoppler in the repos:
libpoppler-dev
libpoppler-glib-dev
libpoppler-glib-ruby
libpoppler-glib-ruby1.8
libpoppler-glib2
libpoppler-glib4
libpoppler-qt4-3
libpoppler-qt4-dev
libpoppler0c2
libpoppler0c2-glib
libpoppler2
libpoppler4
libpoppler5

I was thinking, now that we have Qt 4.6, that it would be a good time to clean out the redundant and/or broken and/or obsolete packages and push libpoppler to the autobuilder once again with all subpackages enabled. The problem is i don't know where to begin and what needs to be done.

Presumably some apps are currently using one or more of the existing library packages, like Evince:
Help, please? :)

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

What I said then was true (although I apologise for the anti-Qt sentiment; I've grown up since then and do rather like Qt apps): I *did* upload Poppler with Qt support. Someone else decided, without me knowing, to upload the same version in a shittier form with Qt support disabled.

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

I remember that coming up when i inquired before and am sorry to bother you again.

What is the best way to fix it? How was it even possible for someone else to upload when you had maintainer status for uploading it? Does that mean i could get the latest source and override it again?

Hmm so many noob questions. Where to begin...

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

Here's a good one. It says there's a missing dependency for the armel (and only the armel) build of libpoppler-qt4-dev:
http://maemo.org/packages/package_in....12.2-2maemo0/

It says libqt4-dev is missing. However, it's right here: http://maemo.org/packages/view/libqt4-dev/

What's going on?

Only the SDK version remains because the Extras-devel packages were removed by xfade.

:confused:

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

Anyone have an idea why the dependency situation in previous post is the way it is? Why the i386 package doesn't claim to be missing the package while the armel one does, even though the exact same version of the dependency package exists in both targets?

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

I wanna know that too, I managed to install libpoppler-qt4-dev on scratchbox but I can't install on the device.

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

Bump. Why does the repo not work in a consistent fashion for dependencies?

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

Hi Flandry,

Posting here to keep things to one thread.

I don't know a great deal about the repositories. I'd suggest you mail maemo-developers list, or possibly talk to X-Fade who (IIRC) is the resident repository mangler, it might help to better get the attention of the right people.

Something does look rather messed, though.

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

The 'problem' with dev files is that they are intended to be installed inside the sdk. The actual libraries are for sdk and on device use.

The interface only links to repositories which are intended to be used on device.

For -dev packages it is a complicated case. Do you really want to have the -dev headers on your device? Otherwise wouldn't Build-Depends be a better solution?

Re: Libpoppler, Qt 4.6 and repos oh, my!
 

Well that clears up some of my questions, but the original problem remains.

My app has:
Build-Depends: debhelper (>= 4.0.0), libpoppler-qt4-dev

It fails at the autobuilder regardless. I understand that having the -dev packages on the device doesn't make much sense but it's failing to build on the autobuilder because of the dependency problem.