=== Feren^IRCCloud_ is now known as Feren^IRCCloud
=== hikiko is now known as hikiko|ln
=== Ken is now known as Guest14755
=== scottt is now known as Guest41818
=== hikiko|ln is now known as hikiko
attentehi, i'm trying to sru bubblewrap to xenial: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/164933015:57
ubot5`Ubuntu bug 1649330 in bubblewrap (Ubuntu) "[SRU] bubblewrap unavailable on xenial" [Undecided,New]15:57
attentei'm not sure what the process is for sru'ing a new package there, is there something i need to do? i don't have upload rights15:58
rbasakattente: there's not much of a defined process as it's a pretty rare thing. You'll need sponsorship, an archive admin's approval, and an SRU team member's approval.16:02
rbasakattente: and you'll need to prepare the upload.16:02
rbasakI won't know what ordering to recommend.16:03
rbasakdon't know16:03
rbasakIf it were me, I'd seek approval from everyone involved before getting a sponsor to upload, since that avoids tangling stuff up with Launchpad technicalities.16:03
rbasakThe archive admin and SRU team member may be the same person, I don't know.16:04
rbasakHope that helps.16:04
rbasakAnd I'd prepare the proposed upload in a git or bzr tree, so that every reviewer can review in one place instead of the scattergun-and-reject-from-the-queue approach.16:04
attenterbasak: ok, thanks16:05
rbasakattente: OTOH, consider using the backports pocket, but I presume you've already ruled that out for some reason?16:07
attenterbasak: i believe the integration tests don't run in an environment with backports enabled16:08
attenterbasak: (this is for a snapcraft branch)16:08
rbasakIf that's the only reason, it sounds like the integration tests need fixing to work with backports, rather than putting the package in updates just because of that.16:10
attenteis it ok to generally assume that backports will be enabled on a user's machine?16:11
attenteif this branch gets merged, then snapcraft on xenial will require that once that's sru'd16:12
rbasakI believe backports is generally available by default but pinned from packages from it being used except when specifically requested.16:12
rbasakIf snapcraft is in updates, it shouldn't have a dependency on backports.16:12
rbasakSo that's a more solid reason that this needs to go into updates.16:12
rbasak(or it's a reason that snapcraft should have been in backports, depending on your perspective)16:12
attentesnapcraft is generally sru'd back to xenial, right?16:13
rbasakI don't know.16:13
attentei see for example: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/161432216:14
ubot5`Ubuntu bug 1614322 in snapcraft (Ubuntu Yakkety) "[SRU] New stable micro release 2.15" [Undecided,Fix released]16:14
attenteso my impression is that backports might not be enough for this case16:15
rbasakIt does sound that way.16:17
attenterbasak: would it be frowned upon if i copied the packaging from yakkety's or zesty's archive?16:22
rbasakattente: no, that's absolutely fine.16:23
rbasakattente: just add a new changelog entry to the top, and get the package versioning right. Assuming it works :-)16:23
attenterbasak: sounds good, thanks! :)16:23
=== scottt is now known as Guest87990

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!