registry team mailing list archive

Thread
Date

[Bug 508861] Re: bastille sets dpkg-statoverride permissions to 0000

To: registry@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <508861@xxxxxxxxxxxxxxxxxx>
Date: Thu, 30 Sep 2010 18:11:00 -0000
Reply-to: Bug 508861 <508861@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug was fixed in the package bastille - 1:3.0.9-13

---------------
bastille (1:3.0.9-13) unstable; urgency=high

  * Bastille/Debian_API.pm: Fix bug in the permissions
    definition in the B_statoverride.Also, return inmediately if distribution
    is Debian or if dpkg-statoverride is not available.
    This bug caused bastille to set 0000 permissions when using
    dpkg-statoveride, thus the 'high' urgency. (Closes: #596954, 545052)
  * Bastille/API.pm: do not warn multiple times about the OS not being supported,
    just send this message to STDERR once.
  * Use debhelper compatibility version 5
  * debian/control: Depend on perl instead of on perl5.
  * debian/bastille.substvars: removed
 -- Andrew Starr-Bochicchio <a.starr.b@xxxxxxxxx>   Sun, 19 Sep 2010 14:46:19 +0200

** Changed in: bastille (Ubuntu)
       Status: In Progress => Fix Released

-- 
bastille sets dpkg-statoverride permissions to 0000
https://bugs.launchpad.net/bugs/508861
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.