rubberband is unstripped #72
Comments
|
FWIW, the executable() call looks alright... but I don't understand why this would lead to e.g. rubberband being unstripped, but not rubberband-r3? |
|
I am now manually stripping the file. |
archlinux-github
pushed a commit
to archlinux/svntogit-community
that referenced
this issue
Apr 6, 2023
Split out ladspa,lv2 and vamp plugin into separate packages. Strip rubberband manually: breakfastquay/rubberband#72 Consolidate meson calls to adhere to packaging guidelines. git-svn-id: file:///srv/repos/svn-community/svn@1439226 9fca08f4-af9d-4005-b8df-a31f2cc04f65
archlinux-github
pushed a commit
to archlinux/svntogit-community
that referenced
this issue
Apr 6, 2023
Split out ladspa,lv2 and vamp plugin into separate packages. Strip rubberband manually: breakfastquay/rubberband#72 Consolidate meson calls to adhere to packaging guidelines. git-svn-id: file:///srv/repos/svn-community/svn@1439226 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! When packaging rubberband > 3.0.0 for Arch Linux, I noticed that
/usr/bin/rubberbandremains unstripped after it is added to the package file.Usually makepkg takes care of stripping executables and libraries when they are added to the package directory (this is done in a fakeroot environment).
It is rather unexpected to not be stripped and I'm a bit puzzled as to why that would happen. Maybe it is a false positive of our namcap tooling, but I don't think I have seen this before.
This behavior started with rubberband 3.0.0.
The text was updated successfully, but these errors were encountered: