=== jjohansen is now known as jj-afk [01:12] who is a good target for pestering about invoke-rc.d and the equivalent upstart stuff? [01:16] SpamapS probably [01:16] or slangasek, if you're asking about policy stuff around that [01:26] lamont: What did you want to whine^H^H^H^H^Htalk about regarding invoke-rc.d? [01:27] SpamapS: puppet uses it to tell what runstate we're in, and well, when puppet starts during system start up, it goes 'zomg dunno', and the dryrun output looks fugly. [01:28] I'd like something cleaner than: @reboot root echo service puppet restart | at now+2min [01:33] lamont: is puppet starting as a sysv init or an upstart job? [01:34] sysv [01:34] lamont: if it needs to run before anything else ever.. it needs to be converted to an upstart job most likely. [01:35] lamont: the alternative is starting it manually in an upstart task at the appropriate time [01:35] lamont: I would think puppet should run very late in the boot tho [01:35] like, almost last [01:35] well, actually, i think the real right answer is not to have puppet cache the startup answer FOREVER [01:35] since, you know, init level could change [01:36] so it checks the output of the 'runlevel' command ? [01:36] I'm not really sure I understand the problem actually.. :-P [01:38] invoke-rc.d --query [01:38] and doesn't like 105, which it then caches forever [01:38] which I believe to be a bug. [01:38] so nm... off to file a bug against puppet [01:40] Yeah.. I see now.. 105 is "don't ask me, I just work here" [01:41] They should probably check for an upstart job if 105 is returned. [01:44] SpamapS: and more to the point "we're in startup, so I really don't know" [01:45] the job in question isn't an upstart job [01:45] right yeah that sounds like a bug in the way they're handling the uncertainty [01:46] mind you, ISTR that adding support for upstart was on the roadmap for puppet/oneiric [01:46] which will be nice [01:46] as long as upstart doesn't make changes to make that possible [01:47] There's talk of having a more definitive "disable" capability added [03:26] Is that the burn with fire option? === TerminX_ is now known as TerminX [05:18] Good morning [05:21] morning pitti [05:23] Whoah. It's LaserJock. [05:23] Hello LaserJock [05:26] hey LaserJock, how are you? [05:27] I'm doing OK [05:27] morning pitti [05:27] a bit jobless atm (hence being on IRC) but otherwise OK :-) [05:28] * StevenK rubs eyes, looks again [05:30] I know, I know, it's been a while [05:30] no excuses [05:30] Haha [05:30] I got a PhD, move to Boston, taught a couple classes at my alma mater, and am now ... here [05:44] http://paste.ubuntu.com/612150/ ->ireally need this ! please, help me [05:57] !support | hmchinh1986 [05:57] hmchinh1986: The official ubuntu support channel is #ubuntu. Please be aware that this channel is for development only. [06:00] ok === _LibertyZero is now known as LibertyZero [06:54] hello room i have to go to bed. sorry... [07:47] pitti: Can you think of a library package off-hand that is in main but has some binary packages in universe? [07:53] StevenK, IIRC for jackd the library is in main but the daemon in universe [07:53] diwic: I thought of a victim package already, but thanks [07:54] good morning [07:54] good morning didrocks [07:54] hey diwic [08:00] good morning [08:02] hey dholbach [08:02] hi didrocks [08:09] the new dbus depends on netbase (>= 4.45ubuntu3), but the one uploaded yesterday was 4.45ubuntu2 ? === smb` is now known as smb [08:22] @pilot on [08:22] (pilot (in|out)) -- Set yourself an in or out of patch pilot. [08:22] @pilot in === udevbot_ changed the topic of #ubuntu-devel to: Oneiric Archive: OPEN | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> natty | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: smb === doko_ is now known as doko [08:31] StevenK: libnotify as well, if you want something tiny; libnotify-bin is in universe === yofel_ is now known as yofel [09:51] SpamapS: FYI, fixing dbus netbase dependency to a version that actually exists, to make dbus installable again === hunger_ is now known as hunger [10:39] is it known that cdbs is uninstallable on ppc? [10:39] Laney: Half the archive is not installable on ppc :( Are you talking about Natty or Oneiric? [10:39] oneiric [10:40] cdbs is hardly 'half the archive' though — it's a relatively high-up package [10:41] it's probably the dbus breakage, which powerpc is an archive cycle behind on [10:41] cdbs : Depends: dh-translations but it is not going to be installed [10:42] no idea, I'm not a big archive evaluator, especially not on [ shadeslayer] [ vrodic ] [10:42] oops [10:42] again I wish for BD-uninst in launchpad ;-) [10:42] blame the new gnome-control-center for pasting things randomly [10:42] Laney: yeah, this really should be considered as depwait [10:43] Y'know, I had half-finished an uninst->dep-wait parser years ago... [10:43] pitti: I filed bug 5277245 for that some time ago [10:43] Error: Launchpad bug 5277245 could not be found [10:43] er [10:43] hmm, not dbus [10:43] bug 5272453 [10:43] Error: Launchpad bug 5272453 could not be found [10:43] bug 527245 [10:43] Someone should talk me into finishing it. [10:43] Launchpad bug 527245 in Launchpad itself "Implement a BD-Uninstallable build state" [Wishlist,Triaged] https://launchpad.net/bugs/527245 [10:43] argh! [10:43] Package liblwp-protocol-https-perl is not available, but is referred to by another package. [10:43] hm, and everything FTBFSes on armel :/ [10:43] I've seen a couple of ld segfaults [10:43] Laney: That build state shouldn't exist, the correct solution is to drill down for the right dep-wait. [10:43] I think I just NEWed that [10:44] including the dbus fix [10:44] yeah, it's accepted, next publisher cycle should fix it [10:44] it's more complicated than dep-wait [10:44] Laney: Not in this case. [10:44] this case should be dep-wait: liblwp-protocol-https-perl [10:45] sometimes discovering the correct dep-wait is AI-complete though [10:45] Laney: If you literall mean "failed installation", then yes, you can't always intelligently dep-wait on, say, broken postinsts. [10:45] Laney: But "apt can't even being to install" (which is the case here) is always a dep-wait. [10:45] Laney: Just not always an immediately obvious one. [10:45] cdbs: lol [10:45] oh, hmm, liblwp-protocol-https-perl needs an emergency MIR [10:46] in fact that's a split-out, so I'll promote it [10:46] shadeslayer: Sorry for the ping, its because the new GNOME3 stack doesn't play well with Unity and can behave really weirdly at times [10:46] can you dep-wait on multiple packages? [10:47] * cjwatson does the override-in-accepted-queue trick [10:47] You can call it the same thing if you'd like, but I suspect you'll end up implementing a rather similar solution to that which Debian did :-0 [10:47] :-) [10:48] Laney: Debian's solution re-checks installability, and is fairly opaque to the end user. But it's the same concept, yes. [10:48] it uses an external tool to determine the same information, indeed [10:48] what does it do, edos-debcheck? [10:48] Laney: (Debian does dep-wait checks before pushing to needs-build, our checks happen at a different time, so the solution is different regardless) [10:48] cjwatson: yeah [10:48] cjwatson: Aye. [10:50] cdbs: yeah no problem ;) [10:50] Laney: Either way, I agree that the functionality's been missing for a while, it just failed Round Tuit tests, I guess. And the only person who cared stopped working on lp-buildd for a year and a half... [10:51] Laney: (The only person who seemed to care about this feature, that is, not lp-buildd entirely) [10:56] huh, cron update broke my personal crontab [10:57] nah, not a package update, but something did corrupt it [10:59] infinity, So, what is a good way to generate a solution. Cookies? [11:01] persia: Peanut butter cookies! [11:01] Oooh. That makes it trickier. [11:02] You'll sort it out. You're a clever man. [11:18] pitti, have you looked into this ffmpeg/libav issue on the t-b list? [11:18] (April) [11:18] mdz: we quickly discussed it in the TB meeting [11:18] pitti, is it safe to let the mails be archived, or do I need to pay attention to it? [11:18] mdz: the outcome was that we really need to hear both sides of the story, someone had an action item to follow up with siretart [11:19] , [11:19] ok [11:20] sabdfl: do you happen to have the minutes from that meeting somewhere? we should add them to https://wiki.ubuntu.com/TechnicalBoard/TeamReports/11/May [11:20] pitti: i definitely edited it [11:20] did i forget to save it? [11:20] fml [11:20] sabdfl: used editmoin by any chance? then they might still be in ~/.moin_lastedit [11:21] * pitti was rescued more than once by that [11:21] no, just in-browser [11:21] chrisccoulson_: please add full automatic etherpad-like revision control to firefox input fields :) [11:22] heh :) [11:25] pitti: "Lazarus" does that partly ;) [11:27] cjwatson, i am about to do the MIR for the linux-lts-backports-natty backport kernel. we don't seem to have any written proceedures for this, and its a little bit of an odd case as its not in universe currently, should i be uploading it to lucid -proposed in advance ? [11:28] meh, I don't think the backport kernel bits need MIRs [11:28] ^ === MacSlow is now known as MacSlow|lunch [11:28] technically yes it's a new source package in main, but we've already had source packages with the same purpose in main before [11:29] and basically the same set of code [11:29] As long as there's a sane rationale for it existing at all, we already trust upstream and downstream maintainers. [11:29] cjwatson, ok so just go ahead and upload it to lucid -proposed and get with your to get it sorted out ? [11:29] well, not me, but yes [11:29] linux-lts-backport-maverick was just uploaded to lucid-proposed [11:30] and it clearly can't go to a development release first [11:30] cjwatson, yeah thats the previous one, so i'll just get it uploaded :) [11:30] except in the sense that the same code is already in the real kernel in newer releases [11:30] right its identicle in code terms, packaging is slightly neutered to produce less architectures otherwise identicle [11:38] infinity, Just to confirm, do the numbers 616, 4640, 52 and 6716 seem likely to be useful? [11:38] persia: I'm not a cookie expert, but I suspect you might be barking up the wrong tree. [11:40] cjwatson: do you know why translatoid isn't auto-synced? [11:44] sync-blacklisted: translatoid # james_w: Older version in Debian causing issue for autosyncer, drop this entry later. [11:44] I can retry it [11:45] debfx: seems fine, synced now [11:46] thanks [12:18] seb128, pitti: could you have a look at component-mismatches? tracker xmldiff lightdm [12:22] doko, do we care that early in the cycle? [12:23] seb128: yes, I care about buildability [12:23] doko, ok so you are welcome to file mirs for those ;-) [12:23] rodrigo is working on dropping the tracker one [12:23] xmldiff needs investigation [12:23] ScottK: muon tries to pull in libqzeitgeist [12:23] lightdm needs a mir if it didn't get one yet [12:23] ok, thanks [12:24] doko: I'll ask someone to look into that. [12:25] I imagine you'll see a MIR shortly since adding that feature was entirely not accidental. [12:28] seb128: there is one filed by robert [12:28] doko, ^ what is the issue with lightdm? there is a mir waiting for it [12:28] didrocks, thanks [12:29] seb128: ahh, didn't update the page [12:31] ok [12:37] seb128: if we don't care early in the cycle, we end up panicking latere [12:37] *later [12:39] cjwatson, well there is some desktop ones we know about but we are just busy and didn't manage to get to those yet [12:40] seb128: sure, nobody expects it to be at zero; all I'm asking is that we don't blow off people when they ask about it [12:41] cjwatson, ok, fair enough, the question was rather to know if we should drop everything we are doing and prioritize those or if they can wait a few days [12:42] we seem to have this conversation every time somebody from the archive team asks about something :) [12:42] we'll tell you if it's drop-everything urgent ... [12:43] pitti: i found a copy of the minutes i had [12:43] can i just save it to .../11/May ? === MacSlow|lunch is now known as MacSlow [12:44] cjwatson, ok, I never if people ping to raise a bit the priority or just as an informational hint when they do ping about such things ;-) [12:45] well, I would expect that it's generally meant to raise the priority above background-noise, since there's an awful lot of the latter [12:47] well in any case we might need a better way to list those as "block <....>" where .... can be CD build or other thing because IRC pings are not really the best way to deal with such notices [12:47] especially than often it doesn't reach the right people [12:48] like xmldiff is coming from a sync of debian, I'm fine having a look when I will have time but other people might be less busy or have a better clue about it [12:54] pitti, mdz: https://wiki.ubuntu.com/TechnicalBoard/TeamReports/11/May === zyga is now known as zyga-afk [13:02] sabdfl, thanks [13:09] doko: did you promote qt-gstreamer as well? [13:09] or do we fix the said issues first? [13:12] thanks! [13:18] doko: If you're still on component mismatches, please promote kdegames-card-data-extra binary. It's a split of an existing Main package that inadvertently dropped to Universe in Natty. I've just seeded it so it'll show up on the next component mismatches run if not promoted. [13:19] doko: robert is writing a MIR for lightdm, but that doesn't affect buildability [13:19] it was just added to the seeds [13:20] xmldiff seems harmless, we can do a MIR [13:20] sabdfl: thanks [13:21] pitti, the mir is already written [13:21] seb128: IMHO we should fix brasero to not pull in tracker, OK for you? [13:22] pitti, rodrigo is already on it, we discussed that on #ubuntu-desktop early today [13:22] ah, cheers [13:28] seb128, pitti: is bacula desktop stuff? tries to pull in postgresql-8.4 [13:28] no it's server [13:28] probably enough to bump the b-dep to -9.0 [13:29] Daviey: bacula ^^^ [13:29] Daviey: ^ [13:29] faster ;) [13:29] * Daviey looks [13:30] doko, it's 'both' :) [13:31] cool, aliasing 'both' to 'not me' :) [13:31] bah.. it's the foundations that ties desktop to server :) [13:32] ScottK: done [13:32] doko: Thanks. === ihateyou1oo is now known as elmo === akher0n is now known as akheron === Quintasan_ is now known as Quintasan [14:05] @pilot in === udevbot_ changed the topic of #ubuntu-devel to: Oneiric Archive: OPEN | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> natty | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: ogasawara, smb === dendro-afk is now known as dendrobates [15:05] slangasek: I posted the initial review for libtirpc in bug 781516 and I'm now looking at rpcbind. For libtirpc it seems like I could just re-upload the package without the build-dep on libgss-dev as it doesn't seem to be used at all, though if you know that package better than I do, I'd appreciate a second opinion. [15:05] Launchpad bug 781516 in rpcbind (Ubuntu Oneiric) "[MIR] libtirpc, rpcbind" [High,Incomplete] https://launchpad.net/bugs/781516 [15:22] pitti or SpamapS: (I assume) one of you copied qt4-x11 from natty-proposed to natty-updates, but didn't forward copy to oneiric. I'd appreciate it if one of you would do this to save an upload/multi-day build. [15:24] I could just do another bulk copy run [15:24] That would work for m. [15:24] m/me [15:25] and it's just qt4-x11 at the moment anyway [15:25] done [15:26] Thanks. === jtechidna is now known as JontheEchidna [15:37] jhunt, who looks after udev ? [15:37] apw: You. Didn't you get the memo? [15:38] pitti, i think you sync'd udev recently? am getting reports that a full oneiric install is a 25% chance of booting, downgrading udev sorts it ... no real details other than that yet [15:38] apw: not synced, updated, but yes [15:38] apw: do you have a machine which reproduces it? works fine here (oneiric du jour, but I never had such a problem any time in oneoric) [15:39] oneiric .. one eye rick .. whatever [15:39] pitti, i've asked them to get it all in a bug and i'll get the number i [15:39] when i have it ... nothing here with oeniric userspace as yet [15:41] apw, pitti: I "think" I have this issue in one of my VMs here. Gets stuck at boot time almost 50% of the time, rebooting eventually makes it start. [15:41] it's a simple server VM with just isc-dhcp-server, radvd and ssh installed, so nothing fancy [15:42] stgraber, yep, looks like a broked udev, with udev barfing about Address already in use [15:42] pitti, i'll have to get a vm updated to oneiric then [15:42] sig [15:42] sigh [15:45] apw: FTR, there are several folks in #u-desktop running oneiric as well, haven't heard about problems from anyone; might that be kvm specific somehow? [15:46] pitti, checking with my reporter ... possible indeed [15:47] pitti, ok this one is a real machine ... will see what i can find out once we have a bug [15:47] kirkland: not sure if you get at all into this kind of maintenance for byobu, but one thing that bugs me is that in escape mode, i can't do things like 'f' - it just brings me back to insert mode. Have you considered fixing that? [15:48] hallyn: hmm, i'm not sure I understand the problem, but I'd like to ... can we take this to #ubuntu-server ? [15:50] doko, do you know how i can see a java console (in firefox) with openjdk ? [15:51] k [16:02] hi pitti. Could you point me to that wiki page where the syntax of work items in a blueprint's whiteboard is explained? [16:02] dpm: https://wiki.ubuntu.com/WorkItemsHowto#Defining%20work%20items [16:02] pitti, great, thanks [16:13] doko: do we miss anything important with the last gcc-defaults upload being "Failed to upload"? (https://launchpadlibrarian.net/71061220/upload_2523174_log.txt) [16:18] pitti: huh? did I typo the version? [16:19] SpamapS: yes, you said >= ubuntu3, but netbase is at ubuntu2 [16:20] pitti: oh no the real problem is that I didn't upload netbase 4.45ubuntu3! [16:20] pitti: 4.45ubuntu2 is bad [16:20] SpamapS: hm, the changelog of https://launchpad.net/ubuntu/+source/netbase/4.45ubuntu2 seemed to add what you wanted [16:21] pitti: but --wait is a non-existant parameter [16:21] pitti: I forgot to debuild -S again and upload.. the .deb I was using to test was 4.45ubuntu3 [16:22] SpamapS: ok, sorry about that; then I figure you need to revert my dbus change as well [16:22] pitti: I'll take care of it [16:23] ahh oops.. I accidentally tried to upload 4.45ubuntu3 to natty. [16:23] thats what I get for not going to inbox 0 every day. ;) [16:23] * SpamapS really wishes the upload process would tell him that and not an email 5 minutes later [16:32] stgraber: hmm, I don't know why libtirpc would need libgss-dev, but I also can't categorically say that it's spurious... I don't know what's going on there [16:43] dholbach: Where can I find these open backports request statistics? [16:44] ScottK, on my local hard-drive - I'll publish in a bit [16:44] dholbach: OK. I was going by the "DONE" status in the work item. [16:45] I'll update the blueprint with an url in a bit [16:45] I guess the work item was for create. [16:45] Sharing would be another one. [16:45] ;-) [16:45] Thanks. [16:45] [5~/wg 159 [16:45] bah [16:46] smoser: I think the icedtea plugin never had one [16:47] geser: know, currently doesn't hurt [16:47] so how should one go about seeing java console output? [16:47] is there anything better than running firefox from a console and getting the output there? [16:51] doko: I'm promised the libqzeitgeist MIR will be filed 'today'. Not sure how that relates to today where you and I are, but soon in any case. === jj-afk is now known as jjohansen === beuno is now known as beuno-lunch [17:03] ScottK, published the url - the reason they look boring and have no lines is because there's just one data point right now :) [17:03] Right. Thanks. [17:08] * pitti chuckles at SpamapS' dbus changelog -- I declare defeat! [17:09] SpamapS: now you are TIL again, I'm not unhappy about this ;) [17:15] pitti, ping [17:17] pitti, I have reported a CUPS SRU bug, bug 787635. The special thing is that I have discovered the problem and I have fixed it and posted the SRU. How does the verification work then. I have naturally tested the fix and it works for me. [17:17] Launchpad bug 787635 in cups (Ubuntu Natty) "Natty SRU: pstopdf not working correctly with non-default paper sizes" [Medium,Fix committed] https://launchpad.net/bugs/787635 [17:20] tkamppeter: first it should be fixed in Oneiric actually. [17:21] tkamppeter: once it is in Oneiric, the fixed package should be available in natty-proposed for 7 days at least, and at least one user needs to "verify" the package, then it should move to natty-updates === zyga-afk is now known as zyga === dendrobates is now known as dendro-afk [17:41] SpamapS: Looks like a fun FTBFS on armel for you to go with your witty dbus repartee. [17:47] ScottK: yeah I saw the earlier build failure too. :-/ [17:49] collect2: ld terminated with signal 11 [Segmentation fault] [17:49] Toolchain bug? [17:50] slangasek: as building with and without libgss-dev gives me an identical resulting lib, I'd be tempted to just drop the build-dep. I'll poke the Debian maintainer see if he knows why the build-dep is there. [17:51] SpamapS: ld should never segv, so yes. But you may be able to work around it fiddling with flags. [17:51] SpamapS: (Which can be handy in isolating the bug too) [17:52] stgraber: cool, thanks === deryck is now known as deryck[lunch] [17:55] slangasek: the Debian maintainer is planning on uploading a new upstream release and will drop the build-dep in that upload. I guess we can just wait for it then. [17:55] cool [17:56] infinity: I suppose first tep would be getting access to armel hardware.. :-P [17:56] SpamapS: qemu, go? [17:57] I have zero experience w/ this [17:57] if there's a HOWTO tho.. I'd be interested in playing [17:58] SpamapS: https://wiki.linaro.org/Resources/HowTo/Qemu-beagleboard [17:58] that's for full-system emulation [17:58] alternatively, you can do a qemu chroot [17:59] not sure if we have a howto for that somewhere [18:00] slangasek: ty! [18:01] SpamapS: if you just want syscall emulation on a chroot, you can install qemu-user-static and use /usr/sbin/qemu-debootstrap to set up a chroot [18:01] (will run faster than whole-machine emulation) [18:01] SpamapS: I was planning on setting up my pandaboard with LXC a bit later today so I can easily run multiple Oneiric ARM systems for testing. I can probably give you access to one of them once it's ready ;) [18:01] But won't catch if your ld segv is actually a kernel bug. [18:02] (But it probably isn't) [18:02] slangasek: I think given the segfault I want full machine [18:03] SpamapS: Generally not, unless you really do suspect the kernel. [18:03] SpamapS: And then, you need to run against the same kernel the buildds are using... [18:03] SpamapS: what infinity said; 9 times out of 10 you'll be able to reproduce with just syscall emulation, which is faster *and* easier to configure, so you might as well try it first [18:04] Ahh ok [18:05] SpamapS: Realistically, if the kernel *is* breaking ld, you'd be seeing it across many/most builds. If you're just seeing it in a specific case, it's probably binutils. [18:05] SpamapS: (And it's binutils being tickled by a very specific grumpy output from gcc) [18:05] *handwavy* [18:25] kirkland: ping, did you find the bug against gnome-settings-daemon? === dendro-afk is now known as dendrobates === hallyn is now known as hallyn_afk === beuno-lunch is now known as beuno === deryck[lunch] is now known as deryck === kiwinote_ is now known as kiwinote [20:00] SpamapS: I'm seeing armel toolchain weirdness too (that upstart FTBFS plus nih) [20:01] barry: ping === negronjl_ is now known as negronjl [20:02] RoAkSoAx: pong [20:02] barry: I have a qcuik question about UDD that's driving me crazy :)!! Should be submit branches with patches applied or not? [20:03] barry: cause when doing some merges I encounter the situation that there's diff's in .pc/what-ever-patch.patch [20:03] RoAkSoAx: you're not alone about that one ;) it's somewhat of an open question, but current thinking is that your branch will both have the debian/patches file(s) *and* the patches applied in tree [20:03] RoAkSoAx: thinking goes: [20:04] when you branch, you have the patches applied, so you'll just make your changes, do a bit of magic to generate the d/p file, commit and push [20:05] RoAkSoAx: yes, that's one large suck about the process. i think the best thing to do is to revert the .pc directory before you push [20:05] cjwatson: how do I check to see if a given LP user has package upload rights? where is that visible? [20:05] barry: right, so I';d revert the .pc directory and leave the patches unapplied? [20:06] kees: cant do it in lp itself [20:06] kees: pull down ubuntu-archive-tools from lp [20:06] RoAkSoAx: you can certainly do that. when i said "revert the .pc" directory, i mean 'bzr revert .pc' so that could lead to a patches applied push [20:06] maco: I thought not. But I don't know where to look. Ah-ha. [20:06] kees: and run edit_acl.py [20:06] kees: bzr+ssh://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/ [20:07] RoAkSoAx: just realize that this is a very uncomfortable place you're in, and something the bzr guys have a high motivation to fix [20:07] barry: but would it hurt to push with patches un-applied? [20:07] RoAkSoAx: no, i don't think it would because a reviewer is mostly going to be looking at the debian/ directory anyway [20:07] ./edit_acl.py query -p lpusername [20:07] kees: ^ [20:08] RoAkSoAx: and they should be able to 'quilt push -a' for example if they wanted to see the effects in tree [20:08] maco: oh, it can be done. you meant LP web, not LP API? [20:08] RoAkSoAx: so i think you're okay either way [20:08] kees: right [20:08] kees: sorry, this is the part of my brain that likes guis talking :) [20:08] barry: right, cool! Cause I've run into situations that I unpack the source and end up with patches applied with nothing under .pc, however, when quilt push -a, it fails to apply patches because they are already applied [20:09] so I have to do some magic to get that fixed [20:09] RoAkSoAx: yep. when you 'bzr branch ubuntu:foo' you always get patches applied [20:10] RoAkSoAx: just as an example, i've rewritten that section in the udd docs like three times already ;) [20:10] barry: cool I think I'll just start pushing without patches applied cause at the end generates issues when extracting the source with dpkg [20:10] barry: hjehe yeah grey area :) [20:10] barry: but anyways, Thanks for the input I now have a clearer view [20:11] RoAkSoAx: please do feel free to email the udd list and/or submit bugs for any problems or experience you have. i know the bzr guys would love to get more data points :) === hallyn_afk is now known as hallyn [20:11] barry: hehe will do ;) thanks! [20:11] np! [20:14] maco: who was supposed to put brad-figg in ~ubuntu-kernel-uploaders ? [20:14] kees: i dont know but i guess i could do it now [20:15] ok. did. [20:15] maco: thanks! [20:15] np [20:20] ogra_: you may be interested by bug 787749 [20:20] Launchpad bug 787749 in linux-ti-omap4 (Ubuntu) "Missing configuration for LXC containers on omap4" [Undecided,New] https://launchpad.net/bugs/787749 [21:02] slangasek, you broke gdk-pixbuf in oneiric! ;-) [21:03] seb128: I won't claim to be surprised ;), but I don't know what's broken - pointer? [21:03] slangasek, IRC reports but [21:03] https://launchpadlibrarian.net/71185137/gdk-pixbuf_2.23.3-0ubuntu1_2.23.3-0ubuntu2.diff.gz [21:03] + /usr/lib/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders \ [21:03] + /usr/lib/#MULTIARCH#/gdk-pixbuf-2.0/2.10.0/loaders/*.so \ [21:04] slangasek, the gdk-pixbuf-2.0/gdk-pixbuf-query-loaders dir is false it's in #MULTIARCH# as well [21:04] slangasek, that broke today with the librsvg update, the trigger empty the cache and no icon can be loaded [21:04] slangasek, you forgot to push your update to the vcs also btw [21:04] slangasek, do you want to fix it or should I add that to my list for tomorrow? [21:05] seb128: oh, indeed; I see that I had the right path in postinst configure, but wrong for postinst trigger, doh [21:05] (it's 10pm and I was about to go but I can fix that tomorrow when I start my day) [21:05] seb128: I'll try to get to it today but no promises [21:05] slangasek, ok, thanks [21:06] well seems easy enough, let see if I can get that done now before going [21:06] Vcs> sorry; further evidence that this some-UDD-some-not world is error prone :/ [21:06] slangasek, do you have the vcs revision and forgot to push or should I fix that? [21:06] slangasek, debcheckout is your friend ;-) [21:07] seb128: I have it all on the wrong Vcs (the UDD branch), you should probably go ahead and fix it [21:07] (we just sort of decided today in the desktop team meeting to stay away from UDD for another cycle) [21:07] slangasek, ok [21:07] eh, no, debcheckout isn't my friend, it doesn't have a sensible fallback to UDD === yofel_ is now known as yofel [21:32] i have a problem with logging into unity, every few times i login the desktop doesn't appear [21:32] anyone have any thoughts on which logs i should be checking to see what's hanging? === ximion1 is now known as ximion [21:34] brendand: .xsession-errors [21:34] psusi - in? [21:36] ~/.xsession-errors [21:37] a bunch of nm related warnings at the end [21:39] compiz (core) - Error: Plugin 'text' not loaded. [21:39] ? [21:39] not sure if that should do any harm [21:40] psusi knows more than I do about that stuff [21:40] this happens seemingly randomly [21:40] and so far has never happened when trying to login to classic desktop === ximion is now known as ximion1 [21:54] @pilot out === udevbot_ changed the topic of #ubuntu-devel to: Oneiric Archive: OPEN | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> natty | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: smb === ximion1 is now known as ximion [22:19] SpamapS: OOI, why is it dbus that needs to 'stop on deconfiguring-networking', rather than network-manager? [22:20] slangasek: because network-manager also needs to 'stop on stopping dbus' [22:21] slangasek: in order to express it differently, we have to jump through similar hoops to the portmap issues... [22:21] slangasek: I don't like it.. but until we have 'while' ... the hacks are going to pile up. :( [22:21] SpamapS: oh, because n-m shutdown would race dbus shutdown, heh [22:21] got it [22:22] As proud as I am of wait-for-state .. I'm hoping to avoid actually using it again. :) [22:23]