From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/obsidian-cursors: drop package
Date: Wed, 5 Feb 2025 12:50:10 +0100 [thread overview]
Message-ID: <20250205125010.5927617f@windsurf> (raw)
In-Reply-To: <20250205103042.12955-1-peter@korsgaard.com>
On Wed, 5 Feb 2025 11:30:41 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> Fixes http://autobuild.buildroot.net/results/97ac940d6e279cfa493c6b5d9b4d318d8dda10da/
>
> The tarball is no longer available for direct download as kde-look.org has
> hidden the downloads behind a nag screen, there are no reverse dependencies
> or DEVELOPERS entry for it and the package has not been updated since it was
> added in 2015 by commit ae2faeffb17d ("obsidian-cursors: new package"), so
> drop it.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> Config.in.legacy | 7 +++++++
> package/Config.in | 1 -
> package/obsidian-cursors/Config.in | 6 ------
> package/obsidian-cursors/obsidian-cursors.hash | 2 --
> package/obsidian-cursors/obsidian-cursors.mk | 18 ------------------
> 5 files changed, 7 insertions(+), 27 deletions(-)
> delete mode 100644 package/obsidian-cursors/Config.in
> delete mode 100644 package/obsidian-cursors/obsidian-cursors.hash
> delete mode 100644 package/obsidian-cursors/obsidian-cursors.mk
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-02-05 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 10:30 [Buildroot] [PATCH] package/obsidian-cursors: drop package Peter Korsgaard
2025-02-05 11:50 ` Thomas Petazzoni [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=20250205125010.5927617f@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=peter@korsgaard.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.
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.