-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No more man page for version 2.1.0? #5513
Comments
Fix for now:
|
Thanks for reporting this! I have indeed missed out on this when I updated the project to be packaged by Poetry 🙂 will get it sorted for the next release |
@snejus may I ask you to include tests back to the pypi as well? It is quite useful for maintaners. |
Possibly - is there anything specific that you need? We're trying to expose the relevant test helpers under |
@snejus 2.0.0 had the full test suite which allows me to run it to be sure that everything is working. 2.1.0 hasn't got them, see:
|
This makes sense - though what are you testing in this case? |
Beets when I update packages for OpenBSD I'd love to use unit tests from software to be sure that everything is working fine. |
Are you installing beets in some sort of a different way, potentially overriding its dependencies? |
Unit tests is nice way to check that everything works after updating version for example. |
And no, using |
Stop
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Kirill A. Korinsky ***@***.***>
Sent: Friday, November 22, 2024 11:21:12 AM
To: beetbox/beets ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [beetbox/beets] No more man page for version 2.1.0? (Issue #5513)
And no, using pipx or something similar requires some work on OpenBSD because user need rust and some hacks to be able to build all needed dependencies. Or at least it had like year ago when I had tried it the last time.
—
Reply to this email directly, view it on GitHub<#5513 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADEKIIWO3IICQUONRE5NTO32B5KXRAVCNFSM6AAAAABSJCHH6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUGEZTSOJSGY>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
I see. Practically speaking, how do you ensure that dependencies are present for one of the plugins? Let's say you want to use |
By adding some runtime dependencies for most popular plugins, or add in readme that if you would like to use plugin X, please install Y and Z. |
Sorry my question was ambiguous: I meant what sort of commands do you run as a user to install additional dependencies for beets on your system? |
If I understand your question when it’s documented here: https://beets.readthedocs.io/en/stable/guides/main.html |
I'm just curious about the process you mentioned above since I am not aware how things work in OpenBSD world. You mentioned that For example, on my end (on Arch) I could
$ pacman -Syu beets
# however this does not include plugins, so I'd have to hack something like this, probably
$ /bin/python -m pip install beets[replaygain,fetchart]
$ pipx install beets[replaygain,fetchart]
# this way it's isolated from the system and I have flexibility to install more plugins
# for example I'd use something like below to make sure 'autobpm' dependencies are present
$ pipx runpip beets install beets[autobpm]
$ git clone https://github.com/beetbox/beets
$ cd beets
$ poetry install
# make the command available everywhere
$ ln -s $VIRTUALENV/bin/beet ~/.local/bin Since I'm actively working on it, I have it installed in a virtual environment as an editable package. |
Well, in OpenBSD world the simplest way is install
And in case of development of |
So if I understand correctly you're not able to install plugin dependencies together with beets, like |
@snejus a kind of. When someone pack beets to a package he usually copies dependnecies to ask package system to install it. Like this https://github.com/openbsd/ports/blob/master/audio/beets/Makefile#L21-L39 And unit test is good way to be sure that all needed dependnecies really installed and works as expected, due to new enough ot not new enough version for example. |
That's great! Thanks for your patience walking me through this. I've just checked previous versions of beets - it seems like neither beets |
np
As I show in #5513 (comment) |
Ah this makes sense! I will include the manual and the tests in the |
See #5520 |
Problem
When I download https://pypi.io/packages/source/b/beets/beets-2.1.0.tar.gz I don see any man pages anymore which was a part of https://pypi.io/packages/source/b/beets/beets-2.0.0.tar.gz, see:
Setup
The text was updated successfully, but these errors were encountered: