Control: tags -1 moreinfo Hi,
On Mon, Dec 08, 2014 at 05:53:28PM +0100, Laszlo Boszormenyi (GCS) wrote: > Please consider unblocking the current Sid version of SQLite3. It's one > of the rare upstream immediate bugfix release. What does 'immediate bugfix release' mean? > There's an RC bug filed against the source package of the Wheezy version. You didn't mention the bug number, but I guess you're talking about #771341. > But as the reporter states the version in Jessie is also effected. Please adjust the found versions, so that the BTS knows this. > The bug is very hard to reproduce so it's not yet known if this version > fixes that bug or not. If you don't have any idea whether this new version fixes the bug or not, we certainly aren't going to unblock it. Please read the freeze policy. We are only allowing unblocks for targeted fixes for certain types of bugs. Random 'fixes' from upstream are not appropriate at this time. > There's an other upstream immediate bugfix release, which if allowed I > would like to upload. Diffs are attached and the upstream bugfix log is: > 1) for 3.8.7.2[2]: > Enhance the ROLLBACK command so that pending queries are allowed to > continue as long as the schema is unchanged. Formerly, a ROLLBACK would > cause all pending queries to fail with an SQLITE_ABORT or > SQLITE_ABORT_ROLLBACK error. That error is still returned if the > ROLLBACK modifies the schema. This doesn't sound like a bug fix. It's a new feature, which even changes the behaviour. > * Bug fix: Make sure that NULL results from OP_Column are fully and > completely NULL and do not have the MEM_Ephem bit set. Ticket > 094d39a4c95ee4. > * Bug fix: The %c format in sqlite3_mprintf() is able to handle > precisions greater than 70. > * Bug fix: Do not automatically remove the DISTINCT keyword from a > SELECT that forms the right-hand side of an IN operator since it is > necessary if the SELECT also contains a LIMIT. Ticket db87229497. If you think any of these changes is appropriate (based on the freeze policy), please explain why. > 2) for 3.8.7.3[3]: > Bug fix: Ensure the cached KeyInfo objects (an internal abstraction not > visible to the application) do not go stale when operating in shared > cache mode and frequently closing and reopening some database > connections while leaving other database connections on the same shared > cache open continuously. Ticket e4a18565a36884b00edf. > * Bug fix: Recognize that any column in the right-hand table of a LEFT > JOIN can be NULL even if the column has a NOT NULL constraint. Do > not apply optimizations that assume the column is never NULL. Ticket > 6f2222d550f5b0ee7ed. > As SQLite3 is used by several other packages, it would be good to have > these safe, immediate upstream fixes for Jessie. Calling the changes 'safe' or 'immediate' doesn't make more appropriate for an unblock. It seems none of these changes complies with the freeze policy, so they are not appropriate for an unblock. If you have a targeted fix for #771341, please upload it to unstable (reverting the other changes) and file an unblock for that. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
