You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
virtnbd-nbdkit-plugin gets installed in /usr/bin, as a non-executable file. That triggers errors from rpmlint for example. The proper place to me (at least in a packaged install) would be /usr/share.
I'm looking at submitting a package to Fedora, and I expect that would be a blocker. I could use a downstream patch to move it to /usr/share, and change libvirtnbdbackup/map/requirements.py to hard-code the path (which should be fine for an RPM install anyway), but wanted to check before making such a change.
rpmlint also doesn't like the shebang lines at the start of the module files (which aren't needed so will probably also strip out for an RPM).
The text was updated successfully, but these errors were encountered:
no real reason for that, it was just the simplest solution i picked back in the days. Not sure if i want to change that currently, the debian packages install in the same path and the linters are fine with it ..
virtnbd-nbdkit-plugin gets installed in /usr/bin, as a non-executable file. That triggers errors from rpmlint for example. The proper place to me (at least in a packaged install) would be /usr/share.
I'm looking at submitting a package to Fedora, and I expect that would be a blocker. I could use a downstream patch to move it to /usr/share, and change libvirtnbdbackup/map/requirements.py to hard-code the path (which should be fine for an RPM install anyway), but wanted to check before making such a change.
rpmlint also doesn't like the shebang lines at the start of the module files (which aren't needed so will probably also strip out for an RPM).
The text was updated successfully, but these errors were encountered: