Package Details: python-logfury 1.0.1-2

Git Clone URL: (read-only, click to copy)
Package Base: python-logfury
Description: Responsible, low-boilerplate logging of method calls for python libraries
Upstream URL:
Licenses: BSD
Submitter: jarondl
Maintainer: 2bluesc
Last Packager: 2bluesc
Votes: 2
Popularity: 0.045986
First Submitted: 2019-02-23 15:49
Last Updated: 2022-01-10 17:00

Latest Comments

2bluesc commented on 2022-01-10 17:05

@njhanley Thanks for the heads-up.

I've updated the package and disabled the test as well as fixing adding a commented out checkdepends() for those who might want to check in the future.

Apparently running the tests causes more problems then it's worth.

LMK if there's anything else that should be tweaked.

njhanley commented on 2022-01-07 05:51

@Kage-Yami I think you're running into an issue with the developer's CI setup. is configured not to create a venv if the environment variable CI is set, leading pip to perform a user install outside of PATH.

The wiki warns that running tox in a check function is basically useless and I'd think the same applies to nox. Maybe it should be removed?

As an aside, python-nox and python-coverage should be checkdepends, not makedepends.

Kage-Yami commented on 2021-12-26 08:04

Looks like this is failing to build for me (specifically the check phase). I'm not too familiar with Python, so I could be misinterpreting the logs, but I think pip is downloading python-pytest (as it's not specified in this package's makedepends, and then nox is trying to use it, but pip doesn't install it into PATH, so it can't be found.

So my guess is that this issue can be resolved by adding python-pytest to the makedepends (as it would then be in the PATH once installed, right?)

Full logs are here:

2bluesc commented on 2021-12-08 17:41

@Subject-17 Builds fine in my clean chroot and on my host machine. Chroot command:

$ makechrootpkg -c -r $CHROOT

Try setting up a chroot to see if that works. If it does I suspect there's something wrong with your environment.

Let me know if you find anything as I can't reproduce the failure.

Subject-17 commented on 2021-12-08 00:46

Hey, I'm getting the following issues when attempting to upgrade this package

 nox > Running session test-3.9
 nox > Creating virtual environment (virtualenv) using python3.9 in      .nox/test-3-9
 nox > Command /usr/bin/python -m virtualenv /tmp/makepkg/python-logfury     /src/logfury-1.0.1/.nox/test-3-9 -p python3.9 failed with exit code 1:
 ModuleNotFoundError: No module named 'virtualenv.activation.nushell'

I've reinstalled all dependencies of python-logfury (as per PKGBUILD) just in case. Is there perhaps another dependency I'd need to install?

2bluesc commented on 2021-11-17 16:16

Ping @jarondl, anything I can do to help to move this along? Flagged out of date 2021-11-05 and I provided patches to get it up to speed 4 days ago.

Could you add me as a co-maintainer to help update this 2.5 year old package so I can update dependent packages?

2bluesc commented on 2021-11-13 02:38

@jarondl can you please update this package? I've put together a patch that you can apply.

This patch was tested against python-b2sdk and backblaze-b2 packages I maintain which this package is currently blocking from upgrading.

Patch to update to v1.0.1:

jarondl commented on 2019-03-02 15:44

moved the license file. Thanks wlritchi@

wlritchi commented on 2019-02-26 07:54

This package installs the license file to /usr/share/licenses/python2-logfury/ instead of the correct /usr/share/licenses/python-logfury/ (note the 2). Maybe worth just using the $pkgname variable to minimize copy-paste errors?