Hi,
It looks like this was already fixed for the non-legacy driver in bug
#735630
I'd imagine for consistency (and to stay in sync with the fedora patches
that fix came from) we should do the same here?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
Marc Haber wrote:
Please verify that you have actually updated the init script. The init
script is a conffile, so if you have done manual changes (which
shouldn't be necessary) you need to manually interfere to allow the
update to proceed.
The relevant code should have constructs like
Package: exim4-base
Version: 4.69-5+b1
Severity: serious
Justification: 6
Updating exim4 fails because the exim init script refuses to start the daemon.
From the changelog, I'm guessing this might be related to the quoting problems
encountered in a few recent bugs (476987 is one). This release
Package: tomcat5.5
Version: 5.5.20-4
Severity: grave
Justification: renders package unusable
The installation of tomcat5.5 uses relative symlinks in many places
including in the directories under CATALINA_BASE.
Example:
conf
logs - ../../log/tomcat5.5
shared
temp
webapps
work -
already been removed, any future attempt to
install it requires manual intervention.
I can imagine this scenario is going to apply to many more packages than
just uw-imapd. Anything that performs an update-inetd during its postrm
script will cause this same behavior.
--Mike Young
newcomp:/var
, but I wouldn't be suprised if the two are interrelated.
(Every clue helps.)
the only main interaction I can see in the install files is that
uw-imapd does some update-inetd commands.
Let me know if you need anything more.
--Mike Young
Aptitude 0.4.4: log report
Tue, Mar 6 2007 22:02:44 -0500
6 matches
Mail list logo