From: Fatima Toothpaste via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>, ludo@gnu.org
Cc: 54273@debbugs.gnu.org
Subject: [bug#54273] [PATCH V2] gnu : nicotine+: Update to 3.2.1.
Date: Mon, 14 Mar 2022 00:45:03 +0900 [thread overview]
Message-ID: <d37bcc37-ec84-8753-4138-46d03d2c6621@disroot.org> (raw)
In-Reply-To: <c4ce5882f2c171e6316b2b6be2735794eaff5709.camel@telenet.be>
Sorry, I forgot to lint. By the way, I also included some optional
dependencies on new patch, which i excluded on purpose before.
gspell: spell checking doesn't work on my machine. However, gtk and
gspell both are loaded with pygobject, and gtk works fine. so it might
be the problem of nicotine+, or might work on other environment.
libappindicator: i excluded it because i heard it is unmaintained and
should be replaced with libayatana-appindicator. But, still though there
are some packages depend on libappindicator in guix. So, Just using
libappindicator for a now and replacing it all together with
libayatana-appindicator someday doesn't seems so bad to me, What do you
think?
next prev parent reply other threads:[~2022-03-13 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 5:45 [bug#54273] [PATCH] gnu: nicotine+: update to 3.2.1 Fatima Toothpaste via Guix-patches via
2022-03-11 22:11 ` Ludovic Courtès
2022-03-13 1:14 ` Fatima Toothpaste via Guix-patches via
2022-03-12 13:59 ` [bug#54273] [PATCH V2] gnu : nicotine+: Update " Fatima Toothpaste via Guix-patches via
2022-03-13 1:14 ` Fatima Toothpaste via Guix-patches via
2022-03-13 11:06 ` Maxime Devos
2022-03-13 15:45 ` Fatima Toothpaste via Guix-patches via [this message]
2022-03-13 15:41 ` [bug#54273] [PATCH V3] " Fatima Toothpaste via Guix-patches via
2022-03-15 9:52 ` bug#54273: [PATCH] gnu: nicotine+: update " Ludovic Courtès
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=d37bcc37-ec84-8753-4138-46d03d2c6621@disroot.org \
--to=guix-patches@gnu.org \
--cc=54273@debbugs.gnu.org \
--cc=fatimatoothpaste@disroot.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.