All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock in F7/F8 to current 0.9 on/around Feb 1.
The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now.
The *only* difference between 0.8.<latest> and 0.9.<latest> at this point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.
-- Michael
On 01/05/2008 12:49 AM, Michael_E_Brown@Dell.com wrote:
All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock in F7/F8 to current 0.9 on/around Feb 1. The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now. The *only* difference between 0.8.<latest> and 0.9.<latest> at this point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.-- Michael
Hey all
Did I hit a bug here or am I doing something very stupid ? According to the paragraph above, I should either be allowed to build as user, or be asked for the root password. Helas.... [wolfy@wolfy ~]$ id wolfy uid=500(wolfy) gid=500(wolfy) groups=500(wolfy),497(mock) context=user_u:system_r:unconfined_t [wolfy@wolfy ~]$ rpm -qi mock Name : mock Relocations: (not relocatable) Version : 0.9.7 Vendor: Fedora Project Release : 1.fc7 Build Date: Sat 02 Feb 2008 02:14:01 AM EET Install Date: Tue 04 Mar 2008 01:12:56 AM EET Build Host: ppc3.fedora.redhat.com [wolfy@wolfy ~]$ mock -r fedora-5-x86_64-epel /tmp/rpmlint/devel/rpmlint-0.82-3.fc9.src.rpm ERROR: [Errno 1] Operation not permitted Traceback (most recent call last): File "/usr/sbin/mock", line 630, in <module> main(retParams) File "/usr/sbin/mock", line 412, in main uidManager._becomeUser(unprivUid, unprivGid) File "<peak.util.decorators.rewrap wrapping mock.uid._becomeUser at 0x008F4500>", line 3, in _becomeUser def _becomeUser(self, uid, gid): return __decorated(self, uid, gid) File "/usr/lib/python2.5/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 65, in _becomeUser self._elevatePrivs() File "<peak.util.decorators.rewrap wrapping mock.uid._elevatePrivs at 0x008F0F50>", line 3, in _elevatePrivs def _elevatePrivs(self): return __decorated(self) File "/usr/lib/python2.5/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 60, in _elevatePrivs setresuid(0, 0, 0) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 91, in setresuid raise OSError(_errno.value, os.strerror(_errno.value)) OSError: [Errno 1] Operation not permitted
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Manuel Wolfshant wrote:
On 01/05/2008 12:49 AM, Michael_E_Brown@Dell.com wrote:
All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock inF7/F8 to current 0.9 on/around Feb 1.
The mock 0.9 branch has brewed in rawhide since early Dec, and sofar it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now.
The *only* difference between 0.8.<latest> and 0.9.<latest> atthis point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.
-- Michael
Hey all
Did I hit a bug here or am I doing something very stupid ? According to the paragraph above, I should either be allowed to build as user, or be asked for the root password. Helas.... [wolfy@wolfy ~]$ id wolfy uid=500(wolfy) gid=500(wolfy) groups=500(wolfy),497(mock) context=user_u:system_r:unconfined_t [wolfy@wolfy ~]$ rpm -qi mock Name : mock Relocations: (not relocatable) Version : 0.9.7 Vendor: Fedora Project Release : 1.fc7 Build Date: Sat 02 Feb 2008 02:14:01 AM EET Install Date: Tue 04 Mar 2008 01:12:56 AM EET Build Host: ppc3.fedora.redhat.com [wolfy@wolfy ~]$ mock -r fedora-5-x86_64-epel /tmp/rpmlint/devel/rpmlint-0.82-3.fc9.src.rpm ERROR: [Errno 1] Operation not permitted Traceback (most recent call last): File "/usr/sbin/mock", line 630, in <module> main(retParams) File "/usr/sbin/mock", line 412, in main uidManager._becomeUser(unprivUid, unprivGid) File "<peak.util.decorators.rewrap wrapping mock.uid._becomeUser at 0x008F4500>", line 3, in _becomeUser def _becomeUser(self, uid, gid): return __decorated(self, uid, gid) File "/usr/lib/python2.5/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 65, in _becomeUser self._elevatePrivs() File "<peak.util.decorators.rewrap wrapping mock.uid._elevatePrivs at 0x008F0F50>", line 3, in _elevatePrivs def _elevatePrivs(self): return __decorated(self) File "/usr/lib/python2.5/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 60, in _elevatePrivs setresuid(0, 0, 0) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 91, in setresuid raise OSError(_errno.value, os.strerror(_errno.value)) OSError: [Errno 1] Operation not permitted
Hmmm, looks like a bug to me. Please file a BZ against mock.
Just to be sure I understand, this is from an F7 host? I wonder if there's a config difference for the consolehelper stuff on F7?
Clark
Clark Williams wrote:
Manuel Wolfshant wrote:
On 01/05/2008 12:49 AM, Michael_E_Brown@Dell.com wrote:
[...] The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now.
The *only* difference between 0.8.<latest> and 0.9.<latest> atthis point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup. [...]
Hey all
Did I hit a bug here or am I doing something very stupid ? According to the paragraph above, I should either be allowed to build as user, or be asked for the root password. Helas.... [wolfy@wolfy ~]$ id wolfy uid=500(wolfy) gid=500(wolfy) groups=500(wolfy),497(mock) context=user_u:system_r:unconfined_t [wolfy@wolfy ~]$ rpm -qi mock Name : mock Relocations: (not relocatable) Version : 0.9.7 Vendor: Fedora Project Release : 1.fc7 Build Date: Sat 02 Feb 2008 02:14:01 AM EET Install Date: Tue 04 Mar 2008 01:12:56 AM EET Build Host: ppc3.fedora.redhat.com [wolfy@wolfy ~]$ mock -r fedora-5-x86_64-epel /tmp/rpmlint/devel/rpmlint-0.82-3.fc9.src.rpm ERROR: [Errno 1] Operation not permitted Traceback (most recent call last): File "/usr/sbin/mock", line 630, in <module> main(retParams) File "/usr/sbin/mock", line 412, in main uidManager._becomeUser(unprivUid, unprivGid) File "<peak.util.decorators.rewrap wrapping mock.uid._becomeUser at 0x008F4500>", line 3, in _becomeUser def _becomeUser(self, uid, gid): return __decorated(self, uid, gid) File "/usr/lib/python2.5/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 65, in _becomeUser self._elevatePrivs() File "<peak.util.decorators.rewrap wrapping mock.uid._elevatePrivs at 0x008F0F50>", line 3, in _elevatePrivs def _elevatePrivs(self): return __decorated(self) File "/usr/lib/python2.5/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 60, in _elevatePrivs setresuid(0, 0, 0) File "/usr/lib/python2.5/site-packages/mock/uid.py", line 91, in setresuid raise OSError(_errno.value, os.strerror(_errno.value)) OSError: [Errno 1] Operation not permitted
Hmmm, looks like a bug to me. Please file a BZ against mock.
Just to be sure I understand, this is from an F7 host? I wonder if there's a config difference for the consolehelper stuff on F7?
Clark
On Thu, Mar 06, 2008 at 01:08:39PM +0200, Manuel Wolfshant wrote:
Clark Williams wrote:
Manuel Wolfshant wrote:
On 01/05/2008 12:49 AM, Michael_E_Brown@Dell.com wrote: Hey all
Did I hit a bug here or am I doing something very stupid ? According to the paragraph above, I should either be allowed to build as user, or be asked for the root password. Helas.... [wolfy@wolfy ~]$ id wolfy uid=500(wolfy) gid=500(wolfy) groups=500(wolfy),497(mock) context=user_u:system_r:unconfined_t [wolfy@wolfy ~]$ mock -r fedora-5-x86_64-epel /tmp/rpmlint/devel/rpmlint-0.82-3.fc9.src.rpm ERROR: [Errno 1] Operation not permitted
Hmmm, looks like a bug to me. Please file a BZ against mock.
Just to be sure I understand, this is from an F7 host? I wonder if there's a config difference for the consolehelper stuff on F7?
Clark
Most likely cause of this problem is a bad PATH that has /usr/sbin/ before /usr/bin/, meaning that the consolehelper suid utility is *not* run, but you end up running /usr/sbin/mock directly, which expects to only ever be run with elevated privs.
Assuming this is the case, there are two possible fixes:
A) fix your path or B) run /usr/bin/mock directly -- Michael
Most likely cause of this problem is a bad PATH that has /usr/sbin/ before /usr/bin/, meaning that the consolehelper suid utility is *not* run, but you end up running /usr/sbin/mock directly, which expects to only ever be run with elevated privs.
Assuming this is the case, there are two possible fixes:
A) fix your path or B) run /usr/bin/mock directly -- Michael
You are right, reversing the order of /usr/bin and /usr/sbin fixes the above but I get another strange problem now: - if I run mock directly, I get the prompt back immediatly - if I use strace mock , it works OK.
Any idea what's the issue here?
On Thu, Mar 06, 2008 at 08:26:15PM +0200, Manuel Wolfshant wrote:
Most likely cause of this problem is a bad PATH that has /usr/sbin/ before /usr/bin/, meaning that the consolehelper suid utility is *not* run, but you end up running /usr/sbin/mock directly, which expects to only ever be run with elevated privs.
Assuming this is the case, there are two possible fixes:
A) fix your path or B) run /usr/bin/mock directly -- Michael
You are right, reversing the order of /usr/bin and /usr/sbin fixes the above but I get another strange problem now:
- if I run mock directly, I get the prompt back immediatly
- if I use strace mock , it works OK.
Any idea what's the issue here?
Absolutely no idea. Is this still happening? -- Michael
On 03/13/2008 03:48 AM, Michael E Brown wrote:
You are right, reversing the order of /usr/bin and /usr/sbin fixes the above but I get another strange problem now:
- if I run mock directly, I get the prompt back immediatly
- if I use strace mock , it works OK.
Any idea what's the issue here?
Absolutely no idea. Is this still happening?
Yes, it does, but I am 100% sure it is not a mock but a consolehelper problem (it does not call /usr/sbin/mock if I directly call /usr/bin/mock as normal user; however this does work as intended if I run it under strace ).
On Fri, Mar 14, 2008 at 05:24:56AM +0200, Manuel Wolfshant wrote:
On 03/13/2008 03:48 AM, Michael E Brown wrote:
You are right, reversing the order of /usr/bin and /usr/sbin fixes the above but I get another strange problem now:
- if I run mock directly, I get the prompt back immediatly
- if I use strace mock , it works OK.
Any idea what's the issue here?
Absolutely no idea. Is this still happening?
Yes, it does, but I am 100% sure it is not a mock but a consolehelper problem (it does not call /usr/sbin/mock if I directly call /usr/bin/mock as normal user; however this does work as intended if I run it under strace ).
Ok, I am very interested in hearing about the root cause if you can manage to figure out what is going on.
Any consolehelper experts out there? -- Michael
On Fri, Jan 4, 2008 at 4:49 PM, Michael_E_Brown@dell.com wrote:
All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock in F7/F8 to current 0.9 on/around Feb 1. The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now. The *only* difference between 0.8.<latest> and 0.9.<latest> at this point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.
Do any changes, fixes, etc need to be done for EPEL since they are basically F-3/F-6?
On Thu, 2008-03-13 at 11:11 -0600, Stephen John Smoogen wrote:
Do any changes, fixes, etc need to be done for EPEL since they are basically F-3/F-6?
We've been using 0.9.5 on the koji builders for a while now, with great success.
On Thu, Mar 13, 2008 at 11:11:33AM -0600, Stephen John Smoogen wrote:
On Fri, Jan 4, 2008 at 4:49 PM, Michael_E_Brown@dell.com wrote:
All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock in F7/F8 to current 0.9 on/around Feb 1. The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now. The *only* difference between 0.8.<latest> and 0.9.<latest> at this point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.Do any changes, fixes, etc need to be done for EPEL since they are basically F-3/F-6?
We need to pull mock from EPEL 4, I havent put in the request for that yet.
I am pretty sure that clark put in the update for epel5 to migrate it to the latest as well (since that is what is being used on the fedora build systems.) Clark? -- Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael E Brown wrote:
On Thu, Mar 13, 2008 at 11:11:33AM -0600, Stephen John Smoogen wrote:
On Fri, Jan 4, 2008 at 4:49 PM, Michael_E_Brown@dell.com wrote:
All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock in F7/F8 to current 0.9 on/around Feb 1. The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now. The *only* difference between 0.8.<latest> and 0.9.<latest> at this point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.Do any changes, fixes, etc need to be done for EPEL since they are basically F-3/F-6?
We need to pull mock from EPEL 4, I havent put in the request for that yet.
I am pretty sure that clark put in the update for epel5 to migrate it to the latest as well (since that is what is being used on the fedora build systems.) Clark? -- Michael
The only requests I see in bodhi are the f7/f8 ones; same in koji. I did not build or push E-4 or E-5.
Sounds like we (we == I) need to do so?
Clark
On Thu, Mar 13, 2008 at 02:24:50PM -0500, Clark Williams wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael E Brown wrote:
On Thu, Mar 13, 2008 at 11:11:33AM -0600, Stephen John Smoogen wrote:
On Fri, Jan 4, 2008 at 4:49 PM, Michael_E_Brown@dell.com wrote:
All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock in F7/F8 to current 0.9 on/around Feb 1. The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now. The *only* difference between 0.8.<latest> and 0.9.<latest> at this point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.Do any changes, fixes, etc need to be done for EPEL since they are basically F-3/F-6?
We need to pull mock from EPEL 4, I havent put in the request for that yet.
I am pretty sure that clark put in the update for epel5 to migrate it to the latest as well (since that is what is being used on the fedora build systems.) Clark? -- Michael
The only requests I see in bodhi are the f7/f8 ones; same in koji. I did not build or push E-4 or E-5.
Sounds like we (we == I) need to do so?
EPEL 5 doesnt use bhodi/koji, it uses plague. If you can push it, that would be great. If not, I still have the required client stuff installed to do an EPEL 5 push. -- Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael E Brown wrote:
On Thu, Mar 13, 2008 at 02:24:50PM -0500, Clark Williams wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael E Brown wrote:
On Thu, Mar 13, 2008 at 11:11:33AM -0600, Stephen John Smoogen wrote:
On Fri, Jan 4, 2008 at 4:49 PM, Michael_E_Brown@dell.com wrote:
All mock users,
The mock maintainers (Clark, Jesse, me) will upgrade mock in F7/F8 to current 0.9 on/around Feb 1. The mock 0.9 branch has brewed in rawhide since early Dec, and so far it looks good. The 0.9 branch is now being used on the official build systems, so if there were any major problems, we would expect to have hit them by now. The *only* difference between 0.8.<latest> and 0.9.<latest> at this point is that we have dropped the old mock setuid wrapper and now use the consolehelper subsystem. For this, you will notice new /etc/pam.d/mock, /etc/consolehelper/mock files which configure mock. The default config is set up to operate exactly the same as the old 0.8 branch: ie. you must be a member of the 'mock' group to run mock. Additionally, with consolehelper comes one new feature: if you are not in the 'mock' group, you will be prompted to enter the root password and it will run. This means you can run mock without worrying about any pre-setup.Do any changes, fixes, etc need to be done for EPEL since they are basically F-3/F-6?
We need to pull mock from EPEL 4, I havent put in the request for that yet.
I am pretty sure that clark put in the update for epel5 to migrate it to the latest as well (since that is what is being used on the fedora build systems.) Clark? -- Michael
The only requests I see in bodhi are the f7/f8 ones; same in koji. I did not build or push E-4 or E-5.
Sounds like we (we == I) need to do so?
EPEL 5 doesnt use bhodi/koji, it uses plague. If you can push it, that would be great. If not, I still have the required client stuff installed to do an EPEL 5 push. -- Michael
Ugh, when we went to koji, I dropped that stuff like, well, the plague.
If you still have it, please do a EPEL 5 push. I'll see about getting plague-client and whatever it needs back on my box so I can do them too.
Sorry I dropped the ball on EPEL.
Clark
devel@lists.stg.fedoraproject.org
-
Clark Williams -
Jesse Keating -
Manuel Wolfshant -
Michael E Brown -
Michael E Brown
-
Stephen John Smoogen