Re: +1 maint - phpunit 9 bootstrap proposal

2021-02-03 Thread Bryce Harrington
On Wed, Jan 27, 2021 at 05:50:14PM -0800, Bryce Harrington wrote: > On Wed, Jan 27, 2021 at 01:40:48PM -0800, Bryce Harrington wrote: > > Brief update: > > > > I've gotten most everything passing now, except composer and > > php-http-request2. > > > > My best guess is that these two packages'

Re: Call for testing: 20.04.2 release candidate images ready!

2021-02-03 Thread Brian Murray
On Wed, Feb 03, 2021 at 06:37:13PM +, Ian Bruntlett wrote: > Hi Lukasz, > > On the page > http://iso.qa.ubuntu.com/qatracker/milestones/420/builds/226354/downloads > "Download links for Ubuntu Desktop amd64", there is a minor error. It > refers to "MD5 checksum" and it should refer to "SHA256

Re: Setting NotAutomatic for hirsute+1-proposed

2021-02-03 Thread Iain Lane
On Thu, Jan 21, 2021 at 02:15:59AM -0800, Julian Andres Klode wrote: > Hi people, > > I'd like to suggest that we start setting NotAutomatic: yes for the > proposed pocket with hirsute+1, such that things like SRU verification > will be easier, and all those people who enable proposed in

addressing universe/multiverse merges in +1 maintenance

2021-02-03 Thread Matthias Klose
With the feature and Debian import freeze approaching in about three weeks, I'd like to propose to also address universe/multiverse merges in our +1 maintenance tasks within these three weeks. There's a lot untouched for more than one or two years. For merges of the main pocket, owned by the

+1 maintenance

2021-02-03 Thread Matthias Klose
- removal of NBS in -proposed - looked at some "uninstallable" packages, two of them were caused by ftbfs of dependent packages. successfully retried builds. - looked at openmpi and connected transitions - very puzzled about the dolfin ftbfs ... - finally found out that openmpi needed a

Re: General mechanism to supply "rich history" to git-ubuntu

2021-02-03 Thread Robie Basak
On Wed, Feb 03, 2021 at 10:23:37AM +0100, Julian Andres Klode wrote: > On Tue, Feb 02, 2021 at 01:03:23PM +, Robie Basak wrote: > > We need the Refs field because git is designed not to be able to fetch a > > commit by hash, but by a ref that can reach it only. So Vcs-Git-Refs > > must specify