Front page | perl.perl6.users |
Postings from February 2021
>> On Sat, Feb 13, 2021 at 1:53 PM ToddAndMargo via perl6-users
>> <perl6-users@perl.org <mailto:perl6-users@perl.org>> wrote:
>>
>> On 2/13/21 12:35 PM, ToddAndMargo via perl6-users wrote:
>> > Hi All,
>> >
>> > After updating from
>> >
>> > https://github.com/nxadm/rakudo-pkg/releases
>> <https://github.com/nxadm/rakudo-pkg/releases>
>> >
>> > RakudoPkgFedora33-2020.12.x86_64.rpm
>> > -->
>> > RakudoPkgFedora33-2020.12.04.x86_64.rpm
>> >
>> > If you are getting getting a TON of warning errors when
>> > starting your programs beginning with:
>> >
>> > WARNING: unhandled Failure detected in DESTROY. If
>> > you meant to ignore it, you can mark it as handled
>> > by calling .Bool, .so, .not, or .defined methods.
>> > The Failure was:
>> >
>> > Failed to create directory
>> '/opt/rakudo-pkg/share/perl6/vendor/short'
>> > with mode '0o777': Failed to mkdir: Permission denied
>> > in any statement_control at
>> > /opt/rakudo-pkg/bin/../share/perl6/lib/Perl6/Grammar.moarvm line 1
>> >
>> >
>> > The fix is to do it yourself:
>> >
>> > $ cd /opt/rakudo-pkg/share/perl6/vendor
>> > $ su root -c "mkdir short; chmod -R 777 short"
>> >
>> > (You can do this with sudo too. I just don't like
>> > the command.)
>> >
>> > I did 2777 to see if the ownership would change after
>> > running a program. It did not.
>> >
>> >
>> > I have reported the bug over at:
>> > ‘/opt/rakudo-pkg/share/perl6/vendor/short’: Permission denied
>> > https://github.com/nxadm/rakudo-pkg/issues/78
>> <https://github.com/nxadm/rakudo-pkg/issues/78>
>> >
>> >
>> > Hope this helps someone else,
>> > -T
>>
>> Apparently this error occurs if you are using
>> customer modules, which I use out the wazoo.
>> ("Wazoo" is American slang for "plentiful")
>>
>>
On 2/14/21 8:27 AM, William Michels via perl6-users wrote:
> 'chmod 777' not 'chmod 755' ?
>
> What are the security implications?
>
> Thx, Bill.
>
> https://linuxhandbook.com/chmod-command/
> <https://linuxhandbook.com/chmod-command/>
Without the write bit in group and general, only
root will be able to write in the directory.
And Raku, when run by a user, would not have access.
When I create it as 2777 -- meaning anyone can take
ownership -- the ownership remained as root.
as root.
Thread Previous