Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 247776
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: bart9h <rodolfo.borges@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
emerge--info.txt emerge --info text/plain bart9h 2008-11-20 23:49 0000 2.97 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 247776 depends on: Show dependency tree
Bug 247776 blocks: 210077 216231
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2008-11-20 15:45 0000 
After a "emerge world" that upgraded sudo to 1.6.9_p17, I can't sudo anymore.
Looks like the /etc/sudoers file has been overwritten, and my configuration was
lost.  sudo says I'm not even in the sudoers file.


(sad part is I don't remember the root password :)

Reproducible: Didn't try

Steps to Reproduce:

------- Comment #1 From Diego E. 'Flameeyes' Pettenò 2008-11-20 16:09:11 0000 ------- 
Hmm I'm quite sure that it should be config protected. Zac, do you have any
ideas whether something might cause this?

------- Comment #2 From Zac Medico 2008-11-20 17:54:40 0000 ------- 
I CONFIG_PROTECT_MASK had been configured to contain '/etc' then that would
cause it. Please post emerge --info output (shows CONFIG_PROTECT and
CONFIG_PROTECT_MASK settings).

------- Comment #3 From bart9h 2008-11-20 23:49:52 0000 ------- 
Created an attachment (id=172574) [details]
emerge --info

------- Comment #4 From Zac Medico 2008-11-21 01:40:41 0000 ------- 
(In reply to comment #3)
> Created an attachment (id=172574) [edit] [details]
> emerge --info
> 

See, CONFIG_PROTECT is empty. Maybe you have CONFIG_PROTECT="-*" set in
make.conf or in your environment. That's bad.

------- Comment #5 From Zac Medico 2008-11-21 23:23:44 0000 ------- 
In svn r12022 I've added a warning message that emerge will show if
CONFIG_PROTECT is empty for some reason.

------- Comment #6 From bart9h 2008-11-21 23:45:18 0000 ------- 
This is weird:

$ emerge --info | grep CONFIG_PROTECT=
CONFIG_PROTECT=""
$ cat /etc/make.conf | grep CONFIG_PROTECT=
CONFIG_PROTECT="-*"
$

------- Comment #7 From bart9h 2008-11-21 23:46:30 0000 ------- 
No, it's not.

I misunderstood it, sorry.

------- Comment #8 From Zac Medico 2008-11-22 05:56:39 0000 ------- 
The warning message is in 2.2_rc15.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug