> There really is a policy about spending time in unstable. See: > > http://www.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-t-p-u
bogofilter isn't frozen yet. testing-proposed-updates doesn't apply. > http://release.debian.org/sarge_rc_policy.txt > > " makes unrelated software on the system (or the whole system) > break" > > When this breaks it stops Exim in my setup. Thus there are actually two > policy violations. bogofilter isn't breaking exim. Apparently bogofilter is breaking, and exim is failing to handle that. > At least bogofilter_0.93.1-1_i386.deb or the one before works without > crashing the db file. You have to realize that sarge is about to go > stable. Lots of people are starting to run sarge on production machines. > This didn't spend any time in unstable after the upstream release. I > think 30 days to see what bugs come back would be a starting point. You seem to be the only person to experience such a problem for at least the past month. > >For the record, this user is describing switching from a db4.2-linked > >bogofilter to a db4.3-linked bogofilter. > > Not true --- I rebuilt the databases You may have rebuilt the databases, but that doesn't change the fact that you're claiming that the db4.2-version is fine, and the db4.3-version is experiencing corruption. > It worked for most of 48 hours. > > Did the same for the last debian release - with the same problem. Are you using libdb4.3 4.3.27-1 with the problematic bogofilter versions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
