PAM 0.77 and DB emerge failure

[brownowl]

I seem to have a strange error going on with pam, and given that it's affected about 12 of my servers (but not all) I'm amazed nothing has appeared in the fora:

Code: Select all

# emerge world -up

These are the packages that I would merge, in order:

Calculating world dependencies \
!!! all ebuilds that could satisfy ">=sys-libs/db-4.1.25" have been masked.
!!! possible candidates are:
- sys-libs/db-4.2.52_p1 (masked by: profile, package.mask, ~keyword)
- sys-libs/db-4.1.25_p1-r3 (masked by: profile)
!!!    (dependency required by "sys-libs/pam-0.77" [ebuild])

!!! Problem with ebuild dev-php/php-4.3.4-r4
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.

Ok, fair enough, so let's try forcing an emerge of db:

Code: Select all

# ACCEPT_KEYWORDS="~x86" emerge db -p

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-libs/db-4.0.14-r3

Not 4.1.25 then...

Have run emerge sync several times, and tried this:

Code: Select all

# ACCEPT_KEYWORDS="~x86" emerge =sys-libs/db-4.1.25 -p

These are the packages that I would merge, in order:

Calculating dependencies
emerge: there are no masked or unmasked ebuilds to satisfy "=sys-libs/db-4.1.25".

!!! Error calculating dependencies. Please correct.

So there is no such package as db 4.1.25 available on this machine.

However, on one of the servers unaffected by this problem:

Code: Select all

 # emerge db -p

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-libs/db-4.1.25_p1-r3

There is...

Is there an rsync problem about at the moment? However many times I try to "emerge sync" I'm told I'm up-to-date, when it appears that's not true...

How can I force rsync to go to the "master" rsync server?

Cheers, Laurie,

[JABowker]

I am seeing the same problem. Started after last nights rsync. I'm still trying to figure it out. I can't update anything untill this is resolved.

[Veto]

I'm seeing this problem with PAM:

Code: Select all

make[2]: Leaving directory `/var/tmp/portage/pam-0.77/work/Linux-PAM-0.77/modules/pam_chroot'
make[2]: Entering directory `/var/tmp/portage/pam-0.77/work/Linux-PAM-0.77/modules/pam_console'
bison -d -p _pc_yy config.y
config.y: conflicts: 1 shift/reduce
bison: cannot open file `/usr/share/bison/m4sugar/m4sugar.m4': No such file or directory
make[2]: *** [config.tab.c] Error 1
make[2]: Leaving directory `/var/tmp/portage/pam-0.77/work/Linux-PAM-0.77/modules/pam_console'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/var/tmp/portage/pam-0.77/work/Linux-PAM-0.77/modules'
make: *** [modules] Error 2

!!! ERROR: sys-libs/pam-0.77 failed.
!!! Function src_compile, Line 199, Exitcode 2
!!! PAM build failed

[brownowl]

The overnight rsync (I run it on all servers between 01:00 and 02:00 UTC) seems to have fixed this problem on all of my servers. It looks to me as if we have a problem with the rsync mirrors not being properly up-to-date.

Cheers, Laurie.

[gt231]

It seems to be the same problem coming back. When I tried to update a pretty old system:

Code: Select all

$ sudo emerge -Dup world

These are the packages that I would merge, in order:

Calculating world dependencies |
!!! all ebuilds that could satisfy ">=sys-libs/db-4.1.25" have been masked.
!!! possible candidates are:
- sys-libs/db-4.1.25_p1-r3 (masked by: profile)
- sys-libs/db-4.2.52_p1 (masked by: profile, package.mask)
!!!    (dependency required by "sys-libs/pam-0.77" [ebuild])

!!! Problem with ebuild sys-apps/man-pages-1.65
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.

I've tried to rsyn for 3 days. Is this still a rsyn server problem?

[TheZog]

I've had the same problem forever.
I've tried adding the db package to the /etc/portage/package.unmask file (does Portage even check this anymore?), rsync, etc.
Nothing.

It shows up whenever I do a deep statement. ie "emerge -pe world" or "emerge -puD world".

It's driving me crazy. Is there some switch where we can tell emerge just to ignore certain packages when calculating dependecies?

Another crazy thing is that when I do an "emerge --nodeps pam"
it shows db-4.1.25 being untarred and compiled as part of the pam ebuild. The only why I can make it temporarily go away is to edit the pam ebuild and change the db dependancy line.


Just for completeness here's a copy of my error.

Calculating world dependencies |
!!! all ebuilds that could satisfy ">=sys-libs/db-4.1.25" have been masked.
!!! possible candidates are:
- sys-libs/db-4.1.25_p1-r3 (masked by: profile)
- sys-libs/db-4.2.52_p1 (masked by: profile, package.mask)
!!! (dependency required by "sys-libs/pam-0.77" [ebuild])

!!! Problem with ebuild sys-apps/man-pages-1.65
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.

*Note this machine is running the stable profile, my ~x86 box gets the same error minus the ", package.mask".

[TheZog]

SOLVED!

It seems that when I moved my protage directory to a central server long ago the /etc/make.profile file still pointed to /usr/portage/profiles/default-x86-1.4

Instead of the new location. So I updated the the symlink and everything's great once more.
I hope this helps someone.

[hooligan]

SOLVED!

It seems that when I moved my protage directory to a central server long ago the /etc/make.profile file still pointed to /usr/portage/profiles/default-x86-1.4

Instead of the new location. So I updated the the symlink and everything's great once more.
I hope this helps someone.

Hey bro... /etc/make.profile is a directory... any idea what file to edit? I am having this issue.

[TheZog]

Well actually /etc/make.profile is a symlink to the real default profile.

Do a "ls -l /etc/make.profile" and see where it's pointing.

It should point to something like

/etc/make.profile -> /usr/portage/profiles/default-x86-1.4

But if you've made a central portage directory on a network share for all you Gentoo machines to use like I did then you'll have to "rm /etc/make.profile"

and then
"ln -s /mycentralshare/Linux/Gentoo/portage/profiles/default-x86-1.4 /etc/make.profile"

Let me know if you're still having issues.