[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Review/Sponsor ITP for libxmlb



> -----Original Message-----
> From: Steve McIntyre <steve@einval.com>
> Sent: Tuesday, February 5, 2019 9:51 AM
> To: Limonciello, Mario
> Cc: mak@debian.org; debian-efi@lists.debian.org
> Subject: Re: Review/Sponsor ITP for libxmlb
> 
> 
> [EXTERNAL EMAIL]
> 
> On Tue, Feb 05, 2019 at 03:46:18PM +0000, Mario.Limonciello@dell.com wrote:
> > From: Steve McIntyre <steve@einval.com>
> >>
> >> As we're short of time to get this in for Buster, I've fixed up a few
> >> things on the Debian branch, tagged, and uploaded. Fixes:
> >>
> >> f8dcc49 Medium urgency for upload
> >> 369ff58 Update to a current Standards-Version
> >> 5e5dbf3 Tweak maintainer name: Debian EFI team
> >> 542478d Fix typo in ITP bug#
> >
> >Appreciated.  In terms of operational timing now, should I wait until it clears
> >NEW to build a new fwupd against it?  Or should that happen now?
> 
> Until it's cleared NEW it's not in the archive at all, so there's no
> point at all - the new fwupd will then be totally blocked. I'm hoping
> ftpmaster will be kind to us and get us out of NEW quickly...
> 

Right, at least in Ubuntu-land that's OK, it just stays blocked in proposed until it can
build.  It also ends up putting pressure on AA to review/release the thing in NEW for
it.  Wasn't sure if that's appropriate in Debian and why I was asking.

I'll get the packaging ready in the debian-next branch and it should hopefully just be
a matter of pulling the trigger when released from NEW.


Reply to: