From: jirutka <jirutka@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xbps-src throws an error of unknown trigger
Date: Sun, 11 Jul 2021 00:04:57 +0200 [thread overview]
Message-ID: <20210710220457.8nmx_rn7VDdc4XKxNbG7Iw9sVq6Gr-Rk-z7VhTe19ww@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26717@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
New comment by jirutka on void-packages repository
https://github.com/void-linux/void-packages/issues/26717#issuecomment-877709955
Comment:
I just ran into the same problem.
> This is not supported, it looks up the xbps-triggers package to verify that the trigger exist.
>Deleting all packages from the repository breaks a lot more things like dependency checks.
How can the users create repository for their own templates?
next prev parent reply other threads:[~2021-07-10 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26717@inbox.vuxu.org>
2021-07-10 22:03 ` jirutka
2021-07-10 22:04 ` jirutka [this message]
2021-07-10 22:05 ` jirutka
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=20210710220457.8nmx_rn7VDdc4XKxNbG7Iw9sVq6Gr-Rk-z7VhTe19ww@z \
--to=jirutka@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).