From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: compton-conf: remove package
Date: Thu, 27 Oct 2022 04:13:37 +0200 [thread overview]
Message-ID: <20221027021337.Ked1Ab3GYBxF7BYiBD07vAMb9s1ZbqVX-ZkiJOkZZKw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36034@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
There's a closed pull request on the void-packages repository
compton-conf: remove package
https://github.com/void-linux/void-packages/pull/36034
Description:
Not usable because compton was replaced by picom and this program writes outdated values into a wrong configuration file.
On https://github.com/lxqt/compton-conf it also says, that it will receive no further updates and should be considered deprecated.
Another possibility is to use this fork: https://github.com/redtide/picom-conf? Unfortunately, this doesn't have a release yet.
<!-- 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**|**NO**
-->
<!-- 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-10-27 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 11:36 [PR PATCH] " tibequadorian
2022-03-20 22:11 ` paper42
2022-03-20 22:17 ` [PR PATCH] [Updated] " tibequadorian
2022-03-20 22:17 ` tibequadorian
2022-06-28 2:15 ` github-actions
2022-07-12 2:16 ` [PR PATCH] [Closed]: " github-actions
2022-07-12 2:29 ` classabbyamp
2022-10-12 2:14 ` github-actions
2022-10-27 2:13 ` github-actions [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-26 17:34 [PR PATCH] " ardadem
2021-07-27 7:51 ` [PR PATCH] [Closed]: " ardadem
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=20221027021337.Ked1Ab3GYBxF7BYiBD07vAMb9s1ZbqVX-ZkiJOkZZKw@z \
--to=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).