On Fri, 26 May 2006, Alberto Gonzalez Iniesta wrote:
On Tue, May 03, 2005 at 08:14:06PM +0800, [EMAIL PROTECTED] wrote:
On Tue, 3 May 2005, Alberto Gonzalez Iniesta wrote:
Well, as the debconf text reads:
'This option will take effect in your next upgrade.'
I can't fix change the behavior in the very same upgrade you change it,
'cos it'll be already stopped when the question pops :)
I'm sorry this problem got you, you were not the only one. But the
solution is already in place. I'm closing it.
One thing you've not clarified is how it got to openvpn/stop2upgrade: true
in the first place.
If it's not necessary ever to stop openvpn to upgrade it, then where's
the point in the question? Just never stop to upgrade.
openvpn/stop2upgrade: true was the default, and is not longer that way,
because that's the way the Debian packaging system worked before I put
the debconf question. This means that *witouth* the debconf question,
the default behaviour of a 'daemon' upgrade is:
1) stop daemon
2) upgrade
3) start daemon
When I first introduced the debconf question, I mimicked that behaviour.
That's the only reason. And you won't be asked if you have a low/medium
debcon priority.
NOW, (actually some time ago, just revisiting bugs now) that has *changed*.
Now openvpn/stop2upgrade defaults to false which is what this report
asks for (AFAICT), so let me know if it's OK to close it now.
Sounds good to me.
Regards,
Alberto
--
Cheers
John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
