On Sun, Dec 09, 2007 at 12:21:50PM +0000, Olly Betts wrote: > On Sun, Dec 09, 2007 at 11:39:18AM +0530, Kumar Appaiah wrote: > > Package: xapian-omega > > Version: 1.0.4-1 > > Severity: important > > Hmm, I don't really see how this bug "has a major effect on the > usability of [the] package". I'm not going to fight over it, but > artificially inflating the severity rarely gets a bug fixed any > quicker.
Well, a release goal demands severity important. You may want to confirm this with the Release managers, I may be wrong. > > /var/lib/xapian-omega owned by: xapian-omega > > /var/lib/xapian-omega/templates not owned > > /var/lib/xapian-omega/templates/anyalldropbox not owned > > /var/lib/xapian-omega/templates/anyallradio not owned > > /var/lib/xapian-omega/templates/godmode not owned > > /var/lib/xapian-omega/templates/opensearch not owned > > /var/lib/xapian-omega/templates/query not owned > > /var/lib/xapian-omega/templates/toptermsjs not owned > > /var/lib/xapian-omega/templates/xml not owned > > The problem seems to be that xapian-omega.prerm contains: > > if [ "$1" = purge ] ; then > rm -rf /var/lib/xapian-omega/templates > fi > > But it's postrm that gets called with purge according to the developers > reference, not prerm. Well, the release goal dictates that a purge must result in removal of all files and directories belonging to that package. Therefore, I presume that this should imply that the postrm must also get rid of these files. Of course, please confirm this with a release manager in charge of this task (Luk Claes) if you are unsure. Thanks! Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036
signature.asc
Description: Digital signature