| 15 Jan 2019 |
 andrewsh | 😀 | 08:40:07 |
 richvdh | andrewsh: what can we do to get 0.34.0.1 or better into stretch-backports asap? | 11:15:41 |
| andrewsh | why ASAP? | 11:15:52 |
| andrewsh | the fix is there | 11:15:56 |
| richvdh | is where? | 11:16:14 |
| andrewsh | I cherry-picked the patch | 11:16:17 |
| andrewsh | which I said in TWIM | 11:16:23 |
| andrewsh | and here | 11:16:26 |
| andrewsh | erm | 11:16:33 |
| andrewsh | not here, but elsrewhere | 11:16:37 |
| richvdh | oh, you backported it to 0.34.0 | 11:16:43 |
| richvdh | ok | 11:16:45 |
| richvdh | sorry, I missed that then | 11:16:49 |
| andrewsh | I decided to postpone the Python 3 upload to until 0.34.1.1 reaches testing | 11:17:37 |
| andrewsh | since the packages were not built anyway when I was looking | 11:18:13 |
| andrewsh | treq and frozendict | 11:18:21 |
| andrewsh | not built, installed | 11:18:24 |
| andrewsh | and the policy says you should only backport things from testing | 11:18:40 |
| richvdh | yup, makes sense. I'm now just a bit concerned that "am I on an affected version" now has a complicated answer | 11:18:56 |
| andrewsh | indeed | 11:46:37 |
| richvdh | was there a particular reason for backporting to 0.34.0 rather than picking up the 0.34.0.1 fix? | 11:49:56 |
| richvdh | also: looks like the version in testing is still unpatched? | 11:50:46 |
| andrewsh | yes: patching is not (formally) introducing a new upstream package version | 12:01:19 |
| andrewsh | re testing: https://qa.debian.org/excuses.php?package=matrix-synapse | 12:01:35 |
| andrewsh | I made a mistake and set urgency=medium | 12:01:46 |
| andrewsh | which means migration takes 5 days | 12:01:53 |
| richvdh | that's not ideal | 12:02:31 |
| andrewsh | while I could either bump it by uploading a new no-change package or ask for an override, I’m not sure that’s very bad | 12:02:49 |
| richvdh | I guess it will get fixed in the next 24 hours anyway | 12:02:54 |
| andrewsh | yes | 12:03:03 |
