[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

mucking with dpkg control files in maintainer scripts?

hey all,

i recently saw that apache2.2-common's prerm script has the following
block of text:

= = = = =
rm -f /var/lib/dpkg/info/apache2-common.postrm
= = = = =

and the following from the changelog:

= = = = =
apache2 (2.2.3-2) unstable; urgency=low
  * rm -f /var/lib/dpkg/info/apache2-common.postrm.  So apache2-common
    be purged. Yes, we're on crack.  Closes: #390823
= = = = =

is this even remotely acceptable?  i had the impressions that packages
must not assume the inner workings of dpkg.  but, i can't back this up
with anything in policy from what i can tell, hence the posting of
this question.


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: