Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1172206 > unrolled thread

Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21.

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. Jeremy Jongepier <jeremy+debian@autostatic.com> - 2023-10-19 18:10 +0200
    Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. Sebastian Ramacher <sramacher@debian.org> - 2023-10-29 13:20 +0100
      Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. Erich Eickmeyer <eeickmeyer@ubuntu.com> - 2023-10-29 15:10 +0100
        Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. Sebastian Ramacher <sramacher@debian.org> - 2023-10-29 17:50 +0100
          Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. Sebastian Ramacher <sramacher@debian.org> - 2023-10-29 19:20 +0100

#1172206 — Bug#1054233: liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21.

Package: liblilv-0-0
Version: 0.24.14-1
Severity: important

Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. The addition of this line indicates that something fundamental has changed, namely the default path where Debian installs its LV2 plugins. These go into /usr/lib/$(DEB_HOST_MULTIARCH) too now which breaks setups running software that uses the FHS as a starting point for LV2 plugin discovery. The LV2 plugin packages that Debian now installs are now not discovered anymore.

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.7-1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages liblilv-0-0 depends on:
ii  libc6          2.36-9+deb12u3
ii  libserd-0-0    0.30.16-1
ii  libsord-0-0    0.16.14+git221008-1
ii  libsratom-0-0  0.6.14-1

liblilv-0-0 recommends no packages.

liblilv-0-0 suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]

#1173237

Control: tags -1 moreinfo

On 2023-10-19 17:51:33 +0200, Jeremy Jongepier wrote:
> Package: liblilv-0-0
> Version: 0.24.14-1
> Severity: important
> 
> Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. The addition of this line indicates that something fundamental has changed, namely the default path where Debian installs its LV2 plugins. These go into /usr/lib/$(DEB_HOST_MULTIARCH) too now which breaks setups running software that uses the FHS as a starting point for LV2 plugin discovery. The LV2 plugin packages that Debian now installs are now not discovered anymore.

I think you are mistaken. It you compare the the default path in
meson.build and the one specified in debian/rules, it extends the
default path with /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 (note the lv2).

Please describe the actual problem that you are seeing.

Cheers
-- 
Sebastian Ramacher

[toc] | [prev] | [next] | [standalone]

#1173248

Sebastian,

I'm fairly certian Robin Gareus made it quite clear what Jeremy was 
saying in his reply:

 >The LV2 FHS that Jeremy mention can be found at
 >https://lv2plug.in/pages/filesystem-hierarchy-standard.html
 >
 >Now you may not like, or disagree with the official standard, but 
breaking it is not acceptable. This affects various >3rd party software, 
notably Reaper, Harrison Mixbus, Ardour and other non-free DAWs that 
expect LV2 plugins in >/usr/lib/lv2/
 >
 >LV2s are to be installed $PREFIX/lib/lv2 (unrelated to $LIBDIR).
 >Most LV2 plugin build systems use LV2DIR = $PREFIX/lib/lv2 for this.

This does divert from the standard location in which shared libraries 
are expected to be located, but LV2 plugins, as you are aware, are not 
normal shared libraries. If they cannot be found in /usr/lib/lv2, then 
it literally breaks the functionality of several DAWs out there, 
including Ardour (which we ship). Sure, users can always manually add 
the search path of /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 to the software, 
but that's an unnecessary inconvenience.

I checked the salsa repo for liblilv (and another) and it seems as 
though /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 is being intentionally set as 
the install location here, so this simply needs to be reverted. I can 
even set-up the pull request.

Beyond that, I will be fairly unhappy if I have to downstream patch this.

Cheers,
Erich

--
Erich Eickmeyer
Project Leader - Ubuntu Studio
Technical Lead - Edubuntu

On 10/29/23 05:10, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo
>
> On 2023-10-19 17:51:33 +0200, Jeremy Jongepier wrote:
>> Package: liblilv-0-0
>> Version: 0.24.14-1
>> Severity: important
>>
>> Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. The addition of this line indicates that something fundamental has changed, namely the default path where Debian installs its LV2 plugins. These go into /usr/lib/$(DEB_HOST_MULTIARCH) too now which breaks setups running software that uses the FHS as a starting point for LV2 plugin discovery. The LV2 plugin packages that Debian now installs are now not discovered anymore.
> I think you are mistaken. It you compare the the default path in
> meson.build and the one specified in debian/rules, it extends the
> default path with /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 (note the lv2).
>
> Please describe the actual problem that you are seeing.
>
> Cheers

