From: r-ricci <r-ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] srcpkgs/*: remove stale symbolic links
Date: Sat, 25 May 2024 00:24:07 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50513@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
There is a new pull request by r-ricci against master on the void-packages repository
https://github.com/r-ricci/void-packages symlinks
https://github.com/void-linux/void-packages/pull/50513
srcpkgs/*: remove stale symbolic links
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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
-->
A patch file from https://github.com/void-linux/void-packages/pull/50513.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-symlinks-50513.patch --]
[-- Type: text/x-diff, Size: 1370 bytes --]
From f175c24724b14263fe899acee3a931a5325b5c8a Mon Sep 17 00:00:00 2001
From: Roberto Ricci <io@r-ricci.it>
Date: Sat, 25 May 2024 00:17:23 +0200
Subject: [PATCH] srcpkgs/*: remove stale symbolic links
---
srcpkgs/kcalcore | 1 -
srcpkgs/kcalcore-devel | 1 -
srcpkgs/kjsembed-devel | 1 -
srcpkgs/kpty-devel | 1 -
4 files changed, 4 deletions(-)
delete mode 120000 srcpkgs/kcalcore
delete mode 120000 srcpkgs/kcalcore-devel
delete mode 120000 srcpkgs/kjsembed-devel
delete mode 120000 srcpkgs/kpty-devel
diff --git a/srcpkgs/kcalcore b/srcpkgs/kcalcore
deleted file mode 120000
index a2e99fc894168b..00000000000000
--- a/srcpkgs/kcalcore
+++ /dev/null
@@ -1 +0,0 @@
-kcalendarcore
\ No newline at end of file
diff --git a/srcpkgs/kcalcore-devel b/srcpkgs/kcalcore-devel
deleted file mode 120000
index a2e99fc894168b..00000000000000
--- a/srcpkgs/kcalcore-devel
+++ /dev/null
@@ -1 +0,0 @@
-kcalendarcore
\ No newline at end of file
diff --git a/srcpkgs/kjsembed-devel b/srcpkgs/kjsembed-devel
deleted file mode 120000
index 0f86a5bd7e8c45..00000000000000
--- a/srcpkgs/kjsembed-devel
+++ /dev/null
@@ -1 +0,0 @@
-kjsembed
\ No newline at end of file
diff --git a/srcpkgs/kpty-devel b/srcpkgs/kpty-devel
deleted file mode 120000
index a58e79c51d6b5d..00000000000000
--- a/srcpkgs/kpty-devel
+++ /dev/null
@@ -1 +0,0 @@
-kpty
\ No newline at end of file
next reply other threads:[~2024-05-24 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 22:24 r-ricci [this message]
2024-05-25 2:36 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50513@inbox.vuxu.org \
--to=r-ricci@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).