fair (0.5.3-4) [PTS] [DDPO]

NEW: VCS has unreleased changes: 0.5.3-5 > 0.5.3-4

Git: https://salsa.debian.org/salvage-team/fair.git
JSON
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: master
Path: debian/changelog
Repo size: 139264
Browser: https://salsa.debian.org/salvage-team/fair
Last scan: 2025-10-08 12:22:06+00
Next scan: 2025-10-14 12:38:00+00
CI pipeline status: success

Debian changelog in Git:

fair (0.5.3-5) unstable; urgency=medium

  * Team upload.

  [ Jochem Kossen ]
  * debian/*.service: fix ConditionFileExists -> ConditionPathExists
    Closes: #1115290

 -- наб <nabijaczleweli@nabijaczleweli.xyz>  Mon, 15 Sep 2025 23:14:33 +0200

This branch is 2 commits ahead of tag debian/0.5.3-4

Git log:

commit 426ee237b5994b51a2fd11d0d6f345ea70b90f3f
Author: наб <nabijaczleweli@nabijaczleweli.xyz>
Date:   Mon Sep 15 23:15:22 2025 +0200

    fair 0.5.3-5

commit 4efbc62580e062e6d9e91c22d05f93e4caab8555
Author: Jochem Kossen <jochem@jkossen.nl>
Date:   Mon Sep 15 10:01:21 2025 +0200

    Bug#1115290: fair: systemd service files have nonexisting ConditionFileExists instead of ConditionPathExists
    
    Package: fair
    Version: 0.5.3-4
    Severity: minor
    Tags: patch
    
    Dear Maintainer,
    
       * What led up to the situation?
       During packaging of a different piece of software, someone on #debian-mentors
       IRC suggested I use ConditionFileExists in my systemd unit files.
    
       I searched for its usage using codesearch.debian.net and found just a single
       package using it.
    
       Turns out it should be ConditionPathExists, and by coincidence, fair has
       ConditionFileExists.
    
       * What exactly did you do (or not do) that was effective (or
         ineffective)?
       Changing ConditionFileExists to ConditionPathExists in both service units
       fixed the problem:
       - /usr/lib/systemd/system/fair-carrousel.service
       - /usr/lib/systemd/system/fair-transponder.service
    
       * What was the outcome of this action?
       The services depend on configuration. So when the systemd service is enabled,
       and started, but there's no configuration yet, it gives an error.
    
       After applying my change, it will just refuse to start and notify:
         Condition: start condition unmet at Mon 2025-09-15 09:42:28 CEST; 11min ago
                 └─ ConditionPathExists=/etc/fair.conf was not met
    
    -- System Information:
    Debian Release: 13.1
      APT prefers stable-updates
      APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
    Architecture: amd64 (x86_64)
    
    Kernel: Linux 6.16.3+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
    Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
    Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled
    
    Versions of packages fair depends on:
    ii  init-system-helpers  1.69~deb13u1
    pn  libavl1t64           <none>
    ii  libc6                2.41-12
    
    fair recommends no packages.
    
    fair suggests no packages.