Hello @francesco.ceruti:matrix.org, how would I go about building a distro rpm package of lisp 0.6.0-dev? as far as I can see the install process via poetry etc. targets the user's home and virtual env, I have no experience in packaging python apps, is there a way to end up with a binary below /usr and using distro packages instead PyPi for build dependencies? there is python3-poetry available in openSUSE, so that's a start :)
I ask because there is an initiative to create a more official (than before) community project for proaudio currently, to bundle efforts and packages in one place instead spread across several repos, partially by SUSE, partially by 3rd party users
And I've been invited to take part in that, as I created and maintain a bunch of rpms during the last 15 years or so
So what I am missing is basically whether there is a way to install to usr/ or I have to find myself which files would have to go where in the filesystem, after all python packaging (at least how you do it) seems different from usual C++ etc. applications with make/cmake/whatever, in that regard
I just fired off my questions, have to go and will read any answers later when back at home, or meanwhile on my smartphone :)
Just so you know, downloading during build is no option in OBS (Open Build Service), so any build dep would have to be packaged too, or included as submodule in your git tree
bye and thanks
@edogawa23: Interesting :) So, packaging python apps it's a "complicated" topic. The standard way is is to install your packages (apps or libs) in a folder (site-packages) within the python installation, for example
For the develop branch what you can do is to use
If you need a full list of all the required python packages, you can look into the
to get a classic requirements.txt file.
/usr/lib/python3.10/site-packages, dependencies should be installed as separated packages. This may depends on the distro, Debian use a different folder to avoid conflicts between pip and their packages.For the develop branch what you can do is to use
pip install . --no-deps --root ./build --ignore-installed to get the files you need, without dependencies, those should be packaged separately, but I'll suggest to look how it's done by other python packages for the target distro.If you need a full list of all the required python packages, you can look into the
poetry.lock file, or use poetry exportto get a classic requirements.txt file.
but will go slow as my main job needs my time this week, going on tour with a theater piece
I've got all the build dependencies as distro packages now, except typing-extensions==4.0.1, having python38-typing_extensions 3.10.0.2 - tried to update this package but the updated rpm doesn't build for some reason i can't spend time on now (setup.py missing, thus the build magic via python rpm macros doesn't work)
is there a reason in code to ask for minimum version 4.0.1?
er, exact version that is
mmh, it's not a direct dependency, the minimum required version is 3.6.4
I'll leve here the output of
poetry show --no-dev --tree which might be more helpful than looking at the raw lockfileappdirs 1.4.4 A small Python module for determining appropriate platform-specific dirs, e.g. a "user data dir".
cython 0.29.28 The Cython compiler for writing C extensions for the Python language.
falcon 3.0.1 An unladen web framework for building APIs and app backends.
humanize 3.14.0 Python humanize utilities
└── importlib-metadata *
├── typing-extensions >=3.6.4
└── zipp >=0.5
jack-client 0.5.3 JACK Audio Connection Kit (JACK) Client for Python
└── cffi >=1.0
└── pycparser *
mido 1.2.10 MIDI Objects for Python
pyalsa 1.2.6 Python binding for the ALSA library.
pygobject 3.42.0 Python bindings for GObject Introspection
└── pycairo >=1.16,<2.0
pyliblo 0.10.0 Python bindings for the liblo OSC library
pyqt5 5.15.6 Python bindings for the Qt cross platform application toolkit
├── pyqt5-qt5 >=5.15.2
└── pyqt5-sip >=12.8,<13
python-rtmidi 1.4.9 A Python binding for the RtMidi C++ library implemented using Cython.
requests 2.27.1 Python HTTP for Humans.
├── certifi >=2017.4.17
├── charset-normalizer >=2.0.0,<2.1.0
├── idna >=2.5,<4
└── urllib3 >=1.21.1,<1.27
sortedcontainers 2.4.0 Sorted Containers -- Sorted List, Sorted Dict, Sorted Set
I think I got it working now https://build.opensuse.org/package/show/home:edogawa/linux-show-player
going to install and test
nice i just discovered countdown mode in cart layout
I'd like to use LiSP with a midi/usb foot controller but it doesn't capture it ! I've tried two of them : midi mouse tech21 and Blackstar live logic. In the midi preferences I can connect them but when I try to capture it in the midi controls of the cue it doesn't match. I can only use it with my akai mpk mini. Any tips for that or foot controller available ?
Debian/Mate and LiSP 0.5.1. So, double-click in the cue and in cue control > midi controls when I start "capture" a usb foot controller, no notes adding in "type-channel-note-action" when I trigger the foot controller. But it works with my akai mpk mini. But I need to use a foot controller because I'm guitarist and my hands are occupied. I try to see with qmidiroute if I can change something. If you can find why I can't capture any foot controller you'll be awesome ! I'm not particularly noob or expert but between the two
Hi, sorry for not replaying earlier. The 0.5.x versions support only "notes" On/Off as cue triggers, maybe the foot controllers send a different kind of messages? I'm not familiar with them, but from the "tech21" manual it seems like only "program change" messages are sent
Yes, you should be able change the message type with qmidiroute
I had forgotten to add runtime requirements to the spec file they get calculated for C++ packages but not so for python obviously), and realized only yesterday when trying on the freshly set up RPi4
I pushed my package up to GeekosDAW (multimedia:proaudio) repositories which I am part of/helping to maintain now
@francesco.ceruti:matrix.org if you'd like to add a permanent link to your web page, this would be a candidate https://software.opensuse.org/download/package?package=linux-show-player&project=multimedia%3Aproaudio
@SouthernHauler_twitter: Hi! You need to use the "experimental" version to get OSC support, an easy way is to use the flatpak that you can find here: https://www.linux-show-player.org/download.html
@SouthernHauler_twitter: Hi, sorry for the delay. I've searched about the issue and apparently it doesn't work, and cannot work, unless you use pipewire-jack, even in that case I think I need to make some adjustments to the flatpak build.
Hi! I'm using the Debian testing repository's deb-Package of Linux-show-player. Seems a bit out of date. And it shows 0.5.1 as the version number, allthough apt claims to use the 0.5.2 version. But that's not the point… I changed to pipewire on my Thinkpad T410 and Thinkpad T530 and on both machines I can't get them to work using Linux-Show-Player with jackd output (the cue can be started but it stays at 0:00). Other jackd apps are working okay. AND LiSP works using the pulseaudio output, but - you know - jackd's better when using complex output wiring or trying to use LV2-plugins.
As I read in this chat there were other people having the same or similar issues. So, I don't want to report it, but I want to know if this is already fixed in the development branch, if there is a release with the fix immanent and - if there's something, you can do about it - when it will finally reach Debian testing… Greets and thanks for the cool stuff!
As I read in this chat there were other people having the same or similar issues. So, I don't want to report it, but I want to know if this is already fixed in the development branch, if there is a release with the fix immanent and - if there's something, you can do about it - when it will finally reach Debian testing… Greets and thanks for the cool stuff!
Hi! I'm not sure, I need to test if it works, but, if you're running pipewire, you should be able to wire all audio inputs/outputs in same way
5 replies