Activity log for bug #1829944

Date Who What changed Old value New value Message
2019-05-22 00:21:07 Robert C Jennings bug added bug
2019-05-22 00:23:29 Launchpad Janitor merge proposal linked https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/367728
2019-05-22 00:23:31 Launchpad Janitor merge proposal linked https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/367729
2019-05-22 00:25:42 Robert C Jennings description When there is an error with the apt proxy the headers are not returned which makes debugging hard. [Impact] When there is an error with the apt proxy the headers are not returned which makes debugging hard. [Test Case] This was tested on xenial when the release lacked the InRelease file by-hash. It's hard to test otherwise unless there are problems with the archive. [Regression Potential] Low. This was tested on xenial when the release lacked the InRelease file by-hash. Also, this code is not yet in use.
2019-05-22 08:31:50 Tobias Koch description [Impact] When there is an error with the apt proxy the headers are not returned which makes debugging hard. [Test Case] This was tested on xenial when the release lacked the InRelease file by-hash. It's hard to test otherwise unless there are problems with the archive. [Regression Potential] Low. This was tested on xenial when the release lacked the InRelease file by-hash. Also, this code is not yet in use. [Impact] When there is an error with the apt proxy the headers are not returned which makes debugging hard. [Test Case] This was tested on xenial when the release lacked the InRelease file by-hash. This can be verified manually as follows: * Start the proxy via ./magic-proxy -t `python -c "import time; print(int(time.time() - 300))"` * In an empty directory do mkdir -p ubuntu/dists/xenial/by-hash/SHA256 touch ubuntu/dists/xenial/InRelease python3 -m http.server * In a separate terminal telnet to port 8080 and paste GET /ubuntu/dists/xenial/InRelease HTTP/1.1 HOST: localhost:8000 followed by an empty line. Without the patch, the response will be the string "No InRelease file found for given mirror, suite and timestamp". With the patch applied, the response will start with a HTTP status line "HTTP/1.0 404 Not Found" and a set of HTTP headers. [Regression Potential] Low. This was tested on xenial when the release lacked the InRelease file by-hash. Also, this code is not yet in use.
2019-05-23 00:31:25 Michael Hudson-Doyle nominated for series Ubuntu Disco
2019-05-23 00:31:25 Michael Hudson-Doyle bug task added livecd-rootfs (Ubuntu Disco)
2019-05-23 04:27:02 Launchpad Janitor livecd-rootfs (Ubuntu): status New Fix Released
2019-05-23 20:42:46 Steve Langasek livecd-rootfs (Ubuntu Disco): status New Fix Committed
2019-05-23 20:42:47 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2019-05-23 20:42:51 Steve Langasek bug added subscriber SRU Verification
2019-05-23 20:42:54 Steve Langasek tags verification-needed verification-needed-disco
2019-05-23 21:42:48 Robert C Jennings tags verification-needed verification-needed-disco verification-done verification-done-disco
2019-05-28 20:37:54 Launchpad Janitor livecd-rootfs (Ubuntu Disco): status Fix Committed Fix Released
2019-05-28 20:38:03 Steve Langasek removed subscriber Ubuntu Stable Release Updates Team