Your message dated Sun, 2 Aug 2020 08:50:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#966516: mako-notifier: Runtime failure when the config
file is a symlink
has caused the Debian Bug report #966516,
regarding mako-notifier: Runtime failure when the config file is a symlink
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
966516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966516
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
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.
I'm using Debian Sid, Linux kernel 5.7.10-1, x86_64, libc6 2.31-2
Warm regards,
Kate
--- End Message ---
--- Begin Message ---
Hi,
On 7/30/20 4:31 PM, Kate wrote:
> 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.
Great!
> I suppose the issue can now be closed
I think so too, thus closing the bug report.
> 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.
We will see. The bug report will still be listed, so people can find it.
If there are more people having that issue, we might want to talk with
upstream about loosening the apparmor config. But I think thats actually
not a problem which is mako specific.
cheers,
Birger
>
> Thanks a lot!
> Kate
>
> July 30, 2020 9:11 AM, "Birger Schacht" <[email protected]> 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
>
--- End Message ---
