Package: caffeine
Version: 2.9.8-1
Severity: serious
Justification: Policy §9.1.1 / FHS §4.1 and §4.11

By chance I stumbled upon the two unexpected files

  /usr/VERSION
  /usr/compile_translations.py

and noticed that these both belong to caffeine.

These two files definitely don't belong there. I though can't find any
explicit rule, but IIRC there should be no file at all directly in
/usr/, just directories or symlinks to directories. FHS seems to declare
that indirectly though by declaring where all the files belong to:
/usr/share/, /usr/lib*/, /usr/*bin/, etc.

Python scripts either belong into /usr/bin/ or /usr/libexec/ or maybe
/usr/lib/python3/ or /usr/share/python3/, but definitely not into
/usr/. (And usually without the .py suffix.)

And the /usr/VERSION file seems completely displaced. Maybe it should go
into /usr/share/caffeine/ or so.

Not to mention that both filenames, especially /usr/VERSION are overly
generic.

Lintian actually also argues about this as file-in-unusual-dir:
https://lintian.debian.org/sources/caffeine

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-5-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages caffeine depends on:
ii  gir1.2-ayatanaappindicator3-0.1  0.5.90-7
ii  gir1.2-gtk-3.0                   3.24.33-1
ii  python3                          3.9.8-1
ii  python3-ewmh                     0.1.6-2
ii  python3-gi                       3.42.0-3
ii  python3-pkg-resources            59.6.0-1.2
ii  python3-xlib                     0.29-1
ii  xdg-utils                        1.1.3-4.1

caffeine recommends no packages.

caffeine suggests no packages.

-- no debconf information

Reply via email to