public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: CI system cryptic error
Date: Thu, 20 Jan 2022 15:50:15 +0000	[thread overview]
Message-ID: <DB3PR0202MB35613247524BC9B577560FF5E75A9@DB3PR0202MB3561.eurprd02.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

Hi there,

Recently, I created a test package for python-imaging, and the CI system 
gave a build error that I didn't see locally:

*** ERROR: unknown wheel filename.

This only occurred for the Python 3.8 build (3.6 and 3.7 are 
unaffected). Considering some of the library name changes between these 
versions, is it possible that this is a bug in the CI tool setup or in 
cygport?

Attached is the offending cygport file that caused the error.

Hamish

[-- Attachment #2: python-imaging.cygport --]
[-- Type: text/plain, Size: 4442 bytes --]

ORIG_PN="Pillow"
PYTHON_WHEEL_VERSIONS="3.6:3.7:3.8:3.9"
inherit python-wheel

NAME="python-imaging"
VERSION=8.4.0
RELEASE=1
CATEGORY="Python"
SUMMARY="Python Imaging Library"
DESCRIPTION="The Python Imaging Library (PIL) adds image processing capabilities
to your Python interpreter. This library supports many file formats, and provides
powerful image processing and graphics capabilities."
HOMEPAGE="https://python-pillow.github.io/"

SRC_URI="https://files.pythonhosted.org/packages/7d/2a/2fc11b54e2742db06297f7fa7f420a0e3069fdcf0e4b57dfec33f0b08622/Pillow-8.4.0.tar.gz"
SRC_DIR="Pillow-${VERSION}"
PATCH_URI=""

BUILD_REQUIRES="libjpeg-devel libjpeg8 zlib-devel zlib0 libtiff-devel libtiff6 libfreetype-devel libfreetype6 liblcms2-devel lcms2 libwebp libwebp-devel tcl-devel tcl libimagequant-devel libimagequant0 libraqm-devel libraqm0 libX11-xcb-devel libX11-xcb1 libxcb-devel libxcb1 python36 python36-devel python36-setuptools python36-wheel python36-pip python36-olefile python37 python37-devel python37-setuptools python37-wheel python37-pip python37-olefile python38 python38-devel python38-setuptools python38-wheel python38-pip python38-olefile python39 python39-devel python39-setuptools python39-wheel python39-pip python39-olefile"

DIFF_EXCLUDES="build"

src_test() {
	cd ${B}
	for v in ${PYTHON_WHEEL_VERSIONS//:/ }
	do
		echo PYTHONPATH="${B}/build/lib.cygwin-$(uname -r | sed -e 's|s*(.*||')-$(uname -m)-$v"
		PYTHONPATH="${B}/build/lib.cygwin-$(uname -r | sed -e 's|s*(.*||')-$(uname -m)-$v" \
		python$v selftest.py
	done
}

PKG_NAMES=" python36-imaging python36-imaging-tk"
PKG_NAMES+=" python37-imaging python37-imaging-tk"
PKG_NAMES+=" python38-imaging python38-imaging-tk"
PKG_NAMES+=" python39-imaging python39-imaging-tk"

# ImageQt no longer imports PyQt or PySide, but simply integrates with
# whatever has already been imported.  Therefore there is no need to
# break it out separately, as it has no hard dependencies of its own.
python36_imaging_REQUIRES="python36 python36-olefile"
python36_imaging_OBSOLETES+=" python3-imaging-devel python3-imaging-qt"
python36_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python36_imaging_CONTENTS}
"
python36_imaging_tk_OBSOLETES="python3-imaging-tk"
python36_imaging_tk_REQUIRES="python36-imaging python36-tkinter"
python36_imaging_tk_CONTENTS="
	usr/lib/python3.6/site-packages/PIL/_imagingtk*
	usr/lib/python3.6/site-packages/PIL/ImageTk*
	usr/lib/python3.6/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.6/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.6/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python37_imaging_REQUIRES="python37 python37-olefile"
python37_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python37_imaging_CONTENTS}
"
python37_imaging_tk_REQUIRES="python37-imaging python37-tkinter"
python37_imaging_tk_CONTENTS="
	usr/lib/python3.7/site-packages/PIL/_imagingtk*
	usr/lib/python3.7/site-packages/PIL/ImageTk*
	usr/lib/python3.7/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.7/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.7/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python38_imaging_REQUIRES="python38 python38-olefile"
python38_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python38_imaging_CONTENTS}
"
python38_imaging_tk_REQUIRES="python38-imaging python38-tkinter"
python38_imaging_tk_CONTENTS="
	usr/lib/python3.8/site-packages/PIL/_imagingtk*
	usr/lib/python3.8/site-packages/PIL/ImageTk*
	usr/lib/python3.8/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.8/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.8/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python39_imaging_REQUIRES="python39 python39-olefile"
python39_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python39_imaging_CONTENTS}
"
python39_imaging_tk_REQUIRES="python39-imaging python39-tkinter"
python39_imaging_tk_CONTENTS="
	usr/lib/python3.9/site-packages/PIL/_imagingtk*
	usr/lib/python3.9/site-packages/PIL/ImageTk*
	usr/lib/python3.9/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.9/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.9/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python_imaging_debuginfo_OBSOLETES="python3-imaging-debuginfo"
PKG_IGNORE="usr/share/doc/python*-imaging-*/"

             reply	other threads:[~2022-01-20 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 15:50 Hamish McIntyre-Bhatty [this message]
2022-01-21 14:06 ` Jon Turney
2022-01-21 16:03   ` Hamish McIntyre-Bhatty
2022-01-22  5:34     ` Marco Atzeri
2022-01-22 12:11       ` 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=DB3PR0202MB35613247524BC9B577560FF5E75A9@DB3PR0202MB3561.eurprd02.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --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).