Merge lp:~adeuring/launchpad/no-feng-shui-in-the-server-room into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Robert Collins |
Approved revision: | no longer in the source branch. |
Merged at revision: | 11621 |
Proposed branch: | lp:~adeuring/launchpad/no-feng-shui-in-the-server-room |
Merge into: | lp:launchpad |
Diff against target: |
112 lines (+0/-92) 3 files modified
lib/canonical/launchpad/pagetests/standalone/xx-librarian-upload-errors.txt (+0/-60) lib/canonical/launchpad/templates/launchpad-librarianfailure.pt (+0/-23) lib/canonical/launchpad/zcml/launchpad.zcml (+0/-9) |
To merge this branch: | bzr merge lp:~adeuring/launchpad/no-feng-shui-in-the-server-room |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Collins (community) | Approve | ||
Review via email: mp+36427@code.launchpad.net |
Commit message
removed the special page template for Librarian related failures.
Description of the change
(11:49:07) lifeless: adeuring: regarding the librarian OOPS ID change
(11:49:14) lifeless: adeuring: could we just delete that template altogether ?
(11:49:20) lifeless: adeuring: and stop special casing it?
(11:49:43) adeuring: lifeless: yeah, I wondered too if we really needed it. but...
(11:49:51) adeuring: there might be one reason:
(11:49:58) lifeless: adeuring: if you'd like to delete it, +1 from me :)
(11:50:57) adeuring: lifeless: well, these errors involve another machine, the librarian server, so they can occur due to reasons like hardware failures, network problems etc
(11:51:09) lifeless: adeuring: so do all our requests.
(11:51:23) lifeless: adeuring: (the database server is another machine ...)
(11:51:28) adeuring: well, yes, but there one more machine involved that usually
(11:51:49) lifeless: true, but its not a unique thing
(11:51:53) lifeless: its just more of the same
(11:51:59) lifeless: global searches use google
(11:52:08) lifeless: gpg key checking uses the keyserver
(11:52:47) adeuring: hrmm, yeah... ok, I delete it. Though I'll be missing the "feng shui in the server room" message ;)
Might be nice to check (manually) that it does generate and show an oops without this - and then land it!