Bug#822491: influxdb: Incompatible metadata format

2016-05-02 Thread Matijs van Zuijlen
On 02/05/16 04:00, Alexandre Viau wrote: > In the future, I think that one good way to handle this would be to > issue a warning preinst and canceling the upgrade on user request. Yes, I think that would be a good and simple solution. Regards, -- Matijs signature.asc Description: OpenPGP

Bug#822491: influxdb: Incompatible metadata format

2016-05-01 Thread Alexandre Viau
Hello, On 25/04/16 10:44 AM, Matijs van Zuijlen wrote: > At the very least, I think there should be an entry in the NEWS file to give > people the earliest possible warning. I agree with that, I wouldn't mind uploading a new version with an entry in the NEWS file. > What could in fact still be

Bug#822491: influxdb: Incompatible metadata format

2016-04-25 Thread Matijs van Zuijlen
Hi Alexandre, On 25/04/16 12:23, Alexandre Viau wrote: > Hello, > > On 24/04/16 08:03 PM, Matijs van Zuijlen wrote: >> The influxdb server won't start anymore and logs the following >> complaint: >> >> run: create server: detected /var/lib/influxdb/meta/raft.db. To proceed, >> you'll need to

Bug#822491: influxdb: Incompatible metadata format

2016-04-24 Thread Alexandre Viau
Hello, On 24/04/16 08:03 PM, Matijs van Zuijlen wrote: > The influxdb server won't start anymore and logs the following > complaint: > > run: create server: detected /var/lib/influxdb/meta/raft.db. To proceed, > you'll need to either 1) downgrade to v0.11.x, export your metadata, > upgrade to

Bug#822491: influxdb: Incompatible metadata format

2016-04-24 Thread Matijs van Zuijlen
Package: influxdb Version: 0.12.0+dfsg1-1 Severity: important The influxdb server won't start anymore and logs the following complaint: run: create server: detected /var/lib/influxdb/meta/raft.db. To proceed, you'll need to either 1) downgrade to v0.11.x, export your metadata, upgrade to the