| View previous topic :: View next topic |
| Author |
Message |
UncleOwen
Veteran
Joined: 27 Feb 2003
Posts: 1493
Location: Germany, Hamburg
|
 Posted: Tue Jul 25, 2006 9:13 am Post subject: |
 |
|
| imotlaw wrote: | | but doesn't it also mean that shadow won't be updated when doing updates to world |
No. |
|
| Back to top |
|
 |
sommersg
n00b
Joined: 24 Jul 2006
Posts: 65
|
|
| Back to top |
|
|
UncleOwen
Veteran
Joined: 27 Feb 2003
Posts: 1493
Location: Germany, Hamburg
|
| Posted: Tue Aug 01, 2006 4:56 pm Post subject: |
|
|
| Yeah, that's fine, too. |
|
| Back to top |
|
|
sommersg
n00b
Joined: 24 Jul 2006
Posts: 65
|
| Posted: Tue Aug 01, 2006 5:05 pm Post subject: |
|
|
| Ok, if i used that is it safe to emerge --unmerge pam completely and switch off the pam use flag? |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Tue Aug 01, 2006 8:08 pm Post subject: |
|
|
| sommersg wrote: | | Ok, if i used that is it safe to emerge --unmerge pam completely and switch off the pam use flag? |
You'd have to also do "emerge world --newuse" because there are quite a few packages that have USE=pam |
|
| Back to top |
|
|
bur
Apprentice
Joined: 20 Feb 2004
Posts: 229
|
| Posted: Tue Aug 01, 2006 11:36 pm Post subject: |
|
|
| sommersg wrote: | | Ok, if i used that is it safe to emerge --unmerge pam completely and switch off the pam use flag? |
I asked more or less the same, see USE=pam still needed? |
|
| Back to top |
|
|
dragonetes
n00b
Joined: 17 Oct 2005
Posts: 21
Location: Barcelona - Spain
|
| Posted: Wed Aug 02, 2006 3:59 pm Post subject: |
|
|
Hi all!
Nice to see how is all solved with portage here in forums!
I'm surprised that nobody posted (here) the problem I'm having. When I try to unmerge the pam-login package I get this msg:
| Code: |
gentooza ~ # emerge -C pam-login
sys-apps/pam-login
selected: 3.17
protected: none
omitted: none
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging sys-apps/pam-login-3.17...
No package files given... Grabbing a set.
Traceback (most recent call last):
File "/usr/bin/emerge", line 3940, in ?
emerge_main()
File "/usr/bin/emerge", line 3921, in emerge_main
ldpath_mtimes, raise_on_missing=False):
File "/usr/bin/emerge", line 2332, in unmerge
vartree=vartree, ldpath_mtimes=ldpath_mtimes)
File "/usr/lib/portage/pym/portage.py", line 3173, in unmerge
ldpath_mtimes=ldpath_mtimes)
File "/usr/lib/portage/pym/portage.py", line 5978, in unmerge
mydbapi=self.vartree.dbapi, vartree=self.vartree)
File "/usr/lib/portage/pym/portage.py", line 2731, in doebuild
builddir_lock = portage_locks.lockdir(
File "/usr/lib/portage/pym/portage_locks.py", line 35, in lockdir
return lockfile(mydir,wantnewlockfile=1)
File "/usr/lib/portage/pym/portage_locks.py", line 64, in lockfile
raise portage_exception.DirectoryNotFound, os.path.dirname(mypath)
portage_exception.DirectoryNotFound: '/var/tmp/binpkgs'
gentooza ~ #
|
This is a new installed computer, I think that the point here is that I've obtained pam-login with the stage3 structure (is this true?), so Portage is unable to find the information concerning the package installation...
I've installed the system in this way:
- installed gentoo with the handbook, step-by-step one
- updated Portage to 2.1 <----------------------------- MAYBE HERE'S THE PROBLEM ?
- emerged xorg
- emerged blackbox
- emerged gdm
- emerged gaim
- emerged amarok
- emerged firefox-bin
and finally tried to: - emerge -uDav system
(and got the message that pam-login is blocked)
I've emerged (with --buildpkgonly and --nodeps) shadow and pam-login, but nothing changes, still the errormessage trying to unmerge pam-login.
Any help?
Thanks in advance,
Dragonetes.
RESOLUTION> just create the folder not found and launch emerge again!!
| Code: | | mkdir /var/tmp/binpkgs |
| Code: | | emerge --unmerge pam-login |
|
|
| Back to top |
|
|
bonesaw
n00b
Joined: 06 Aug 2006
Posts: 2
|
| Posted: Mon Aug 07, 2006 2:36 am Post subject: |
|
|
Okay, so I have been all day at trying to do an emerge --update --deep world on my new system, and I found this thread!
I got into the pam-login / shadow block.
I ran 'emerge -C pam-login' and then dispatch-conf'd and etc-updated.
I ran 'emerge shadow' and then etc-updated and dispatch-conf'd.
It took me some tries to get that done - involved updating some other stuff. But it seems like they were successful merges.
However, now I try to run emerge --update --deep world and it still complains about the block. What else is it I need to do?
Thanks everybody. |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Mon Aug 07, 2006 3:59 am Post subject: |
|
|
You've got something that depends on pam-login it would seem. That's your problem.
You've got package A that blocks package B but package C depends on package A. |
|
| Back to top |
|
|
bonesaw
n00b
Joined: 06 Aug 2006
Posts: 2
|
| Posted: Mon Aug 07, 2006 4:01 am Post subject: |
|
|
I get this kind of thing:
| Code: |
system# emerge --update --deep --newuse world
Calculating world dependencies... done!
!!! Error: the sys-apps/pam-login package conflicts with another package;
!!! the two packages cannot be installed on the same system together.
!!! Please use 'emerge --pretend' to determine blockers.
system# emerge --unmerge pam-login
--- Couldn't find 'pam-login' to unmerge.
>>> No packages selected for removal by unmerge.
system#
|
I've got a lot to learn about portage but...what should I be doing to clean up cruft after I unmerge something, to finish the job? |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Mon Aug 07, 2006 7:59 am Post subject: |
|
|
| bonesaw wrote: | I get this kind of thing:
| Code: |
system# emerge --update --deep --newuse world
Calculating world dependencies... done!
!!! Error: the sys-apps/pam-login package conflicts with another package;
!!! the two packages cannot be installed on the same system together.
!!! Please use 'emerge --pretend' to determine blockers.
system# emerge --unmerge pam-login
--- Couldn't find 'pam-login' to unmerge.
>>> No packages selected for removal by unmerge.
system#
|
I've got a lot to learn about portage but...what should I be doing to clean up cruft after I unmerge something, to finish the job? |
You need to find out what depends on pam-login.
One way to do it is to do "echo sys-apps/pam-login >> /etc/portage/package.mask && emerge --update --deep --newuse world"
The second command should fail but it's ouput will tell you which package it was that was needing pam-login.
It might be as simple as doing an update on whichever package it is you find (updating it to a version that doesn't have that dependency). |
|
| Back to top |
|
|
sargek
Apprentice
Joined: 13 Mar 2005
Posts: 170
Location: Texas
|
| Posted: Fri Aug 18, 2006 2:14 am Post subject: yay! |
|
|
| ecatmur wrote: | [edit: changed to be safer]
emerge --buildpkgonly --nodeps shadow && emerge -C pam-login && emerge --usepkgonly shadow |
Once again these forums prove to be invaluable  Thanks ecatmur.
_________________
"Amongst all things, knowledge is truly the best thing: from it's not being liable ever to be stolen, from it's not being purchasable, and from it's being imperishable." |
|
| Back to top |
|
|
Simius
Apprentice
Joined: 26 Oct 2002
Posts: 219
Location: Budapest, Hungary
|
| Posted: Fri Aug 18, 2006 5:29 pm Post subject: Pesky Stage3's... |
|
|
The solution WORKS. That's great.
It's really not a dirty hack, but a perfectly logical and clean solution. That's even greater.
However, I have no fregging idea why Stage1's are now unsupported. For years I have been using Gentoo, and I always used Stage1 installs - sure, it takes time. It took about 2 days on a PIII - it takes several hours on a dualcore Opteron at 2300Mhz...
However, it was clean, straightforward, and one didn't have to put up with update sillinesses like this right at the install. |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Fri Aug 18, 2006 8:08 pm Post subject: Re: Pesky Stage3's... |
|
|
| Simius wrote: | The solution WORKS. That's great.
It's really not a dirty hack, but a perfectly logical and clean solution. That's even greater.
However, I have no fregging idea why Stage1's are now unsupported. For years I have been using Gentoo, and I always used Stage1 installs - sure, it takes time. It took about 2 days on a PIII - it takes several hours on a dualcore Opteron at 2300Mhz...
However, it was clean, straightforward, and one didn't have to put up with update sillinesses like this right at the install. |
1) Using a stage3 plus "emerge -e system" gives you the EXACT SAME THING though much quicker
2) It also fails far less often than bootstrapping.
This is essentially it. Bootstrapping failed quite often all over the place for most users; you just happen to be lucky that it didn't. And in the end you get the exact same system w/ stage3. |
|
| Back to top |
|
|
Gergan Penkov
Veteran
Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)
|
| Posted: Fri Aug 18, 2006 8:15 pm Post subject: Re: Pesky Stage3's... |
|
|
| slycordinator wrote: | | Simius wrote: | The solution WORKS. That's great.
It's really not a dirty hack, but a perfectly logical and clean solution. That's even greater.
However, I have no fregging idea why Stage1's are now unsupported. For years I have been using Gentoo, and I always used Stage1 installs - sure, it takes time. It took about 2 days on a PIII - it takes several hours on a dualcore Opteron at 2300Mhz...
However, it was clean, straightforward, and one didn't have to put up with update sillinesses like this right at the install. |
1) Using a stage3 plus "emerge -e system" gives you the EXACT SAME THING though much quicker
2) It also fails far less often than bootstrapping.
This is essentially it. Bootstrapping failed quite often all over the place for most users; you just happen to be lucky that it didn't. And in the end you get the exact same system w/ stage3. |
Of course this is not exactly what you receive when you emerge -e system just once - it does not give what you would have if you bootstrapped the system system or if you have built the stage1 of yourself - kernel-header updates, glibc updates, gcc updates, linker flags, cflags.
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Fri Aug 18, 2006 11:26 pm Post subject: Re: Pesky Stage3's... |
|
|
| Gergan Penkov wrote: | | Of course this is not exactly what you receive when you emerge -e system just once - it does not give what you would have if you bootstrapped the system system or if you have built the stage1 of yourself - kernel-header updates, glibc updates, gcc updates, linker flags, cflags. |
1) kernel-headers, glibc, and gcc are all updated when you run "emerge -e system", assuming you did "emerge --sync" first like the standard stage3 guide tells you to.
2) The stage3 install guide tells you to change your CFLAGS already before doing "emerge -e system." You change CFLAGS whether you are bootstrapping or not; so being able to change CFLAGS in no way makes bootstrapping great considering bootstrapping has nothing to do with CFLAGS.
3) Unless I'm very mistaken none of the official gentoo guides made mention of changing LDFLAGS. In fact, the official documentation reccommends not to do it. But since you bring them up, I've done many gentoo installs where I've not bootstrapped and I was able to specify LDFLAGS quite well and it worked perfectly. So what, if anything, does bootstrapping have to do with LDFLAGS? |
|
| Back to top |
|
|
Gergan Penkov
Veteran
Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)
|
| Posted: Sat Aug 19, 2006 12:13 am Post subject: |
|
|
Bootstrapping has nothing to do with cflags and ldflags, the problem with single simple emerge -e system is not enough to emulate the bootstrap && emerge -e system.
The problem is the order in which certain components are build and rebuild, in fact stage3 is simply a little bit lengthier than the stage1 (if it works), you'll need two emerge -e system (or sth like emwrap) on major upgrade of the toolchain components - such as going ~arch for example on install (probably there should be just two types stage-tarballs - arch and ~arch).
Of course one could build himself custom stages (catalyst is a wonderfull tool) and in this case stage3 is the better alternative to stage1
P.S. (examples including unsupported things - you need to upgrade kernel-headers before upgrading glibc (also includes changing the ebuild) to have inotify support in glibc, else you have only a stub; you need binutils before glibc to have the --hash-style; you need gcc before glibc to have glibc compiled with gcc-4.1.1 for example, and again in circle)
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack |
|
| Back to top |
|
|
necromncr
n00b
Joined: 21 Mar 2004
Posts: 44
Location: Ig, Slovenia
|
| Posted: Sat Aug 19, 2006 9:55 pm Post subject: |
|
|
I just wanted to add. I unmerged pam-login without previously merging shadow and got stuck with no ssh login for root (relax, ip based firewall to static adressed etc, etc..).
Well, openssh didnt work until i re-set my root password with passwd. After that I could login into ssh with root password normaly.
re! |
|
| Back to top |
|
|
alechiko
Guru
Joined: 01 Feb 2004
Posts: 465
Location: Inside piano, do not disturb.
|
| Posted: Mon Aug 28, 2006 12:44 am Post subject: |
|
|
Um... someone here wrote this: | Quote: | | # emerge --buildpkgonly --nodeps shadow && emerge -C pam-login && emerge --usepkgonly shadow |
And now my compoota does this:
| Quote: | alechiko@genbox ~ $ su -
Password:
configuration error - unknown item 'FAILLOG_ENAB' (notify administrator)
configuration error - unknown item 'LASTLOG_ENAB' (notify administrator)
configuration error - unknown item 'MOTD_FILE' (notify administrator)
configuration error - unknown item 'FTMP_FILE' (notify administrator)
configuration error - unknown item 'ENV_ROOTPATH' (notify administrator)
configuration error - unknown item 'PASS_MIN_LEN' (notify administrator)
configuration error - unknown item 'CHFN_AUTH' (notify administrator)
|
Um.... how can this be fixed? 
_________________
None |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Mon Aug 28, 2006 4:42 am Post subject: |
|
|
| alechiko wrote: | Um... someone here wrote this: | Quote: | | # emerge --buildpkgonly --nodeps shadow && emerge -C pam-login && emerge --usepkgonly shadow |
And now my compoota does this:
| Quote: | alechiko@genbox ~ $ su -
Password:
configuration error - unknown item 'FAILLOG_ENAB' (notify administrator)
configuration error - unknown item 'LASTLOG_ENAB' (notify administrator)
configuration error - unknown item 'MOTD_FILE' (notify administrator)
configuration error - unknown item 'FTMP_FILE' (notify administrator)
configuration error - unknown item 'ENV_ROOTPATH' (notify administrator)
configuration error - unknown item 'PASS_MIN_LEN' (notify administrator)
configuration error - unknown item 'CHFN_AUTH' (notify administrator)
|
Um.... how can this be fixed? |
By doing "etc-update" to edit config files that need to be changed so they no longer are using pam. |
|
| Back to top |
|
|
alechiko
Guru
Joined: 01 Feb 2004
Posts: 465
Location: Inside piano, do not disturb.
|
| Posted: Mon Aug 28, 2006 10:50 am Post subject: |
|
|
Thanks very much man
_________________
None |
|
| Back to top |
|
|
majko036
n00b
Joined: 11 Jul 2004
Posts: 7
|
| Posted: Tue Sep 26, 2006 12:24 pm Post subject: |
|
|
I had the same problem and tried to solve it like you all did. But then another problem apeared. shadow compilation fails with following error: | Code: |
# emerge -1 shadow
Calculating dependencies... done!
>>> Emerging (1 of 1) sys-apps/shadow-4.0.15-r2 to /
...
...
checking libaudit.h usability... no
checking libaudit.h presence... yes
configure: WARNING: libaudit.h: present but cannot be compiled
configure: WARNING: libaudit.h: check for missing prerequisite headers?
configure: WARNING: libaudit.h: see the Autoconf documentation
configure: WARNING: libaudit.h: section "Present But Cannot Be Compiled"
configure: WARNING: libaudit.h: proceeding with the preprocessor's result
configure: WARNING: libaudit.h: in the future, the compiler will take precedence
configure: WARNING: ## ------------------------------------------ ##
configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ##
configure: WARNING: ## ------------------------------------------ ##
checking for libaudit.h... yes
...
...
then mv -f ".deps/age.Tpo" ".deps/age.Po"; else rm -f ".deps/age.Tpo"; exit 1; fi
In file included from /usr/include/linux/sched.h:21,
from /usr/include/linux/audit.h:28,
from /usr/include/libaudit.h:36,
from ../lib/defines.h:343,
from ../lib/prototypes.h:28,
from addgrps.c:6:
/usr/include/asm/semaphore.h:46: error: expected specifier-qualifier-list before 'wait_queue_head_t'
/usr/include/asm/semaphore.h: In function 'sema_init':
/usr/include/asm/semaphore.h:73: error: 'struct semaphore' has no member named 'wait'
/usr/include/asm/semaphore.h: In function 'down':
/usr/include/asm/semaphore.h:106: error: expected ':' or ')' before 'LOCK_SECTION_START'
/usr/include/asm/semaphore.h: In function 'down_interruptible':
/usr/include/asm/semaphore.h:133: error: expected ':' or ')' before 'LOCK_SECTION_START'
/usr/include/asm/semaphore.h: In function 'down_trylock':
/usr/include/asm/semaphore.h:158: error: expected ':' or ')' before 'LOCK_SECTION_START'
/usr/include/asm/semaphore.h: In function 'up':
/usr/include/asm/semaphore.h:182: error: expected ':' or ')' before 'LOCK_SECTION_START'
|
I reemerged linux-headers but the error is still there. 
Anyone? |
|
| Back to top |
|
|
bdgenz
n00b
Joined: 28 Oct 2006
Posts: 13
Location: TX, US
|
| Posted: Wed Nov 01, 2006 9:37 pm Post subject: pam-login blocked by shadow (that shadow isn't installed!) |
|
|
GLSA 200606-20 said pam-login was blocking shadow so I uninstalled it for a moment. GLSA still didnt work so I emerged shadow. Now GLSA is happy, but pam-login wont emerge. Logout or loose my connection and it's all over - I,m 1500 miles from this production machine!
emerge -pv pam-login
These are the packages that would be merged, in order:
Calculating dependencies... done!
[blocks B ] >=sys-apps/shadow-4.0.14-r2 (is blocking sys-apps/pam-login-4.0.14)
[ebuild N ] sys-apps/pam-login-4.0.14 USE="nls -livecd (-selinux) -skey" 1,217 kB
Total size of downloads: 1,217 kB
root@home distfiles # emerge --search shadow
Searching...
[ Results for search key : shadow ]
[ Applications found : 2 ]
* sys-apps/shadow
Latest version available: 4.0.15-r2
Latest version installed: 4.0.15-r2
Size of files: 1,264 kB
Homepage: http://shadow.pld.org.pl/
Description: Utilities to deal with user accounts
License: BSD
I don't find shadow anything in package.mask.
Any suggestions would really help right about now. |
|
| Back to top |
|
|
kevman
n00b
Joined: 22 Sep 2006
Posts: 44
Location: Pittsburgh, PA.
|
| Posted: Wed Nov 01, 2006 9:48 pm Post subject: |
|
|
Yeah, that's becuase pam-login has been replaced with Shadow. Pam-login isn't needed anymore.
But if you remove pam-login, if have to install Shadow.
So you are fine without pam-login. Everything is cool.
_________________
[INSERT 800x600 SIGPIC HERE] |
|
| Back to top |
|
|
amne
Bodhisattva
Joined: 17 Nov 2002
Posts: 6378
Location: Graz / EU
|
| Posted: Wed Nov 01, 2006 9:50 pm Post subject: |
|
|
Merged bdgenz' post here.
bdgenz - please take a look at the posts in this thread - shadow and pam-login block each other because pam-login was merged into shadow iirc. So unless you still have problems logging a second session (don't close the old one yet  ) in right now, things should be fine.
_________________
Dinosaur week! (Ok, this thread is so last week) |
|
| Back to top |
|
|
|
Portage & Programming
