GNU bug report logs - #34971
[PATCH] gnu: Add mako.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34971 in the body.
You can then email your comments to 34971 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Meiyo Peng <meiyo <at> riseup.net>
To: guix-patches <at> gnu.org
Cc: Meiyo Peng <meiyo <at> riseup.net>
Subject: [PATCH] gnu: Add mako.
Date: Sun, 24 Mar 2019 14:08:45 +0800

* gnu/packages/wm.scm (mako): New variable.
---
 gnu/packages/wm.scm | 31 ++++++++++++++++++++++++++++++-
 1 file changed, 30 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/wm.scm b/gnu/packages/wm.scm
index 0a05ff4ae4..cc7cd56d66 100644
--- a/gnu/packages/wm.scm
+++ b/gnu/packages/wm.scm
@@ -17,7 +17,7 @@
 ;;; Copyright © 2017 Oleg Pykhalov <go.wigust <at> gmail.com>
 ;;; Copyright © 2018, 2019 Tobias Geerinckx-Rice <me <at> tobias.gr>
 ;;; Copyright © 2018 Pierre-Antoine Rouby <contact <at> parouby.fr>
-;;; Copyright © 2018 Meiyo Peng <meiyo.peng <at> gmail.com>
+;;; Copyright © 2018, 2019 Meiyo Peng <meiyo <at> riseup.net>
 ;;; Copyright © 2019 Rutger Helling <rhelling <at> mykolab.com>
 ;;;
 ;;; This file is part of GNU Guix.
@@ -1228,3 +1228,32 @@ modules for building a Wayland compositor.")
     (synopsis "Screen locking utility for Wayland compositors")
     (description "Swaylock is a screen locking utility for Wayland compositors.")
     (license license:expat))) ; MIT license
