evergreen:tags/rel_2_2_rc1

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

aa84994... by Thomas Berezansky on 2012-05-14

Bumping version numbers and adding Changelog

Signed-off-by: Thomas Berezansky <email address hidden>

27cfefc... by Lebbeous Fogle-Weekley <email address hidden> on 2012-05-14

Avoid collisions of normalized values going into metabib.browse_entry

This fixes a bug that prevented successful reingestion of bib records
during the 2.1->2.2 upgrade in some cases. Reported by George Duimovich.

Key part here:

> ERROR: duplicate key value violates unique constraint
> "browse_entry_value_key"
> DETAIL: Key (value)=(545575) already exists.
> CONTEXT: SQL statement "INSERT INTO metabib.browse_entry (value) VALUES
> (metabib.browse_normalize(ind_data.value,

George confirmed that the changes to the version upgrade script fixed
the problem for him.

Signed-off-by: Lebbeous Fogle-Weekley <email address hidden>

172ebd6... by Lebbeous Fogle-Weekley <email address hidden> on 2012-05-11

Be more prepared for malformed serial holding code data in upgrade scripts

Signed-off-by: Lebbeous Fogle-Weekley <email address hidden>

0c04d11... by Dan Scott on 2012-05-11

Move PLPERL dropping outside of 2.1-2.2 upgrade transaction

Sites might have added custom PLPERL database functions for migrations,
data clean up, etc, so don't make the success of the 2.1-2.2 upgrade
hinge on a database schema that exactly matches vanilla Evergreen;
just move it outside of the upgrade transaction and output a reassuring
note.

Signed-off-by: Dan Scott <email address hidden>
Signed-off-by: Lebbeous Fogle-Weekley <email address hidden>

6238c9e... by Thomas Berezansky on 2012-04-18

Add missing weights fm_IDL entries

Signed-off-by: Thomas Berezansky <email address hidden>
Signed-off-by: Lebbeous Fogle-Weekley <email address hidden>

7f46dc3... by Lebbeous Fogle-Weekley <email address hidden> on 2012-05-10

In the 2.1-2.2 upgrade script, move 0691 into a failures-are-ok zone

Mainly because it's already covered in the 2.1.1-2.1.2 upgrade script.
Thanks to George Duimovich for pointing this out in LP #997759.

Signed-off-by: Lebbeous Fogle-Weekley <email address hidden>

749de68... by Thomas Berezansky on 2012-05-10

Version Upgrade Cleanup

Merge tacked on transactions into the "primary" transaction.
Add in 0708 for tracking purposes.

Separate 0672 and 0679+0680 in the version-to-version upgrade script
They're all potentially slow.

Signed-off-by: Lebbeous Fogle-Weekley <email address hidden>

123751f... by Bill Erickson on 2012-05-04

Check if transaction needs closing after adding billings

This addresses the issue where issuing refunds results in a negative
ballance and it is then impossible to close the transaction by creating
new billings.

https://bugs.launchpad.net/evergreen/+bug/758982

Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Mike Rylander <email address hidden>

b3ef008... by Thomas Berezansky on 2012-05-07

Nearest Hold: Look at 100 instead of 10 holds

At the suggestion of Mike Rylander.

Because DB-wise the extra 90 IDs isn't a big deal, and this way we get more
chances to capture (or block renewal, etc).

Jeff Godin claims they have done this and it has produced no issues for them.

Signed-off-by: Thomas Berezansky <email address hidden>
Signed-off-by: Mike Rylander <email address hidden>

6bbd809... by Thomas Berezansky on 2012-05-07

Hold Capture: Run permit tests on "old" holds

Because we shouldn't be trusting that the copies are still valid.

Signed-off-by: Thomas Berezansky <email address hidden>
Signed-off-by: Mike Rylander <email address hidden>