Reply
Thread Tools
merlin1991's Avatar
Posts: 125 | Thanked: 1,142 times | Joined on Feb 2010 @ Austria
#801
Originally Posted by awett View Post
i use both pierogi and modrana what do you think i should do ?
run
Code:
dpkg-query -S /etc/sudoers.d/powedit.sudoers
remove the offending package, redo the cssu update.

After that you can install the bad package again (though that would break the next cssu update that updates the enabler), or notify the maintainer of the offending package so we get a proper version in extras.
__________________
"Fog is neither water nor air, it's something between." Merlin
 

The Following 4 Users Say Thank You to merlin1991 For This Useful Post:
Copernicus's Avatar
Posts: 1,986 | Thanked: 7,698 times | Joined on Dec 2010 @ Dayton, Ohio
#802
Hey, as the maintainer of one of the possibly offending packages (Pierogi), I'm quite willing to make it less offensive. That said, Pierogi's entry in the sudoers directory should be pierogi.sudoers, not powedit.sudoers...
 

The Following 2 Users Say Thank You to Copernicus For This Useful Post:
Posts: 50 | Thanked: 16 times | Joined on May 2011
#803
i removed powedit and deleted powedit.sudoers now what specific did you mean by redo cssu update dpkg --configure -a or what :-)?
 
Posts: 1,523 | Thanked: 1,997 times | Joined on Jul 2011 @ not your mom's FOSS basement
#804
Ups, yes, i forgot powedit...
 
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#805
Originally Posted by don_falcone View Post
Ups, yes, i forgot powedit...
What's the problem with this entry

Code:
user ALL = NOPASSWD: /usr/bin/run-standalone.sh /opt/powedit/bin/powedit
'cause I don't know?
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here
 
Posts: 1,100 | Thanked: 2,797 times | Joined on Apr 2011 @ Netherlands
#806
I can confirm that Pierogi and Modrana are NO offending packages for this update. So don't deinstall them
 

The Following 6 Users Say Thank You to ade For This Useful Post:
Copernicus's Avatar
Posts: 1,986 | Thanked: 7,698 times | Joined on Dec 2010 @ Dayton, Ohio
#807
Originally Posted by marmistrz View Post
What's the problem with this entry

Code:
user ALL = NOPASSWD: /usr/bin/run-standalone.sh /opt/powedit/bin/powedit
'cause I don't know?
It looks good to me. (Is it possible that your script was edited on a Windows machine, and therefore has a cr/lf pair at the end of the line that the sudoers system doesn't like? That's the only thing I can think of off the top of my head...)
 

The Following 2 Users Say Thank You to Copernicus For This Useful Post:
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#808
Originally Posted by Copernicus View Post
It looks good to me. (Is it possible that your script was edited on a Windows machine, and therefore has a cr/lf pair at the end of the line that the sudoers system doesn't like? That's the only thing I can think of off the top of my head...)
I didn't use Windows for ages :P

But reinstalling powedit reports no problem. Will the breaking sudoers error appear on first install only?
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here
 
fw190's Avatar
Posts: 584 | Thanked: 700 times | Joined on Jan 2010
#809
If this is any help, for me the update went well.

Again thank you very much for the hard work to all the developers and to merlin1991 who pushed the update.

Keep up the good work
__________________
per ardua ad astra
 

The Following User Says Thank You to fw190 For This Useful Post:
Posts: 204 | Thanked: 423 times | Joined on Jan 2011
#810
Originally Posted by marmistrz View Post
What's the problem with this entry

Code:
user ALL = NOPASSWD: /usr/bin/run-standalone.sh /opt/powedit/bin/powedit
'cause I don't know?
The problem is that powedit.sudoers does not contain THAT line.
It contain following line, which is not valid sudoers entry:
Code:
user ALL = NOPASSWD: sudo /usr/bin/run-standalone.sh `dirname $0`/powedit
There is no problem during (re)installing powedit because your package's postinst and postrm don't run update-sudoers to update sudoers, how it's even supposed to work?
 

The Following 4 Users Say Thank You to hxka For This Useful Post:
Reply

Tags
cssu testing


 
Forum Jump


All times are GMT. The time now is 11:11.