Package Details: edl-git r549.d2c585e-1

Git Clone URL: https://aur.archlinux.org/edl-git.git (read-only, click to copy)
Package Base: edl-git
Description: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools
Upstream URL: https://github.com/bkerler/edl
Keywords: edl firehose flashing qfil qualcomm sahara
Licenses: GPL-3.0
Conflicts: edl
Provides: edl
Submitter: zkm2fw
Maintainer: SelfRef
Last Packager: SelfRef
Votes: 8
Popularity: 0.51
First Submitted: 2022-01-10 10:15 (UTC)
Last Updated: 2024-10-11 00:54 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

dreieck commented on 2023-12-20 16:34 (UTC) (edited on 2023-12-20 16:35 (UTC) by dreieck)

Ahoj,

I recognise that for some reasons "loaders" repository is downloaded both in source retrieval step and in prepare().

makepkg -do:

[...]
==> Retrieving sources...
[...]
  -> Cloning Loaders git repo...
Cloning into bare repository '/tmp/makepkg/sources/Loaders'...
remote: Enumerating objects: 1442, done.
remote: Counting objects: 100% (15/15), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 1442 (delta 5), reused 11 (delta 3), pack-reused 1427
Receiving objects: 100% (1442/1442), 67.57 MiB | 1.09 MiB/s, done.
Resolving deltas: 100% (879/879), done.
[...]
==> Starting prepare()...
Cloning into '/tmp/makepkg/build/edl-git/src/edl/Loaders'...
[↑ this actually creates lots of network traffic again]
Submodule path 'Loaders': checked out 'a83850577f32faaf4694cda8f00666e0d9d34654'
[...]

Is it possible to make the download taking place only once, e.g. in prepare() using the stuff downloaded via the source array?

Regards!

SelfRef commented on 2023-09-23 16:28 (UTC) (edited on 2023-09-23 16:34 (UTC) by SelfRef)

OK guys, I've added the python-exscript as a required dependency. I hope this resolve these issues all together.

Also the strip errors come from stripping process by makepkg. I don't see any mention in documentation how to disable it for some files. So it is what it is.

nilz3000 commented on 2023-09-22 18:58 (UTC) (edited on 2023-09-22 19:01 (UTC) by nilz3000)

Hi @SelfRef, the issue is still present, and yes, I also tested with "makepkg -sC", after I ran into this with yay. The last two commits of this package are affected by this. But as I said, installing python-exscript and building again resolved it. The error message I got is the one @dreieck posted.

dreieck commented on 2023-09-22 17:49 (UTC) (edited on 2023-09-22 18:01 (UTC) by dreieck)

Ahoj,

I also get an error about missing python-exscript:

==> Starting build()...
* Getting build dependencies for wheel...
/usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
!!

        ********************************************************************************
        The license_file parameter is deprecated, use license_files instead.

        By 2023-Oct-30, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  parsed = self.parsers.get(option_name, lambda x: x)(value)
running egg_info
writing edlclient.egg-info/PKG-INFO
writing dependency_links to edlclient.egg-info/dependency_links.txt
writing requirements to edlclient.egg-info/requires.txt
writing top-level names to edlclient.egg-info/top_level.txt
reading manifest file 'edlclient.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'edlclient.egg-info/SOURCES.txt'

ERROR Missing dependencies:
    Exscript
==> ERROR: A failure occurred in build().

I was using makepkg -sfi, non-chroot build, but clean build directory.

namcap shows an Exscript related message in the built package as

edl-git W: Referenced python module 'Exscript.protocols.telnetlib.Telnet' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/edlclient/Tools/boottodwnload', 'usr/bin/sierrakeygen.py', 'usr/bin/enableadb', 'usr/lib/python3.11/site-packages/edlclient/Tools/enableadb', 'usr/lib/python3.11/site-packages/edlclient/Tools/sierrakeygen.py', 'usr/bin/boottodwnload'])

(together with some other python packages) -- interestingly also when python-exscript is installed.

Regards!

SelfRef commented on 2023-09-22 09:09 (UTC)

@nilz3000 That's odd. python-exscript isn't necessary for build process. I cannot reproduce this. Have you tried clean build and using makepkg -s? If you still has this error please post it here.

nilz3000 commented on 2023-09-21 18:45 (UTC) (edited on 2023-09-21 18:49 (UTC) by nilz3000)

Hey @Selfref, the build step fails if python-exscript is not installed. Could you please move it from optdepends to depends. And thanks for keeping this package alive.

SelfRef commented on 2023-09-20 16:28 (UTC) (edited on 2023-09-20 16:28 (UTC) by SelfRef)

Thanks @dreieck. I just updated the PKGBUILD and it now works flawlessly with both makepkg and yay using new PEP 517 install method.

A saw the strip: error: the input file... errors although they look more like warnings. Despite them being printed in output edl-git still contains all loaders listed so this is not a typical issue. Maybe i can resolve this some day but it should not make any difference inside built package.

dreieck commented on 2023-09-20 08:27 (UTC)

Python deprecates direct use of setup.py, consider using python-wheel, python-build, python-installer.

Regards and thanks for maintaining!

dreieck commented on 2023-09-20 08:25 (UTC) (edited on 2023-09-20 08:30 (UTC) by dreieck)

I get some "big fat" warnings during python build:

==> Starting build()...
/usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
!!

        ********************************************************************************
        The license_file parameter is deprecated, use license_files instead.

        By 2023-Oct-30, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  parsed = self.parsers.get(option_name, lambda x: x)(value)
[...]
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'Loaders.GM' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'Loaders.GM' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'Loaders.GM' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'Loaders.GM' to be distributed and are
        already explicitly excluding 'Loaders.GM' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'Loaders.HuaQin' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'Loaders.HuaQin' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        [...]
!!
  check.warn(importable)
[... and a _lot_ of more of this kind. ...]

Regards!

« First ‹ Previous 1 2 3 Next › Last »