Github messages for voidlinux
 help / color / mirror / Atom feed
From: anubhavkini <anubhavkini@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] mako problems on systems without elogind
Date: Sun, 09 May 2021 06:37:47 +0200	[thread overview]
Message-ID: <20210509043747.KD-60r1eUBQlxs8HF_JAc_nUyeO9ynDZwzndQrrEnL8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30428@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

Closed issue by anubhavkini on void-packages repository

https://github.com/void-linux/void-packages/issues/30428

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  `Void 5.11.15_1 x86_64 GenuineIntel notuptodate rrFFFF`
* package:  
  `mako-1.4.1_1`

### Expected behavior
`makoctl reload` should reload the mako config file.
### Actual behavior
```
$ makoctl reload
/bin/makoctl: 19: busctl: not found
```
### Steps to reproduce the behavior
* Install `mako` without `elogind` and run it.
* Run `makoctl reload`.
### Other
`mako` can now be built with [basu](https://github.com/emersion/basu) instead of  elogind
https://github.com/emersion/mako/commit/805663cc76e0a58dc67c60b0df43170d5e489615
maybe we can have `mako-basu` for systems without elogind

      parent reply	other threads:[~2021-05-09  4:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 17:35 [ISSUE] " itsanubhavkini
2021-04-22 18:10 ` ericonr
2021-04-22 18:14 ` st3r4g
2021-04-22 18:14 ` st3r4g
2021-04-22 21:06 ` FollieHiyuki
2021-05-04  3:50 ` itsanubhavkini
2021-05-09  4:37 ` anubhavkini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210509043747.KD-60r1eUBQlxs8HF_JAc_nUyeO9ynDZwzndQrrEnL8@z \
    --to=anubhavkini@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).