Arch Linux User Repository

There was no harassment involved.

I wanted to make sure if the package gets further maintained or not. This wasn't clear to me as waiting for upstream to release something more appealing is IMO no reason to postpone a simple version upgrade for two weeks.

I understand that right now the situation with the python2 dependencies is not optimal, but they are all still maintained.

When the time comes and these dependencies are gone from the AUR, the daily builds are probably already on the python3 branch, which is actively maintained by upstream.

I orphaned the packaged because 0b100100 wouldn't stop harassing me via email long enough to let me get any meaningful work done, over the main holiday season of the year, when everyone is busy with not being on the PC.

Hi dhtseany, Thank you for stepping in as the new maintainer. What speaks against the daily builds? Will they be dropped by upstream?

The non-flatpak version still compiles on Arch, so I don't see a reason to wait until something changes upstream. Furthermore, if the package does not get updated it will end up as an orphan again.

The following PKGBUILD file is what I have come up with (newest version with some cleanup done): http://ix.io/3HVJ

FYI: The python3 branch of chirp (directly cloned from the mercurial repository) is already on AUR [1]

[1] https://aur.archlinux.org/packages/chirp-hg-py3/

edit: added some further info

Hi everyone, I just took ownership of this package since I've been actively following along with development of the py3 version of chirp. For the time being the unpopular but technically functional flatpak version works with installation instructions provided in another recent comment I made. In the mean time I'd appreciate your patience while we wait for upstream to release something that I would at least consider a beta level product. Once there's something to maintain I'll be happy to have co-maintainers help me out but for right now there's not much help needed.

Hi ashleyr, Thank you for maintaining this great package until now. I would be delighted to jump in as a (co-)maintainer.

@davvore33: Can be fixed by rebuilding python2-gobject2 against the newest libffi package as the libffi.so.7 compat library got removed from libffi.

Probably can be fixed if you install libffi7 package.

freshly installed Traceback (most recent call last): File "/usr/bin/chirpw", line 131, in <module> from chirp.ui import mainapp File "/usr/lib/python2.7/site-packages/chirp/ui/mainapp.py", line 26, in <module> import gtk File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 30, in <module> import gobject as _gobject File "/usr/lib/python2.7/site-packages/gobject/__init__.py", line 47, in <module> from gobject.constants import * File "/usr/lib/python2.7/site-packages/gobject/constants.py", line 24, in <module> import gobject._gobject ImportError: libffi.so.7: cannot open shared object file: No such file or directory

might be a problem with python2

Hi Everyone,

I am no longer able to make any progress on keeping chirp up to date for a number of reasons. Not the least of which is I no longer can run it on my installation due to Python2 being deprecated.

Therefore I'm going to disown the package, and hope that someone else can take it on.

73's. Ash.

@max_meyer I don't have the ability to verify that the build works as I have no python2 packages any longer.

I've updated the PKGBUILD after verifying the version and hash match, however there is no solution yet from upstream to support python3.

I'm happy to keep bumping the build along if people let me know, but there is little I can do to verify it.