Package Details: python-dukpy 0.5.0-1

Git Clone URL: https://aur.archlinux.org/python-dukpy.git (read-only, click to copy)
Package Base: python-dukpy
Description: Python bindings for the duktape embeddable JavaScript engine
Upstream URL: https://github.com/amol-/dukpy
Licenses: MIT
Submitter: jelly
Maintainer: matthewq337 (micwoj92)
Last Packager: micwoj92
Votes: 2
Popularity: 0.091726
First Submitted: 2022-06-30 19:05 (UTC)
Last Updated: 2024-11-13 01:37 (UTC)

Dependencies (2)

Sources (1)

Latest Comments

micwoj92 commented on 2024-07-16 17:49 (UTC)

Point 1: There is package_python-dukpy which is remnant of when this split package. If the tool you are using to build packages in clean chroot does not support this, then it is issue of the tool and not of the package. I always build using makechrootpkg and it works.

Point 2: No, it is not "definitely wrong" In your first comment you mentioned ${pkgdir} and not you mentioned ${srcdir}. I think I get what you mean now

In the past it was not the case, but as of "few years"(I don't know exactly when) the functions (with exeption of verify()) already "start" in $srcdir. You can check this with this minimal example:

pkgname=qwertyuiop
pkgver=1
pkgrel=1
arch=('any')

prepare() {
pwd
cd $srcdir
pwd
}
verify() {
pwd
cd $srcdir
pwd
}
build() {
pwd
cd $srcdir
pwd
}
check() {
pwd
cd $srcdir
pwd
}
package() {
pwd
cd $srcdir
pwd
}

daniel_shub commented on 2024-07-16 00:29 (UTC)

It still does not build in a clean chroot for me. It is missing a package function and 'cd dukpy-${pkgver}' is definitely wrong and likely should be 'cd "${srcdir}/dukpy-${pkgver}"'

Have you seen https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

micwoj92 commented on 2024-07-14 19:21 (UTC)

Fixed. I don't understand what you mean by "line 23 at a minimum needs to be referenced to ${pkgdir}".

daniel_shub commented on 2024-07-14 19:14 (UTC)

This does not build in a clean chroot for me. I am pretty sure that the pkgname variable needs to be set (probably just uncomment line 4) and line 23 at a minimum needs to be referenced to ${pkgdir}

micwoj92 commented on 2024-07-08 23:53 (UTC)

This is not proper way to do this. pip is definitely not needed to build, this issue was due to missing python-mutf8 checkdependency. Now that you have deleted check, this issue is no longer present.

micwoj92 commented on 2024-07-08 21:07 (UTC)

Check fails:

==> Starting check()...
running test
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
/usr/lib/python3.12/site-packages/setuptools/command/test.py:193: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************

!!
  ir_d = dist.fetch_build_eggs(dist.install_requires)
WARNING: The wheel package is not available.
/usr/bin/python: No module named pip
error: Command '['/usr/bin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpv86ka41b', '--quiet', 'mutf8']' returned non-zero exit status 1.
==> ERROR: A failure occurred in check().
    Aborting...