[01:16] mdeslaur: I see you got lvm2 merged... do you have any idea what the hell upstream-2.02.72.patch is? the debian devs don't seem to bother ever documenting their quilt patches and the bzr commit that introduced it is rather terse. It sounds like it is a diff to go from upstream .66 to .72, but then why is it a patch rather than a new .orig.tar.gz, and why is the rev of the package still .66 instead of .72? [01:17] psusi: let me take a look, hold on [01:17] psusi: yes, that's what it looks like to me too [01:17] I've been trying to get that package updated for some time now and it's been a real pain trying to figure out these undocumented patches [01:17] psusi: I don't know why they didn't just update to .72... [01:18] oh, actually [01:18] psusi: it may just be a diff between .71 and .72 [01:18] because that was a security fix [01:19] ahhh [01:19] psusi: yeah, that's it...it's just the security fixes that were added for .72 [01:19] I had updated to .76 and have been running that locally for a few months, testing out the snapshot merge support, but pitti wanted to avoid further divergence from debian [01:21] psusi: maybe you could convince debian to go to .76 (or at least package that in experimental), then we could merge it [01:54] for a package like zoneminder where it seems like it's mostly from debian unstable, should I report enhancement-ey bugs to ubuntu or to debian or both? [01:55] (kinda late, already did it https://bugs.launchpad.net/ubuntu/+source/zoneminder/+bug/691375 , but I'm trying to figure out the right way) [01:55] Ubuntu bug 691375 in zoneminder (Ubuntu) "Please compile with --enable--mmap=yes" [Undecided,New] [01:58] floam: From the bug title it sounds like it also affects Debian, so filing a Debian bug (and linking it to the Launchpad bug) is a good idea. === nenolod_ is now known as nenolod [02:17] RAOF: thanks, will do === asac_ is now known as asac === JanC_ is now known as JanC === almaisan-away is now known as al-maisan [06:24] i am a computer undergraduate and i want to contribute for ubuntu [06:26] i need some guidance regarding how to start working for ubuntu development [06:27] gs: So, what sort of thing are you interested in doing? [06:28] i am interested in working on projects using c/c++ [06:28] i am also familiar with python [06:29] So, almost all of the work involved in Ubuntu is done upstream; if you want to code, then picking a project and fixing something you find annoying that it doesn't do correctly is a good way to start. [06:30] so i should work for debugging ?? [06:30] There are also a bunch of Debian/Ubuntu projects, many of which use Python (software-centre, apport, etc) or C/C++ (unity, upstart, apt) [06:30] There's a huge amount to do; you can do whatever you want ☺ [06:30] gs: the idea is to "scratch your own itch" -- find something in existing software today that makes you unhappy and fix it. [06:30] actually sir i am interested in participating in gsoc so i wanted to be familiar with open source development procedure. [06:32] RAOF : ok. so the idea is to take a source code and modify it according to my requirements [06:32] Pretty much, yeah. [06:32] If it's a simple change you do it first and then send a patch to the associated project (generally this is handled on mailing lists). [06:33] If it's a more complex change it can often be worth sending a message to the mailing list outlining what you propose to do. [06:34] Precisely what happens depends greatly on how the specific project is run. [06:34] RAOF: ok. that sounds pretty interesting [06:34] ok. [06:34] Of course, there's *also* the option of wandering through bug reports on Launchpad and fixing them :) [06:34] ok i will try that also [06:35] But for gsoc you'll (probably) be working with an upstream project, so that's what I'd pick. [06:35] ok ya i wanted to do something for that [06:36] sorry but what do you mean by an upstream project? [06:38] Almost all of the programs that make up Ubuntu aren't developed by us; they're developed by other people, each as their own separate project, and we do the integration work. [06:39] So, projects like the linux kernel, X.org, GNOME, etc are “upstream” of us. [06:39] ok so whats ubuntu ? [06:40] We do the integration work; we take the code that upstreams release, optionally make some Ubuntu-specific changes, and build packages which conform to the various Debian policies. [06:41] ok so i should start working for upstream projects rather than ubuntu [06:41] gs: ubuntu is much easier to work with than debian [06:41] ok. [06:41] rigved: That depends; and it's pretty much moot if you want to do upstream coding anyway. [06:42] rigved : ok ya and i am ubuntu user so its a bit comfortable for me to work with ubuntu [06:43] RAOF: what i meant was that it's easier to use it. but yes ubuntu has made many things easier and safer to customise, like grub2 for example [06:44] * RAOF notes that our grub2 package is largely worked on *in* Debian :) [06:44] I'll agree that Ubuntu is easier to use, though :) [06:47] RAOF: ok. well it's not there in lenny. maybe in squeeze. thanx for the info :) [06:48] rigved: Oh, yeah. You don't get the shiny new toys in Debian stable! [06:50] cjwatson: ping === diwic is now known as diwic_afk [07:35] Package wmii depends on suckless-tools | dwm-tools. Package dwm-tools is NBS and replacement is suckless-tools. However, I still get http://people.canonical.com/~ubuntu-archive/NBS/dwm-tools . IMHO if a package has choice depends (|) and one of them if available, then the other should be considered free of reverse-depends [07:35] isn't it? [07:37] cdbs: it was dropped in the latest update [07:38] micahg: In the latest update of what? [07:38] cdbs: latest sync of suckless-tools from Debian [07:39] micahg: I know that. I am currectly talking about multiple possible depends, like: foo | bar | baz [07:40] cdbs: I'm saying, that's why you get the NBS and yes, it's rdepends free if it's an alternative [07:40] micahg: package wmii depends on suckless-tools | dwm-tools , the former is a replacement of the latter, but still, it appears, that the script on people.canonical.com/~ubuntu-archive/NBS is taking it the wrong way [07:40] micahg: yes, that's what I mean [07:41] cdbs: does that answer it sufficiently? [07:41] yes === hunger_ is now known as hunger [08:32] cjwatson, tseliot: Apparently my IRC client has actually been bitbucketting traffic all day for me, so I missed the blacklist discussion until now. Please feel free to ping me if there's anything I can do to make the blacklists easier to manage === ara_ is now known as ara [09:42] JamesPage, ping [09:42] jibel: pong [09:44] JamesPage, Hey, I've made some good progress on desktop iso smoke test using the server team work. [09:44] jibel: excellent; glad its been of use; [09:44] jibel: any issues or nuances you need a had with? [09:45] /had/hand/ [09:45] JamesPage, Not really, I've done a small set of changes to the main script to adapt it to the desktop [09:46] JamesPage, and duplicated the templates directory. [09:46] jibel: makes sense; it would be good if we could consolidate the code base into a single project [09:46] jibel: maybe that would be a good objective to achieve during the platform rally in Jan [09:47] JamesPage, I use a casper hook instead of a preseed to install ldtp and download a script from couchdb which I autostart when the Live session user log in [09:47] JamesPage, I also had to increase memory and disk size, but basically that's all that needed to be changed. [09:48] ebroder: do we really need the complicated chroots detection for sbuild.update() ? [09:48] jibel: sounds like we could easily consolidate then; I'd also like to abstract the tests from the rest of the code base; [09:48] bdrung: We don't if we assume mk-sbuild, but I'd prefer not to make that assumption [09:48] jibel: so we can distribute a package for the code; but the test still come from a bzr branch [09:49] jibel: means they can be updated every time the tests are run using Hudson [09:49] bdrung: sbuild-update and friends are really more schroot tools than sbuild. They take a chroot name. sbuild translates information about a target distribution and release into a chroot name using that logic (it's documented in sbuild(1)) [09:50] JamesPage, sure, it can be easily done. [09:50] ebroder: then i like to see the same translation logic in the sbuild-update and friends tools [09:51] bdrung: mk-sbuild always uses %(distribution)-%(arch), but I've inherited configurations in the past that use %(distribution)-%(arch)-sbuild [09:51] JamesPage, I still have few bits to fix and I'll push my changes next week, then I'll need your review and help to integrate to hudson. [09:51] bdrung: I'll make a note to open a bug with the sbuild maintainer. He's usually friendly [09:52] jibel: no problem [09:52] ebroder: thanks [09:52] ebroder: i'll fix sponsor-patch and merge your update-builder branch [09:53] bdrung: Fix sponsor-patch? [09:54] bdrung: Oh, that reminds me that I wanted to thank you for merging backportpackage, and also for pushing me on making the interface more flexible. I think that script has now completely replaced the functionality of 3+ simpler ones I've written in the past, not to mention innumerable hand-crafted shell loops [09:55] ebroder: the update logic in sponsor-patch doesn't work correctly - i'll fix that [09:55] bdrung: Ok, cool === bilalakhtar_ is now known as cdbs [09:56] ebroder: one feature request left for backportpackage: an environment variable for the upload destination (e.g. BACKPORTPACKAGE_UPLOAD) [09:56] bdrung: Oh, huh, that didn't make it to the todo list I was keeping. I'll add it back [09:56] * tumbleweed really must get around to the environment variable / connfille thing [09:57] I thought I'd do that yesterday... [09:58] tumbleweed: my idea, add the environment variable to devscripts config file - and then parse the files too [09:58] bdrung: yeah, I like that idea [09:58] it'll mean some central config parsing code for the whole of u-d-t, which will make it harder for people to just stick one of the scripts in ~/bin [09:59] bdrung, tumbleweed: It would be kind of awesome if I could say something like ubuntutools.config.get_config('BUILDER') and it would check all of the permutations of os.environ[sys.argv[0].upper() + '_' + 'BUILDER'] and 'UBUNTUTOOLS_' + 'BUILDER' and so forth [09:59] ebroder: yes, that's my plan [10:00] tumbleweed: yes, and then putting the found variable into the environment [10:00] tumbleweed: We're already moving in that direction. There's a *lot* of duplicated code right now, and I don't think it's a bad thing if that duplicated code consolidated into Python modules, even if it costs us the ability to drop things into ~/bin [10:00] bdrung: yes and no, because you want the command line options to take precedence [10:00] tumbleweed: look at our code - we use the env variable as default and override it with command line options [10:01] bdrung: yes [10:01] * bdrung have to go to university now. [10:01] it's time to develop a compiler. :) === dbarth__ is now known as dbarth [10:01] sounds like you found a more interesting thesis topic than I ended up with :P [10:02] heh [10:03] BTW, should I go ahead with adding a command-line arg --pbuilder-dist in sponsor-patch to force usage of pbuilder-dist DISTRIBUTIONHERE rather than DIST=DISTHERE pbuilder whatever ? [10:05] cdbs: no, I'd say pbuilder-dist should be supported as a Builder for u-d-t [10:05] tumbleweed: hmmm? [10:06] tumbleweed: so you mean all tools should support it? [10:06] cdbs: Check out the ubuntutools/builder.py module bdrung just merged in from me [10:06] cdbs: yes, there's a common builder abstraction in the ubuntutools package (in u-d-t) [10:06] I have a slightly older version [10:06] * cdbs bzr pulls [10:10] ebroder: so it doesn't have pbuilder-dist support yet [10:10] cdbs: Correct, but it should be pretty trivial to add [10:10] ebroder: yup, should I add? or you are adding? [10:11] cdbs: I am not [10:11] * cdbs gets working :D [10:38] Admiral! There be whales here! [10:38] deathspank calendar% ./nexttime2 "MDAY=-1" [10:38] Friday, 31 December 2010 00:00:00 GMT (+0000) [10:38] deathspank calendar% ./nexttime2 "MWDAY=-1THU" [10:38] Thursday, 30 December 2010 00:00:00 GMT (+0000) === al-maisan is now known as almaisan-away [10:39] (time_t of the last day in the month, and last Thursday of the month, respectively) [10:43] \o/ well done === pedro__ is now known as pedro_ [11:00] fargiolas: yes? === diwic_afk is now known as diwic [11:55] apw: just so you know, my ppa rebuild for bug 683605 is due to start apparently in 7 hrs (!!! and will probably fail! :( ) [11:55] Launchpad bug 683605 in util-linux (Ubuntu) "kernel hibernate signature has changed from S1SUSPEND to LINHIB0001" [High,Confirmed] https://launchpad.net/bugs/683605 [11:57] apw: annoying since there appear to be 4x idle i386 disto build machines. [11:57] jhunt, can't you build it locally to test ? [11:57] jhunt, but yes mine are in the morass too [12:06] jhunt: The distro build machines are nothing like the ppa build machines ... === doko_ is now known as doko [12:10] apw: I've built it on maverick, but will need to spend some time getting a local natty build env setup. lp guys thought the failures I was seeing might be natty related. I'll find out... [12:11] StevenK: we don't have xenmotion-type capabilities then? [12:12] jhunt: The distro buildds are real hardware. So, it doesn't work that way. [12:12] * StevenK -> bed [12:13] ah, I thought on the ppa boxes atleast VMs were being used. [12:14] yes, the PPA builds are in Xen [12:14] they're deliberately isolated so that a malicious PPA can't break the distro buildds [12:14] (or each other, for that matter) [12:16] jhunt: you may have trouble anyway since the earlier version you had failed to upgrade [12:16] cjwatson: yeah, I'm struggling with this. [12:16] jhunt: which means that if you try to build a later version of util-linux in the same archive, it'll try to upgrade itself first and fail [12:16] jhunt: I'd recommend deleting the broken version from the archive first (you'll still need to use a later version number) [12:17] this strategy doesn't work for the distro itself - if this sort of thing happens there, we need to recover manually. it's happened a few times [12:18] yeah, looks like that's what's happening. deleting it then reuploading should help. [12:18] cjwatson: thx! [12:18] (transitively) essential packages are such fun [12:19] actually not even transitively in this case, it's just plain Essential [12:34] Hello, please sponsor those merges: LP #691512 , LP #691448 [12:34] Launchpad bug 691512 in mutt (Ubuntu) "Candidate revision mutt 1.5.21-1ubuntu1" [Undecided,Confirmed] https://launchpad.net/bugs/691512 [12:34] Launchpad bug 691448 in irssi (Ubuntu) "Candidate revision irssi 0.8.15-2ubuntu1" [Undecided,Confirmed] https://launchpad.net/bugs/691448 === sam---___---- is now known as sam-_- [12:43] Not knowing bazaar enough is one of my weaknesses, so excuse me for a (probably) newbie question. [12:44] If I do "apt-src install pulseaudio", it says: [12:44] NOTICE: 'pulseaudio' packaging is maintained in the 'Bzr' version control system at: [12:44] http://bazaar.launchpad.net/~ubuntu-audio-dev/pulseaudio/ubuntu.natty [12:44] Please use: [12:44] bzr get http://bazaar.launchpad.net/~ubuntu-audio-dev/pulseaudio/ubuntu.natty [12:44] to retrieve the latest (possibly unreleased) updates to the package. [12:45] But if I do that, I only get a "debian" subdirectory and not the upstream source. [12:46] Given that workflow, how do I get original source? [13:15] diwic, does the packaging actually know how to get the source for you, sometimes you can debian/rules patch (or something similar) [13:16] apw, hmm, I think I solved the problem as it seems like bzr-buildpackage seems to go get the source for me; although I don't know from where it got that pointer [13:17] apw, but while you're listening, I'm not trying to push my branch with "bzr push bzr+ssh://bazaar..." but it asks for my canonical ssh key instead of a password [13:17] diwic, have you logged in ? [13:18] diwic, via bzr launchpad-login ? [13:19] apw, "bzr launchpad-login diwic" just returns after a moment, I'm assuming it does what it should [13:19] hmm [13:19] maybe I need to add the ssh key to the launchpad account? [13:19] diwic, you need to have your ssh key in your account i think, the public part [13:19] diwic, but i thought you needed that in there for our internal infrastructure too [13:23] apw, seems to have done it, thanks [13:26] seb128: hi! with the patch you backed out of compiz, my login hangs... [13:26] seb128: I think we can confirm this bug now ;) [13:26] jdstrand, :-( [13:26] jdstrand, can't win [13:27] seb128: fwiw, I did see the menu bug too, but oddly only after a few hours [13:27] njpatel, ^ [13:27] it's going to be no fun, either way we are screwed [13:28] seb128: it there a bug for the stalled login? [13:28] (I don't have a usable desktop atm) [13:28] jdstrand, https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/690239 [13:28] Ubuntu bug 690239 in glib2.0 (Ubuntu) "hang in g_spawn_sync and select()" [Undecided,New] [13:28] seb128, urgh :/ === almaisan-away is now known as al-maisan [13:29] jdstrand, starting the classic session doesn't work? [13:29] seb128: thanks. and finally-- is there something I can poke from a vt to get things going again? [13:29] jdstrand, are you sure compiz hangs? [13:29] like the process is running but hanging? [13:30] does ctrl-alt-right or left works? [13:30] I don't know what is hanging-- I login and I get a spinning cursor [13:30] jdstrand, waht do you see? the background ? [13:30] apw: I see the background [13:30] * apw always recommends a windows-E to see if you get expose [13:30] ctrl+alt+right and left does nothing [13:30] (likely not then) [13:30] windows+E does nothing [13:31] njpatel, is sam working today? [13:31] i think rtg was seeing that failure mode too ... [13:31] jdstrand, here the classic session works [13:31] all I have in ps related to compiz is compiz-decorator [13:31] I had issue with the default one [13:31] jdstrand, seems similar to what I was having yesterday [13:32] seb128: well, right, I am kinda committed to the unity one since I blew away my gnome-panel gconf settings to run a small panel in unity [13:32] I do have a backup of those though... [13:32] jdstrand, well I can start the classic one, alt-f2, ccsm and activate unity [13:32] then I've a working unity session [13:32] the unity session in gdm is buggy in a way similar to what you get though [13:33] I thought didrocks expressly told me to *not* use ccsm to activate unity :) [13:33] I though that was maybe a local issue [13:33] jdstrand, well didrocks is away until eoy [13:33] I'm telling you what I did there [13:33] if you want a workaround to get back a working desktop... [13:33] hmm [13:33] seb128: I am not being testy, just thought it funny I got different info [13:34] :) [13:34] jdstrand, oh I didn't take it wrongly don't worry ;-) [13:34] I'm a bit annoyed by that compiz bug though [13:34] yes, me too ;) [13:34] it's being between a rock and an hard place [13:34] we have no compiz guy around today [13:34] then I'm on holiday as well until eoy [13:35] sucks if that stay this way for the next 2 weeks [13:35] well, I can downgrade compiz and live with the menus then [13:35] well it's not only you [13:35] but yeah, better menu issues than no desktop [13:35] jdstrand, can you try to downgrade to -0ubuntu1 [13:35] that is way less painful than logging into classic, fiddling with my panel, starting unity, fiddling with my panel, etc [13:35] see if you get the issue as well? [13:36] jdstrand, why would you have to fiddle with those? [13:36] the panel config should be the same [13:36] ccsm and activate unity in your classic compiz config [13:36] you can alt-f2 to run it [13:36] I guess that's true [13:36] that's what I did there [13:37] the only difference between the sessions is the compiz plugin in use [13:37] jdstrand, is that the no menus appearing on right click and stuff dissappearing issue ? [13:37] no [13:38] that's the side effect of rolling back the patch which created the menu issue [13:38] apw: I have nothing but a background. compiz didn't start [13:38] though compiz-decorator did [13:38] jdstrand, it's likely that compiz crashes [13:38] it does there [13:38] I suppose that's true about the gnome-panel-- I was thinking I need a working classic desktop. I do not [13:39] s/working/fully functional/ [13:43] ok, going the classic route worked fine [13:46] jdstrand, ok, thanks, same issue than me then [13:46] seb128: I'm guessing since there are no compiz specialists around that there isn't a lot I can provide to help atm? [13:47] I also wonder if the next time I login to classic, if unity will try to start and then crash again... [13:48] seb128: do you still want me to try ubuntu1? [13:48] jdstrand, can you clean /var/crash, log in an unity session and see if it crashes? [13:48] yes [13:49] * jdstrand goes to try [13:50] huh, indicator-sound isn't showing rhythmbox anymore [13:52] seb128: ok. I accidently logged into classic desktop and was pleased to see compiz did *not* crash even though I had the unity plugin checked [13:52] seb128: put to the point of your question [13:53] jdstrand, ok, I've the same issue there then [13:53] mdeslaur, try starting it once? [13:53] seb128: I logged in, I saw the unity launcher for half a second, it went away and compiz did crash, leaving a crash file in /var/crash [13:53] seb128: nope, still not showing up [13:54] mdeslaur: weird, but it did before? I know yesterday or possibly the day before it was still there [13:55] jdstrand: it worked fine until this morning updates and reboot [13:55] s/put/but/ [13:56] seb128: that may not have all been clear. I accidentally logged into the classic desktop and it worked fine with unity (good). I then logged out, and back in with the unity desktop, saw the unity launcher for a moment, then compiz crashed with a crash file in /var/crash [13:56] jdstrand, can you upload the .crash to launchpad? [13:56] jdstrand, no, same than here, what I told you before [13:56] seb128: k [13:56] jdstrand, the unity session crashes but unity in a normal session works [13:56] I'm not sure why [13:56] seb128: apport-collect to a bug number or a new bug? [13:56] mdeslaur, try asking ronoc on #ayatana [13:56] seb128: tanks [13:56] s/tanks/thanks [13:57] jdstrand, new one, I couldn't submit mine because I've some other upgraded not done [13:57] jdstrand, so if your box is uptodate... [13:57] will do [13:57] it is [14:09] cjwatson (and pitti), thanks for the debconf libgnome cleaning ;-) [14:11] no problem, that's 660KB or so cleared [14:11] it's still not entirely free of deprecated interfaces, so may need further attention in future [14:13] ebroder: merged [14:25] seb128: incidentally, do you read all of natty-changes or something? :) [14:26] cjwatson, I do go through the titles at least [14:26] ;-) [14:26] I stopped on debconf because I was waiting on that part of the stack to be able to go away [14:28] seb128: mvo's cleaning up the two remaining Recommends on it [14:29] seb128: uploaded [14:30] cjwatson, mvo: thanks ;-) [14:31] yw === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [14:31] cjwatson: looking at http://launchpadlibrarian.net/60797448/buildlog_ubuntu-natty-i386.apturl_0.4.2ubuntu2_FAILEDTOBUILD.txt.gz [14:33] huh, didn't change anything in that area [14:34] ah, ok, python default change [14:34] doko: I can fix it if you like [14:34] already doing [14:34] ok [14:58] seb128: bug #691561 [14:58] Launchpad bug 691561 in compiz (Ubuntu) "compiz crash on login" [Undecided,New] https://launchpad.net/bugs/691561 [14:58] seb128: I had to do my own apport-retrace since the crash report wasn't formatted correctly (lacked 'Package: compiz') [14:58] jdstrand, thanks [14:58] njpatel, ^ [14:58] seb128: but it should be ok [14:59] looking [14:59] #1 0x00007f94bc80391d in UnityScreen::getWindowPaintList (this=) at /build/buildd/unity-3.2.6/src/unity.cpp:246 [14:59] pl = @0x12b8d50 [14:59] xwns = @0x7fff5f672120 [14:59] njpatel, ^ is unity bog [15:00] well, it's a bad pointer [15:00] from nux! [15:00] hm, how can it happen that we have a cups in maverick-updates that depends on "cups-ppdc" when the later is in universe? [15:00] :) [15:00] mvo, ! [15:00] mvo, how are you : [15:00] ? [15:00] even [15:00] * njpatel can't type [15:00] hey njpatel - good, thanks! [15:00] and you? [15:01] good thanks, looking forward to the break :) [15:01] me too :) [15:02] jej [15:02] we have perfect winter weather, I will undust the sledge ! [15:02] heh* [15:02] lol [15:02] you really can't type today ;) [15:02] mvo, no, which doesn't bode well for the unity release ;) [15:03] lol ! [15:05] mvo: reminder about bug 671016, alpha-2-milestoned bug left over from last week's release meeting [15:05] Launchpad bug 671016 in update-manager (Ubuntu Natty) "EOL needs to be handled more elegantly" [High,In progress] https://launchpad.net/bugs/671016 [15:06] cjwatson: cups in maverick-updates depends on cups-ppdc but that is in universe for maverick. is it possible to promote it in maverick-updates? if not I think I should uplodate a new version with cups-ppdc as a recommends instead a depends [15:06] cjwatson: EOL reminder> thanks [15:07] jhunt: you're good at coming up with random calendar schedules, can you think of a few tests? === dendrobates is now known as dendro-afk [15:08] mdeslaur: I can confirm rb is not in the sound indicator menu [15:08] mdeslaur: do you have a bug? [15:08] Keybuk: how complex can we go here? Have we got knowledge of boot/resume times? [15:08] geser, Laney, jpds: requestsync owns 13 of 45 ubuntu-dev-tools bugs. you touched the script. can you have a look at the bugs? https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools?field.searchtext=requestsync [15:09] jhunt: I think I've covered every reasonable complexity [15:09] durations are easy - this is more of the "last sunday of the year" variety [15:10] jdstrand: bug 691556 [15:10] Launchpad bug 691556 in rhythmbox (Ubuntu) "[natty] rhythmbox doesn't appear in indicator-sound menu anymore" [Undecided,New] https://launchpad.net/bugs/691556 [15:11] mvo: normally we wouldn't, but since it's changed in -updates anyway, and since it's in main in natty, I think it's safe enough to promote [15:12] mvo: promoted, unless somebody screams at me really loudly [15:12] deathspank calendar% ./nexttime2 -c 3 "WDAY=SUN;HOUR=4;MIN=30;INTERVAL=2" [15:12] Sunday, 19 December 2010 04:30:00 GMT (+0000) [15:12] Sunday, 2 January 2011 04:30:00 GMT (+0000) [15:12] Sunday, 16 January 2011 04:30:00 GMT (+0000) [15:12] -- [15:13] jhunt: e.g. every second sunday at 4:30am [15:13] Keybuk: how about... last weekday of this year / 2nd tuesday after easter / first friday 2 months + 3 days from now. [15:14] can't do that first one [15:14] mdeslaur: thanks [15:14] thanks cjwatson [15:15] jhunt: I can do last day of the year, or last friday of the year, etc. [15:15] Keybuk: oh - another nasty one: "Monday closest to 29th January" (aka "Auckland Anniversary Day") [15:17] nope, you can have last monday of jan or 1st monday of feb though ;-) [15:18] Keybuk: can you discriminate between "every hour on the hour" vs. "every hour since boot/resume time"? [15:18] all of the rules I support are of the form "nth n in n" [15:18] jhunt: yes [15:18] Keybuk: *awesome* [15:19] bdrung: will try to triage them during the weekend. I've to think what I should do about the crashes somewhere down the chain towards LP API (mostly likely caused by timeouts) [15:20] can do things like "the day you get for xmas" [15:21] deathspank calendar% ./nexttime2 -b "25/12/2010" "WDAY=MON" [15:21] Monday, 27 December 2010 00:00:00 GMT (+0000) [15:22] Keybuk: fwiw I think "remind" would handle the "last weekday of this year" scenario as "(first Friday of *next* year) - 7 days" [15:23] that doesn't necessarily give you the last weekday ;-) [15:26] Keybuk: no, it also has to use scanning to slide back/forwards around a date looking for a goal. [15:27] yeah [15:27] we don't want upstart to be remind or calendar(1) === tkamppeter_ is now known as tkamppeter [15:30] it's worth pointing out that as far as I could tell, remind works on the principle of "what time is it => do I have anything that I can run now?" [15:30] ie. same as cron [15:42] after last updating natty, my pbuilder is broken [15:42] E: File /root/pbuilder/natty-base.tgz does not exist [15:42] pbuilder is installed [15:44] and why it looks for natty-base.tgz in root instead in ~/pbuilder? [15:44] yesterday pbuilder worked fine === dendro-afk is now known as dendrobates [15:47] could someone binNEW libzeigeist and dee? [15:48] they need promotion as well [15:48] the new unity will need those [15:55] doko: thanks, hopefully, it should be the last abicheck.sh :p [15:56] mr_pouit: please forward these upstream [15:56] and debian [15:56] yep, done already for upstream [16:06] hum [16:07] jdstrand, cjwatson, Riddell: ^ someone to do the 2 binNEW reviews? [16:08] * cjwatson needs to focus on release meeting just now ... [16:08] seb128: I am working on them today [16:08] cjwatson: ^ [16:09] Riddell: ^ [16:09] seb128: which 2 do you need right now? [16:09] * jdstrand was going oldest to newest [16:09] thanks [16:10] jdstrand, libzeitgeist and dee [16:10] k === mako_ is now known as mako [16:16] doko: hm, maverick-updates has a newer glibc than natty, that makes the auto-upgrader unhappy [16:17] mvo: I asked to copy it to natty [16:17] cjwatson: ^^^ [16:17] aha, thanks [16:21] doko: done [16:23] thanks cjwatson [16:24] seb128: done. I threw in vte for giggles [16:25] jdstrand, thanks === Sarvatt_ is now known as Sarvatt [16:26] sure [16:27]