User1: can someone please reject my musescore upload in Xenial? I did the version numbering incorrectly :(
User1: please reject the first one and approve the second one :3
User2: infinity, Morning
User2: infinity, I've got a couple of package deletions for Yakkety.
User2: https://bugs.launchpad.net/ubuntu/+source/mate-netspeed/+bug/1584769
User3: Launchpad bug 1584769 in mate-netspeed (Ubuntu) "Please remove mate-netspeed from the Yakkety archive, it is now included in mate-applets" [Undecided,New]
User2: https://bugs.launchpad.net/ubuntu/+source/gnome-main-menu/+bug/1584767
User3: Launchpad bug 1584767 in gnome-main-menu (Ubuntu) "Please remove gnome-main-menu from the Yakkety archive, it is obsolete" [Undecided,New]
User4: hello, please reject "s390-tools (xenial-proposed/main) [1.34.0-0ubuntu8 => 1.34.0-0ubuntu8.1] (no packageset)"
User4: will reupload with one more bugfix
User5: xnox, done
User4: thanks
User6: cjwatson hey, sorry to bug you but I uploaded a package on Friday and can't find it, this is all I have "[ubuntu/xenial-proposed] snapcraft 2.10 (Waiting for approval)"
User7: User6 it's in https://launchpad.net/ubuntu/xenial/+queue?queue_state=1 awaiting SRU team approval
User6: cjwatson I swear I checked there :-/ Thanks!
User8: User9 I got emails about possible SRU regresisons (multiple mails actually :-)), but I think they're nothuing new.
User9: User8 I agree about the regressions not being new issues.  I'll look into why you got multiple emails too.
User6: infinity hi there, can I get snapcraft allowed into xenial-proposed?
User5: sergiusens, the exception for that has all sorts of QA requirements, where are you documenting they are complete?  I don't see anything in the first couple of bugs.
User6: apw are you talking about https://wiki.ubuntu.com/StableReleaseUpdates#Snapcraft ?
User5: sergiusens, yep that one
User6: apw everything change lands with a test in code (snapcraft.tests for unit tests, integration_tests and/or demo_tests)
User5: sergiusens, right but the SRU is supposed to indicate that all of the steps on https://wiki.ubuntu.com/SnapcraftUpdates have been completed
User10: User5 QA here. Everything for this release is tested in autopkgtests. Once it gets to proposed, I do a manual verification.
User6: apw but our package hasn't been built yet, it is stuck in the unnapproved queue
User5: sergiusens, i was unable to find that easily, so i was asking where as i was sure infinity will ask
User6: apw https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=snapcraft
User5: sergiusens, ahh ok the write up there is not well worded as i took it to mean before queueig, and yet in there is says -proposed, so ... ignore me
User6: elopio mind rewording a bit ^ ?
User10: User5 we do parts before it gets to proposed, and parts after it gets to proposed. I thought that by proposing it, we were saying that we followed the process.
User10: User5 I'm happy to make this clearer, just not sure how. Should I comment on every bug the tests we did before proposing it?
User4: elopio, apw, sergiusens - autopkgtests do run from silos. you should get a silo assigned, upload for xenial sru, which will build and run packages.
User4: then sru team can copy that into -proposed.
User4: autopkgtests will run again, and things will publish in -proposed
User4: and then migrate to -updates if all is good.
User4: please use silos in the future, and then you can satisfy everything upfront.
User10: User4 we run the autopkgtests in jenkins. That works the same as putting the package in the silo, afaik. I'm not sure what we will win by that extra step.
User4: elopio, not needing jenkins =) and the fact that SRU team has no visibility into jenkins, but do have visibility into http://autopkgtest.ubuntu.com/
User4: and that you don't need to block on stable release updates team accepting your package, to see if it will be accepted. as silo assgniment is self-service.
User4: and it's the same binary that will be used into the -updates pocket, as the one build in silo.
User4: things built in jenkins, are obviously thrown away =)
User10: User4 so if we put the package in a silo, and it passes the autopkgtests there, it will get to proposed without any manual step?
User4: elopio, there is manual step still. but there are less questions about those =)
User4: as in, it's more trivial to process then opaque thing. as above.
User4: *than
User10: User4 if it simplifies things, I'm not against doing that. But I still don't understand some things, like, I don't see any results from silos in autopkgtest.ubuntu.com.
User10: what we are trying to explain in the SRU exception page is that no PR lands into master if the autopkgtests don't pass.
User6: xnox I cannot dput to silos
User4: sergiusens, i know i can.
User6: xnox we are trying to move people away from the equation, not add them
User4: sergiusens, do you release from git/bzr branches? silos can just take that, merge branches for you and throw things into a silo...
User6: xnox I can dput to the archives but not that train ting
User4: sergiusens, and e.g. i think it's easy to get right sto dput thing sinto silos.
User6: xnox yes, git branches on gitub
User4: sergiusens, e.g. i can dput to silos.
User6: github
User4: silos can take things from github direct, without $someone in the middle generating things and dput things
User6: xnox I don't want to depend on people being around, I already have to chase people down to get the darn package accepted.
User4: sergiusens, talk to sil2100 to get dput permissions into silos.
User6: xnox does it still mangle changelogs and versions?
User4: sergiusens, yes, that's what i'm trying to reduce too!
User6: xnox last I talked to him he said it wasn't possible
User4: silos are entirely self-service.
User4: i'm sure it is, cause i can dput stuff =/
User4: into silos
User6: xnox yeah, they let core devs dput to silos, no one else
User4: sergiusens, oh y, r u not core dev? =)
User6: xnox no, just ppu
User11: User6 hey! Policies changed a bit, if you have PPU access for some packages then we can give you direct-silo upload permissions
User11: User6 we generally do not want to give those powers right now to people that we don't know
User11: User6 let me add you in a minute
User6: sil2100 xnox ok, I'll do that for the next upload then
User6: I consider this one running under the agreed upon course
User6: it would be good to see the StableReleaseUpdates wiki page mention the fact that silos are now required
User6: slangasek ^
User4: sergiusens, they are not required.
User4: but they help you, satisfy your requirements.
User6: xnox ah, then I'll probably pass. We already satisfy our requirements
 * apw regrets muddying the water