+
+(define-public mako
+  (package
+    (name "mako")
+    (version "1.2")
+    (source (origin
+              (method git-fetch)
+              (uri (git-reference
+                    (url "https://github.com/emersion/mako")
+                    (commit (string-append "v" version))))
+              (file-name (git-file-name name version))
+              (sha256
+               (base32
+                "112b7s5bkvwlgsm2kng2vh8mn6wr3a6c7n1arl9adxlghdym449h"))))
+    (build-system meson-build-system)
+    (inputs
+     `(("cairo" ,cairo)
+       ("elogind" ,elogind)
+       ("pango" ,pango)
+       ("wayland" ,wayland)))
+    (native-inputs
+     `(("pkg-config" ,pkg-config)
+       ("scdoc" ,scdoc)
+       ("wayland-protocols" ,wayland-protocols)))
+    (home-page "https://github.com/emersion/mako")
+    (synopsis "Lightweight Wayland notification daemon")
+    (description "@code{mako} is a lightweight notification daemon for
+Wayland.")
+    (license license:expat)))
-- 
2.21.0

Message #8 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Meiyo Peng <meiyo <at> riseup.net>
To: 34971 <at> debbugs.gnu.org
Subject: Re: [PATCH] gnu: Add mako.
Date: Sun, 24 Mar 2019 14:39:35 +0800

Hi everyone,

If you have trouble running mako and mako gives you an error message
like:

#+begin_example
  Failed to connect to user bus: No such file or directory
#+end_example

The problem is caused by that $DBUS_SESSION_BUS_ADDRESS is not set in
your GUI session.  You can start mako with this command:

#+begin_src sh
  dbus-launch --autolaunch=$(dbus-uuidgen --get) mako
#+end_src

I run mako with Sway.  And I put this line in Sway config file:

#+begin_src conf
  exec sh -c 'dbus-launch --autolaunch=$(dbus-uuidgen --get) mako'
#+end_src


--
Meiyo Peng
https://www.pengmeiyu.com/

Message #11 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Meiyo Peng <meiyo <at> riseup.net>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Mon, 25 Mar 2019 11:39:08 +0100

Hello,

Meiyo Peng <meiyo <at> riseup.net> skribis:

> If you have trouble running mako and mako gives you an error message
> like:
>
> #+begin_example
>   Failed to connect to user bus: No such file or directory
> #+end_example

I would expect Mako to automatically spawn the D-Bus user bus if it’s
not already needed, no?  We don’t need to do anything special with other
D-Bus applications AFAIK.

Thanks,
Ludo’.

Message #14 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 34971 <at> debbugs.gnu.org, Meiyo Peng <meiyo <at> riseup.net>
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Mon, 25 Mar 2019 15:35:01 +0100

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hello,
>
> Meiyo Peng <meiyo <at> riseup.net> skribis:
>
>> If you have trouble running mako and mako gives you an error message
>> like:
>>
>> #+begin_example
>>   Failed to connect to user bus: No such file or directory
>> #+end_example
>
> I would expect Mako to automatically spawn the D-Bus user bus if it’s
> not already needed, no?  We don’t need to do anything special with other
> D-Bus applications AFAIK.

When the desktop environment has a D-Bus session daemon, this should
just work.  I suppose using dbus-lauch is necessary in cases where a
minimalist desktop environment is used that does not take steps to
launch/configure the D-Bus daemon.

In that sense I think mako behaves like any other D-Bus application.

-- 
Ricardo

Message #17 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Meiyo Peng <meiyo <at> riseup.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Tue, 26 Mar 2019 00:31:53 +0800

Hi Ludovic,

Ludovic Courtès writes:

> Meiyo Peng <meiyo <at> riseup.net> skribis:
>
>> If you have trouble running mako and mako gives you an error message
>> like:
>>
>> #+begin_example
>>   Failed to connect to user bus: No such file or directory
>> #+end_example
>
> I would expect Mako to automatically spawn the D-Bus user bus if it’s
> not already needed, no?  We don’t need to do anything special with other
> D-Bus applications AFAIK.

Yeah.  I expect that too.  I am not sure why mako is so special.  mako
uses the sd-bus library of systemd/elogind instead of libdbus.  Do you
think that could be the cause?

I don't know much about D-Bus.  Maybe it's just because of mako's bad
program design.  I used dunst as my notification daemon and dunst did
just works.  dunst provides a D-Bus service file.  I don't even have to
manually start dunst.


--
Meiyo Peng

Message #20 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 34971 <at> debbugs.gnu.org, Meiyo Peng <meiyo <at> riseup.net>
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Mon, 25 Mar 2019 22:24:25 +0100

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> Ludovic Courtès <ludo <at> gnu.org> writes:
>
>> Hello,
>>
>> Meiyo Peng <meiyo <at> riseup.net> skribis:
>>
>>> If you have trouble running mako and mako gives you an error message
>>> like:
>>>
>>> #+begin_example
>>>   Failed to connect to user bus: No such file or directory
>>> #+end_example
>>
>> I would expect Mako to automatically spawn the D-Bus user bus if it’s
>> not already needed, no?  We don’t need to do anything special with other
>> D-Bus applications AFAIK.
>
> When the desktop environment has a D-Bus session daemon, this should
> just work.  I suppose using dbus-lauch is necessary in cases where a
> minimalist desktop environment is used that does not take steps to
> launch/configure the D-Bus daemon.

I thought along these lines, but then I use Ratpoison and D-Bus programs
“just work” for me.  There’s no DBUS_SESSION_BUS_whatever environment
variable set for me.  I’m curious!

Ludo’.

Message #23 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Meiyo Peng <meiyo <at> riseup.net>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Wed, 03 Apr 2019 18:02:37 +0200

Hi Meiyo,

Meiyo Peng <meiyo <at> riseup.net> skribis:

> Ludovic Courtès writes:
>
>> Meiyo Peng <meiyo <at> riseup.net> skribis:
>>
>>> If you have trouble running mako and mako gives you an error message
>>> like:
>>>
>>> #+begin_example
>>>   Failed to connect to user bus: No such file or directory
>>> #+end_example
>>
>> I would expect Mako to automatically spawn the D-Bus user bus if it’s
>> not already needed, no?  We don’t need to do anything special with other
>> D-Bus applications AFAIK.
>
> Yeah.  I expect that too.  I am not sure why mako is so special.  mako
> uses the sd-bus library of systemd/elogind instead of libdbus.  Do you
> think that could be the cause?

Could you check with ‘strace’ whether it tries to connect to
/run/dbus/system_bus_socket instead of /var/run/dbus/system_bus_socket?

Thanks,
Ludo’.

Message #26 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Meiyo Peng <meiyo <at> riseup.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Wed, 10 Apr 2019 16:44:21 +0800

Hi Ludovic,

Ludovic Courtès writes:

> Meiyo Peng <meiyo <at> riseup.net> skribis:
>
>> Ludovic Courtès writes:
>>
>>> Meiyo Peng <meiyo <at> riseup.net> skribis:
>>>
>>>> If you have trouble running mako and mako gives you an error message
>>>> like:
>>>>
>>>> #+begin_example
>>>>   Failed to connect to user bus: No such file or directory
>>>> #+end_example
>>>
>>> I would expect Mako to automatically spawn the D-Bus user bus if it’s
>>> not already needed, no?  We don’t need to do anything special with other
>>> D-Bus applications AFAIK.
>>
>> Yeah.  I expect that too.  I am not sure why mako is so special.  mako
>> uses the sd-bus library of systemd/elogind instead of libdbus.  Do you
>> think that could be the cause?
>
> Could you check with ‘strace’ whether it tries to connect to
> /run/dbus/system_bus_socket instead of /var/run/dbus/system_bus_socket?

I get this output from `strace mako`:

#+begin_example
  ...
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  connect(3, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 21) = -1 ENOENT (No such file or directory)
  close(3)                                = 0
  write(2, "Failed to connect to user bus: N"..., 57Failed to connect to user bus: No such file or directory
  ) = 57
  exit_group(1)                           = ?
  +++ exited with 1 +++
#+end_example

It tries to connect to /run/user/1000/bus.

And that error message is from
https://github.com/emersion/mako/blob/master/dbus/dbus.c:

#+begin_src c
  ret = sd_bus_open_user(&state->bus);
  if (ret < 0) {
      fprintf(stderr, "Failed to connect to user bus: %s\n", strerror(-ret));
      goto error;
  }
#+end_src

--
Meiyo Peng
https://www.pengmeiyu.com/

Message #29 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Meiyo Peng <meiyo <at> riseup.net>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Wed, 10 Apr 2019 22:35:00 +0200

Hi,

Meiyo Peng <meiyo <at> riseup.net> skribis:

> I get this output from `strace mako`:
>
> #+begin_example
>   ...
>   socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
>   getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
>   setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
>   getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
>   setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
>   connect(3, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 21) = -1 ENOENT (No such file or directory)

So I’m a bit at loss but what I can say is that /run/user/UID/bus
doesn’t seem to exist in practice.

For example, if I strace “dbus-monitor --session”, I see this:

  connect(3, {sa_family=AF_UNIX, sun_path=@"/tmp/dbus-ktJE8…"}, 23) = 0

I have no idea where this file name comes from but it seems to be
deterministic.

So… more investigation needed!

Ludo’.

Message #32 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Stefanović <stefanx2ovic <at> gmail.com>
To: 34971 <at> debbugs.gnu.org
Cc: Ricardo Wurmus <rekado <at> elephly.net>,
 Ludovic Courtès <ludo <at> gnu.org>, Meiyo Peng <meiyo <at> riseup.net>
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Tue, 23 Apr 2019 12:14:48 +0000

Hello.

AFAIK mako relies on elogind to access user DBus session daemon.

elogind relies on environment variable DBUS_SESSION_BUS_ADDRESS.
In my case DBUS_SESSION_BUS_ADDRESS is set to
"unix:path=/run/user/1000/dbus-1/session_bus_socket".

DBUS_SESSION_BUS_ADDRESS is created by user session manager.
In my case it is set in a shell script by executing:
echo "Starting user DBus session daemon."
dbus-daemon \
  --syslog --fork \
  --address="${DBUS_SESSION_BUS_ADDRESS}" \
  --print-pid --session

This is not perfect solution but it works, for now.

Please take a look at relevant elogind issue:
https://github.com/elogind/elogind/issues/87

Stefan.

Message #35 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Meiyo Peng <meiyo <at> riseup.net>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Tue, 21 May 2019 16:50:51 +0200

Hi Meiyo,

Did you make any progress on this front?

Thanks,
Ludo’.

Ludovic Courtès <ludo <at> gnu.org> skribis:

> Hi,
>
> Meiyo Peng <meiyo <at> riseup.net> skribis:
>
>> I get this output from `strace mako`:
>>
>> #+begin_example
>>   ...
>>   socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
>>   getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
>>   setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
>>   getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
>>   setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
>>   connect(3, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 21) = -1 ENOENT (No such file or directory)
>
> So I’m a bit at loss but what I can say is that /run/user/UID/bus
> doesn’t seem to exist in practice.
>
> For example, if I strace “dbus-monitor --session”, I see this:
>
>   connect(3, {sa_family=AF_UNIX, sun_path=@"/tmp/dbus-ktJE8…"}, 23) = 0
>
> I have no idea where this file name comes from but it seems to be
> deterministic.
>
> So… more investigation needed!
>
> Ludo’.

Message #38 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Meiyo Peng <meiyo <at> riseup.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Thu, 23 May 2019 19:24:27 +0800

Hi Ludovic,

Ludovic Courtès writes:

> Did you make any progress on this front?

I have discussed with the author of mako.  He agreed to add a D-Bus
service file for mako.  That will solve this issue here.  I have tested
it on my computer.  The D-Bus service file will cause mako to be
automatically started when needed.  mako will work out of the box after
installation.  No user action is required.

Link:
1. https://github.com/emersion/mako/issues/155
2. https://github.com/emersion/mako/pull/156

When that pull request is merged, I will send a new package definition
for mako.

> Ludovic Courtès <ludo <at> gnu.org> skribis:
>
>> Hi,
>>
>> Meiyo Peng <meiyo <at> riseup.net> skribis:
>>
>>> I get this output from `strace mako`:
>>>
>>> #+begin_example
>>>   ...
>>>   socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
>>>   getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
>>>   setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
>>>   getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
>>>   setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
>>>   connect(3, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 21) = -1 ENOENT (No such file or directory)
>>
>> So I’m a bit at loss but what I can say is that /run/user/UID/bus
>> doesn’t seem to exist in practice.
>>
>> For example, if I strace “dbus-monitor --session”, I see this:
>>
>>   connect(3, {sa_family=AF_UNIX, sun_path=@"/tmp/dbus-ktJE8…"}, 23) = 0
>>
>> I have no idea where this file name comes from but it seems to be
>> deterministic.
>>
>> So… more investigation needed!
>>
>> Ludo’.


--
Meiyo Peng
https://www.pengmeiyu.com/

Message #41 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Meiyo Peng <meiyo <at> riseup.net>
Cc: 34971 <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH] gnu: Add mako.
Date: Fri, 24 May 2019 17:26:52 +0200

