public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Cygport: How can I ignore duplicated files in packages
Date: Thu, 15 Sep 2022 21:24:18 +0200	[thread overview]
Message-ID: <87pmfw4f19.fsf@Rainer.invalid> (raw)
In-Reply-To: <22158b5d-ae70-1dd6-611b-0f1df824fa20@hamishmb.com> (Hamish McIntyre-Bhatty's message of "Tue, 13 Sep 2022 11:46:07 +0100")

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.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  parent reply	other threads:[~2022-09-15 19:24 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 [this message]
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=87pmfw4f19.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).