User4: general srus are one-off, for unique bugs, and hence upload to unapproved queue, wait forever, test whenever, release whenever is good enough.
User4: sergiusens, well, not quite.
User6: xnox we have an exception
User4: sergiusens, silo is self-service, and will allow you to do all the testing sans las publications, and you will find your reviewes from a silo copy of binaries to be done reqlly quickly.
User4: instead of always being stuck for 1-5 weeks in the SRU unapproved queue.
User4: even though you do satisfy requirements.
User6: xnox so far we've gone from initial upload to publication in 3 days
User4: #toolong =)
User12: User4 Err, since when do silo SRUs get reviewed "really quickly"?
User4: silos get same day publication, and you essentially can do manual testing straight away, and autopkgtest testing is done straight away.
User4: infinity, you are back =)
User12: User4 The SRU team tends to hate reviewing copies. :P
User4: infinity, how alive are you? =)
User4: or just really good meds?
 * apw hits the rewind time button, and keeps quiet
User12: I'm about 60% alive.
 * xnox passes infinity +5 hp healing potion
User4: infinity, i guess it's up to you if you want to see bi-weekly snappy SRU as a source dput, or a copy.
User4: one might not build, might fail tests, might fail autopkgtest - the other one managed to pass all that, just before a copy.
User7: User4 it might be a good idea to check what the SRU team wants before spending ages advising people what to do :-)
User7: the problem with copies is mainly the age-old one that it's a pain to get diffs for them
User7: (which is an LP bug, and so my problem, sure, but it's Hard)
User12: User7 Soyuz Redesign!
ubuntu-release
Ubuntu IRC