/srv/irclogs.ubuntu.com/2015/04/03/#ubuntu-release.txt

robruHey release team, does this change need an FFe? https://ci-train.ubuntu.com/job/ubuntu-landing-006-2-publish/81/artifact/libqtdbusmock_packaging_changes.diff/*view*/ it technically adds new features but they're only used for testing as far as I can tell, shouldn't affect the image really01:30
infinityrobru: I wonder what "futher" is.01:32
robruinfinity: new NSA spying tools surely.01:33
infinityrobru: Anyhow, that sure likes like features to me, but without seeing the actual diff, who can say how invasive it is.01:34
robruinfinity: https://ci-train.ubuntu.com/job/ubuntu-landing-006-2-publish/lastSuccessfulBuild/artifact/libqtdbusmock_content.diff/*view*/ here's the full diff01:35
infinityrobru: THat said, I assume from the package name that the whole thing is just a mocking tool, so if things that use it for tests don't all regress, it's probably fine.01:35
robruinfinity: that's what I was thinking01:35
infinityrobru: So, the output of "reverse-depends -b src:libqtdbusmock" is rather short.01:36
infinityrobru: If there's any concern at all, copy all of those into the same silo, see if they build and pass their testsuites, then delete them before you publish.01:36
robruinfinity: looks right to me (although I'm not intimiately familiar). it is a newish tool01:36
robruinfinity: define concern? is it not ok to just publish this and let the regular proposed-migration decide whether it regresses or not?01:37
infinityrobru: p-m won't notice this sort of regression, unless all those rdeps happen to have autopkgtests that rebuild the packages and rerun the testsuites.  Which they might, but might not.01:37
infinityrobru: I dunno, I'm not hugely concerned.  It's the same upstreams (more or less) for all of this, so if they broke their own testing tool, they'll find out soon enough. :P01:38
robruinfinity: well indicator-network is already part of the same silo and it passed the build & also went through qa already01:38
infinityrobru: Did it pull in the new libqtdbusmock when it built, though?01:39
robruinfinity: hm, let me check that...01:39
* infinity looks for a build log.01:39
infinityYup, it did.01:40
infinityThat satisfies me, then.01:40
robruinfinity: yeah just grabbed the buildlog myself, looks legit01:40
infinityNo further FFe faff needed, let 'er go.01:40
robruinfinity: ok thanks01:40
robruinfinity: seems libqtdbusmock got stuck in UNAPPROVED, can you poke that through? thx03:06
infinityrobru: Was planning on it, just went out for a burger. :P03:53
robruinfinity: ah, thanks03:59
=== adam_g is now known as adam_g_out
smosercan i get someone to take a look at taht ^15:19
smoserdidrocks, are you able ?15:19
ogra_no, he is french15:20
ogra_:P15:20
didrockssmoser: I'm not in the release team, so I technically can, but can't :p15:58
smoseri didn't know if you were on release team.16:01
smoserso ogra_, it wasn't *just* because he's was french.16:02
* smoser works on his english :)16:02
didrocksahah16:03
smoserpretty please, can someone on the release team ack that for me ? the bug has hopefully reasonable description of why the fix is ok.16:29

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