Hi Meiyo,

Meiyo Peng <meiyo <at> riseup.net> skribis:

> I have discussed with the author of mako.  He agreed to add a D-Bus
> service file for mako.  That will solve this issue here.  I have tested
> it on my computer.  The D-Bus service file will cause mako to be
> automatically started when needed.  mako will work out of the box after
> installation.  No user action is required.
>
> Link:
> 1. https://github.com/emersion/mako/issues/155
> 2. https://github.com/emersion/mako/pull/156
>
> When that pull request is merged, I will send a new package definition
> for mako.

Alright, sounds good to me.  Thanks for the update!

Ludo’.

Message #44 received at 34971 <at> debbugs.gnu.org (full text, mbox):

From: Meiyo Peng <meiyo <at> riseup.net>
To: 34971 <at> debbugs.gnu.org
Cc: Meiyo Peng <meiyo <at> riseup.net>
Subject: [PATCH v2] gnu: Add mako.
Date: Wed, 29 May 2019 11:09:24 +0800

* gnu/packages/notification.scm: New file.
* gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
---
 gnu/local.mk                  |  1 +
 gnu/packages/notification.scm | 59 +++++++++++++++++++++++++++++++++++
 2 files changed, 60 insertions(+)
 create mode 100644 gnu/packages/notification.scm

