From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Making a devel subpackage: File conflicts
Date: Wed, 18 Nov 2020 09:15:53 +0100 [thread overview]
Message-ID: <20201118081553.5b3ubwBGX7D0x1ZHiJWbcAEgiueLORo3TO8_r4lq2Go@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26474@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/26474#issuecomment-729510983
Comment:
It seems that your `tree-sitter` and `tree-sitter-devel` binary packages contain some identical files. Maybe you added the `devel` subpackage after the first was already created or something like that. I would start again from a clean state:
```
./xbps-src clean tree-sitter
./xbps-src -f pkg tree-sitter
```
Note: you can see the contents of a built package with `xls <name>`
next prev parent reply other threads:[~2020-11-18 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 6:10 [ISSUE] " harrisonthorne
2020-11-18 8:10 ` st3r4g
2020-11-18 8:11 ` st3r4g
2020-11-18 8:11 ` st3r4g
2020-11-18 8:15 ` st3r4g
2020-11-18 8:15 ` st3r4g [this message]
2020-11-18 14:41 ` harrisonthorne
2020-11-18 14:41 ` [ISSUE] [CLOSED] " harrisonthorne
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=20201118081553.5b3ubwBGX7D0x1ZHiJWbcAEgiueLORo3TO8_r4lq2Go@z \
--to=st3r4g@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).