Processed: Re: Bug#573232: uptimed: truncating database to maxrecords lead to data loss

2010-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 573232 normal Bug #573232 [uptimed] uptimed: truncating database to maxrecords lead to data loss Severity set to 'normal' from 'grave' > tags 573232 upstream Bug #573232 [uptimed] uptimed: truncating database to maxrecords lead to data

Bug#573232: uptimed: truncating database to maxrecords lead to data loss

2010-03-09 Thread Martin Steigerwald
Package: uptimed Version: 1:0.3.16-3.1 Severity: grave Justification: causes non-serious data loss I don't know when exactly, maybe today I updated uptimed and somehow either debconf didn't ask me whether I'd like uptimed.conf being overwritten or I accidently answered yes to this question. This s

Bug#573232: uptimed: truncating database to maxrecords lead to data loss

2010-03-09 Thread Thibaut VARENE
severity 573232 normal tags 573232 upstream forwarded 573232 ra...@podgorny.cz thanks On Tue, Mar 9, 2010 at 11:42 PM, Martin Steigerwald wrote: > Severity: grave > Justification: causes non-serious data loss "grave" and "non-serious"? > I don't know when exactly, maybe today I updated uptimed