Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 4499:431bf4e7d3d7 1.4.18
- release preparation
- upgrading docs contains script to find affected issues and how to fix
these
| author | Ralf Schlatterbeck <schlatterbeck@users.sourceforge.net> |
|---|---|
| date | Sun, 29 May 2011 19:35:41 +0000 |
| parents | 47bd330e3d17 |
| children | 9f488541802f |
comparison
equal
deleted
inserted
replaced
| 4498:8df9492c2746 | 4499:431bf4e7d3d7 |
|---|---|
| 10 then you don't need to do anything. If you're upgrading from 0.5.6 to | 10 then you don't need to do anything. If you're upgrading from 0.5.6 to |
| 11 0.6.8 though, you'll need to check the "0.5 to 0.6" and "0.6.x to 0.6.3" | 11 0.6.8 though, you'll need to check the "0.5 to 0.6" and "0.6.x to 0.6.3" |
| 12 steps. | 12 steps. |
| 13 | 13 |
| 14 .. contents:: | 14 .. contents:: |
| 15 | |
| 16 Migrating from 1.4.16 to 1.4.17 | |
| 17 =============================== | |
| 18 | |
| 19 There was a bug in 1.4.16 where files were unlinked from issues if a | |
| 20 mail without attachment was received via the mail interface. The | |
| 21 following script will list likely issues being affected by the bug. | |
| 22 The date in the script is the date of the 1.4.16 release. If you have | |
| 23 installed 1.4.16 later than this date, you can change the date | |
| 24 appropriately to your installation date. Run the script in the directory | |
| 25 of your tracker. | |
| 26 | |
| 27 #!/usr/bin/python | |
| 28 import os | |
| 29 from roundup import instance | |
| 30 from roundup.date import Date | |
| 31 dir = os.getcwd () | |
| 32 tracker = instance.open (dir) | |
| 33 db = tracker.open ('admin') | |
| 34 # you may want to change this to your install date to find less candidates | |
| 35 last_release = Date('2011-05-13') | |
| 36 affected = {} | |
| 37 for i in db.issue.getnodeids(): | |
| 38 for j in db.issue.history(i): | |
| 39 if i in affected: | |
| 40 break | |
| 41 if j[1] < last_release or j[3] != 'set' or 'files' not in j[4]: | |
| 42 continue | |
| 43 for op, p in j[4]['files']: | |
| 44 if op == '-': | |
| 45 affected [i] = 1 | |
| 46 break | |
| 47 print ', '.join(sorted(affected.iterkeys())) | |
| 48 | |
| 49 To find out which files where attached before you can look in the | |
| 50 history of the affected issue. For fixing issues you can re-attach the | |
| 51 files in question using the "set" command of roundup-admin, e.g., if the | |
| 52 list of files attached to an issue should be files 5, 17, 23 for issue42 | |
| 53 you will set this using | |
| 54 | |
| 55 roundup-admin -i /path/to/your/tracker set issue42 files=5,17,23 | |
| 15 | 56 |
| 16 Migrating from 1.4.x to 1.4.17 | 57 Migrating from 1.4.x to 1.4.17 |
| 17 ============================== | 58 ============================== |
| 18 | 59 |
| 19 There is a new config-option `migrate_passwords` in section `web` to | 60 There is a new config-option `migrate_passwords` in section `web` to |