I've installed bzr 2.2.1 from maverick-proposed and used it for the last few days without hitting any regressions.
I've manually tested the upgrade from 1.14 to 2a described by this bug.
I'm running the sefltests and the only failures are the already-known problems to do with tests not liking being run from an installed copy. (And also as discussed above, these are fixed in trunk and will be fixed in 2.2.2.)
Hi Pitti,
I've installed bzr 2.2.1 from maverick-proposed and used it for the last few days without hitting any regressions.
I've manually tested the upgrade from 1.14 to 2a described by this bug.
I'm running the sefltests and the only failures are the already-known problems to do with tests not liking being run from an installed copy. (And also as discussed above, these are fixed in trunk and will be fixed in 2.2.2.)
I don't see any new bugs in <https:/ /bugs.edge. launchpad. net/ubuntu/ +source/ bzr/?field. searchtext= &orderby= -datecreated& search= Search& field.status: list=NEW& field.status: list=INCOMPLETE _WITH_RESPONSE& field.status: list=INCOMPLETE _WITHOUT_ RESPONSE& field.status: list=CONFIRMED& field.status: list=TRIAGED& field.status: list=INPROGRESS &field. status: list=FIXCOMMITT ED&field. assignee= &field. bug_reporter= &field. omit_dupes= on&field. has_patch= &field. has_no_ package=> that would indicate that other people running maverick-proposed had any trouble.
According to <https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification# Updating% 20the%20bug% 20report>we need one more positive verification...