From: Hamish McIntyre-Bhatty <cygwin@hamishmb.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Cygport: How can I ignore duplicated files in packages
Date: Tue, 13 Sep 2022 11:46:07 +0100 [thread overview]
Message-ID: <22158b5d-ae70-1dd6-611b-0f1df824fa20@hamishmb.com> (raw)
Hi there,
Today I'm attempting to update my python-imaging package, but I'm now
finding that cygport has made the warning about duplicated files an error.
The source is at: https://gitlab.com/hamishmb/cygwin-python-imaging
Files are duplicated in these packages because there are .py files for
each python release in /usr/lib/python3.*.
This doesn't seem to actually break package creation, but I'd like to
get this reproducing correctly in scallywag, which I think will flag as
failed because of this error.
I'm not sure whether this indicates that I'm packaging things the wrong
way. If so, I'd be happy to learn how to improve my packages.
Hamish
next reply other threads:[~2022-09-13 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:46 Hamish McIntyre-Bhatty [this message]
2022-09-15 17:45 ` Jon Turney
2022-09-15 19:24 ` Achim Gratz
2022-09-25 11:14 ` Hamish McIntyre-Bhatty
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=22158b5d-ae70-1dd6-611b-0f1df824fa20@hamishmb.com \
--to=cygwin@hamishmb.com \
--cc=cygwin-apps@cygwin.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).