=== glebihan__ is now known as glebihan
bkerensaLaney: https://code.launchpad.net/~bkerensa/ubuntu/raring/swauth/fix-for-1061020/+merge/13319500:23
bkerensaLaney: you asked me to forward to Debian but the package does not exist in Debian00:23
xnoxLaney: somehow the packages list is ~8 hours out of date on the transition-tracker.00:24
=== emma is now known as em
=== cpg is now known as cpg|away
=== attente is now known as attente_zzz
=== cpg|away is now known as cpg
pittiGood morning05:38
mightyiamthanks, TheMuso, i'll check07:42
dholbachgood morning07:46
=== dpb_ is now known as Guest76575
=== smb` is now known as smb
=== Tonio__ is now known as Tonio_aw
=== doko_ is now known as doko
mightyiam good morning indeed08:46
* seb128 looks at dholbach and opt-in for some extra friday sponsoring out of his normal shift09:16
seb128!pilot in09:16
seb128@pilot in09:16
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: seb128
* dholbach hugs seb12809:16
* seb128 hugs dholbach back09:17
dholbachI'll sponsor a few bits later on, got to finish 2 other things first :)09:17
mightyiammy kernel in raring is "obsolete"09:23
=== henrix_ is now known as henrix
cjwatsonmightyiam: Yes, I'm processing the 3.7.0-0 one through the archive at the moment.  No need to report it.09:32
mightyiamthanks, cjwatson09:33
Laneybkerensa: fair enough, comment in the MP to that effect then09:42
Laneyxnox: uhh09:42
=== mcclurmc_away is now known as mcclurmc
xnoxLaney: or maybe there is a mistake in my tracker. http://people.canonical.com/~ubuntu-archive/transitions/onlypy3oncd.html shows ndisgtk at 0.8.5-1 while if I generate the tracker locally  it's at 0.8.5-1ubuntu1.09:58
LaneyI'll look in a second09:58
Laneyjust collecting the pieces from that libgcrypt11 thingy09:58
Laneystokachu: !!!09:59
Laney-rw-r--r-- 1 ubuntu-archive ubuntu_archive 1140090 Nov  8 14:09 Packages.bz210:16
Laneyxnox: suspicious eh10:16
Laneycjwatson: I suppose you didn't intend to turn that off :-)10:17
mlankhorstis the dpkg-diverts from libgtk-3-bin good enough as dumb example for dpkg-divert? :p10:17
cjwatsonLaney: no - I'll lok10:18
Laneywould JFDI but bzr10:18
Laneyalternatively if I can just branch that and fix/push then I will10:18
cjwatsonedit in place and commit10:18
cjwatsonLaney: raring-proposed is up to date - I thought you'd stopped using raring in the transition tracker10:18
Laneyit merges the two10:19
Laneybecause partial suite10:19
cjwatsonoh, so you need to be triggered on a change to either, then?10:19
Laneywell I suppose you could just sync release as well if proposed changes10:19
Laneyyou should only need to regenerate the tracker if proposed changes, right?10:20
cjwatsonLaney: ok, should be fixed now10:21
ScottKseb128: Where there API changes in 12.10 for messaging menu?  I'm looking at Bug 1076362 and I'm really confused because it works for me fine with the Qt/KDE messaging indicator and literally nothing changed in Quassel between 12.04 and 12.10.10:25
ubottuLaunchpad bug 1076362 in quassel (Ubuntu) "Quassel messaging menu integration broken in Ubuntu 12.10" [Undecided,New] https://launchpad.net/bugs/107636210:25
seb128ScottK, yes, https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/104025910:25
ubottuLaunchpad bug 1040259 in skype-wrapper "FFE: libmessaging-menu transitions for quantal" [High,In progress]10:25
seb128ScottK, there is a new lib,api in quantal10:26
seb128I didn't know KDE has a messaging indicator compatible with the old api10:27
seb128sorry about that, we should probably have added that to the list of things to port or at list consider it10:27
seb128who synced glew?10:28
seb128whoever did I hope there was a test rebuild of the unity stack with the new glew, we had glew updates breaking unity in the past10:29
seb128Laney, "Sorry, changesfile not available."10:29
Laneythe From line says who did it10:30
seb128oh, there is the signed-by10:30
seb128does alessio do IRC?10:30
seb128not there10:30
didrockscjwatson: is there a way hold manually proposed -> release pocket migration for this component?10:31
pittihm, we don't yet have unity in autopkgtest; that ought to catch that?10:31
didrockspitti: well, we can't run autopilot in autopkgtest as discussed in the UDS session10:32
didrockspitti: because of need of bare metal10:32
cjwatsondidrocks: I've blocked it for the time being10:34
ScottKseb128: It's not just us as DBus menu is in upstream KDE, so it needs porting work upstream too and we're now too late for KDE 4.10.10:34
didrockscjwatson: thanks a lot. Let's try to sync with quadrispro when he's here (or sending an email if we can't catch him)10:35
ScottKseb128: I'm not actually sure all the bits it touches.10:35
cjwatson(lp:~ubuntu-release/britney/hints-ubuntu - it just has a file for me at the moment, but the list of hinters is in britney.conf in lp:~ubuntu-release/britney/britney2-ubuntu)10:36
didrockssweet, that the conf is versionned :)10:36
cjwatsonso please let me know if/when that can be unblocked10:36
cjwatsonhaving that in bzr is probably overengineering but meh10:37
seb128didrocks, I emailed him and ubuntu-devel10:37
didrocksseb128: thanks!10:38
didrockscjwatson: well, at least, we are sure to have a reason written in10:38
cjwatsonyeah (I've just added a reference to this conversation)10:39
cjwatsonI have no problem with anyone in ~ubuntu-release setting themselves up as a hinter10:39
cjwatsonalthough I think any changes to lp:~ubuntu-release/britney/britney2-ubuntu still need to be deployed manually10:40
Laneyyou forced something in the other day - was that not through hints?10:40
Laney(I'm aware that the release team can do copies directly)10:40
cjwatsonLaney: I forced eagle in using a hint10:42
LaneyI see it in history indeed10:43
Laneyused to Debian ones where they use 'finished'10:43
cjwatsonthe release team can but shouldn't - better get britney to do it10:43
cjwatsonyeah, their hints files aren't versioned, or weren't when I was last involved10:43
cjwatsongiven a VCS I see no point in leaving cruft in the file10:43
=== henrix is now known as henrix_
pittimvo: does https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-ubuntu-release-upgrader/lastFailedBuild/ARCH=i386,label=albali/artifact/results/dsc0t-nose-tests-stdout make any sense to you?10:55
pittimvo: I see that the "äää" appears on stdout (or err), and the fp.read() doesn't seem to get it10:55
mvopitti: let me check11:00
mvopitti: I wonder if mabye "less" is not installed in the test env11:04
pittiplausible, let me check11:04
mvopitti: I update the test depends11:04
* pitti runs run-adt-test -l11:04
=== _salem is now known as salem_
pittimvo: hm, I do have it installed here; that's a standard prepare-testbed VM11:07
* pitti runs tests in there11:08
mvopitti: I can do a upload with it added, maybe the server version is a bit different11:08
pittioh, the tests runs a while11:09
pittihm, no Python 3.2 any more in raring :(11:13
xnoxpitti: nope. please rebuild your chroot as well, as there are packages that try to compile themself againsts "--installed"11:14
xnoxpython versions.11:14
pittioh, I did, it's a fresh VM from yesterday11:14
pittibut we have packages which don't work yet with 3.3, so its removal seems a bit premature11:15
xnoxpitti: which packages?11:15
pittifor comparing/debugging I can install it from quantal, though11:15
* xnox thought we ported everything.....11:15
pittilike python-docutils; there are certainly more, though, it's just the one I'm currently looking at11:15
xnoxI thought doko & mitya managed to get python-ductils workings....11:16
pittithe last build in raring was against 3.211:17
ogra_xowow, thanks for the fstools, that was really fast11:17
ogra_xnox, ^^^11:17
pittibut oh well, I'll disable thre six failing test cases for now to fix the FTBFS; the other 1204 work, after all11:18
* ogra_ wishes some archive admin would review the nexus kernel now so it can get out of NEW11:18
pittiand that's happening from current upstream svn trunk as well, so upstream should be on it11:18
xnoxogra_: and it's in the ppa.11:18
ogra_xnox, well, its on archive.u.c and ports.u.c11:18
xnoxogra_: everywhere, where it matters =)11:21
* ogra_ is just missing the kernel now to start playing with the first images11:21
cjwatsonwhy was the last linux-nexus7 upload in the queue rejected, do you know?11:22
cjwatsonI saw a reject/reupload cycle but no explanation11:22
ogra_iirc there was an ftbfs with the tools package11:22
ogra_jani only discovered after upload11:22
ogra_janimo, ^^^11:22
janimocjwatson, FTBFS with raring gcc. I reuploaded with tools package build disabled as it was don efor linux-ac100 as suggested by infinity11:23
janimoogra_, so for the firmware are we settled on a separate package that puts up a notice when installed?11:25
ogra_janimo, apparently :/11:25
ogra_janimo, it needs to be preseedable though11:25
janimois there a package I can look at that does something similar?11:25
ogra_so we can suppress the notice on image builds11:25
ogra_since there usb-creator will show it at image flash time11:26
ogra_the notice in the package just needs to be there for people installing the package separately11:26
xnoxogra_: hmmm....11:28
xnoxogra_: is the notice required, i thought we were meant to step that aside.11:28
ogra_xnox, apparently it is :(((11:30
xnoxogra_: so are you driving the legal workitem from the spec then?11:30
ogra_i'm not keen having it either11:30
ogra_legal is done11:31
ogra_victorp_, ^^^^11:31
ogra_we just need to display the same npotice that the shell script installer does nowadays11:31
ogra_(same thing for the package)11:31
xnoxogra_: ... and the notice will be a text file inside the tarball? (tar.gz: boot.img rootfs.img notice.txt README)11:32
ogra_oh, sure, i could fish that out of the rootfs at build time11:33
xnoxogra_: that would be lovely, cause currently the website lists it on the hwe. So the notice needs to be accesible on cdimage as well.11:34
xnoxogra_: and within tarball should be sufficient. Or maybe along side the tarball as well for apache to pick up as README11:34
ogra_i prefer inside if possible11:34
* ogra_ doesnt like to touch make-web-indicies if avoidable :)11:35
xnoxack =)11:35
pittimvo: I can reproduce the failure with less installed11:35
ogra_the first builds will be without firmware anyway i guess11:35
seb128could somebody mark https://code.launchpad.net/~ubuntu-branches/ubuntu/precise/kde-l10n-sl/precise-updates/+merge/133394 as merged?11:36
seb128it was uploaded: https://launchpad.net/ubuntu/+source/kde-l10n-sl/4:4.8.5-0ubuntu0.111:36
pittimvo: "xvfb-run python3 tests/test_view.py" succeeds, though11:36
didrockscjwatson: should I still use syncSources() compared to syncSource()? I remember we discussed about it a year ago and you told me to use the first one11:37
cjwatsondidrocks: Generally?  Neither.  What are you doing?11:37
didrockscjwatson: I'm written the latest script for the copy from the PS release ppa to -proposed11:38
didrocksI have a list of package source name for a serie that are validated at this stage11:39
cjwatsonI probably told you to use syncSources because it would either succeed or fail all at once rather than maybe copying some but not others11:40
cjwatsonBut I don't really think that's a concern with copies into -proposed11:40
cjwatsonBesides, both syncSource and syncSources are (lightly?) deprecated because they're synchronous and often time out11:40
cjwatsonI would recommend using copyPackage instead11:40
cjwatson(you'll need to use the devel API version)11:41
didrockscjwatson: copyPackage, not copyPackages? (like if one operation times out, maybe I'll push the validated stack partially)11:41
didrocksah, it's async11:42
cjwatsonYou *could* use copyPackages, but I wouldn't as that suppresses announcement mails11:42
cjwatsonTimeouts are very unlikely with copyPackage11:43
cjwatsonAnd the proposed-to-release process should protect against most partial-copy situations11:43
cjwatsonSo I wouldn't worry about that11:43
didrockscjwatson: makes sense, I'll follow your advice and test between ppas meanwhile. Thanks :)11:44
didrocksas I'm seeing the "auto_approve" parameter, I think I can keep it to False, so that we don't bypass potential freezes11:45
cjwatsondidrocks: You're acting with a developer hat on here rather than with an archive admin hat on, so you shouldn't use auto_approve11:45
didrockscjwatson: agreed, just checking that I understand the parameter corectly.11:46
cjwatsonYou do11:46
pittimvo: I confirmed it's not TMPDIR and similar; something more involved11:46
didrockscjwatson: last thing (sorry to bother you), but I see that the relationship between source and binary packages is established here. However, if I try source.getPublishedBinaries(), I can get some tricky situation11:47
didrockscjwatson: like some binaries were published for amd64, but then the source becomes superseded, and the following call to source.getPublishedBinaries() won't give anything as it's only PUBLISHED or PENDING binary package state11:47
didrocksand there is no parameter compared to ppa.getPublishedBinaries() to catch them11:48
didrocksI wonder if I miss any obvious API to ensure I always get all the published binaries, even superseded (this is not for the copy, but for another step of the build process)11:48
=== victorp_ is now known as victorp
victorpogra_ hi11:51
cjwatsondidrocks: not sure there's a desperately good way at the moment; maybe figure out the binary names you care about and call Archive.getPublishedBinaries repeatedly (ugh)11:52
ogra_victorp, hey, see backlog11:52
pittimvo: aaah!11:52
cjwatsonSPPH.getPublishedBinaries is not my favourite interface11:52
pittimvo: reproduces with xvfb-run python3 tests/test_view.py |cat11:53
pittimvo: happens because stdout is not a pipe11:53
pittimvo: so presumably less fails to start up?11:53
cjwatsonless is normally quite happy if stdout isn't a tty - it basically just acts like cat11:53
didrockscjwatson: yeah, I have a workaround to avoid making all those calls for Archive.getPublishedBinaries and infering the binary names… :/ But wanted to ensure I wasn't missing something obvious at least. Thanks again for your advice.11:54
victorpogra_, read that, not sure what did you decide11:56
ogra_victorp, i just wanted you to confirm to xnox that legal work is done :)11:56
ogra_so its only some code thats missing now to chow the notice ...11:57
victorpdone as in, I have talked to our legal team and they are happy that if we display the notice we can distribute the fw blobs11:57
ogra_thats enough11:57
pittimvo: so I tried this, which works in a shell: PAGER="sh -c 'cat >/tmp/xx; true'" man man12:06
pittimvo: but it doesn't work in that test, I get "Syntax error: Unterminated quoted string"12:06
dokoxnox, are there any outstanding patches?12:08
xnoxdoko: not that I can find. but pitti reports that it's not working.12:14
seb128bdmurray, https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1064962/comments/100 ... is that an hard requirement? we track libreoffice 3.7 for raring, not 3.6 but it's not ready for upload yet12:14
seb128slangasek, ^12:14
ubottuLaunchpad bug 1064962 in indicator-appmenu (Ubuntu Quantal) "[SRU] Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running" [High,Confirmed]12:14
xnoxogra_: victorp: ack.12:14
dokoxnox, well, yes, disable these three odp tests ...12:17
dokoor odt. I don't think packages build docs for this format12:17
seb128pitti, could you mark https://code.launchpad.net/~ubuntu-branches/ubuntu/precise/kde-l10n-sl/precise-updates/+merge/133394 as merged? it's in  https://launchpad.net/ubuntu/+source/kde-l10n-sl/4:4.8.5-0ubuntu0.112:18
seb128pitti, (sorry for the direct ping but I mentioned it earlier and noboby picked it)12:18
cjwatsonapw: did you intentionally drop linux-headers-omap, linux-image-omap, and linux-omap from linux-meta for armel and armhf?  There's no clear mention in the changelog, and the diff for linux-meta has lots of */DEBIAN/* junk in it too ...12:19
cjwatsonapw: wait, never mind, I'm misreading and those binaries weren't actually dropped.  The */DEBIAN/* junk in the diff indicates that your source package build tree is dirty though, I think12:20
cjwatsonapw: but that shouldn't block migration to release, so just for your next upload or whatever12:21
seb128can somebody mark https://code.launchpad.net/~matttbe/ubuntu/quantal/rhythmbox/1010619_795765/+merge/133343 as merged?12:26
seb128pitti, ^12:26
apwcjwatson, yeeks, i was pretty sure i git zapped the tree first ... :/  will look at it12:29
ogra_dpkg-gencontrol: error: the Depends field contains an arch-specific dependency but the package is architecture all+12:29
ogra_GRRR !12:29
ogra_silly stuff, its a binary dep why shouldnt an arch all package not have arch specific binary deps12:31
cjwatsonBecause arch-specific dependencies are valid in source package control files, but are processed at build time and are syntactically invalid in the binary package's control file12:31
ogra_hmm, k12:32
pittiseb128: looking (just returned from lunch, sorry for delay)12:34
seb128pitti, no worry, nothing urgent, thanks!12:34
pittiseb128: fini12:35
seb128pitti, danke12:36
diwicI've got an SRU for PulseAudio coming up. Any religious sacrifice I can do to make it a smooth sailing experience instead of it getting stuck on the stormy patch review ocean?12:37
seb128diwic, don't have an impossible to review diff, have SRU compliant bugs for the changes you include?12:38
diwicseb128, hmm, I think I got that covered12:38
diwicIt's okay to SRU four different bugs in one SRU, right?12:40
Laneyif they all meet the criteria12:40
diwicin case of PulseAudio, we've agreed to be a little more flexible; which is the case for at least one of the bugs, to avoid having to do a backport stack thing like we do for X12:41
seb128diwic, yeah, as long as each bug is SRU compliant it's fine12:41
=== MacSlow is now known as MacSlow|lunch
* diwic uploads and hopes it all will go well12:46
diwicseb128, btw, how is the transition to gnome 3.6 going and should I do my reduction of the sound-nua delta before or after you upload 3.6 to raring?12:49
pittimvo: ok, committed a verified fix now, using tee instead of less12:51
pittimvo: doing an upload now; I want more green on jenkins :)12:51
seb128diwic, 3.6 is being prepared in the vcs and and in https://launchpad.net/~ubuntu-desktop/+archive/ppa ... you are welcome to rebase the sound-nua ui bits, we just dropped that in favor of the upstream version so far12:53
seb128diwic, it's not a blocker for the update but would be good to have12:53
mvopitti: thanks!12:54
mvopitti: I like tee more actually not less12:54
* mvo makes a cup of tea12:54
pittimvo: yeah, I couldn't make it work with a "sh -c"; and dd doesn't work either as it stumbles over the appended "-"12:55
diwicseb128, okay. I think the unity UI looks better :-)12:56
* pitti chalks up the 6th fixed autopkgtest12:59
pittimvo: I'll fix unattended-upgrades now (stderr and missing dependency), ok?13:03
pittiah, cjwatson already committed the dep13:03
mitya57pitti: thanks for docutils & python-markdown uploads, two items less in my todo list! :)13:04
pittimitya57: ah, I thought you already fixed markdown independently in svn?13:04
pittimitya57: docutils now built, so test suite runs fine during package build; it still failed in jenkins though, will have a look later13:04
mitya57pitti: yes, but now it's not urgent for me to do a new upload13:05
mitya57upstream bug for docutils is http://sourceforge.net/tracker/?func=detail&atid=422030&aid=3582720&group_id=3841413:05
mitya57I'll maybe look at it if I have time13:05
pittimitya57: ah, thanks; I had a quick try to fix the _ElementWrapper → Element thingy, but failed13:06
pittiyeah, and I have no clue about that one13:06
cjwatsonutlemming: I notice hv-kvp-daemon-init is built on all architectures - is it actually useful on non-x86?13:13
=== bdrung_ is now known as bdrung
* mitya57 hopes that wifi will work better here13:19
mitya57did I miss anything? :)13:19
pittimitya57: I said two things to you after your previous comment, then nothing related13:20
mitya57pitti: please repeat...13:20
pittimitya57: ah, thanks; I had a quick try to fix the _ElementWrapper → Element thingy, but failed13:20
pittiyeah, and I have no clue about that one13:20
pittimitya57: "that" -> the bug you referred to13:21
mitya57that was not after my last comment, seems like it was not sent actually13:21
mitya57<mitya57> pitti: "it still failed in jenkins though, will have a look later" — I don't see -0ubuntu3 jenkins job — where is it?13:21
=== attente_zzz is now known as attente
pittimitya57: still on the internal one, will publish soon13:22
pittimitya57: actually it is: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-proposed-adt-python-docutils/lastFailedBuild/13:22
pittiyay, unattended-upgrades now works locally, /me uploads13:23
=== Ursinha is now known as Ursinha-afk
mitya57that one is with -0ubuntu113:23
* pitti aime le vert13:23
mitya57but ok, I'll wait until it's published13:23
pittioh right, that was the FTBFSing one13:24
Laneyricotz: OK uploaded with some changes. Look at the diff to see what I changed - I suggest you do the same in Debian too13:25
pittimitya57: yay, it just succeeded!13:25
Laneyoops, was meant to be in #-desktop13:25
pittimitya57: (on the internal one for -proposed)13:25
=== cpg is now known as cpg|away
mitya57well done pitti!13:25
pittimitya57: well, it's at the price of disabling tests, but I don't know enough about it, and the failures are at least visible upstream13:26
pittiI feel better about the other 6 fixes, as these fix things properly13:26
=== Ursinha-afk is now known as Ursinha
pittimitya57: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-proposed-adt-python-docutils/ :)13:27
snikker|2i'm tring to recompile ubuquity, but i've got this error: http://pastebin.com/H2ke9ne3 can oyu help me, please?13:28
mitya57I'll take a quick look at that right now13:29
snikker|2mitya57: ok, thanks13:29
pittimvo: is someone working on the software-center failures?13:30
mitya57snikker|2: that was for pitti, not for you :((13:30
xnoxsnikker|2: please see #ubuntu-installer. please publish _full_ build log.13:31
mitya57snikker|2: maybe xnox knows13:31
mitya57oops, he's already here13:31
seb128is a build-depends "change libtiff4-dev to libtiff-dev" something worthing having a diff for on universe package?13:32
seb128do we try to drop libtiff4-dev from ubuntu? (I didn't follow much what was happening in quantal thereà13:32
xnoxseb128: yes. it's a tiff4 -> tiff5 transition.13:32
seb128e.g http://launchpadlibrarian.net/117905009/love_0.8.0-1_0.8.0-1ubuntu1.diff.gz13:32
seb128xnox: we do it without debian on the whole archive?13:33
cjwatsonPlease don't drop those changes, I spent ages on them13:33
cjwatsonBesides, they should be forwardable13:33
cjwatsonlibtiff-dev is tiff4 in Debian right now; after wheezy releases it'll be flipped to tiff513:33
seb128cjwatson, I didn't plan to drop them don't worry, I was just asking because I was unsure if that was a "let's migrate the default install" or something we would take diff on the whole universe for13:33
cjwatsonthe latter13:34
seb128cjwatson, xnox: thanks13:34
cjwatsonI ran a transition tracker for it13:34
seb128cjwatson, so "please use libtiff-dev" is valid for Debian reports as well? (double checking)13:35
snikker|2xnox: i'm lookng for the full log, because in the terminal i don't have the full log13:35
cjwatsonseb128: Yes13:35
seb128cjwatson, excellent, will forward that one then, thanks13:35
cjwatsonseb128: Though maintainers might well not apply it until later ...13:35
seb128well, I just want to send a bug to the bts13:36
cjwatsonFor anything that uses libtiff-dev in Debian, a binNMU will suffice to transition it to tiff513:36
seb128that's fine if it sits there for a while13:36
seb128that makes sense13:36
cjwatsonseb128: the reason I did the whole archive rather than just a subset is that it became very quickly clear that if we transitioned just a subset then we ran into build failure problems with libtiff4-dev and libtiff5-dev conflicting13:37
cjwatsonit was *very* much easier to just do the lot13:37
seb128I see13:38
seb128that will go away once debian release as well and those are easy to cary until then so no worry13:39
* cjwatson fixes MoM again, hopefully13:44
mightyiamricotz: thanks for the libsecret patch13:54
=== seb128_ is now known as seb128
ricotzLaney, thanks!14:30
pittimvo: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-proposed-adt-ubuntu-release-upgrader/lastFailedBuild/ failed on amd64 because it expects "main restricted universe multiverse" in apt sources, but something writes it as "... multiverse universe"14:40
seb128pitti, can you set https://code.launchpad.net/~hggdh2/ubuntu/precise/cobbler/lp-967815/+merge/132172 to "work in progress"?14:40
pittimvo: is that apt's fault, or u-r-upgrader's itself?14:41
pittiseb128: done14:41
seb128pitti, danke14:41
pittimvo: at least it succeeds on i386 now14:41
pittimvo: might be py 3.3 hash randomization or so?14:41
xnoxpitti: smells like PYTHONHASHSEED14:42
xnoxoh =)14:42
mvopitti: need to look in detail, but it does smell like the randomization14:44
pittimvo: I ran it two times with the same result14:44
pittimvo: but shouldn't this be ordered explicitly anyway?14:45
ScottKseb128: There's no bug in debian/changelog for the havp upload you just did.  Would you please add it and reupload.  It breaks SRU tracking if we don't have it.14:49
mvopitti: let me check the failure in detail, it should be yes14:49
* pitti misses the gdb magic for debugging python (printing Python objects)14:51
seb128ScottK, sorry about that, rejected the upload and redid it with the bug reference14:52
ScottKseb128: Thanks.  No problem.14:57
mlankhorstugh this rename libdrm stuff scares me, hopefully it works and I'll never have to look at it again..14:58
=== MacSlow|lunch is now known as MacSlow
seb128pitti, could you see https://code.launchpad.net/~betienne/ubuntu/quantal/gelemental/update/+merge/131998 to "Work in progress"?15:15
snikkerxnox: sorry but i've got a problem with internet connection, btw the full log is here: http://pastebin.com/S3mTkpee15:15
xnoxsnikker: it doesn't say what machine you are building it on.15:17
xnoxsnikker: also 2.12.16 is the latest quantal installer. not
xnoxsnikker: are you building this on quantal?15:17
snikkeryes i'm on quantal 64-bit15:18
snikkerxnon: --^15:18
snikkerxnox: --^15:18
bdrungcjwatson: what does oif stand for?15:18
xnoxsnikker: please try 2.12.16, not 2.12.14. We released images with 2.12.1615:19
cjwatsonbdrung: I just work here15:19
cjwatsonbdrung: I think it's Open Input Framework or some such15:20
snikkerxnox: on launchpad page of ubiquity, i've got this error: "Failed to fetch package details"15:22
snikkerxnox: now download page work15:23
cjwatsonjust try again or follow the link rather than the expander15:24
mlankhorstLaney: ok can I get all of -lts-quantal added to the xorg package list? :p15:24
Laneymlankhorst: mail devel-permissions with a complete list15:24
seb128could somebody set https://code.launchpad.net/~betienne/ubuntu/quantal/gelemental/update/+merge/131998 to "Work in progress"?15:31
seb128https://code.launchpad.net/~utlemming/popularity-contest/oneiric.lp707311/+merge/131878 to rejected as well15:31
mlankhorstLaney: ok is it enough that those packages were uploaded to a ppa in launchpad?15:43
stokachuLaney: did i break something? :D15:46
Laneystokachu: yeah :( https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/107690615:47
ubottuLaunchpad bug 1076906 in libgcrypt11 (Ubuntu) "1.5.0-3ubuntu2 breaks gpg-agent" [Undecided,Confirmed]15:47
hallynslangasek: yuck, udevadm trigger action=change to fix the perms is as ugly as the initial udev and consolekit acls on the device :)  but, of course, if that's the proper way, i'll change to that (when I get a good chance to test).15:47
hallynslangasek: one downside would have been that containers can't do udevadm trigger, but then they shouldn't get /dev/kvm auto-created by udev either so shouldn't have this bug.15:48
stokachuLaney: this libgcrypt library is really becoming a headache15:48
LaneyI hadn't heard of it before this morning :-)15:49
stokachuLaney: do you want to assign that to me?15:52
stokachuIll nominate it for the raring series15:52
Laneythe bug description there understates the impact BTW15:53
Laneyit meant I couldn't log in15:53
stokachuah ok15:53
Laneysee the dupe15:53
xnoxstokachu: hah. breaking gpg-agent, breaks me logging into my desktop environment.15:53
* xnox disabled gpg-agent and carried on.....15:54
cjwatsontime for a quick revert if you won't be able to fix it before the weekend?15:55
stokachucjwatson: yes please15:55
cjwatsoncan you do that yourself or do you need help?15:55
stokachucjwatson: am i just creating a new debdiff with the previous code path?15:56
argestyhicks, hey when you have time, can you let me know what else is needed for bug 1052038? thanks15:56
ubottuLaunchpad bug 1052038 in ecryptfs-utils (Ubuntu Precise) "ecryptfs_fnek_sig missing when login at the same time on cron session close" [Medium,In progress] https://launchpad.net/bugs/105203815:56
cjwatsonJust reverse-apply the debiff from 1.5.0-3ubuntu1 -> 1.5.0-3ubuntu2 apart from debian/changelog, and add a new changelog entry documenting the reason for the reversion15:56
xnoxstokachu: take old package, add the current changelog entry, add a higher version changelog entry saying "this reverts previous upload", generate package done =)15:57
stokachugotcha ill do that now15:57
cjwatsonThat reminds me, I was going to create a wiki page with a brief log of all the reversions we do during the development cycle15:57
xnoxstokachu: well, and debdiff it =)15:57
cjwatsonSeems like a good time to start15:57
stokachucjwatson: i also updated teh appmenu-gtk with what i hope is correct way to m-a it15:58
stokachucould i get a review/sponsor for bug 93286016:02
ubottuLaunchpad bug 932860 in appmenu-gtk (Ubuntu Quantal) "Broken (or missing) multiarch support" [High,In progress] https://launchpad.net/bugs/93286016:02
stokachualso an approval for raring nomination16:02
xnoxDaviey: any good reason why python-gnupginterface is explicitely seeded in development/ubuntu-server?16:04
Davieyxnox: i wasn't aware it was!16:05
Davieyxnox: did you blame?16:06
xnoxDaviey: nah, I didn't blame. In precise the upgrade-tarball / landscape-client were using them. But not any more.16:06
xnoxDaviey: asking you as the ubuntu-server's seed point of contact.16:07
xnoxDaviey: unless I am very confused how/where development seed is included.16:07
Davieyxnox: i don't think development was really defined.. If i am honest, foundations normally touches that16:09
xnoxDaviey: blame says mdz 2006 "add development seed"16:09
cjwatsonxnox: Feel free to ditch it if it's no longer appropriate16:10
xnoxDaviey: ok, thanks. I'll go talk to somebody in foundations..... =)16:10
Davieywell that is the first commit, so doesn't help.. clealry broken out from something16:10
xnoxcjwatson: ack.16:10
cjwatsonstokachu: Of course this patch was in itself a regression fix :-/16:10
Davieyxnox: JFDI. :)16:10
xnoxDaviey: it's just scary, why $ seeded-in-ubuntu -b python-gnupginterface16:11
xnoxreports: ubuntu-server: daily16:11
xnoxtumbleweed: ^^^^ can you help me understand above16:12
jpdsxnox: landscape-common ?16:12
stokachucjwatson: yea to many dependencies on libgcrypt16:12
cjwatsonseeded-in-ubuntu is badly named and concerns what's actually in images16:12
stokachuLaney: i uploaded a revert to that gpg bug if you want to take a look16:12
xnoxjpds: not in raring anymore ;-)16:12
cjwatsonthe development seed isn't relevant to images16:13
xnoxjpds: as in, in raring, landscape-common does not depend on python-gnupginterface.16:13
tumbleweedbetter name suggestions are always appreciated16:13
cjwatsonxnox: well, germinate thinks that's why it's pulled in16:14
DavieyAnyway, it's unseeded now :-)16:14
cjwatsonxnox: remember that seeded-in-ubuntu's output is based on the last successful image build16:14
xnoxcjwatson: so germinate will catch up, on the next run =)16:14
xnoxcjwatson: ah, so tomorrow it will be ok =)16:15
cjwatsonxnox: And you only changed landscape-client today16:15
snikkerxnox: smare error with ubiquity 2.12.16: http://pastebin.com/xLRJUbac16:15
Davieyseeded-in-ubuntu IMO is just a guide.. i wouldn't trust it's output entirely.16:15
cjwatsonI trust its output, but only for the specific thing it does16:16
cjwatsoni.e. "what images is this on"16:16
cjwatsontumbleweed: something like grep-ubuntu-images?  But I don't know whether it's worth the effort of renaming.16:16
tumbleweedif there is a reasonable way to include germinate seeding, it could do that16:16
Davieycjwatson: Last cycle it reported openvswitch was in kubuntu, which it didn't seem to be.16:16
xnoxcjwatson: "smare error with ubiquity 2.12.16: http://pastebin.com/xLRJUbac " <--- any idea why the test now gests Eastern/Canada instead of Eastern/US on that users machine?16:17
cjwatsonDaviey: that was because I didn't purge the Kubuntu images that we weren't building any more for some time16:17
cjwatsonDaviey: But they were still the last on disk so it was reasonable16:17
Davieycjwatson: I don't believe it was /ever/ in kubuntu16:17
cjwatsonxnox: No16:17
xnoxsnikker: can you reproduce this in a pbuilder? have you modified tzdata / ubuntu packages?16:18
xnoxsnikker: the test does not fail on ubuntu dev machines, nor in ubuntu sbuild / pbuilder.16:19
xnoxsnikker: if you really, really want to build ubiquity disable that test. but I'm guessing you are mixing up embeded software somewhere.16:19
xnoxcjwatson: Daviey: i'd like to drop all of the development seed. It only has a semi-random set of  python2 libraries that we want to all port to python3 and drop python2 equivalents from main.16:20
cjwatsonDaviey: Hard to debug at this point.  If you see oddities such as that again I'd be happy to look when the evidence is still present.16:20
cjwatsonxnox: If you do anything like that then please do a before/after comparison of germinate output to make sure that you aren't dropping things out of main that we want to keep supporting.16:21
cjwatson(In terms of source packages.)16:21
snikkerxnox: i don't have modified nothing... i'll try in pbuild...how can u disable the test?16:21
xnoxcjwatson: ack. that was my first though. cause something useful might be hanging on via that.16:23
cjwatsonstokachu,slangasek: I've created https://wiki.ubuntu.com/UbuntuDevelopment/RevertLog so that we can collect data about these kinds of discussions16:23
Davieycjwatson: turns out, that example you already did.. http://irclogs.ubuntu.com/2012/10/02/%23ubuntu-release.html#t18:32 :)16:24
stokachucjwatson: ok cool ill update the wiki with outcome16:25
=== brendand_ is now known as brendand
cjwatsonDaviey: you were apparently asking about package sets there, not about seeded-in-ubuntu output16:27
cjwatsonDaviey: so are you sure you're remembering it correctly now? :-)16:27
Davieycjwatson: Why let facts get in the way of a perfectly good rant? :)16:30
bdmurrayIs anybody uploading libgcrypt11 to raring?  If not I will.16:31
LaneyI'm test building it now16:31
Laneyyou can take care of rejecting the SRUs16:31
Laneyif not done already16:31
bdmurrayLaney: I did that already16:31
Laneystokachu: you don't need to explicitly target proposed when uploading to the dev series16:32
stokachuLaney: ok ill note that down16:32
seb128could somebody set https://code.launchpad.net/~betienne/ubuntu/quantal/gelemental/update/+merge/131998 to "Work in progress"?16:39
seb128 https://code.launchpad.net/~utlemming/popularity-contest/oneiric.lp707311/+merge/131878 to rejected as well16:39
seb128stgraber, ^?16:39
mptev, why have the 12.04 and 12.10 lines stopped?16:46
mptev, yes, at October 2616:47
mptwhereas the 13.04 line goes on to November 816:47
xnoxev: https://errors.ubuntu.com/ the graph not plotting 12.04 and 12.1016:47
evoh, that's fixed in trunk16:47
mptok :-)16:47
xnoxalso, raring has mood swings =)16:47
Laneystokachu: ok, seems to work, uploading16:48
cjwatsonso few users of 13.04 as yet that the granularity is rather coarse, I suspect ...16:49
cjwatsona lot of it seems to be failures to install ia32-libs-multiarch16:49
mptBy my calculations there are 40.5 machines running Raring16:50
xnoxmpt: 1/8 of which are mine.16:50
* Laney has 2 of them16:50
mptIt's probably the 0.5 of a machine that's causing all the trouble16:50
stgraberthat seems a bit low considering I have 8 just here, but quite a few never reported a crash so I guess that may still be correct ;)16:51
mptstgraber, yeah, I really mean 40 that have reported any errors so far16:51
* xnox is still at 1/8th16:52
* xnox goes to regenerate uuids....16:52
Laneystokachu: ok, done. I expanded your changelog a bit, fixed the target and inserted a bug reference16:52
cjwatsonia32-libs seems installable here, although I guess that's a relatively sensitive test16:53
cjwatsonbut proposed-migration *should* have rendered that much more robust in the development series16:54
stokachuLaney: ok thanks!16:54
cjwatsonfour of the six reports I saw were from the same user16:54
bdmurrayseb128: I've accepted libreoffice now16:58
seb128bdmurray, thanks a lot16:58
seb128Sweetshark, ^16:58
Sweetsharkbdmurray: thanks, awesome17:07
xnoxbarry: python3-chardet is packaged as a separate source package.17:15
xnoxbarry: so chardet is "ported"17:15
xnoxbarry: do I mark it green on the spreadsheet? remove it? or simply drop it from the tracker?17:15
barryxnox: yep, it's a separate upstream code base too17:15
xnoxbarry: is it compatible?17:16
barryxnox: in the 13.04 spreadsheet, i guess let's mark it green (doesn't matter too much i guess either way)17:16
xnoxbarry: how about I drop it from the tracker?17:16
barryxnox: i haven't done an exhaustive api comparison ;)17:16
barryxnox: +117:16
xnoxbarry: =))) http://people.canonical.com/~ubuntu-archive/transitions/onlypy3oncd.html17:17
xnoxbarry: similarly python-oauth should not be on the tracker, as we have oauthlib.17:17
barryxnox: agreed.  i'm in the process of filing bugs on the relevant task:destktop packages to switch to oauthlib17:17
xnoxbarry: ack.17:18
xnoxbarry: is oauthlib in main yet? (Main-Inclusion-Report etc...)17:18
barryxnox: that's a good question17:18
barryxnox: yes, i think so.  fwiw, upstream just released 0.3.2 and that's now packaged in raring.  it fixes all the outstanding bugs we've had (and quilt patches we were carrying)17:19
xnoxbarry: cool =)17:20
=== deryck is now known as deryck[lunch]
seb128@pilot out17:49
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
seb128stgraber, can you mark https://code.launchpad.net/~vanvugt/ubuntu/quantal/nux/fix-1039155/+merge/128422 as "work in progress" as well?18:02
=== mcclurmc is now known as mcclurmc_away
stgraberseb128: done18:05
slangasekseb128: I'm not convinced that LibO should have a general exception to the SRU rule of "fix in dev first", but it doesn't need to be a hard rule, yeah18:16
slangasekhallyn: udevadm trigger + containers> right, presumably you've already solved the general class of problem of udevadm called in a container18:16
slangasek(or will soon :)18:16
hallynslangasek: nope :)18:18
hallyni meant :(18:18
hallynthat's device ns18:18
hallynall we have now is a big stick18:19
hallyn("no writes under /sys)18:19
=== Ursinha_ is now known as Ursinha
=== rsalveti_ is now known as rsalveti
=== attente is now known as attente_zzz
=== deryck[lunch] is now known as deryck
=== yofel_ is now known as yofel
=== mcclurmc_away is now known as mcclurmc
micahg@pilot in18:59
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: micahg
micahgI forget, was it decided to enable proposed when test building?19:00
marruslquick question... even for raring, the changelog for a patch should target raring-proposed yes?19:10
ogra-cbno need for that19:10
dobeymarrusl: it doesn't matter if the changelog says raring or raring-proposed; it will go straight to -proposed anyway19:10
ogra-cbyour behavior doesnt need to change at all19:10
marruslwhile I'm here... is there a doc/wiki that will help me divine whether to bump the #ubuntu# version by 1 or .1 ?  (it's a really trivial patch)19:11
dobeydch -i19:12
* micahg wonders how ogra doe IRC over CB19:13
marrusldobey, I should be in a raring chroot though, yes?  or does that not matter.19:13
ogra-cbmicahg, using ubuntu ;)19:13
ogra-cband xchat19:13
micahgdobey: that's not clear19:13
dobeymarrusl: doesn't matter, you can change the entry to raring if it doesn't set it to it19:13
marrusldobey, right.  ok just wondering if that affects the behavior of dch -i....  which now makes no sense to me. basically I'm hearing trust dch -i  :)19:14
dobeymarrusl: using .1 is typically for special cases where the exact same version already exists on development version and stable version, and you need to update both; the stable version would get the .119:14
micahgmarrusl: SRUs general bump by .X, dev release is generally X, dch -i won't DTRT for the first SRU of something19:14
marruslaaah.... that helps!19:14
ogra-cbsecurity is also usually .X19:14
marrusldobey, micahg, ogra-cb .....  much appreciated!19:15
micahgsecurity update versioning is documented: https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging19:15
dobeymarrusl: simple solution; never trust software. but it's text file and dch -i just adds a new section. you can still tweak it appropriately in $EDITOR :)19:15
marrusldobey, right yeah, for something this minor I can't think of a good reason to bother with a chroot even.  that's pretty much what I've done before.  minimal effor... pull-lp-source; vi  :)19:16
micahgogra-cb: stgraber: is https://launchpad.net/ubuntu/+source/classmate-initramfs still useful?19:27
ogra-cbmicahg, no, should be burned19:28
micahgogra-cb: thanks, will file for removal19:28
micahgcan a TB person please mark this as WIP or rejected: https://code.launchpad.net/~vericalcroft/ubuntu/quantal/classmate-initramfs/added-misc-depends/+merge/12544219:30
micahgcan I get a TB person to mark this as merged: https://code.launchpad.net/~obounaim/ubuntu/quantal/z3c.formui/added-homepage/+merge/12541819:43
stgrabermicahg: done19:56
stgrabermicahg: feel free to highlight me directly for those, I don't always notice "TB" :)19:56
micahgstgraber: ok, thanks19:57
slangasekseb128: isn't the conclusion here that we should make Logan a MOTU and then the sponsorship queue will be manageable again? :)20:14
micahg@pilot out20:14
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
seb128slangasek, yeah, I told Daniel that he should get him onboard ;-)20:15
* slangasek grins20:15
obounaimmicahg, what does TB stands for?20:34
infinityobounaim: Tech Board.20:35
obounaimok thanks20:36
ogra-cbor thunderbirs if tou are in the #ubuntu-desktop channel ;)20:39
=== salem_ is now known as _salem
zZommmhello everyone, i have a packaging question, hope someone can help me here.20:55
zZommmi tried building libvirt-1.0.0 for quantal.20:56
zZommmthrew out a few patches that were not needed, a few other changes and now it builds.20:56
zZommmbut libvirt0 depends on libyajl1 instead of libyajl2. what could have gone wrong? libyajl1 is not even in quantal.20:56
zZommmshlibs:Depends is obviously right, because the library in the built package is linked to yajl1:20:58
zZommm$ ldd libvirt.so.0.1000.0  | grep yajl20:58
zZommm        libyajl.so.1 => not found20:58
slangasekzZommm: to have generated such a reference, you must have had libyajl.so.1 somewhere on your system when you built it.  Perhaps there's an embedded copy in the source tree?21:02
zZommmi'll check, but i doubt it.21:02
zZommmthis is a fresh quantal install and i've used pbuilder to build the package.21:02
=== attente_zzz is now known as attente
zZommmslangasek, no, nothing on the system with yajl and 1 in the name21:04
zZommmas i've said, fresh QQ install, pbuilder env created and this package built. Nothing else.21:05
slangasekzZommm: oh.  Does this show up when you instead run 'objdump -p libvirt.so.0.1000.0 | grep NEEDED.*yajl ?21:05
zZommmslangasek, yes:   NEEDED               libyajl.so.121:08
slangasekfun fun21:08
slangasekzZommm: well, it would be nontrivial to generate a library with that content without the library actually being present at build time21:09
zZommmyes it is :) the package build-depends on libyajl-dev, and that has only version 2.0.something available, it couldn't be anything else.21:09
zZommmi'll build again and keep the pbuilder chroot.21:09
slangasekright, let me check the *actual* contents of libyajl221:09
zZommmthis is a first one for me too, i've built (backported mostly) my fair share of packages and never encountered this.21:10
slangasekthe libyajl2 package in the archive is correct (filename libyajl.so.2, soname matches)21:11
slangasekis the source package that you're building available somewher?21:11
zZommmbut i can put it somewhere.21:11
zZommmjust a sec.21:11
zZommmslangasek, http://9bit.biz/libvirt/21:17
slangasekzZommm: and you're sure this isn't a matter of building it in the wrong pbuilder chroot?21:18
zZommmi'll check again21:18
slangasekbecause precise had libyajl121:18
zZommmthat was it21:19
zZommmpbuilder set up a wrong chroot21:19
zZommmstupid stupid stupid me for missing that21:19
zZommmthank you.21:19
slangasekaha, ok :)21:20
zZommmwho would have thought21:20
zZommmthat the debootstrap default on quantal is precise.21:20
zZommmaccording to the manpage pbuilder uses debootstrap default if nothing is specified21:21
=== cpg|away is now known as cpg
Sweetsharkanyone here able to nominate bug 1017125 for quantal pls? thx.21:24
ubottuLaunchpad bug 1017125 in boost1.49 (Ubuntu Quantal) "[SRU quantal] boost::unordered_multimap<>::erase(iterator, iterator) broken in boost1.49" [High,New] https://launchpad.net/bugs/101712521:24
Sweetsharkdisregard that. already happened21:28
cjwatsonzZommm: I can't see such a statement in pbuilder's man page, and debootstrap doesn't *have* a default21:32
zZommmcjwatson, let me check again... i might have misread. Anyway, i ran pbuilder create without any other parameters and it created a precise chroot.21:34
cjwatsonpbuilder has its own default21:35
cjwatsonwhich is indeed still precise21:35
zZommmmy mistake, yes. I was skimming over the manpage and somehow concluded that it used debootstrap defaults. which is strange, since debootstrap requires you to specify the distribution :)21:36
zZommmok, package built and installed, seems to be working :)21:40
zZommmshould i submit this somewhere? Debian already has libvirt-1.0.0 in experimantal, i just used the latest ubuntu packaging and applied it to the new version. I had to remove a few patches that are not needed anymore and make one or two other small changes.21:41
infinityzZommm: You might want to talk to smb and see what he's got going on for libvirt for raring.21:42
infinityzZommm: Or possibly hallyn.21:43
slangasekindeed, there was a UDS session about libvirt plans21:44
zZommmi'll check that out.21:44
sarnold.. I thought someone had a 1.0.0 ready to upload already?21:44
infinityThat's not much for session notes.21:45
zZommmi created a package because 0.9.13 (in Q) has trouble with openvswitch networking.21:46
slangasekthe blueprint has some notes, and also points at the people to harrass :)21:46
infinity(which happens to be the two people I mentioned, though in the inverse order)21:46
infinityzZommm: If you can identify what needs fixing and backport a patch to SRU 0.9.13, that might be nice.  We don't tend to push new versions to old releases, except in exceptional cases.21:47
zZommmi don't need you to put it in Q, i made this for me. But since the package should also work on R, I don't see a reason not to share it :)21:48
zZommminfinity, the problem on Q is that virt-manager does not really know what to do if you're using openvswitch. It just tries to use the classic linux bridge and fails.21:49
slangasekmdeslaur: that reminds me... did you have any further thoughts on the OVMF thing in virt-manager?  Given that we do have to change both the bios and the video bios21:49
zZommmlibvirt 0.9.13 supports ovs, but only if you change the XML config of a VM by hand. Creating a new network type with ovs config doesn't really work (well). Or so I've been told by a libvirt developer earlier today.21:51
zZommmI can't access that blueprint, seems i'm not sexy enough :)21:52
marruslzZommm, I think you just need to join the ~ubuntu-etherpad group in LP.  Anyway, that's the etherpad for the UDS discussion, here's the actual blueprint:21:58
zZommmi msgd him, but he's obviously not here, and I'm not on IRC 24/7. Should I send an email? would that be hallyn at canonical?22:03
zZommmoh i got it, i can get the email off launchpad. good.22:03
=== attente is now known as attente_zzz
mdeslaurslangasek: I've poked at it a bit, but I can't think of a good way to do it that isn't a complete hack....the best idea I've come up with so far is to define a new arch, ie: "x86_64 UEFI" or something, and use a qemu-system-x86_64-uefi wrapper23:08
slangasekmdeslaur: hrm; why is that better than just setting the xml options?23:09
mdeslaurslangasek: because the xml files are handled by libvirt, and virt-manager is a level of abstraction away from that, and all the options are determined by libvirt "capabilities"23:10
slangasekso would libvirt need extended first?23:11
mdeslauryes, and even libvirt doesn't really know things like filesystem paths, it's relying on qemu knowing all about that23:12
mdeslaurso in theory, you can specify the video bios as part of the xml definition of the video adapter, but that part isn't hooked up yet in the qemu libvirt backend23:12
mdeslaurit's a big abstracted mess23:13
slangasekcan you?  I didn't find a libvirt option for specifying a video bios, only a card type23:13
mdeslaurdevices, like network cards, have a "romfile" option23:14
mdeslaurqemu supports the same property for video devices23:15
mdeslaurslangasek: there's some info in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=81122723:15
ubottubugzilla.redhat.com bug 811227 in libvirt "RFE: Ability to specify custom BIOS for QEMU/KVM using <loader> XML (for WHQL testing)" [Unspecified,Closed: errata]23:15
mdeslaurslangasek: and also a link to how to combine the video rom into the main rom23:16
mdeslaurslangasek: but even if we do that, the gui would still be pretty awkward...ie: you'd have to manually specify an alternate bios for the video device, etc.23:17
mdeslaurwhich is why I was thinking of just creating a new arch (x86_64 EUFI)23:17
mdeslaurwhoops, UEFI23:18
slangasekright... it's also not great to allow users to specify incompatible combinations of bios and video rom23:18
mdeslaurthe ovmf package could ship the qemu-system-x86_64-uefi and qemu-system-i386-uefi scripts, which would just be a shell file that adds the appropriate option for the alternate directory23:19
mdeslaurand a trivial distro patch could be added to libvirt to gain knowledge of those two new archs23:20
mdeslaurit's also hackish, but that's where I'm at now23:20
mdeslaur(is i386 relevant for UEFI?)23:22
sarnoldmdeslaur: _maybe_ initial apple intel machines?23:23
mdeslaursarnold: I'm not sure that relevant for ovmf23:23
mdeslauroh, seems vvmf does have some 32 bit stuff23:24
cjwatsonmdeslaur: in principle, although not currently in practice for Ubuntu23:25
mdeslaurslangasek: do you have a package somewhere with the ovmf stuff in it?23:43
slangasekmdeslaur: not yet... jk took the action to provide that23:43
slangasek(I think he has a binary build floating about somewhere)23:44
jelmerOne of my syncs into raring was just rejected "Rejected by archive administrator.". How do I tell why that is?23:53
xnoxjelmer: DO NOT PANIC - we are removing armel23:53
xnoxjelmer: check the publishing history, probably just the armel binary was "rejected"23:54
jelmerxnox: ah, ok - thanks23:55

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