Search Criteria
Package Details: python-picamera 1.13-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-picamera.git (read-only, click to copy) |
---|---|
Package Base: | python-picamera |
Description: | pure Python interface to the Raspberry Pi camera module |
Upstream URL: | https://pypi.python.org/pypi/picamera/ |
Licenses: | BSD |
Submitter: | jpike |
Maintainer: | None |
Last Packager: | TrialnError |
Votes: | 2 |
Popularity: | 0.000000 |
First Submitted: | 2015-02-17 01:47 (UTC) |
Last Updated: | 2019-10-21 21:04 (UTC) |
Dependencies (4)
- python (python37AUR, python311AUR, python310AUR)
- raspberrypi-firmware
- python-setuptools (make)
- python-numpy (python-numpy-flameAUR, python-numpy-gitAUR, python-numpy-mkl-binAUR, python-numpy-mkl-tbbAUR, python-numpy-mklAUR, python-numpy1AUR) (optional) – used by array
Required by (2)
- doorpi (optional)
- ethoscope-device (optional)
Latest Comments
1 2 Next › Last »
TrialnError commented on 2024-06-04 21:15 (UTC)
I'm going to drop this.
libcamera
is the current thing, unknown current status and I didn't get around to test this.TrialnError commented on 2023-11-08 22:07 (UTC)
Regarding your ood-message, DragonX256.
I'm somewhat conflicted about this package. Formally it doesn't belong into the aurweb, as it doesn't benefit Arch Linux (aka x86_64 architecture). Therefore I may request to delete this PKGBUILD.
Regarding the question about the replaced
raspberrypi-firmware
package. Althoughraspistill
may not be available anymore, it shouldn't be a problem, as picamera never used this directly. It was using the libraries and those (at least that is the message) are readily available from the vanilla kernel. So it should still work.Does it still work? Not sure, as development is apparantly stalled. Maybe I get around to test this on the weekend.
TrialnError commented on 2019-10-21 20:56 (UTC) (edited on 2019-10-21 20:58 (UTC) by TrialnError)
Thanks for looking into this. First let me say something about the PKGBUILD. The step done in prepare is unnecessary :) If you declare in source a branch, the makepkg branch is based upon this specific branch. So most of the time makepkg == master unless another branch is specified in the source line. Regarding the missing .so. Well, at least it seems there is a need to add the raspberrypi-firmware package to the deps. As the guys only officially support armv7h I'm not surprised, that there isn't a package for the other archs. But you could try to build the raspberrypi-firmware package for aarch64 locally.
And if it is easily possible, I could backport the specific patch which let it build for other architectures
GeorgeRaven commented on 2019-10-21 08:42 (UTC) (edited on 2019-10-21 08:45 (UTC) by GeorgeRaven)
Hey so I created a PKGBUILD to test the git repo and to see if I could solve this issue, which does indeed install:
But on use I.E >> import picamera, it fails with:
Upon investigation on x86_64 (nothing):
on aarch64 (nothing):
on armv7l:
Looks like this shared object is only present in the raspberry pi firmware. Do you know anything about this?
TrialnError commented on 2019-05-29 23:04 (UTC)
Thanks for the info GeorgeRaven. It could be really the case, that picamera only recognizes the official supported arch (armv7h). The whole armv8h isn't really officially supported and since the last update of picamera is quite old, it maybe just cannot check against the 64bit arch.
GeorgeRaven commented on 2019-05-28 19:29 (UTC) (edited on 2019-10-21 08:12 (UTC) by GeorgeRaven)
Hey TrialInError. I will attempt a pure makepkg -si (on aarch64) when I can and append the results to the end of this. However re flashing the RPi with Archlinux Arm ARMv7l (32bit RPi 3B+) instead of aarch64 ARMv8 (on the same pi) it builds fine with pikaur, and makepkg. Lastly I believe the camera may be nonfunctional on the 64 bit os at the raspbian camera specific drivers don't compile for 64 bit, but that still doesn't reveal why it is not recognized as a raspberry pi.
Edit (exactly the same result although more descriptive now):
TrialnError commented on 2019-05-26 21:17 (UTC)
Hello GeorgeRaven. What happens if you use makepkg to build the package? Does it work? And how was pikaur build packages? Does it create a container, or chroot, or something else?
GeorgeRaven commented on 2019-05-25 08:23 (UTC)
Hey, im having the exact same issue on aarch64 raspberry pi 3B+, trying to build using pikaur -S python-picamera:
TrialnError commented on 2018-12-12 22:50 (UTC)
How did you try to build this package? With makepkg or some wrapper like yaourt? Currently I cannot reproduce your issue so maybe the issue is something else.
greyltc commented on 2018-12-05 17:22 (UTC) (edited on 2018-12-05 18:31 (UTC) by greyltc)
raise ValueError('Unable to determine if this system is a Raspberry Pi') in setup.py here any ideas?
(and yes I'm running on a raspberry pi)
1 2 Next › Last »