=== andreas__ is now known as ahasenack === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [01:29] smoser: lintian throws some warnings and errors on simplestreams, e.g. http://paste.ubuntu.com/6126373/ [01:31] sarnold, do do you have any idea what would do that ? [01:32] i udnestand the man pages. [01:32] but dont understand how 'python3:any' got in there. [01:33] smoser: not a clue on bad-provided-package-name python3:any -- is that ":any" supposed to be there? [01:33] $ grep any debian/control || echo no [01:33] no [01:33] ? [01:33] i'm sure its something 'ive done stupid. but i dont have a clue. [01:33] haha [01:33] (which is probably why i'm 'so sure it was something that i've done stupid) [01:35] man, I just hoped you'd know right off the top of your head a typo somewhere, but .. that's really confusing. [01:50] python3:any is new but it's ok http://lists.debian.org/debian-python/2013/09/msg00044.html [01:50] I guess you need to report a lintian bug then [02:19] dobey: rbasak if the python3 converted code leaked into the python2 package that indeed is bad (or vice versa) [02:20] dobey: rbasak: i'll double check it. But if you say it broke u1, surely it should have been stuck in -proposed because of u1's auto-package-tests, right?! === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [06:19] Can someone hit "rebuild" for language-pack-as and mesa? one failed in chroot the other failed to upload [06:24] Noskcaj: Done. [06:24] thanks [06:56] good morning === geser_ is now known as geser [08:22] dholbach, many, many, thanks!!!!!!!!!!!!! [08:33] nnnnnnnnnn/sb end [08:33] smartboyhw, That was a bit over-the-top, can you explain [08:34] Noskcaj, for sponsoring ubuntustudio-look :) [08:34] Noskcaj, and I'm not saying it to you:P [08:34] smartboyhw, I'm allow to be interested. It looks like studio will have a good release for 13.10 [08:56] Does anyone have a good pbuilderrc file for pbuilder-dist i can copy? it needs at least debian sid and ubuntu saucy support === tkamppeter_ is now known as tkamppeter === gusch is now known as gusch|lunch [10:11] Grr, I'd hoped I'd never have to use a hardy chroot again === freeflying is now known as freeflying_away === doko_ is now known as doko === MacSlow is now known as MacSlow|lunch === freeflying_away is now known as freeflying === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [12:14] dholbach: thanks for sponsoring several of xubuntu's pending packages [12:15] would it be possible for you to take a look at https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1227402 as well? [12:15] it updates each of our themes to their latest version which fixes some minor buglets and addresses some transitionary items [12:16] Ubuntu bug 1227402 in shimmer-themes (Ubuntu) "Please update shimmer-themes to 1.6.2" [Undecided,Confirmed] [12:16] bluesabre, I had a very brief look at it but couldn't quite figure out what to do with the debdiff or the branch [12:16] ochosi, our artwork lead, would have additional details to the changes involved [12:16] ah [12:16] in either case I couldn't produce a source package out of it [12:16] I see [12:17] let me add a comment to the bug so whoever takes care of it can leave some pointers for either myself or another sponsor [12:17] thanks a lot [12:17] normally we'd have one of our devs with upload rights take care of it, but both are currently away and are likely to miss the UIF [12:19] dholbach: thanks for your uploads so far, it's really great for us because (what bluesabre just said) [12:21] ochosi, bluesabre: https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1227402 [12:21] Ubuntu bug 1227402 in shimmer-themes (Ubuntu) "Please update shimmer-themes to 1.6.2" [Undecided,Incomplete] [12:22] thanks dholbach [12:22] I know I could just sign the source package which is in the branch (why?), but I wanted to understand a bit better what I'm uploading there :-) [12:24] fair enough. We have one developer who has been the sole maintainer of that package. We basically drop the latest git-tags of each theme into there and run debuild -S to produce the latest [12:24] ah no, hang on [12:24] as to what he usually does then, its beyond me, but since he has direct upload, its probably known only to him [12:28] bluesabre, ochosi: I still don't know how it's put together, but I could rebuild the source package and can upload it - I just took the liberty of adding (LP: #1227402) to the changelog entry so the bug gets closed automatically [12:28] Launchpad bug 1227402 in shimmer-themes (Ubuntu) "Please update shimmer-themes to 1.6.2" [Undecided,Incomplete] https://launchpad.net/bugs/1227402 [12:28] bluesabre, ochosi: maybe you can suggest adding a debian/README which describes how it's put together [12:29] dholbach: thanks a *lot* ! i can tell you this was a lot of work to put together (i mean the artwork stuff, but maybe also the complicated packaging, who knows ;)) and I'm happy to see it land before UIF [12:29] dholbach: yes, we've already requested the usual developer to do so when he's around next [12:30] bluesabre, ochosi: uploaded [12:31] \o/ [12:31] rock on! [12:31] dude, you rock! [12:31] +1 [12:31] keep up the good work! [12:32] dholbach: a big thank-you from the xubuntu dev-community! [12:32] bluesabre: no dholbach doesn't rock, more trance/techno/dance/dubstep [12:33] haha [12:33] I think what's happening here is that davmor2 is trying to sneak his own music wishlist in :-P [12:33] probably makes the loco meetings more fun [12:34] glatzor online? [12:35] Good morning [12:35] dholbach: No, just going for accuracy, I've heard you DJ it definitely isn't rock, it does however fall nicely into the other categories :D [12:36] I'm not quite sure about the categories, but yeah, Rock doesn't happen that often ;-) [12:39] pitti, apport-noui wants to demote. expected? [12:39] doko: yes, we don't need that on the phone any more [12:39] doko: and server guys certainly want to continue with -cli [12:40] it was a bit of an evolutionary dead end; I should discuss with ev whether we'll still need it at all [12:40] ok, demoted [12:48] jamespage, your libunwind merge ftbfs on every architecture [12:49] doko, yeah - I know [12:49] good =) [12:49] doko, something odd about linking for the mini-debug-info stuff [12:49] urgh [12:50] anything more specific? [12:50] doko, I need to refresh my memory [12:50] that happened > 2 weeks ago === MacSlow|lunch is now known as MacSlow === _salem is now known as salem_ [12:51] doko, the lzma linking was failing for one of the test binaries [12:52] I think I see that someone fixed upstream - I'll take another look [13:07] xnox, can I assign this one to you? bug #1227639 [13:07] bug 1227639 in python-repoze.lru (Ubuntu Saucy) "[MIR] python-repoze.lru needed as a b-d for routes" [High,Incomplete] https://launchpad.net/bugs/1227639 [13:14] doko, this is the build failure I see on i386 [13:14] http://paste.ubuntu.com/6128253/ [13:14] amd64 works OK [13:14] jamespage, looks like libunwind-coredump.so isn't linked with lzma === bfiller is now known as bfiller_away [13:18] fails on the buildd on amd64 too [13:19] doko, oh - does it? [13:19] xnox: paste doesn't work under python 3 either. the patches to make it "work" with 3 as well as 2 are broken. u1db dosen't have an autopkgtest yet, because i wasn't able to make it work right when i was trying to get it working, so i had to leave it out. i've recently discovered another way to do the tests for it though that might work, so i can try to get that in, but the package will of course be held in -proposed because pa [13:19] doko, ignore the failure for the one currently in proposed [13:19] the test failure is me not reading my own README.source [13:19] ahh, good =) === speakman_ is now known as speakman [13:27] Hi folks. I'm trying to build a package using pbuilder-dist, but it insists on running tests and since it's an x11 program it won't pass. How can I disable testing during pbuilder-dist build? [13:40] dholbash, hi [13:42] speakman: I don't know about pbuilder specifically, but in general you need to set or get it to set DEB_BUILD_OPTIONS=nocheck when running debian/rules. With sbuild you can just set the environment variable and it passes through. [13:43] (this assumes the packaging supports this standard) [13:45] is there a trick to make debmirror download Contents? [13:46] --getcontents [13:46] I got that [13:46] Not sure then [13:46] rsajdok: thanks, but I can't find a way to pass the DEB_BUILD_OPTIONS envvar to the "pbuilder" environment. I'll just try to set it in the running environment and hope for it to come along. [13:47] Looks like it worked! :) [13:54] hey. i was looknig at germinate output, basically auditing build process of cloud images. [13:54] https://bugs.launchpad.net/ubuntu/+bug/1224504 [13:54] Ubuntu bug 1224504 in Ubuntu "cloud image package list differs from germinate output" [Medium,Confirmed] [13:54] the build process installs 'ubuntu-minimal' explicitly. [13:54] jibel: do you know why the new python3.3 wasn't held back by the failing apport test? [13:55] is there any reason why we would do that? and if so, is there a reason I should'nt just add it to a seed ? And if so, why would it not be part of all seeds ? [13:55] jibel: someting changed in MIMEText which breaks the handling of encoding (I'm not yet sure whether apport did things wrong all the years or it's a bug in py3.3), but I thought such things were supposed to be kept in -proposed [13:55] Where do I fetch the final .deb when pbuilder is done? It looks disappeard currently. [13:56] doko, OK - fix uploaded for libunwind [13:56] smoser: Most of the packages you list there are installed conditionally and mustn't be seeded [13:57] smoser: and if you try to add ubuntu-minimal to any other seed you will blow things up [13:57] smoser: is any of this actually important? :-) [13:57] smoser: You absolutely must not seed grub-pc. === Guest72565 is now known as mfisch [13:58] smoser: (because that's hardware-dependent) === mfisch is now known as Guest1225 [13:58] it might put some pressure up to get the armhf port ready :) [13:59] ogra: I mean even within a single architecture. [13:59] yeah [13:59] cjwatson, i wont seed grub-pc. but couldn't i ? [13:59] cjwatson, has python3-defaults been forced to -release ? The test result is "apport 2.12.2-0ubuntu1 FAIL apport 2.12.2-0ubuntu1 python3-defaults 3.3.2-14ubuntu1" but it wasn't held back [13:59] smoser: efi, sure [13:59] ly [13:59] dobey, i reported a bug to debian yesterday on that apt issue and they argued themselves out of it being apt-s fault and closed it [13:59] smoser: It's generally a fundamental mistake to assume that the BIOS variant is the only one [13:59] none of it is really important, no. but i was just trying to understand why we would install 'ubuntu-minimal' and 'ubuntu-cloudimg^' [14:00] jibel: No, I sorted out some associated bugs but I didn't force it [14:00] smoser: It's usually a good idea to have the metapackages installed to aid upgrades [14:00] smoser: You've kind of misunderstood seed structure inheritance though [14:01] smoser: The cloud-image seed inherits from standard, yes, which means that germinate computes its expansion starting from the assumption that everything in standard and below is already installed [14:01] jibel, cjwatson: oh, I guess it's because apport depends on python3, not on python3.3 directly [14:01] smoser: But that doesn't translate into package dependencies [14:01] jibel, cjwatson: so it's again a transitive dependency, which we don't yet do unfortunately [14:01] How do I get the resulting .deb package after pbuilder is finished? [14:02] I can't even find the resulting name anywhere on my disk. [14:02] (especially because changes in python-defaults are much less prone to break other python stuff than changes in the actual python interpreters) [14:02] smoser: We deliberately omit those dependencies because if we include them then somebody who wants to vary a single choice we've made in, say, ubuntu-minimal, then has to remove ubuntu-standard and ubuntu-desktop as well [14:02] (or whatever) [14:02] smoser: So you need to track the seed inheritance structure when installing the metapackages/tasks in images [14:03] smoser: IOW you can't assume that installing a task higher in the structure will automatically pull in ubuntu-minimal - it won't [14:03] jibel: ok, nevermind then; I guess we just need to switch to transitive checks at some point [14:03] smoser: does that help? [14:03] maybe. but now i'm more confused. [14:03] so the change i made to structure [14:03] ping cjwatson and rbasak, any ideas how to reach the created .deb package from pbuilder? [14:04] speakman: I don't use pbuilder [14:04] that does not indicate that cloud image is a strict superset of server ? [14:04] cjwatson: ok :/ [14:05] smoser: Sure, but it doesn't translate into dependencies from any metapackage you generate from cloud-image [14:05] smoser: Nor does it mean that, e.g., the server task implicitly includes standard [14:05] it doesn't [14:06] smoser: now, ubuntu-minimal is probably unnecessary for a different reason: it's included by debootstrap [14:06] speakman: IIRC it's in something like /var/cache/pbuilder/result/ though [14:06] speakman: sbuild is more helpful: puts results in the current directory [14:07] i dont understand. what you mean by "the server task implicitly includes standard". [14:07] jibel, is there something wrong? === kentb-out is now known as kentb [14:07] my understanding was that it *explicitly* in STRUCTURE includes standard. [14:07] robert_ancell, hi [14:07] smoser: That only affects how germinate expands the dependencies [14:07] smoser: It intentionally doesn't translate into the Task fields in the archive [14:08] JackYu, hello [14:08] smoser: If nothing else, I have no interest in bloating the Packages file with a gazillion Task fields for everything in minimal ... [14:09] robert_ancell, would you help to upload the fcitx-qimpanel at bug #1226492? [14:09] bug 1226492 in UbuntuKylin "[FFE]upload fcitx-qimpanel into archive" [High,New] https://launchpad.net/bugs/1226492 [14:09] cjwatson, so we *should* be explicitly installing server^ in the build process ? [14:09] if in fact we want to say "its server + stuff" [14:09] smoser: Yes [14:09] JackYu, that has nothing to do with me [14:10] smoser: compare live-build/auto/config in livecd-rootfs [14:10] robert_ancell, oh, sorry. I saw you are the Pilot today:) [14:10] xubuntu) [14:10] add_task install minimal standard xubuntu-desktop [14:11] JackYu, sorry, not available at the moment [14:11] that seems repetitive. but OK. [14:11] smoser: a bit, yes. IIRC I tried the alternatives and they were worse. [14:12] (for other reasons) [14:12] ok then. do you have feelings on if i should put STRUCTURE back ? [14:13] smoser: That depends on whether you want cloud-image to be dependency-expanded with respect to server [14:13] I don't think my feelings come into it :) [14:13] robert_ancell, That's all right. Would you introduce someone available? [14:13] smoser: That said, cloud-image looks substantively duplicated from server [14:13] smoser: So it does look as though that STRUCTURE change might be a mistake [14:13] smoser: Either that, or there's a load of stuff in cloud-image that should now be deleted because it's already in server [14:14] smoser: Either way, you should indeed make the image build process line up with the seed structure [14:14] cjwatson: sbuild..? [14:14] smoser: And consider the future question of whether you might ever want something in the default server install but *not* in cloud images [14:14] speakman: apt-cache show [14:14] JackYu, according to the bug you need an archive administrator which is someone from https://launchpad.net/~ubuntu-archive/+members#active [14:15] alright. i'm gong to revert that change for now. [14:15] JackYu, like cjwatson :) [14:15] speakman: and https://wiki.ubuntu.com/SimpleSbuild [14:15] robert_ancell: he still needs a sponsor to upload it ... [14:15] robert_ancell, thank:) [14:15] not like me [14:16] I have a million things to do today [14:16] cjwatson: thanks [14:16] cjwatson, robert_ancell, yes, I'm looking for a sponsor... [14:16] Laney, why does bug 1226492 need an archive admin? [14:16] bug 1226492 in UbuntuKylin "[FFE]upload fcitx-qimpanel into archive" [High,New] https://launchpad.net/bugs/1226492 [14:17] cjwatson: A quick one; can I build i386 binaries on an x86_64 platform with sbuild? That's why I'm using pbuilder atm. [14:17] I know cjwatson is very busy:) [14:17] speakman: Yes, I do it all the time, you just need an i386 chroot [14:17] xnox: Would you have time to run an update of app-install-data-ubuntu in preparation for final beta? I notice you did some in raring [14:17] cjwatson: correct. Yeap, I can do that now. [14:18] cjwatson: thanks! :) [14:20] doko: seems last py3.3 is missing a Replaces: ? http://paste.ubuntu.com/6128496/ [14:20] speakman: (and rest per that wiki page) [14:21] doko: want a bug report for that? [14:21] pitti, hmm, it should have one ... [14:22] doko: not for libpython3.3-stdlib, only for pyton3.3 and python3.3-minimal [14:23] pitti, ok :-/ are the autopkg tests succeeding? [14:23] doko: for py3.3? yes, they got fixed; thanks! [14:24] we don't test upgrades in britney, though, so above upgrade bug wasn't detected [14:27] pitti, hi, would please help to review the FFE request at bug #1226492? [14:27] bug 1226492 in UbuntuKylin "[FFE]upload fcitx-qimpanel into archive" [High,New] https://launchpad.net/bugs/1226492 [14:27] JackYu: I'm not in the release team [14:28] pitti: you are an archive administrator? [14:28] JackYu: yes [14:29] pitti: Laney said this FFE needs an archive administrator agree:) [14:29] for NEW review, I guess; can do next week, I'm at a conference this week [14:29] pitti, uploaded [14:30] doko: danke sehr [14:30] pitti, this package would be installed in UbuntuKylin. we need upload this package first before upgrade our default-settings package:). [14:37] sbuild doesn't like --jobs=13. At least it doesn't pass it to dpkg-buildpackage [14:38] speakman: Are you sure? Remember that packages have to take explicit care to honour that. [14:38] cjwatson: I did work using pbuild and it's the same package. [14:38] "j|jobs=i" => sub { [14:38] push(@{$self->get_conf('DPKG_BUILDPACKAGE_USER_OPTIONS')}, [14:38] '-j'.$_[1]) [14:38] }, [14:38] seems fairly straightforward, in sbuild [14:40] speakman: What pbuilder invocation were you using to do this? [14:40] Because AFAICS parallel-build support isn't built into pbuilder ... [14:41] cjwatson: --debbuildopts [14:42] Perhaps use "ps aux" while sbuild is running to see what the dpkg-buildpackage command line actually is [14:43] /usr/bin/perl /usr/bin/dpkg-buildpackage -us -uc -mDaniel Nyström -b -rfakeroot -j13 [14:44] HM... [14:44] ogra: do you know if the ubuntu desktop "Texas Instruments OMAP4 (Hard-Float) desktop image" images are working currently? I can't get today's daily to do anything [14:44] Riddell, i have no clue [14:45] * ogra hasnt touched a panda in ages [14:45] cjwatson: http://pastebin.com/Cxpm42Ea [14:45] cjwatson: that's my sbuildrc [14:45] and i dont knw who is up to test them or something [14:45] ogra: do you know if anyone is looking out for it as part of beta 2? [14:45] speakman: sbuild is fine based on that command [14:45] nope [14:45] ogra: what hardware are the cool kids running these days? [14:45] Riddell, either desktop or QA i would imagine [14:45] cjwatson: I also have to make sure it doesn't run any tests (nocheck in DEB_BUILD_OPTIONS), how do I pass that to sbuild? Just setting the env var? [14:45] since it's manifestly passing it through [14:46] speakman: yep [14:46] Riddell, ubuntu touch on nexus devices :) [14:47] speakman: sbuild sanitises the environment but DEB_BUILD_OPTIONS is one of the ones it lets through [14:47] cjwatson: Great! === Maple__ changed the topic of #ubuntu-devel to: Ubuntu 13.10 Beta 1 released | Archive: Open, FF | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> raring | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: [14:53] fasf [14:53] you know [14:53] this needs +t [14:55] Maple__: it's deliberate since in practice it's not much of a problem [14:56] ...if you say so. [14:56] Maple__: And you don't seem to have actually changed anything from my point of view, just set it to the previous value [14:56] I do say so [14:56] If it becomes a practical problem we'll revisit [14:56] (If kicking offenders isn't sufficient) [14:58] cjwatson: and finally - after one day of trying to "cross" compile for i386 I did get one .i386.deb five minutes before "deadline". :D [14:58] cjwatson: thanks a lot for helping! [14:59] you're welcome === bfiller_away is now known as bfiller [14:59] I still do almost all my Debian uploads as i386 despite my host system being amd64, so it's a familiar process [15:07] * xnox started to do _multi and merge amd64&i386 uploads for some of my builds. [15:24] xnox: is "_multi" something sbuild-ish, or just means "you build for multiple architectures and merge the .changes? [15:26] pitti: Not sbuildish, just convention - dak doesn't actually care what the bit between _ and .changes is [15:26] pitti: build for multiple architectures, then use mergechanges -f foo*.changes. [15:27] pitti: mergechanges(1) produces _multi though [15:27] cjwatson: oh, as in "part of the .changes filename", thanks [15:27] pitti: mergechanges, defaults to _multi.changes suffix to not clobber up the rest (source, $arch) . changes. [15:27] nice, I didn't know about mergechanges [15:28] pitti: on #ubuntu-release & in-person there were requests about langpacks refresh. Not sure if it's time to do them again yet, or not. [15:28] xnox: we missed doing fresh -base ones for beta [15:28] cause e.g. archive rebuild is in progress. [15:28] pitti: =( ok. [15:29] xnox: I guess the next sensible -bsae refresh one would be before final beta, and/or final [15:29] xnox: but that's mostly about reducing image size [15:29] ack. [15:29] xnox: updates from LP are auto-uploaded twice a week === Guest1225 is now known as mfisch === cnd` is now known as cnd [16:45] xnox: still around? [16:47] doko: "Jenkins Fixed - saucy-adt-python2.7" \o/ thanks! [17:13] doko, barry: who could take a look at https://code.launchpad.net/~mitya57/ubuntu/saucy/python-defaults/2.7.5-5ubuntu1/+merge/185620? [17:14] * dobey wonders what to do about paste [17:15] dobey: yeah, here. [17:15] dobey: i think i fixed lint.py in debian now, what packages / where was paste failing for you? [17:15] dobey: so waiting on lp mirror to pick it up to merge it. [17:15] xnox: fixed it how? [17:15] it did unbreak convoy at least. [17:15] xnox: did you fix the package to run the unit tests at build time as well? [17:16] happyaron, is https://bugs.launchpad.net/ubuntu/+source/libchewing/+bug/1220224 something we still want to get into saucy? [17:16] Ubuntu bug 1220224 in libchewing (Ubuntu) "Sync libchewing 0.3.5-2 (main) from Debian unstable (main)" [Undecided,Incomplete] [17:16] dobey: which one? paste's? that's failing from before i started to touch it, so no, i didn't enable it. [17:16] xnox: it breaks u1db [17:16] xnox: yes paste. there seem to be a lot more issues than simply the StringType issue [17:17] dobey: let me test it know, just debuild would do? or do I need to run it? [17:17] dholbach: I think it's nice to have. [17:17] xnox: debuild should be enough, it runs the tests during the build [17:17] happyaron, ok, it's still sitting in the sponsoring queue [17:17] good [17:17] dobey: doing test-build against the updated paste now. [17:18] xnox: can you link to the fix you applied to paste? [17:18] dobey: build succesful. [17:18] dobey: well it's in the debian svn / upload. I can link to it once launchpad imports the debian upload..... [17:19] hmm [17:21] xnox: ok, please ping me when it gets merged into saucy [17:21] zul, can you subscribe the server team to blinker bugs? (it needs to be in main for flask) [17:21] blinker bugs? [17:22] mterry: doh...done :) [17:23] dobey: ack. [17:23] zul, thanks. I already patched it to run tests. Seems fine besides [17:23] zul, bug 1227623 if you're curious [17:23] mterry: coold thanks [17:23] bug 1227623 in blinker (Ubuntu Saucy) "[MIR] blinker required as b-d and as recommends for flask" [High,Fix committed] https://launchpad.net/bugs/1227623 [17:36] dholbach: i will look [17:36] thanks [18:00] @pilot in === udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.10 Beta 1 released | Archive: Open, FF | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> raring | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: barry === Maple__ is now known as o3o [18:25] so what magic needs to happen to make the PS auto-uploader actually upload ubuntu-themes in the next 2 hours or so to meet the UIF? [18:28] ev: fginther: ^ [18:31] pitti, are the necessary changes in trunk? [18:32] fginther: yes. [18:32] robru, can help then ^^ [18:33] pitti, hi. i will kick off a release build of misc stack for you (this includes ubuntu-themes) [18:34] robru, thanks [18:40] fginther, pitti: ok, it is done. you should see ubuntu-theme package upload soon. [18:42] pitti, although, I disagree with your changes to the version number... like all daily_release packages, it's built in split mode, which means orig.tar.gz is created by deleting debian/ dir. [18:46] pitti, so with daily_release'd stuff, you only have control over the part of the version number to the left of the '+' sign... the rest is automatically added by jenkins in order to identify when it was released. === Ursinha is now known as Ursinha-afk [18:55] robru: oh, I see; well, I can back that out [18:56] robru: but I was worried as there is no obvious way to build an orig for myself, nor any real "upstream" [18:56] robru: but can we at least drop the 13.04+13.10 stuff? [18:56] pitti, I already fixed the changelog in trunk. [18:56] robru: ok, thanks [18:56] pitti, the 13.10 bit has to stay, but if you want to change the '13.04' part to something else, go right ahead. [18:57] pitti, and if you 'bzr bd' in the branch, it will make orig.tar.gz for you [18:57] robru: yes, basically just drop the 13.04+; that seems useless? [18:57] robru: but oh well, it's already uploaded now according to the changelog, so nevermind [18:57] pitti, I agree, but there needs to be something there for jenkins to build off of. we should discuss with didrocks what makes a good version number. [18:57] robru: thanks for getting it into the archive! [18:58] robru: actually, no -- https://launchpad.net/ubuntu/+source/ubuntu-themes/13.04+13.10.20130919.2-0ubuntu1 doesn't seem to contain my changes? [18:58] pitti, hmmm, let me check [18:58] ah no, that can't be that upload [18:58] robru: that said the upload was from 4 hours ago [18:59] so we need another one with xnox's and my changes [18:59] pitti, hmm, that's strange. it looks like it missed your commits. I'll try it again [18:59] robru: no, xnox' and my commits presumably haven't even been there 4 hours ago === ampelbein_ is now known as Ampelbein [19:00] pitti, i think that timestamp is wrong, because the version number matches what just got uploaded [19:02] pitti, yeah, that's definitely the build I just kicked off, see here: http://10.97.0.1:8080/job/cu2d-misc-saucy-3.0publish/16/console most recent build in the system, and the version number matches. not sure why it says 4hrs ago, maybe one server has a bad clock somewhere/ [19:02] also not sure why it didn't get your commit, but will try again [19:03] robru: ah, so it hasn't actually been uploaded to saucy yet? [19:03] robru: as https://launchpad.net/ubuntu/+source/ubuntu-themes/13.04+13.10.20130919.2-0ubuntu1 definitively doesn't have the latest changes [19:03] pitti, it made an upload but for some reason it didn't include your commit. [19:03] robru: or the tree from xnox [19:03] pitti, this is an issue that has bit me a couple times recently, it's like the jenkins job is caching launchpad branches so it doesn't see new commits sometimes [19:05] pitti, hmmm, jenkins claims to have released revision 315, which would include xnox's work. are you sure it's missing? [19:05] robru: the upload timestamp says "Thu, 19 Sep 2013 14:05:04 +0000" which roughly coincides with "4 hours ago", though [19:05] robru: perhaps that was an auotmatic one? [19:06] pitti, no, automatic uploads are disabled, things are kind of a mess right now. [19:06] robru: ah yes, so 315 has xnox' merges, but mine was 316 [19:06] latest one is 318 [19:06] yeah, ok I'll run it again and hope for the best [19:06] robru: thanks [19:08] pitti, you're welcome [19:10] pitti, hmmm, still doesn't seem to have found it. last time this happened to me it took ~12 hours before jenkins saw the latest commit [19:12] pitti, you might want to file your UIFe now, if necessary. [19:14] smoser: Weren't you going to seed ubuntu-cloudimage-keyring somewhere to keep it in main? [19:14] smoser: (Or have something depend on it) [19:16] infinity, maas will depende on it. [19:16] can i recommends it? [19:16] smoser: Recommend would be fine. Also, cloud-utils wants to move to universe too, is that meant to be? [19:16] Hi! Can patch pilot look at this fix for raring - https://code.launchpad.net/~albertsmuktupavels/ubuntu-themes/restore-space-between-applications-and-places-in-gnome-panel-raring === smb` is now known as smb [19:17] infinity, cloud-utils is in cloud-image seed. [19:17] smoser: Is not. [19:17] smoser: cloud-init and cloud-guest-utils are, but not cloud-utils. [19:18] cloud-guest-utils is binary from cloud-utils. [19:18] is that not enough? [19:18] cloud-utils is now metapackage. [19:18] smoser: Sure, it's a metapackage that depends on cloud-guest-utils and cloud-image-utils. Is all of that supposed to be in main, or just cloud-guest-utils? [19:19] smoser: If it should all be in main, you should seed the metapackage somewhere. [19:19] smoser: Especially if this is required for smooth upgrades from precise. [19:20] smoser: So, you seed cloud-guest-utils to cloud-image, I'd suggest that you might want cloud-utils in supported. [19:20] cloud-guest-utils and cloud-image-utils should be in main. [19:21] yeah. i'll add it in supported. [19:21] Thanks. [19:22] and maas will have the dependency on cloudimage-keyring sometime soon [19:23] roaksoax, ^ can you add that ? [19:23] for your next upload [19:23] Depends: ubuntu-cloudimage-keyring [19:32] smoser: for maas? [19:32] yes [19:33] smoser: what is that for? [19:33] smoser: i mean, what tool? [19:33] region/cluster? [19:36] whatever downloads ephemeral images. [19:56] barry: do you have time? [20:07] alberts: hi, what's up? [20:08] barry: hi! I see you are patch pilot. can you look at this - https://code.launchpad.net/~albertsmuktupavels/ubuntu-themes/restore-space-between-applications-and-places-in-gnome-panel-raring/+merge/178242 [20:08]