El mar, 03-07-2012 a las 10:02 +0200, Michał Górny escribió:
On Mon, 02 Jul 2012 13:45:26 -0700
Zac Medico zmed...@gentoo.org wrote:
On 07/02/2012 01:36 PM, viv...@gmail.com wrote:
Il 02/07/2012 22:01, Zac Medico ha scritto:
On 07/02/2012 12:48 PM, Pacho Ramos wrote:
El lun,
On 07/21/2013 03:53 AM, Pacho Ramos wrote:
El mar, 03-07-2012 a las 10:02 +0200, Michał Górny escribió:
On Mon, 02 Jul 2012 13:45:26 -0700
Zac Medico zmed...@gentoo.org wrote:
On 07/02/2012 01:36 PM, viv...@gmail.com wrote:
Il 02/07/2012 22:01, Zac Medico ha scritto:
On 07/02/2012 12:48 PM,
On 21/07/13 02:25 PM, Zac Medico wrote:
On 07/21/2013 03:53 AM, Pacho Ramos wrote:
El mar, 03-07-2012 a las 10:02 +0200, Michał Górny escribió:
On Mon, 02 Jul 2012 13:45:26 -0700
Zac Medico zmed...@gentoo.org wrote:
On 07/02/2012 01:36 PM, viv...@gmail.com wrote:
Il 02/07/2012 22:01, Zac
On Sun, Jul 21, 2013 at 2:30 PM, Alex Xu alex_y...@yahoo.ca wrote:
userpriv and usersandbox don't work in pypy because os.setgroups isn't
implemented there.
I had a go at it a while back, but the complete and utter lack of any
documentation whatsoever... kinda threw me off.
I don't think we
El lun, 02-07-2012 a las 13:45 -0700, Zac Medico escribió:
On 07/02/2012 01:36 PM, viv...@gmail.com wrote:
Il 02/07/2012 22:01, Zac Medico ha scritto:
On 07/02/2012 12:48 PM, Pacho Ramos wrote:
El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió:
Hi,
In case you aren't familiar
On Mon, 02 Jul 2012 13:45:26 -0700
Zac Medico zmed...@gentoo.org wrote:
On 07/02/2012 01:36 PM, viv...@gmail.com wrote:
Il 02/07/2012 22:01, Zac Medico ha scritto:
On 07/02/2012 12:48 PM, Pacho Ramos wrote:
El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió:
Hi,
In case you
Il 02/07/2012 22:45, Zac Medico ha scritto:
On 07/02/2012 01:36 PM, viv...@gmail.com wrote:
Il 02/07/2012 22:01, Zac Medico ha scritto:
On 07/02/2012 12:48 PM, Pacho Ramos wrote:
El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió:
Hi,
In case you aren't familiar with
I guess something like this might work in pkg_postinst of the portage
ebuild:
find $DISTDIR -maxdepth 1 -type d -uid 0 | xargs chown -R
portage:portage
I would only trigger something like this once, when upgrading from a
version that doesn't have userpriv enabled by default.
If you
I guess something like this might work in pkg_postinst of the portage
ebuild:
find $DISTDIR -maxdepth 1 -type d -uid 0 | xargs chown -R
portage:portage
I would only trigger something like this once, when upgrading from a
version that doesn't have userpriv enabled by default.
El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
Allow portage to drop root privileges and compile packages as
portage:portage without a sandbox (unless usersandbox
On 07/02/2012 12:48 PM, Pacho Ramos wrote:
El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
Allow portage to drop root privileges and compile packages as
Il 02/07/2012 22:01, Zac Medico ha scritto:
On 07/02/2012 12:48 PM, Pacho Ramos wrote:
El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
Allow portage to drop root
On 07/02/2012 01:36 PM, viv...@gmail.com wrote:
Il 02/07/2012 22:01, Zac Medico ha scritto:
On 07/02/2012 12:48 PM, Pacho Ramos wrote:
El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the
On Monday 28 May 2012 14:34:22 Zac Medico wrote:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
Allow portage to drop root privileges and compile packages as
portage:portage without a sandbox (unless usersandbox is also
On 05/29/12 04:43, Agostino Sarubbo wrote:
I'm using usersync since a long time, how about add it too?
This is also a good idea. I second it.
signature.asc
Description: OpenPGP digital signature
On 05/29/2012 01:43 AM, Agostino Sarubbo wrote:
On Monday 28 May 2012 14:34:22 Zac Medico wrote:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
Allow portage to drop root privileges and compile packages as
portage:portage
On Tue, 29 May 2012 02:05:08 -0700
Zac Medico zmed...@gentoo.org wrote:
On 05/29/2012 01:43 AM, Agostino Sarubbo wrote:
On Monday 28 May 2012 14:34:22 Zac Medico wrote:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
On Tue, May 29, 2012 at 10:11 AM, Michał Górny mgo...@gentoo.org wrote:
Wouldn't that break users who sync using a regular user? And then break
again, and again every time portage is merged?
Yup, unless that regular user is the same one used for userpriv (if
I'm correctly understanding the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2012 04:50 PM, Rich Freeman wrote:
On Tue, May 29, 2012 at 10:11 AM, Michał Górny mgo...@gentoo.org
wrote:
Wouldn't that break users who sync using a regular user? And then
break again, and again every time portage is merged?
Yup,
On Tue, May 29, 2012 at 10:57 AM, hasufell hasuf...@gentoo.org wrote:
I am against too many defaults. It's documented and people can
activate it.
I'm already annoyed by pre-set stuff like cups in
releases/make.defaults.
While universal agreement is a bit much to hope for, I just wanted to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2012 05:23 PM, Rich Freeman wrote:
On Tue, May 29, 2012 at 10:57 AM, hasufell hasuf...@gentoo.org
wrote:
I am against too many defaults. It's documented and people can
activate it. I'm already annoyed by pre-set stuff like cups in
On 29 May 2012 12:27, hasufell hasuf...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2012 05:23 PM, Rich Freeman wrote:
On Tue, May 29, 2012 at 10:57 AM, hasufell hasuf...@gentoo.org
wrote:
I am against too many defaults. It's documented and people can
activate
On Tue, 29 May 2012 18:27:51 +0200
hasufell hasuf...@gentoo.org wrote:
Well then let my clarify: I'm against too many pre-set (meaning
activated) features/useflags.
Think of it as nouserpriv feature. ;) Either way, to disable userpriv
is kind of working against QA as a package really should be
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
The migration might be a bit more confusing, but it allows portage to
gradually adopt better stuff without having FEATURES=everything under
the sun.
On Tue, May 29, 2012 at 3:46 PM, Michael Orlitzky mich...@orlitzky.com wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
Portage currently defaults to running the build process as root. The
entire point of this thread is that Zac wants
On Tue, May 29, 2012 at 03:46:39PM -0400, Michael Orlitzky wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
No. Please stay away from things like this.
It is reverse logic and can be very confusing. Just adding -userpriv
to your features
On 05/29/12 15:58, Mike Gilbert wrote:
On Tue, May 29, 2012 at 3:46 PM, Michael Orlitzky mich...@orlitzky.com
wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
Portage currently defaults to running the build process as root. The
On 05/29/2012 07:11 AM, Michał Górny wrote:
On Tue, 29 May 2012 02:05:08 -0700
Zac Medico zmed...@gentoo.org wrote:
On 05/29/2012 01:43 AM, Agostino Sarubbo wrote:
I'm using usersync since a long time, how about add it too?
Yeah, I think that would be a good default too. I guess the
On 29 May 2012 12:46, Michael Orlitzky mich...@orlitzky.com wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
rootpriv instead of nouserpriv?
The migration might be a bit more confusing, but it allows portage to
gradually adopt better
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2012 07:57 AM, hasufell wrote:
I am against too many defaults. It's documented and people can
activate it. I'm already annoyed by pre-set stuff like cups in
releases/make.defaults.
In the case of userpriv and usersync, I expect that we
On 05/29/2012 02:47 PM, Hilco Wijbenga wrote:
On 29 May 2012 12:46, Michael Orlitzky mich...@orlitzky.com wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
rootpriv instead of nouserpriv?
What's the use case for this? Can't we just
On 05/29/12 18:11, Zac Medico wrote:
On 05/29/2012 02:47 PM, Hilco Wijbenga wrote:
On 29 May 2012 12:46, Michael Orlitzky mich...@orlitzky.com wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
rootpriv instead of nouserpriv?
What's
On 05/29/2012 04:22 PM, Richard Yao wrote:
On 05/29/12 18:11, Zac Medico wrote:
On 05/29/2012 02:47 PM, Hilco Wijbenga wrote:
On 29 May 2012 12:46, Michael Orlitzky mich...@orlitzky.com wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
On 29 May 2012 15:11, Zac Medico zmed...@gentoo.org wrote:
On 05/29/2012 02:47 PM, Hilco Wijbenga wrote:
On 29 May 2012 12:46, Michael Orlitzky mich...@orlitzky.com wrote:
How about introducing e.g. FEATURES=nouserpriv, and make the current
userpriv behavior the default?
rootpriv instead of
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
Allow portage to drop root privileges and compile packages as
portage:portage without a sandbox (unless usersandbox is also used).
The rationale for having the separate usersandbox
Am Montag 28 Mai 2012, 23:34:22 schrieb Zac Medico:
I've been using FEATURES=userpriv usersandbox for years, and I don't
remember experiencing any problems because of it, so I think that it
would be reasonable to have it enabled by default. Objections?
No objections. Excellent idea.
--
On Mon, May 28, 2012 at 11:34 PM, Zac Medico zmed...@gentoo.org wrote:
Hi,
In case you aren't familiar with FEATURES=userpriv, here's the
description from the make.conf(5) man page:
Allow portage to drop root privileges and compile packages as
portage:portage without a sandbox (unless
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/28/2012 11:34 PM, Zac Medico wrote:
I've been using FEATURES=userpriv usersandbox for years, and I
don't remember experiencing any problems because of it, so I think
that it would be reasonable to have it enabled by default.
Objections?
On Tue, May 29, 2012 at 12:34 AM, Zac Medico zmed...@gentoo.org wrote:
Note that ebuilds can set RESTRICT=userpriv if they require superuser
privileges during any of the src_* phases that userpriv affects.
Current list of packages in portage using userpriv restriction:
app-laptop/tp_smapi
On Mon, May 28, 2012 at 9:09 PM, Maxim Kammerer m...@dee.su wrote:
Ditto, ~2 years with regular full @world rebuild.
Yup, been years since the last time I even saw a bug for this.
Probably wouldn't hurt to announce in news if it will impact existing
users. I doubt anybody would actually
40 matches
Mail list logo
