=== nudtrobert1 is now known as nudtrobert
=== kickinz1 is now known as kickinz1|lunch
=== kickinz1|lunch is now known as kickinz1
[13:48] <sil2100> Hello! I'm looking for some ubuntu archive admins that could help approving the addition of new binary packages in a landing that's waiting for approval in the CI Train
[13:48] <sil2100> The packaging diff already got approved by kenvandine, we now need someone to +1 the new binary packages that will appear after publishing
[13:48] <sil2100> The packaging diff:
[13:48] <sil2100> https://ci-train.ubuntu.com/job/ubuntu-landing-010-2-publish/80/artifact/unity-scopes-api_packaging_changes.diff
[14:38] <cyphermox> if someone could review this network-manager SRU ^, it's long overdue :)
[14:51] <tjaalton> could someone ack the new binaries of mesa-lts-vivid for trusty-proposed
[15:07] <pitti> tjaalton: done
[15:21] <tjaalton> pitti: nice, thanks
[15:28] <utlemming> hi all...question on the backports process. I've upload open-vm-tools for {trusty,vivid}-backports and its sitting in the queue. The wiki is unclear as to who approves. Is it the release team or the backports team?
[15:28] <utlemming> or can an SRU team member approve it?
=== kickinz1 is now known as kickinz1|eod
=== kickinz1|eod is now known as kickinz1
[17:01] <infinity> utlemming: Backports are the backport team, but the more interesting question would be why are you using backports for that?
[17:02] <infinity> utlemming: Backports isn't appropriate for anything we'll end up "supporting" (ie: if you're putting it in images, or encouraging customers to use it).
[17:38] <utlemming> infinity: oh, no way am I putting that in images. I just backported it because people are asking about it.
[17:39] <infinity> utlemming: Kay.  So, yeah, backports are the backports team, I don't touch 'em.
[21:34] <doko> can't find any email about the rejection of binutils 2.24-5ubuntu14 for trusty. can I re-read the reason ?