diff --git a/gnu/local.mk b/gnu/local.mk
index 3a199f82f8..fb02c8aa8c 100644
--- a/gnu/local.mk
+++ b/gnu/local.mk
@@ -342,6 +342,7 @@ GNU_SYSTEM_MODULES =				\
   %D%/packages/nim.scm  			\
   %D%/packages/ninja.scm			\
   %D%/packages/node.scm				\
+  %D%/packages/notification.scm			\
   %D%/packages/noweb.scm			\
   %D%/packages/nss.scm				\
   %D%/packages/ntp.scm				\
diff --git a/gnu/packages/notification.scm b/gnu/packages/notification.scm
new file mode 100644
index 0000000000..0e7abb8693
--- /dev/null
+++ b/gnu/packages/notification.scm
@@ -0,0 +1,59 @@
+;;; GNU Guix --- Functional package management for GNU
+;;; Copyright © 2019 Meiyo Peng <meiyo <at> riseup.net>
+;;;
+;;; This file is part of GNU Guix.
+;;;
+;;; GNU Guix is free software; you can redistribute it and/or modify it
+;;; under the terms of the GNU General Public License as published by
+;;; the Free Software Foundation; either version 3 of the License, or (at
+;;; your option) any later version.
+;;;
+;;; GNU Guix is distributed in the hope that it will be useful, but
+;;; WITHOUT ANY WARRANTY; without even the implied warranty of
+;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;;; GNU General Public License for more details.
+;;;
+;;; You should have received a copy of the GNU General Public License
+;;; along with GNU Guix.  If not, see <http://www.gnu.org/licenses/>.
+
+(define-module (gnu packages notification)
+  #:use-module (gnu packages freedesktop)
+  #:use-module (gnu packages gtk)
+  #:use-module (gnu packages man)
+  #:use-module (gnu packages pkg-config)
+  #:use-module (guix build-system meson)
+  #:use-module (guix git-download)
+  #:use-module ((guix licenses) #:prefix license:)
+  #:use-module (guix packages))
+
+(define-public mako
+  (let ((commit "ca8e763f06756136c534b1bbd2e5b536be6b1995")
+        (revision "1"))
+    (package
+      (name "mako")
+      (version (string-append "1.3-" revision "."
+                              (string-take commit 7)))
+      (source (origin
+                (method git-fetch)
+                (uri (git-reference
+                      (url "https://github.com/emersion/mako.git")
+                      (commit commit)))
+                (file-name (git-file-name name version))
+                (sha256
+                 (base32
+                  "1w16n58xj4ncaqjlwczq7i8kpxi05hjp2dqkqhajd9dzk0bd77qy"))))
+      (build-system meson-build-system)
+      (inputs
+       `(("cairo" ,cairo)
+         ("elogind" ,elogind)
+         ("pango" ,pango)
+         ("wayland" ,wayland)
+         ("wayland-protocols" ,wayland-protocols)))
+      (native-inputs
+       `(("pkg-config" ,pkg-config)
+         ("scdoc" ,scdoc)))
+      (home-page "https://github.com/emersion/mako")
+      (synopsis "Lightweight Wayland notification daemon")
+      (description "@code{mako} is a lightweight notification daemon for
+Wayland.")
+      (license license:expat))))
-- 
2.21.0

Message #49 received at 34971-done <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Meiyo Peng <meiyo <at> riseup.net>, 34971-done <at> debbugs.gnu.org
Subject: Re: [bug#34971] [PATCH v2] gnu: Add mako.
Date: Thu, 30 Jan 2020 12:41:02 +0100

[Message part 1 (text/plain, inline)]

Meiyo Peng <meiyo <at> riseup.net> writes:

> * gnu/packages/notification.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.

Looks like Gábor committed a version of this in
46dc940c9af3d8b48966d16e52273ba88e92f946.

Sorry for the duplicate work!

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.