Package provides files in `/usr/libexec`

Description:

This package currently (since recently?) ships usr/libexec/e2fsprogs/e2scrub_fail, which according to the packaging guidelines should be under usr/lib/e2fsprogs/e2scrub_fail

Additional info:

• package version(s): 1.47.1-2
• config and/or log files:
• link to upstream bug report, if any:

Steps to reproduce:

1. Step 1
2. Step 2
3. ...

added priority3-normal severity4-low statusunconfirmed labels

assigned to @freswa, @toolybird, and @gromit

changed the description

Caused by upstream commit e2scrub_fail: move executable script to /usr/libexec . Fixed by adding --libexecdir=/usr/lib/$pkgname to the configure invocation.

As this is a split package, wouldn't that need to be --libexecdir=/usr/lib/$pkgbase instead?

added scopeenhancement statusconfirmed labels and removed statusunconfirmed label

assigned to @eworm and unassigned @freswa, @toolybird, and @gromit

closed with commit a1011db8

Checking

As of: e2fsprogs 1.47.1-3

Are these the intended locations:

   /usr/lib/e2fsprogs/e2fsprogs/e2scrub_fail
   /usr/lib/e2initrd_helper

Seems a bit odd?

added resolutioncompleted label

Oh, missed the duplicate "e2fsprogs" in path...

And wondering if e2initrd_helper should be push into libexecdir - but that's upstream topic.

1.47.1-4 looks good now thanks.

The e2initrd_helper doesn't seem to be of much use [to us] - perhaps debian still uses it? I found an ancient reference to it [1] but not much else.

[1] https://lists.openwall.net/linux-ext4/2012/04/11/11