Skip to main content
  1. Blog
  2. Article

Canonical
on 16 August 2017

Ubuntu Foundations Development Summary – August 16, 2017


This newsletter is to provide a status update from the Ubuntu Foundations Team. There will also be highlights provided for any interesting subjects the team may be working on. If you would like to reach the Foundations team, you can find us at the #ubuntu-devel channel on freenode.

Highlights

The State of the Archive

  • After no small amount of effort, the perl 5.26 and gcc-7 transitions migrated to artful on the 10th, unblocking many of the packages that had been stuck in -proposed.
  • As GCC 7 is now the default compiler in artful, the build failures reported at https://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-gcc7-artful.html now apply to 17.10. Please help us resolve these failing packages for the release.
  • Next in line we have the Qt 5.9 transition. Look for more news about this next week!

Upcoming Ubuntu Dates

Weekly Meeting

Related posts


anusha-c
24 July 2026

A day in the life of an Android developer with Anbox Cloud

Ubuntu Article

Meet Alex, an Android developer. In this article, we’ll follow Alex through their day to show you how Anbox Cloud supports Alex from feature development to release. Alex’s focus for today is building a ride-tracking feature for their ride-sharing app. ...


Holly Hall
21 July 2026

Canonical announces the Enterprise Store as part of Ubuntu Pro

Ubuntu Article

Canonical introduces a new way to manage software behind firewalls and in air-gapped environments with the Enterprise Store. The Enterprise Store makes software distribution manageable and scalable behind firewalls or in air-gapped environments. Available with an Ubuntu Pro subscription, the Enterprise Store respects the security protocol ...


Lidia Luna Puerta
17 July 2026

Tracing a memory leak bug in PID 1 and contributing an upstream fix: a Linux support story

Ubuntu Article

How Canonical Support helped a global retail organization trace the cause for an unusual memory leak originating in PID 1. By investigating the issue across three separate system layers our team was able to identify the source and fast-track a patch. ...