-- 
Project Leader - Ubuntu Studio
Technical Lead - Edubuntu

[toc] | [prev] | [next] | [standalone]

#1173259

On 2023-10-29 07:01:07 -0700, Erich Eickmeyer wrote:
> Sebastian,
> 
> I'm fairly certian Robin Gareus made it quite clear what Jeremy was saying
> in his reply:
> 
> >The LV2 FHS that Jeremy mention can be found at
> >https://lv2plug.in/pages/filesystem-hierarchy-standard.html
> >
> >Now you may not like, or disagree with the official standard, but breaking
> it is not acceptable. This affects various >3rd party software, notably
> Reaper, Harrison Mixbus, Ardour and other non-free DAWs that expect LV2
> plugins in >/usr/lib/lv2/



> >
> >LV2s are to be installed $PREFIX/lib/lv2 (unrelated to $LIBDIR).
> >Most LV2 plugin build systems use LV2DIR = $PREFIX/lib/lv2 for this.
> 
> This does divert from the standard location in which shared libraries are
> expected to be located, but LV2 plugins, as you are aware, are not normal
> shared libraries. If they cannot be found in /usr/lib/lv2, then it literally
> breaks the functionality of several DAWs out there, including Ardour (which
> we ship). Sure, users can always manually add the search path of
> /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 to the software, but that's an
> unnecessary inconvenience.

lilv does not install LV2 plugins. If other packages abuse lilv's libdir
as base to determine LV2DIR, those packages are buggy. As you explain
above, it's not $libdir/lv2 but $prefix/lib/lv2 that's to be used.

> I checked the salsa repo for liblilv (and another) and it seems as though
> /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 is being intentionally set as the install
> location here, so this simply needs to be reverted. I can even set-up the
> pull request.

Please point me to the place where this is set as install location.

Cheers
-- 
Sebastian Ramacher

[toc] | [prev] | [next] | [standalone]

#1173265

On 2023-10-29 17:45:56 +0100, Sebastian Ramacher wrote:
> On 2023-10-29 07:01:07 -0700, Erich Eickmeyer wrote:
> > Sebastian,
> > 
> > I'm fairly certian Robin Gareus made it quite clear what Jeremy was saying
> > in his reply:
> > 
> > >The LV2 FHS that Jeremy mention can be found at
> > >https://lv2plug.in/pages/filesystem-hierarchy-standard.html
> > >
> > >Now you may not like, or disagree with the official standard, but breaking
> > it is not acceptable. This affects various >3rd party software, notably
> > Reaper, Harrison Mixbus, Ardour and other non-free DAWs that expect LV2
> > plugins in >/usr/lib/lv2/
> 
> 
> 
> > >
> > >LV2s are to be installed $PREFIX/lib/lv2 (unrelated to $LIBDIR).
> > >Most LV2 plugin build systems use LV2DIR = $PREFIX/lib/lv2 for this.
> > 
> > This does divert from the standard location in which shared libraries are
> > expected to be located, but LV2 plugins, as you are aware, are not normal
> > shared libraries. If they cannot be found in /usr/lib/lv2, then it literally
> > breaks the functionality of several DAWs out there, including Ardour (which
> > we ship). Sure, users can always manually add the search path of
> > /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 to the software, but that's an
> > unnecessary inconvenience.
> 
> lilv does not install LV2 plugins. If other packages abuse lilv's libdir
> as base to determine LV2DIR, those packages are buggy. As you explain
> above, it's not $libdir/lv2 but $prefix/lib/lv2 that's to be used.

FWIW, the only packages in Debian installing LV2 plugins in multi-arch
locations are mda-lv2 and naspro-bridges. Fixes for both have been
uploaded to unstable.

Cheers
-- 
Sebastian Ramacher

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web