From: Julien Lepiller <julien@lepiller.eu>
To: Yoshinori Arai <kumagusu08@gmail.com>
Cc: 34283-close@debbugs.gnu.org
Subject: bug#34283: [PATCH]Add: mypaint
Date: Fri, 15 Jan 2021 20:50:02 +0100 [thread overview]
Message-ID: <20210115205002.2859508e@tachikoma.lepiller.eu> (raw)
In-Reply-To: <20190202044421.44toqidrwk2f6acn@WaraToNora>
Le Sat, 2 Feb 2019 13:44:21 +0900,
Yoshinori Arai <kumagusu08@gmail.com> a écrit :
> Hello,
>
> I made mypaint package from git version.
> libmypaint-git, mypaint-brushes-git may be conflict with gimp package.
>
Hello Yoshinori,
Sorry for the late reply, it seems this patch has indeed fell into the
cracks :/. In the meantime, someone pushed mypaint 2.0.1 last December.
This situation is really not great for you and I apologize.
Since we now have mypaint in Guix, I think this patch series is
obsolete, so I'm going ahead and closing. Of course, feel free to
re-open if you think that's a mistake.
prev parent reply other threads:[~2021-01-15 19:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 4:44 [bug#34283] [PATCH]Add: mypaint Yoshinori Arai
2019-02-05 5:43 ` swedebugia
2019-02-05 5:52 ` [bug#34283] [PATCH] Add: mypaint Maxim Cournoyer
2019-02-05 9:23 ` Yoshinori Arai
2019-02-05 11:42 ` [bug#34283] [PATCH]Add: mypaint Björn Höfling
2019-02-06 11:03 ` Yoshinori Arai
2019-02-07 11:13 ` Yoshinori Arai
2019-02-10 19:57 ` Danny Milosavljevic
2019-02-10 22:15 ` Yoshinori Arai
2019-02-08 4:26 ` Yoshinori Arai
2019-02-08 4:30 ` Brett Gilio
2019-02-09 22:54 ` Yoshinori Arai
2019-02-10 1:24 ` Brett Gilio
2019-02-10 2:36 ` Yoshinori Arai
2019-02-08 7:22 ` [bug#34283] [PATCH-1/4]Add: mypaint@1.2.1 Yoshinori Arai
2019-06-28 5:34 ` swedebugia
2019-02-08 7:24 ` [bug#34283] [PATCH-2/4]Add: libmypaint@2.0.0-alpha Yoshinori Arai
2019-02-08 7:25 ` [bug#34283] [PATCH-3/4]Add: mypaint-blushes@2.0.1 Yoshinori Arai
2019-02-08 7:27 ` [bug#34283] [PATCH-4/4]Add: mypaint@2.0.0-alpha.2 Yoshinori Arai
2021-01-15 19:50 ` Julien Lepiller [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210115205002.2859508e@tachikoma.lepiller.eu \
--to=julien@lepiller.eu \
--cc=34283-close@debbugs.gnu.org \
--cc=kumagusu08@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).