From: Hamish McIntyre-Bhatty <cygwin@hamishmb.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Cygport: How can I ignore duplicated files in packages
Date: Sun, 25 Sep 2022 12:14:08 +0100 [thread overview]
Message-ID: <632956e0-2ad0-7205-0187-021ef43b517d@hamishmb.com> (raw)
In-Reply-To: <87pmfw4f19.fsf@Rainer.invalid>
On 15/09/2022 20:24, Achim Gratz wrote:
> Hamish McIntyre-Bhatty writes:
>> 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.
>
> I don't think anything has changed there lately?
>
>> 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.*.
>
> A duplicate is a file that shows up at exactly the same path in more
> than one package. These files don't fit that description as files with
> the same name are in separate paths, so what is the actual problem?
>
>> 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 think you create it yourself here (and analogous for the other Python
> versions):
>
> --8<---------------cut here---------------start------------->8---
> python36_imaging_CONTENTS="
> --exclude=_imagingtk*
> --exclude=ImageTk*
> --exclude=SpiderImagePlugin*
> ${python36_imaging_CONTENTS}
> "
> --8<---------------cut here---------------end--------------->8---
>
> which seems to package the same files twice in one archive when
> expanded.
>
>
> Regards,
> Achim.
Ah right, okay. I'll see if I can get that fixed. It's strange, because
I haven't changed this since the last build which didn't have any issues
at all, but I'll give it another shot.
Hamish
prev parent reply other threads:[~2022-09-25 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:46 Hamish McIntyre-Bhatty
2022-09-15 17:45 ` Jon Turney
2022-09-15 19:24 ` Achim Gratz
2022-09-25 11:14 ` Hamish McIntyre-Bhatty [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=632956e0-2ad0-7205-0187-021ef43b517d@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).