/srv/irclogs.ubuntu.com/2013/08/16/#ubuntu-release.txt

xnoxi've synced db6.0 twice now. so the older one can be dropped. but i'd like the ^ one to be accepted please =)08:12
cjwatsonxnox: done08:13
jamespageDaviey, how would the SRU team feel about backporting the 1.9.0 openvswitch from raring to 12.04 to support the lts-raring enablement kernel?08:13
xnoxcjwatson: cheers!08:14
jamespageit supports 3.8 natively and I feel its actually much lower risk and trying to backport the multitude of cherry-picks that don't apply cleanly to the 1.4.x codebase we have in 12.0408:14
Davieyjamespage: Hmm, a dedicated NEW versioned package name (like linux), or bumping the version?08:18
jamespageDaviey, hmm08:21
jamespageDaviey, I was thinking a straight backport to updates08:23
Davieyjamespage: Dual supporting both is more favourable IMO, but lack of dynamic dependencies makes this kinda hellish..  I can't think of a good user experience fix for handling this gracefully08:23
jamespageDaviey, the other option which is not ideal is to provide 1.9.0 via precise-backports08:23
jamespageso that 1.4.0 continues to exist for those that want to stick with 3.208:23
jamespagebut lts-raring users have to use the backports version....08:24
jamespageI'd need to run that past the backports team obviously08:24
Davieyjamespage: Probably a good idea to bring this to the TB mailing list, outlining the issue and possible solutions08:25
jamespageactually that might work better - I suspect that for the saucy enablement kernel I'll need to backport 1.10 which drops the brcompat module08:25
jamespageDaviey, OK - I'll send something this morning08:25
Davieyjamespage: Well, straight backports cannot really solve this, can it?  Unless you still do the compat work in the current openvswitch package?08:26
jamespageDaviey, ?08:26
jamespageits already backwards compatible08:26
jamespagei.e. 1.10 works on the 3.2 kernel08:27
Davieyjamespage: Current ovs in precise works with current lts kernel, but not raring backport?08:27
DavieyOh!08:27
jamespageDaviey, yes08:27
jamespageThe version we have in precise is good up to the quantal hwe kernel08:27
jamespagebut that was painful and we have to carry a large number of patches08:27
jamespage(and I got it wrong first go)08:28
Davieyjamespage: Right.. and you want to avoid that again... and I agree the regression potential of trying to cherry pick that much is a problem.08:29
DavieySo what i am saying is, making use of backports will mean that  -updates doesn't work with the most recent HWE kernel.08:29
Davieyjamespage: AND, we ned to move quite quickly... 12.04.3, scheduled for next Thursday (is that still correct?).. will not work with openvswitch as it has the raring kernel, right?08:31
jamespageDaviey, no08:31
DavieyI'm wrong?08:32
Davieyjamespage: Am i wrong?08:40
jamespageDaviey, the version of openvswitch in 12.04 will not work with the raring HWE kernel08:41
jamespagewell the user space tools might with the native kernel module08:41
jamespagebut the openvswitch-datapath-dkms module which is the one everyting uses will not08:41
Davieyjamespage: Right.. the native support doesn't have GRE support, right?08:42
jamespageDaviey, thats correct08:42
jamespageDaviey, hmm - I wonder whether we can skew the userspace tools against the dkms module version08:43
jamespageDaviey, that way we could provide a versioned openvswitch-datapath-dkms-lts-raring package only08:43
DavieyYeah, I think that is what I was thinking earlier.. but create a good user experience as we cannot do dynamic depends08:44
Davieyerr, creates a poor*08:44
jamespageDaviey, well we have todo an explicit install of the dkms package anyway08:52
jamespageDaviey, so its not that much different08:52
Davieyjamespage: true.. Yeah, I think that is the best balance08:54
jamespageDaviey, just testing that now08:55
DavieyWe get raring-hwe compatibility, with no risk of current users.08:55
DavieyI'd also say that it is a manageable workflow in the future08:55
Mirvcould an archive admin add "poppler-qml-plugin" to the whitelist of source packages coming from cu2d? maybe cjwatson? both didrocks and seb128 are away today.08:57
DavieyMirv: Sorry, I would help.. but I do not know how cu2d works, and I have been unable to find any docs.09:08
jamespageDaviey, userspace tools for 12.04 appear to be functional with newer dkms versions!09:08
MirvDaviey: yeah the slight problem here is that I don't know where/what the whitelist didrocks touches is, but cyphermox told it's on the archive machines and not part of cu2d system (https://wiki.ubuntu.com/DailyRelease) as such09:10
Davieyjamespage: Super, that is good news.  I'd be happy processing this approach myself, unless anyone else objects.09:10
jamespageDaviey, great - I'll not bother emailing the TB as we have a low risk approach now09:11
jamespagemarvellous09:11
* jamespage thinks its good to talk these things through!09:11
DavieyMirv: Yeah, I'm not even sure I can do that.. I'd rather not poke around, and risk getting it wrong.  Sorry. :(09:13
MirvDaviey: I totally understand, that's why the idea of getting that Thing documented is a good one :)09:15
LaneyIt's something that gets committed to bzr and then pulled on lillypilly09:20
* Laney waves hands and flails09:20
sil2100Daviey: hi! Maybe you could help us in some other way! Do you have a minute? :)09:43
sil2100Daviey: in the daily-release process, we have a requirement that whenever there is a packaging change in a package that is ready for releasing, we need and archive-admin-or-similar to ACK the change - so that no 'risky' packaging change gets released into Ubuntu09:44
sil2100Daviey: normally didrocks or seb128 do those, but now they're both gone09:44
sil2100Daviey: we have one thing like this now, it's really a one-liner that we already acknowledged, but we still need some core-dev to ACK it as well09:46
sil2100Daviey: I know it's hard to ACK something when you don't know the code, but it's just to make sure nothing unwanted gets into the archive09:47
sil2100Daviey: https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libusermetrics_1.1.1+13.10.20130816-0ubuntu1.diff09:47
sil2100Could you take a look? ;)09:47
=== tkamppeter_ is now known as tkamppeter
jamespageDaviey, I've emailed upstream just to validate the approach we discussed09:55
jamespageI might be missing something re userspace/kernel module compatibility09:55
Davieysil2100: Well, reviewing the packaging diff represented there - it looks like something i'd be happy sponsoring.09:56
sil2100Daviey: !09:57
sil2100Daviey: thank you!09:57
sil2100Mirv: puublish!09:57
Davieyjamespage: well.. this base approach gives us some known compatibility.. in the worsed case, we'd need to also add a raring-hwe user space tools - right?09:57
* sil2100 goes into slow-motion09:57
jamespageDaviey, yes09:57
sil2100Mirv: noooooow~!09:58
sil2100Daviey: thanks!09:59
Mirvsil2100: oh, you were shouting here :)09:59
sil2100;)10:00
cjwatsonMirv: I'm at DebConf and I don't know much about cu2d anyway, sorry.10:19
cjwatsonsil2100: This process should involve verification by somebody with upload privileges, not by an archive admin (a much smaller and much more contended set of individuals)10:20
cjwatsonFor the record10:20
Davieycjwatson: Yeah, i almost said that - but i think sil2100 knew that, as he quantified with "need some core-dev to ACK it" .. I assume it's not in a pkg set.10:31
Mirvcjwatson: ok thanks anyway, and happy debconfing. and yes, the thing sil2100 asked for requires just core-dev.10:59
Mirvit's good that didrocks is away for a small while before real vacation, so that we notice these beforehand :)10:59
sil2100Indeed :)11:15
sil2100Actually, once again we need a core-dev to ACK another packaging change11:15
sil2100A quick one again11:15
Laneycore-devs> #ubuntu-devel11:39
sil2100ogra_: hi! Are you still around?13:38
sil2100ogra_: we have another near-deadline packaging ACK that needs ACKing, maybe you could help this time as well ;) ?13:38
sil2100ogra_: https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libunity_7.0.11+13.10.20130816.2-0ubuntu1.diff13:39
ogra_sil2100, i assume this has been tested (cant really judge the sed lines so i need to truset a testrun you did )13:41
ogra_*trust13:41
sil2100ogra_: it passed our testing (failures in the acceptance threshold)13:42
ogra_sil2100, fine, then, go ahead13:42
sil2100ogra_: thanks! You're a life saver13:42
jamespageDaviey, ^^ updated iscsitarget for lts raring hwe kernel13:45
Davieyjamespage: reviewed and ^13:49
jamespageDaviey, thanks muchly!13:49
=== rtg_ is now known as Guest11042
tkamppeterjdstrand, hi14:52
jdstrandtkamppeter: hey15:00
cyphermoxsil2100: Mirv: when you need a core-dev to review things before upload, that I or kenvandine can do15:22
cyphermoxso, for the cu2d magic that apparently is needed on lillypilly15:22
sil2100\o/15:22
cyphermoxseems like that would be just a matter of a bzr pull for the cupstream2distro-config branch somewhere on the machine15:23
sil2100cyphermox: first of all, do you have a moment for a quick pkg ACK? See #ubuntu-desktop ;)15:23
sil2100cyphermox: awesome15:23
cyphermoxcron should be able to say exactly where, but I don't know how didrocks did it, and I don't have that kind of god powers15:23
Laneyneeds documenting for bus factor reasons15:23
sil2100Ok15:23
sil2100Laney, cyphermox: https://wiki.ubuntu.com/DailyRelease/FAQ#Adding.2BAC8-removing_components_to_a_stack this documents some parts probably15:24
cyphermoxright15:25
cyphermoxit is documented, just in a non-obvious way15:25
cyphermoxI totally read over that without noticing >.<15:26
sil2100hehe15:35
sil2100Right, it's not being explicitly mentioned anywhere15:35
tkamppeterjdstrand, did you have a look into the openjpeg MIR, bug 711061?16:10
ubot2`Launchpad bug 711061 in openjpeg (Ubuntu) "[MIR] libopenjpeg2" [High,Confirmed] https://launchpad.net/bugs/71106116:10
cyphermoxLaney: so, is that wiki page enough information?16:12
Laneydunno16:12
LaneyI don't even know what is being requested. :P16:12
jdstrandtkamppeter: no. let me see if I can get someone else to do it16:13
Laneycyphermox: that branch is on 608 but trunk is 65516:17
tkamppeterjdstrand, OK.16:39
cyphermoxLaney: if you could bzr pull on that branch I suspect it will be enough17:07
LaneyI don't know what it means and so I'm reluctant to do so17:07
=== bjf is now known as bjf[afk]
Sarvattanyone know whats up with x11-utils migration? autopkgtest for gvfs 1.17.2-0ubuntu6: RUNNING but it looks like it succeeded in jenkins unless i'm misunderstanding it21:00

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