Source: wsdd
Version: 2:0.7.0-2.1
Severity: important
Tags: patch trixie sid
Forwarded: https://salsa.debian.org/grantma/wsdd/-/merge_requests/2
Control: affects -1 src:gvfs

gvfs 1.53.90-1 now tries to use wsdd from $PATH but Debian's default
$PATH does not include /usr/sbin/

According to the latest version of the Filesystem Hierarchy System
(FHS) 3.0, § 3.16,
"/sbin contains binaries essential for booting, restoring, recovering,
and/or repairing the system in addition to the binaries in /bin. [18]
Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin."

I don't believe wsdd is any of those categories.

I am filing as Important, but Serious may be appropriate. Debian
Policy § 9.1.1 requires compliance with the FHS with some exceptions
(which don't apply here).

References
---------------
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s16.html https://www.debian.org/doc/debian-policy/ch-opersys.html#file-system-structure

Thank you,
Jeremy Bícha

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Feb 16, 2024 at 10:08 PM Matt Grant <matt@mattgrant.net.nz> wrote:

Symlinking /usr/sbin/wsdd to /usr/bin to fix this path issue.

0.7.1 has the wsdd manpage in section 8. IMHO Gvfs should execute wsdd
from /usr/sbin as wsdd is not purely a user executable binary, but
mostly used with Samba servers.

I think that deciding where to install a package based on its manpage
section could be backwards, but projects should include installers too
instead of leaving distros to figure it out.

I opened https://github.com/christgau/wsdd/issues/198 to request that
the manpage be moved to section 1.

While you originally packaged wsdd for Samba servers, I expect that it
will actually be used by far more people who are not running Samba
servers now that gvfs-daemons recommends it.

I don't think it is necessary or helpful at all to have wsdd
additionally in /usr/sbin/ . Arch Linux and Fedora package it as
/usr/bin/wsdd . I am unaware of any Debian package that has a symlink /usr/bin/foo to /usr/sbin/foo (or the reverse).

https://src.fedoraproject.org/rpms/wsdd/blob/rawhide/f/wsdd.spec#_36 https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wsdd#n25

Thank you,
Jeremy Bícha

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Symlinking /usr/sbin/wsdd to /usr/bin to fix this path issue.

0.7.1 has the wsdd manpage in section 8.  IMHO Gvfs should execute wsdd
from /usr/sbin as wsdd is not purely a user executable binary, but
mostly used with Samba servers.

On 17/02/24 03:40, Jeremy Bícha wrote:

Source: wsdd
Version: 2:0.7.0-2.1
Severity: important
Tags: patch trixie sid
Forwarded: https://salsa.debian.org/grantma/wsdd/-/merge_requests/2
Control: affects -1 src:gvfs

gvfs 1.53.90-1 now tries to use wsdd from $PATH but Debian's default
$PATH does not include /usr/sbin/

According to the latest version of the Filesystem Hierarchy System
(FHS) 3.0, § 3.16,
"/sbin contains binaries essential for booting, restoring, recovering,
and/or repairing the system in addition to the binaries in /bin. [18] Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin."

I don't believe wsdd is any of those categories.

I am filing as Important, but Serious may be appropriate. Debian
Policy § 9.1.1 requires compliance with the FHS with some exceptions
(which don't apply here).

References
---------------
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s16.html https://www.debian.org/doc/debian-policy/ch-opersys.html#file-system-structure

Thank you,
Jeremy Bícha

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)