From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] Ayatana indicators
Date: Tue, 15 Feb 2022 22:03:30 +0100 [thread overview]
Message-ID: <20220215210330.A3GtRqBG-6YoHbSH1wCGGVT8OvW-EPLb-xkWj7H4-7s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35135@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
There's a closed pull request on the void-packages repository
[RFC] Ayatana indicators
https://github.com/void-linux/void-packages/pull/35135
Description:
`libappindicator` hasn't seen a release since 2012 (almost 10 years!)
Debian has removed it in buster and switched to [libayatana-appindicator](https://ayatanaindicators.github.io/).
This PR is intended to prepare void linux for it. Let me know what you think...
I successfully built and tested all changed packages.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
next prev parent reply other threads:[~2022-02-15 21:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 15:34 [PR PATCH] " tibequadorian
2022-01-21 14:55 ` [RFC] " ericonr
2022-01-21 22:18 ` tibequadorian
2022-01-21 22:31 ` tibequadorian
2022-01-28 22:31 ` [PR PATCH] [Updated] " tibequadorian
2022-01-28 22:57 ` tibequadorian
2022-02-15 21:03 ` tibequadorian [this message]
2022-02-18 3:48 ` ericonr
2022-02-18 3:49 ` ericonr
2022-02-18 9:17 ` tibequadorian
2022-03-05 20:17 ` tibequadorian
2022-10-21 0:42 ` paper42
2022-11-25 0:51 ` tibequadorian
2022-11-25 15:52 ` paper42
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=20220215210330.A3GtRqBG-6YoHbSH1wCGGVT8OvW-EPLb-xkWj7H4-7s@z \
--to=tibequadorian@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).