Activity log for bug #1905634

Date Who What changed Old value New value Message
2020-11-25 23:52:13 dann frazier bug added bug
2020-11-25 23:52:24 dann frazier nominated for series Ubuntu Focal
2020-11-25 23:52:24 dann frazier bug task added sbuild-launchpad-chroot (Ubuntu Focal)
2020-11-25 23:52:24 dann frazier nominated for series Ubuntu Bionic
2020-11-25 23:52:24 dann frazier bug task added sbuild-launchpad-chroot (Ubuntu Bionic)
2020-11-25 23:52:35 dann frazier sbuild-launchpad-chroot (Ubuntu): status New Fix Released
2020-11-25 23:52:40 dann frazier sbuild-launchpad-chroot (Ubuntu Bionic): status New In Progress
2020-11-25 23:52:43 dann frazier sbuild-launchpad-chroot (Ubuntu Focal): status New In Progress
2020-11-25 23:52:46 dann frazier sbuild-launchpad-chroot (Ubuntu Focal): assignee dann frazier (dannf)
2020-11-25 23:52:48 dann frazier sbuild-launchpad-chroot (Ubuntu Bionic): assignee dann frazier (dannf)
2020-11-26 00:13:49 dann frazier description [Impact] Currently sbuild-launchpad-chroot fails to build/run in bionic because of bug 1892879, where a backport of ubuntu-dev-tools to bionic accidentally dropped the python2 bindings this package uses. Since this package has been collaterally damaged for months, I propose that we use the same justification used for bug 1892879 and go ahead and update s-b-c to a newer upstream that works with the python3 bindings. Specifically, I suggest we backport the version from groovy to focal and bionic. (The version in hirsute has only non-functional differences that would require extra backporting). Other than moving to python3, all other changes to the source are fixes that have already been SRU'd back to bionic (bug 1872163, bug 1852677, bug 1858458), except for the addition of Vcs tags to debian/control. [Test Case] Test out all 3 commands on all supported releases: for rel in xenial bionic focal groovy hirsute; do sbuild-launchpad-chroot create -n ${rel} -s ${rel} -a $(dpkg --print-architecture) sbuild-launchpad-chroot update -n ${rel} sbuild-launchpad-chroot remove -n ${rel} done [Where Problems May Occur] It's possible there are some different behaviors in the underlying python2/python3 behavior that could cause an unexpected difference. I did check that downloading via proxy still works fine - but perhaps there are other such issues I didn't think to check. [Impact] Currently sbuild-launchpad-chroot fails to build/run in bionic because of bug 1892879, where a backport of ubuntu-dev-tools to bionic accidentally dropped the python2 bindings this package uses. Since this package has been collaterally damaged for months, I propose that we use the same justification used for bug 1892879 and go ahead and update s-b-c to a newer upstream that works with the python3 bindings. Specifically, I suggest we backport the version from groovy to focal and bionic. (The version in hirsute has only non-functional differences that would require extra backporting). Other than moving to python3 (which required minimal changes), all other changes to the source are fixes that have already been SRU'd back to bionic (bug 1872163, bug 1852677, bug 1858458), except for the addition of Vcs tags to debian/control. [Test Case] Test out all 3 commands on all supported releases: for rel in xenial bionic focal groovy hirsute; do   sbuild-launchpad-chroot create -n ${rel} -s ${rel} -a $(dpkg --print-architecture)   sbuild-launchpad-chroot update -n ${rel}   sbuild-launchpad-chroot remove -n ${rel} done [Where Problems May Occur] It's possible there are some different behaviors in the underlying python2/python3 behavior that could cause an unexpected difference. I did check that downloading via proxy still works fine - but perhaps there are other such issues I didn't think to check.
2020-11-30 21:55:06 dann frazier description [Impact] Currently sbuild-launchpad-chroot fails to build/run in bionic because of bug 1892879, where a backport of ubuntu-dev-tools to bionic accidentally dropped the python2 bindings this package uses. Since this package has been collaterally damaged for months, I propose that we use the same justification used for bug 1892879 and go ahead and update s-b-c to a newer upstream that works with the python3 bindings. Specifically, I suggest we backport the version from groovy to focal and bionic. (The version in hirsute has only non-functional differences that would require extra backporting). Other than moving to python3 (which required minimal changes), all other changes to the source are fixes that have already been SRU'd back to bionic (bug 1872163, bug 1852677, bug 1858458), except for the addition of Vcs tags to debian/control. [Test Case] Test out all 3 commands on all supported releases: for rel in xenial bionic focal groovy hirsute; do   sbuild-launchpad-chroot create -n ${rel} -s ${rel} -a $(dpkg --print-architecture)   sbuild-launchpad-chroot update -n ${rel}   sbuild-launchpad-chroot remove -n ${rel} done [Where Problems May Occur] It's possible there are some different behaviors in the underlying python2/python3 behavior that could cause an unexpected difference. I did check that downloading via proxy still works fine - but perhaps there are other such issues I didn't think to check. [Impact] Currently sbuild-launchpad-chroot fails to build/run in bionic because of bug 1892879, where a backport of ubuntu-dev-tools to bionic accidentally dropped the python2 bindings this package uses. Since this package has been collaterally damaged for months, I propose that we use the same justification used for bug 1892879 and go ahead and update s-b-c to a newer upstream that works with the python3 bindings. Specifically, I suggest we backport the version from groovy to focal and bionic. (The version in hirsute has only non-functional differences that would require extra backporting). Other than moving to python3 (which required minimal changes), all other changes to the source are fixes that have already been SRU'd back to bionic (bug 1872163, bug 1852677, bug 1858458), except for the addition of Vcs tags to debian/control. [Test Case] Test out all 3 commands on all supported releases: for rel in xenial bionic focal groovy hirsute; do   sbuild-launchpad-chroot create -n ${rel} -s ${rel} -a $(dpkg --print-architecture)   sbuild-launchpad-chroot update -n ${rel}   sbuild-launchpad-chroot remove -n ${rel} done [Where Problems May Occur] For focal, the only diff ends up being to the changelog because all fixes from groovy have already been backported to focal. But we need to bump the version so that it will be > the bionic version. For bionic, it's possible there are some different behaviors in the underlying python2/python3 behavior that could cause an unexpected difference. I did check that downloading via proxy still works fine - but perhaps there are other such issues I didn't think to check.
2021-01-12 17:51:47 Brian Murray sbuild-launchpad-chroot (Ubuntu Focal): status In Progress Fix Committed
2021-01-12 17:51:50 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2021-01-12 17:51:52 Brian Murray bug added subscriber SRU Verification
2021-01-12 17:51:57 Brian Murray tags verification-needed verification-needed-focal
2021-01-12 18:15:12 Brian Murray sbuild-launchpad-chroot (Ubuntu Bionic): status In Progress Fix Committed
2021-01-12 18:15:19 Brian Murray tags verification-needed verification-needed-focal verification-needed verification-needed-bionic verification-needed-focal
2021-01-12 23:27:36 dann frazier tags verification-needed verification-needed-bionic verification-needed-focal verification-done verification-done-bionic verification-done-focal
2021-01-20 12:36:53 Pedro Principeza bug added subscriber Pedro Principeza
2021-01-21 16:39:46 Launchpad Janitor sbuild-launchpad-chroot (Ubuntu Focal): status Fix Committed Fix Released
2021-01-21 16:39:51 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2021-01-21 16:47:15 Launchpad Janitor sbuild-launchpad-chroot (Ubuntu Bionic): status Fix Committed Fix Released