Olivier, On 04/06/2012 16:52, Olivier Berger wrote: > Damien Raude-Morvan <[email protected]> writes: >> I would expect that users would read upstream upgrade guide before >> upgrading : >> http://opennebula.org/documentation:rel3.4:upgrade >> > > I'm afraid this isn't a valid expectation for a Debian > maintainer.
For a critical software like OpenNebula, I would expect user to at least (1) do a test upgrade before upgrade of controller node and (2) read upstream upgrade guide... but maybe I have too much expectation to debian users. > At least, there should be a NEWS big red warning IMHO. I will had something to NEWS entry, but as you know it's not binding for users (someone who haven't apt-listchanges installed for instance). >> Before installing OpenNebula 3.4, make sure you don't have >> any active VMs. Shutdown or delete all VMs. >> >> Ii will be difficult on the long run to keep maintaining all tricks to >> keep package in sync with upstream handling... >> > > That's the fate of the Debian maintainer : never pretended it would be > easy. > > Anyway, for the problem at stake, I guess there could be some kind of a > check in a script that uses onevm list to check the status for instance > (or some lower level API I'm not aware of). Would you provide a patch ? :) Cheers, -- Damien -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
