From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Update LXQT homepages and update compton-conf
Date: Sun, 02 Oct 2022 04:15:43 +0200 [thread overview]
Message-ID: <20221002021543.99o1OeR_4CdDNfyq9u6xF9BS8oeqIZeCPkmFNhV7kFU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34482@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
There's a closed pull request on the void-packages repository
Update LXQT homepages and update compton-conf
https://github.com/void-linux/void-packages/pull/34482
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
The `https://lxqt.org/` and `https://www.lxqt.org/` websites are dead. The LXQT website has moved to `https://lxqt-project.org/`. This PR updates `homepage`s of some packages so that it won't use the dead links.
This PR only changes package metadata (and `compton-conf`), not the package contents, so CI shouldn't be needed. I can reenable it if it will be requested.
I have tested this locally just to be sure and only `compton-conf` didn't compile. It wasn't my PR's fault, it had some dependencies missing, so I have updated it and fixed it. The 0.16.0 is the official last release of `compton-conf`.
#### 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**
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
Edit: enabling CI
prev parent reply other threads:[~2022-10-02 2:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 17:24 [PR PATCH] Update LXQT homepages meator
2021-12-17 16:06 ` Update LXQT homepages and update compton-conf Johnnynator
2021-12-17 16:10 ` Johnnynator
2021-12-17 19:25 ` [PR PATCH] [Updated] " meator
2022-01-05 15:30 ` meator
2022-01-08 15:54 ` meator
2022-01-16 13:34 ` meator
2022-01-16 13:46 ` meator
2022-01-16 13:49 ` [PR PATCH] [Updated] " meator
2022-06-18 2:13 ` github-actions
2022-06-18 9:03 ` [PR PATCH] [Updated] " meator
2022-06-18 9:15 ` meator
2022-09-18 2:15 ` github-actions
2022-10-02 2:15 ` github-actions [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221002021543.99o1OeR_4CdDNfyq9u6xF9BS8oeqIZeCPkmFNhV7kFU@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).