On Thu, Dec 5, 2019 at 1:34 AM Bryce Harrington <[email protected]> wrote: > > == Proposed Migration == > > walinuxagent > - blocked by LP: #1851064 (block-proposed SRU), as mentioned by paride > - this tag was added recently (11-27) but not spotting rationale? > > mod-wsgi > - Retriggered build with glibc/2.30 > > byobu > - Build failed for amd64 because upstream renamed README to README.md > in this release, but debian/docs still specifies "README" > -> I have a fix but can't push branch to git.launchpad.net for some > reason: "fatal: remote error: Path translation timed out."
That git push problem is a known issue when you push a repo that is based on an existing one. Unfortunately that is a common case with git-ubuntu, I had the same last week. A temporary workaround seem to be repacking refs often on the server side. I know that cjwatson and wgrant are on this already, so I added them to CC, to share updates (if available). > postgresql-common -> php-horde-db > - autopkgtest is failing during database setup: > PHP Fatal error: Declaration of Horde_Db_Adapter_TestBase::setUp() > must be compatible with PHPUnit\Framework\TestCase::setUp(): void in > > /tmp/autopkgtest.lh5Xz0/build.jTq/src/Horde_Db-2.4.0/test/Horde/Db/Adapter/TestBase.php > on line 1184 > - No fix evident in Debian's php-horde-db yet. > - Poking around, best guess is this is caused by the phpunit 8.4.3 > that has hit focal-proposed. In phpunit8, setUp() functions need to > have a ": void" specified in order to match the base class decl. > I've not verified this fixes the tests, but it seems likely. > Looks like 7 test cases need updated. Guessing other php packages > could be similarly affected. Ref.: > + https://thephp.cc/news/2019/02/help-my-tests-stopped-working > + > http://laravel-school.com/posts/php-fatal-error-declaration-of-teststestcasesetup-must-be-compatible-36 > > > == Triage == > > Bugs last updated on 2019-12-03 (Tuesday) > Date range identified as: "Wednesday triage" > Found 19 bugs > > ...most of which were updates from merge activity from the team, or > triaging actions. The few that needed triage action: > > LP: #1854841 - (New) [containerd] - Update to containerd 1.3.1 > * Turns out containerd has an SRU special exception granted via > Docker.io, so this bug is ok to do as requested. > -> Added SRU template needed as per Docker.io policy > -> Marked bug triaged/high, tagged to server-next and subbed ubuntu-server > > LP: #1854880 - (Triaged) [mysql-8.0] - Conflicting Transaction > Sets following Complete Outage of InnoDB Cluster > * Regression in release > * No patch available from upstream yet, but workaround identified > -> Updated bug description and linked upstream report > > LP: #1785383 - *(Triaged) [dnsmasq] - missing EDNS0 record > confuses systemd-resolved > * Bug impacts both dnsmasq and systemd; latter doesn't have a fix yet, > but there is an upstream patch for dnsmasq. > * Reviewed dnsmasq patch, which looks ok to consider for SRU > -> Updated bug for SRUing, tagged to server-next > > > > == Backlog == > Found 2 bugs > > LP: #1795420 - (Triaged) [keepalived] - [SRU] Keepalived update > from 1.2.19 to 1.2.24 breaks support for /dev/tcp health check > --> Still valid for SRU; already in server-next > > LP: #1831773 - (Triaged) [mysql-5.7] - High CPU usage, MySQL > process got stuck on SHOW SESSION VARIABLES LIKE 'FOREIGN_KEY_CHECKS' > * Has been fixed upstream, commits provided > -> Outlined next actions for SRU & added to server-next > > -- > ubuntu-server mailing list > [email protected] > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
