I guess we need to conflict with the packages who expect persistens in
/var/run/ and /var/lock to avoid breaking partial upgrades were
sysvinit is upgraded while other packages are left alone. Something
like
Conflict: exim4-base (= 4.62-4)
might do it, if a updated exim4 version is uploaded
On Sat, 16 Sep 2006, Petter Reinholdtsen wrote:
Not sure how to handle those packages where we do not know when the
fix will be uploaded. A simple conflict without a version seem a bit
harsh for a essential package to do. Any opinions on this?
None, AFAIK. I think we will have to add an
[Henrique de Moraes Holschuh]
None, AFAIK. I think we will have to add an unversioned conflicts on them,
and update it to versioned when they fix their side. This is fine right
now, as our packages are going to experimental (and will have to for quite a
while -- there is a lot to fix to get
3 matches
Mail list logo
