xpdf / poppler dependency problem

asiobob · Posted: Wed Dec 28, 2005 8:47 am Post subject: xpdf / poppler dependency problem

Greetings,

I've having a wierd dependancy issue...when i run emerge world -uvaD

John-Boy · Posted: Wed Dec 28, 2005 8:53 am Post subject:

I've got the same issue, I do have xpdf installed, a swift uninstall doesn't cure the prob either.
_________________
Like the Roman, I seem to see "the River Tiber foaming with much blood"

apache2 · n00b Joined: 06 Jun 2005 Posts: 12

Hey guys, I have this problem too in a world update...... and I really need to get it fixed so I can continue....... anyone have an y ideas?

asiobob · Posted: Wed Dec 28, 2005 9:13 am Post subject:

bug posted: 116957

apache2 · n00b Joined: 06 Jun 2005 Posts: 12

good I was just about to check out bugzilla

apache2 · n00b Joined: 06 Jun 2005 Posts: 12

found a quick get around.........
just put 'app-text/xpdf' into package.keywords and you should be good to go

asiobob · Posted: Wed Dec 28, 2005 9:22 am Post subject:

Good catch, it makes since app-text/xpdf-3.01-r4 is still in ~arch!

EDIT: I'm making a mess of my self on the bugzilla report!!

The blocker is not on the entire package, just for versions below a certain version. Hence apache2's suggestion isn't a quick work around, it is the solution because the required version of xpdf to satisfy not being blocked is stll marked as ~arch. And in that sense only considering poppler and xpdf there is no requirement (yet) for xpdf to be marked stable since basically the lastest version of poppler mentioned in this post is also ~arch

apache2 · n00b Joined: 06 Jun 2005 Posts: 12

heheheh, least we found the problem, now I can finally update my world

have fun,
apache2

_Seth_ · Posted: Wed Dec 28, 2005 3:09 pm Post subject:

hi !
I feel dumb but i'm in ~arch and i have the same "emerge --deep" problem. If i put :

jkressin · n00b Joined: 23 Sep 2004 Posts: 8

I have this same problem. I read thru the bug log, and they seem to to imply that if you use both the ~x86 version of poppler and xpdf, it should all work. I think the whole logic of using '!<' for not less then a specific version number does not work the way the ebuild creator thinks it does.

I made an overlay copy of poppler where that dependency line is changed to >=app-text/xpdf-3.01-r4

Everything runs fine with this change.

Hopefully they make the correction in portage.

Thanks,
Jonathan

yamakawa · Guru Joined: 28 Jul 2003 Posts: 340

If modifying the ebuild file of poppler is not definitely discouraged, why not

asiobob · Posted: Wed Dec 28, 2005 7:47 pm Post subject:

I'm in ~arch for gnome 2.12 packages. Hence Poppler is also in ~arch. Untill the other day I was on stable for xpdf but since then a new poppler ebuild was placed into the tree and it had a xpdf version restriction. So anything BELOW app-text/xpdf-3.01-r4 should be blocked. BUT I'm running stable with selected packages as ~arch and xpdf-3.01-r4 is ~arch but I never had it it in packages.keywords (since I had no reason to, untill now).

By putting xpdf-3.01-r4 in packages.keywords we are allowing to be installed, and by doing this we satisfy the requirement of anything "less" than version xpdf-3.01-r4 blocked. Now since we are greater that the version to be blocked we are fine.

I hope that makes sense. If this version of poppler gets marked stable, xpdf would also have to get marked stable otherwise the entire gentoo "mob" would be posting a problem similiar to this.

omp · Posted: Thu Dec 29, 2005 10:09 am Post subject:

Hmm... I too have this problem.
_________________
meow.

Naib · Posted: Thu Dec 29, 2005 11:20 am Post subject:

same probe here,
un-arching XPDF works tho for me
_________________

TheDebugger · Posted: Thu Dec 29, 2005 11:56 am Post subject:

Ok, who's insane now? Seems to be me ...

I got the same problem as everyone else, but the proposed solution doesn't work.

Adding "app-text/xpdf ~x86" to package.keywords results in the same blocker message as without:

Peach · Posted: Thu Dec 29, 2005 1:19 pm Post subject:

I've solved this way:
unmasked both poppler and xpdf as previously noticed before in this thread
then unmerged xpdf, and reemerged it

the problem is that poppler can't install if there's xpdf, and xpdf can't upgrade if there's old poppler. or something like this.
in other words a reverse dependencies problem..
_________________
Gentoo user since 2004.
"It's all fun and games, until someone loses an eye" - mom

TheDebugger · Posted: Thu Dec 29, 2005 2:30 pm Post subject:

Cintra · Advocate Joined: 03 Apr 2004 Posts: 2111 Location: Norway

doalwa · Posted: Fri Dec 30, 2005 8:39 pm Post subject:

Had the same problem and solved it by following yamakawa's tip...probably not the best solution, but it was quick and dirty, and it worked just fine :-)

_________________
Keepin' the Funk alive since 1983!

mlybarger · Guru Joined: 04 Sep 2002 Posts: 475

i also updated the poppler ebuild. and it seems to be working. somebody with cvs access seems to have left some christmas presents for all to enjoy.

kroenecker · n00b Joined: 10 Aug 2005 Posts: 64

Yamakawas method worked. My question is why isn't !< equivalent to >=

lion1977 · n00b Joined: 21 Nov 2005 Posts: 5 Location: Linz, Austria

Hello,

I got around the problem by removing app-text/xpdf-3.01-r1 and installing the new version 3.01-r5. Poppler doesn't like xpdf below 3.01-r4 but even this version requires poppler to be installed. Portage can't handle this at the moment. It doesn't reconize that if both packages would be installed at one time the blocking package would be removed.

There is difference between !< and >= in portage. As logical operator they would be equivalent but this is bit related to set theory.
!< meens the a version below that one must not be installed
>= meens a version equal or greater must be installed
The !< is satified even if xpdf is not installed, the second condition not.

Bye

WaTcHmE · n00b Joined: 18 Aug 2004 Posts: 36

I dont get it

where is the Problem?

I wanted to emerge world, but my machine showed me the known poppler <> xpdf dependency problem. I searched and found the new xpdf version in the tree. Then I just unmerged xpdf, and then emerged it again.
now I have the newest Version of poppler _and_ xpdf on my machine without much trouble

cya

WaTcHmE
_________________
It doesnt matter how to pronounce "Linux"....
If you use it!

dbergst · Tux's lil' helper Joined: 25 Mar 2003 Posts: 88

mhoskins

The latest xpdf release -r5 appears to have resolved the conflict.

Life is good.
_________________
--
To know even one life has breathed easier because you have lived.
This is to have succeeded. -Bessie Stanely, 1905