> I didn't think this would do much, but gave it a try anyway
> And it doesn't help. :/
I think i meant '-i' -- but I'd have to look at the patch`s interaction.
I can't recreate the problem in the 1.6.x we're running in our internal
release engineering.
1.7.x, and its associated backport,
On 02/25/2009 11:49, Brian A. Seklecki wrote:
>> lowering the umask of the person running sudo.
>>
>> This had the effect of truly screwing up many installed ports for me
>
> Maybe try "sudo -H -u root [command]" NetBSD Pkgsrc is nice in this
> respect because it has sudo(8) integration in the
> lowering the umask of the person running sudo.
>
> This had the effect of truly screwing up many installed ports for me
Maybe try "sudo -H -u root [command]" NetBSD Pkgsrc is nice in this
respect because it has sudo(8) integration in the MKs. ~BAS
signature.asc
Description: This is a digi
On 02/19/2009 15:56, Aleksandr Miroslav wrote:
> For the longest time, I have installed ports via the "sudo make install" or
> "sudo portupgrade" or "sudo portinstall" method and never had a problem.
This seems to have jumped up and bitten me on the arse as well. I
believe the "problem" lies here
For the longest time, I have installed ports via the "sudo make install" or
"sudo portupgrade" or "sudo portinstall" method and never had a problem.
Recently, as of a few weeks ago, I started noticing that ports that were
installed or upgraded were getting the wrong permissions. Not only were
dir
