#423 Permissions on /var/log/prosody/* are unconditionally reset upon package upgrade.

Reporter deoren.moor
Owner Zash
Stars ★ (1)  
  • Milestone-0.9
  • OpSys-Linux
  • Type-Defect
  • Priority-Medium
  • Debian
  • Status-Fixed
  1. deoren.moor on

    == What steps will reproduce the problem? == 1. Add official Prosody package repository 2. Install prosody-0.10 3. Configure prosody to log to syslog 4. Configure syslog (rsyslog in my case) to log to /var/log/prosody/prosody.og 5. Set ownership recursively to syslog:adm on /var/log/prosody/ 6. Upgrade prosody when a new nightly build is released. == What is the expected output? == The expectation was for custom permissions/ownership to be retained. == What do you see instead? == Permissions are unconditionally reset back to the default on /var/log/prosody/* == What version of the product are you using? == prosody 0.10 nightlies == On what operating system? == Ubuntu 12.04.x LTS == Please provide any additional information below. == Mailing list discussion on this: https://groups.google.com/forum/#!topic/prosody-dev/Tk67DUSxVxo

  2. Zash on

    I checked, our own packages don't use dpkg-statoverride for various things that the Debian packages do. I think we should merge most of this (the postinst script iirc) into our packages.

    • tag Milestone-0.9
    • tag Status-Accepted
  3. Zash on

    • tags OpSys-Linux Debian
    • owner MattJ
  4. Zash on

    I started merging with the official Debian package.

    • tags Status-Started
    • owner MattJ Zash
  5. Zash on


    • tags Status-Fixed

New comment