Hi,
Thanks for your reply!
I understand the issue and I simply switched the symlink for a hardlink, in my
case it doesn't really matter.
I suppose the issue can now be closed but I'm wondering whether some other
people might have the same issue later and whether it can be fixed in some way.
I don't know, your call I guess.
Thanks a lot!
Kate
July 30, 2020 9:11 AM, "Birger Schacht" <bir...@debian.org> wrote:
> Hi Kate,
>
> On 7/30/20 1:03 AM, Kate wrote:
>
>> Package: mako-notifier
>> Version: 1.4.1-1
>>
>> When creating a config file for mako using a symlink, the program fails to
>> run successfully:
>>
>> $ mkdir ~/.config/mako
>> $ touch ~/test-config
>> $ ln -s ~/.confiq/mako/config ~/test-config
>> $ mako
>> Unable to open /home/kit_ty_kate/.config/mako/config for readingFailed to
>> parse config
>
> This is due to the shipped apparmor profile, which only allows access to:
>> owner @{HOME}/.config/mako/config r,
>
> (see /etc/apparmor.d/fr.emersion.Mako line 19)
>
>> However, I tried to compile mako from source
>> https://github.com/emersion/mako.git
>> (https://github.com/emersion/mako) using the same tag (v1.4.1):
>>
>> $ git checkout v1.4.1
>> $ meson build
>> $ ninja -C build
>> $ ./build/mako
>>
>> and the resulting binary ./build/mako works fine. I'm not sure what's going
>> on.
>
> The apparmor profile is only enforced for /usr/bin/mako and not for the
> binary in your build environment. If you copy your built binary to
> /usr/bin/mako it will show the same behaviour.
> If you want your config to be stored somewhere else (for example if you
> want to have your dotfiles in a version control system) you could adapt
> the apparmor profile to allow the path to the symlink target.
>
> cheers,
> Birger
>
>> I'm using Debian Sid, Linux kernel 5.7.10-1, x86_64, libc6 2.31-2
>>
>> Warm regards,
>> Kate
