[02:14] robert_ancell: Yo yo! I know you've got a r600+ radeon card - have you noticed rendering problems in unity recently - the title bar being mostly-invisible, only the shadows of notify-osd showing? [02:15] RAOF, sure have [02:15] Any idea when they started? [02:16] a week or two ago? [02:17] Hah. And it's unity only, right? [02:18] I haven't tried anything else, but my guess would be yes [02:18] * RAOF has just tried classic + compiz, and that works. [02:18] Right. So, there's a problem. [02:18] the window title one is the particular one I've noticed, occurs when opening new windows, clicking the top of the screen seems to redraw it right [02:25] Yay! Multi-arch breaks unity builds, due to a dbus header file being in a different place. :) [02:29] TheMuso: I think that's fixed with the most recent dbus upload? [02:29] RAOF: Will check, but I updated this morning... [02:29] It was post-this-morning. [02:30] Ok hasn't come through yet. [02:30] * TheMuso updates his local mirror... [02:31] Anyway, have symlinked the file for now, so things work again. [02:33] Ok. Unity's doing something screwy with transparency it seems. [02:35] Urgh. What's annoyingly worse is that mesa master explodes into a thousand shards. [02:49] heh [02:50] is the Ubuntu font still UbuntuBeta? [03:04] I have fixed a bitesize bug, but I'm having troubles pushing it. I'm following the instructions from http://unity.ubuntu.com/getinvolved/#coding . Any tips? [03:05] The command I'm executing is "bzr push lp:ian-liu88/unity-place-applications/fix-for-bug-736471" [03:06] you seem to be missing a ~ [03:06] try with: bzr push lp:~ian-liu88/unity-place/applications/fix-for-bug-736471 [03:06] or rather: bzr push lp:~ian-liu88/unity-place-applications/fix-for-bug-736471 [03:14] stgraber: I will try, thanks! [03:14] stgraber: it worked ;-) === Amaranth_ is now known as Amaranth [03:24] The "Getting Involved" also mentions to "Propose a Merge". I've found the Merge proposal form, but I'm having some doubts on how to use it. Is the "Target branch" my new branch? [03:25] HAH! [03:26] robert_ancell: Would you be a dear and go to compizconfig settings manager→Blur Windows and disable “alpha blur”? I suspect that will resolve the graphical glitches. [03:27] robert_ancell: No rush, just when there's an appropriate context switch. [03:27] RAOF, hmm, blur windows appeared to be disabled [03:27] Oh. [03:28] I wonder why it is enabled here. Have I enabled it locally, I wonder? [03:34] Well, that's annoying. ‘unity --reset’ doesn't re-enable blur. [03:37] robert_ancell: are you planning to arrange a release exception for webkit 1.4.0? [03:38] micahg, is it released yet? [03:38] robert_ancell: no, but I'm told it [03:38] s coming with GNOME 3 [03:39] Yes, as soon as it's released will do the paperwork [03:39] * micahg wanted to make sure it's on the release team's radar since it'll be a very last minute update [03:41] which reminds me, I need to get a microrelease exception for webkit, but I'll do that later [03:41] robert_ancell: thanks [03:41] micahg, np, it will be nice when we have the release.. [03:42] robert_ancell: indeed, unfortunately, kov couldn't commit to no ABI/API breaks, but said there were none planned [03:43] at least webkit looks like it's taken care of, now I need to worry about getting xul-1.9.2 dropped :-/ [04:52] raof, is blur default now? [04:53] LLStarks: No, it isn't. [05:01] the blur appears quite spotty under the expo [06:57] wow, am i the first one awake in europe for a change? [06:57] good morning everyone [07:02] chrisccoulson: Seems so. [07:08] Good morning [07:10] bryceh: I think we should use the last "path: error: .*" line of DKMSBuildLog.txt for this? [07:11] * pitti sighs -- unity hasn't crashed for two weeks, and with the last update it all went horribly unstable again :/ [07:11] pitti: Yeah, trying to test some merged in branches with nux/unity today and have had a horror of a time. [07:15] * TheMuso realized that he didn't try unity trunk... [07:15] * TheMuso goes and builds. [07:18] good morning pitti [07:19] hey chrisccoulson [07:19] how are you? [07:19] pitti - i'm good thanks, although a little tired. how are you? [07:20] I'm fine, we had a nice weekend [07:22] chrisccoulson: woke up too early again? [07:23] pitti - yeah, my daugher woke several times during the night, and i thought that would mean she would sleep in ;) [07:23] but she woke up at the usual time [07:41] Well well well, with a branch of some a11y signal fixes for nux, we finally have a somewhat accessible launcher. :) [07:41] No quicklists yet, but I can navigate the launcher with orca and hear the application names, and launch them. :) [07:42] Sounds like an important milestone! Rockin! [07:43] Yeah, it certainly is. I am now going to take some time tomorrow to move my primary work environment to unity. [07:43] I'll just put all the most commonly used aps on the launcher, and launch everything else from a nautilus window/a terminal for now. [07:45] alt-f2 isn't a11ied? [07:46] No, and the dash isn't yet either, tahts more work. [07:46] Next cycle I'd say. [07:46] Eep. [07:46] TheMuso: nice to hear about the progress there! do you think this should change the current plan of defaulting to 2d if a11y is enabled? [07:46] ah, ok [07:46] so seems not [07:46] Incidentally, how's gnome-do on the a11y front, and how can I test it? [07:46] pitti: No, unless you are willing to put up with the missing bits, productivity would be severely crippled for anyone not willing to work around things. [07:47] RAOF: Don't know, never tried it. [07:47] TheMuso: right [07:47] So yeah, default to GNOME for some a11y profiles. [07:47] It's made of custom GTK stuff, so I'm not sure whether it's inherited the default GTK a11y. [07:47] RAOF: The easiest way to see if its likely to be accessible is to run accerciser, and look at the application accessibility hierarchy. [07:48] * RAOF adds that to his todo. [07:51] good morning [07:51] OMG it's didrocks! [07:52] RAOF: run run ;) [07:52] bonjour didrocks, ca va? had a nice long weekend? [07:53] pitti: Guten Morgen pitti. yeah, I'm fine, the week-end was nice (even if not enough snow to ski). You? [07:53] pitti: And, I think I might want to switch back to the standard gtk window decorator for accessibility profiles as well, because the unity window decorator window switcher is not accessible, even though it is derived from the gtk window decorator codebase... [07:55] Unless bug 724093 gets fixed soon. [07:55] Launchpad bug 724093 in compiz "unity-window-decorator: When switching between windows, Orca does not speak the title of the focused window." [High,Triaged] https://launchpad.net/bugs/724093 [07:55] grrr another unity window decorator crash... [07:55] * RAOF builds from nux trunk so opening the dash isn't a compiz death sentence. [07:56] COmpiz 0.9 still feels raw to me. === smspillaz|zzz is now known as smspillaz [07:59] it does for me too [07:59] it keeps locking up whilst i'm not at my machine [07:59] i was going to blame RAOF because i thought X was locking up, but it's actually compiz ;) [08:00] I'll let you in on a secret: it's entirely possible that's the fault of the X stack ;) [08:00] lol [08:01] RAOF, it does start working again if I kill -9 compiz and start metacity [08:01] Ah. [08:01] but often, restarting compiz will just make it crash until i reboot [08:01] Then I don't think that's the X stack's fault. [08:02] The typical “X causes compiz to lockup” would be a pageflipping snafu where compiz is sitting around in D state waiting for the swap to complete. === Zdra is now known as xclaesse [08:26] pitti, http://people.ubuntu.com/~fta/apport-kernel.png [08:27] fta2: heh, fun -- that looks like a bug in the kernel package hook; how did you get to this? [08:27] i. e. was it the first question? [08:28] (and is this natty?) [08:28] pitti, no, one of the last, if not the last [08:28] natty [08:28] what did you answer? [08:28] default [08:28] when i filed bug 736667 [08:29] Launchpad bug 736667 in linux "P5Q-PRO kernel OOPs: NETDEV WATCHDOG: eth0 (ATL1E): transmit queue 0 timed out" [Undecided,New] https://launchpad.net/bugs/736667 [08:30] hm, doesn't happen here :/ [08:30] I hade that happen to me [08:30] fta2: do you get the same empty question with "DISPLAY= ubuntu-bug linux"? (that will use the CLI frontend) [08:30] fwiw :) [08:31] pitti, I had a valid DISPLAY at that time [08:31] fta2: I know [08:31] fta2: I just wonder if that's some bug in the GTK UI or in the hook [08:31] fta2: it could also be weird characters which the dialog fails to render [08:33] in cli, it seems ok [08:43] fta2: can you pastebin the entire dialog? [08:49] pitti: here is what i got. http://paste.ubuntu.com/583232/ === lonewolf is now known as serious__sam [08:50] duanedesign: do you know which of the questions you got an empty dialog for? [08:54] pitti, as i said, iirc, it was the last one, before the apport UI with the summary [08:55] fta2: the "Testing the upstream kernel can help isolate issues.."? [08:55] i think i saw that one [08:55] but that was friday.. [08:58] is the retracer dead? [09:05] morning [09:06] hello rodrigo_ [09:13] hi duanedesign [09:23] hey rodrigo_, bonjour seb128 [09:23] hey pitti [09:23] how are you? [09:23] hi pitti, seb128 [09:23] seb128: I'm great, thanks! nice and sunny weekend [09:23] same here ;-) [09:30] hum, GNOME guys are thinking to switch their tarballs to tar.xz [09:30] is soyuz handling the format? [09:32] seb128: I don't know; worth checking in a PPA, I guess [09:48] pitti, is the retracer dead? (been waiting for 2h+ for a retrace) [09:48] fta2: possibly, let me check [09:49] fta2: yep, will fix in a bit [09:50] thanks [09:56] fta2: restarted (udev failed to upgrade in the chroots) [10:46] pitti: was able to reproduce the problem. Itwas after the window asking to test newer kernel versions. [10:49] pitti: strange. I can not reproduce it by running: ubuntu-bug linux [10:50] it has to be triggered by a kernel issue === ogra is now known as Guest34611 === Guest34611 is now known as ogra_ === MacSlow is now known as MacSlow|lunch === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic [11:24] pitti, swt-gtk 3.6.2 has webkit support [11:24] chrisccoulson: wohooo! [11:24] i'm just testing that this morning [11:24] perhaps that's worth a FFe if i can get it to work ;) === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic [11:37] pitti, if you have some time and want to review https://code.launchpad.net/~vorlon/glib/multiarch/+merge/54143 that would be appreciated [11:38] well extra eyes on that are welcome [11:38] seb128: I don't know much about it either, I guess we should just build and test it locally? [11:39] pitti, don't bother much that was in case you had some opinions or comment about it [11:40] seb128: I looked at it, but nothing that jumps out on me [11:40] ok, same here [11:40] quite ugly, though [11:40] I guess slangasek tested it and it doesn't break glib [11:40] (this cries for more abstraction/automation) [11:41] so let's go for it and see if things break [11:41] seb128: gio modules are mainly gvfs, I take it? I. e. URLs like gphoto:// or ssh:// ? [11:42] gvfs uri handling for gio yes and dconf [11:42] those are the obvious ones [11:42] seb128: want me to test it with gphoto? or are you already? [11:43] unity has some magic has well for application running and matching but I'm not sure how to test those, they improve reliability for some cases that's not technically required [11:43] pitti, if you want to do it feel free [11:43] I guess that requires changes to gvfs as well, then, as it ships /usr/lib/gio bits/ [11:43] ? [11:43] I'm about to go for lunch, I will build glib and test when I'm back [11:43] seb128: can do in a bit (still busy with something) [11:43] seb128: ok, sounds good; will build it in the background [11:44] pitti, right, it seems we will need patches for everything installing a .so in that dir [11:45] pitti, well slangasek added a fallback to read the old dir so technical that will not break [11:45] but still [11:45] seb128: ah, his latest changelog says "include /usr/lib/gio/modules as a fallback directory for compatibility" [11:45] right [11:45] do you know when that will land in Debian? seems that will add some extra delta otherwise [11:45] so, testing then [11:46] I don't [11:46] I think we are trailblazing here [11:46] ok, I will chat with steve when he's online [11:46] but the dpkg/apt/debhelper stuff is all in (or at least in git) [11:46] it hasn't been officially announced in Debian yet [11:47] ok [11:49] is anybody there on 10.10? [11:50] 10.10, what's that? [11:50] (SCNR) [11:51] yes [11:52] could you check if exec like in evolution-alarm-notify.desktop there? [11:52] it's in /etc/xdg/autostart [11:53] is the version 2.28 or 2.30 in the url? [11:54] ok, lunch time, I will read the scrollbar when I' back [11:54] be back in a bit [11:56] pitti, still no retrace... [11:57] fta2: they are running now; they have some catch-up to do since they were down over the weekend [11:57] ok === MacSlow|lunch is now known as MacSlow === ogra_ is now known as ogra [14:06] pitti, seb128, kenvandine, mterry: anyone care to sponsor https://code.launchpad.net/~dobey/ubuntu/natty/ubuntuone-control-panel/release-0-9-2/+merge/54081 please? :) [14:06] dobey, can do, I'm patch pilot today [14:06] seb128: ok great. thanks! [14:08] seb128, you are? sponsor https://bugs.launchpad.net/ubuntu/+source/libgda4/+bug/722079 too please! :) [14:08] Launchpad bug 722079 in libgda4 "When installing Anjuta in Natty Alpha libsqlite3.so is missing" [Low,Triaged] [14:08] mterry, that one should be in the desktop set? [14:08] hey mterry [14:08] seb128, srsly? main won't have anything left! [14:08] lol [14:08] it's a GNOME lib... [14:08] k, will ping cjwatson [14:08] thanks [14:09] dobey, btw ubuntuone-client-gnome ship libubuntuone.a and .la in the g-s-d directory, would be nice to clean [14:09] mterry, how are you btw? had a nice weekend? [14:10] seb128: oh right. i'll look into rming those as well [14:10] dobey, thanks [14:11] chrisccoulson, hey, around at all? [14:11] didrocks, there is a new zg in debian if you want to sync it [14:11] rickspencer3, yep [14:11] hey rickspencer3 [14:11] hi chrisccoulson, hi seb128 [14:11] hi :) [14:11] so, flash is really really crashy on my desktop [14:12] are other folks reporting bugs on this? [14:12] it also seems to be playing video better, though [14:12] rickspencer3, yeah. are you on amd64 or i386? [14:13] seb128: if you have time/want to go for it, do not hesitate, I'll go for it over the week otherwise :) [14:13] didrocks, well it's just a sync, I can do it ;-) [14:13] seb128: thanks :) [14:14] seb128, yeah, it was fine. I've been a little under the weather though [14:14] chrisccoulson, i386 [14:15] rickspencer3, it doesn't give you the option of submitting a crash report does it? [14:15] chrisccoulson, no [14:15] in any case, when i saw flash crashing, the backtrace was just full of flash :( [14:15] which means it needs to go to adobe really ;) [14:15] yeah, I figured it was all in upstream binary goo [14:16] there's not much we can do about crashes in the flash plugin, other than hope they fix it (or point to a problem in firefox) [14:16] seb128, didrocks: if you're talking zeitgeist 0.7.1 then I think that's a pretty safe bet. There are only slight tweaks in the Python client API (which we don't use) and then a very slight sql tweak to make it forward compatible with the upcoming 0.8 (which we'll prolly have for Oneiric, so forward compat is nice) [14:16] kamstrup, ok thanks [14:16] rickspencer3, i need to figure out why crash reporting is broken though. i guess it's the same bug that breaks it in chromium too [14:17] chrisccoulson, ok, I was checking to see if I was the only one [14:17] rickspencer3, no, we seem to get quite a lot of reports recently [14:17] ok [14:17] rickspencer3, it might be worth attaching gdb to the plugin-container process before it crashes though, just to make sure it is in the flash plugin [14:17] i'm on amd64 here, so i can't do that [14:17] seb128, You might consider backporting this to Maverick (thought it'd be in appmenu-gtk there) bug 717162 [14:18] Launchpad bug 717162 in libdbusmenu "quodlibet UI freeze in Unity after accessing its menu" [High,Confirmed] https://launchpad.net/bugs/717162 [14:18] i get the wonders and joys of nspluginwrapper instead [14:18] chrisccoulson, sounds like a good afternoon project for me [14:18] will do [14:18] thanks [14:20] tedg, yeah, I doubt the indicator-appmenu is used a lot in 10.10 but seems worth backporting still [14:20] seb128, I used it ;-) [14:20] seb128, It'd be in use by anyone using netbook edition. [14:21] right [14:21] * tedg reminisces about the olden days when Ubuntu had editions [14:23] when the web was the real web, and small furry creatures from alpha centauri were real small furry creatures from alpha centauri [14:25] ugh, that is annoying... every time i open a document in LO i get an ubuntuone notification that it is uploading a .lock file [14:25] and then when i quit i get it again [14:26] that might be annoying enough to make me turn off syncing of my Documents dir [14:26] not sure why syncdaemon needs to tell you it's uploading using a notification bubble to start with [14:26] it's annoying in quite some situations [14:26] yeah [14:27] it's not because you triage things and clean a bit that you want to get notified every time you store a change [14:27] or delete a file [14:27] or move one [14:27] i can see notifying for new shares, etc [14:27] seb128, Because people don't trust the syncdaemon as it's been flaky. So they associate not having trust with needing more information. [14:27] notify-osd is not informations, it's spam ;-) [14:28] hehe [14:28] i guess it would spam me on every auto-save too [14:28] On man's spam is another man's miracle meat. [14:28] just give an obvious way to open the control panel to see what's going on [14:28] yum, spam [14:34] kenvandine: hrmm. the lock files should just be ignored [14:34] dobey, well how should u1 decide what to hide? [14:36] kenvandine: there is a blacklist in the code, to ignore certain file patterns. like vim swp files [14:37] i would think .lock would be included :) [14:37] yeah i thought it was [14:38] .~lock.MoM 2011-03-01.odt# [14:38] whacky filename [14:38] actually, it would be neat if .lock files were handled by not syncing them, and locking changes to the associated file, on the server [14:38] indeed [14:39] so that other changes don't happen elsewhere while you're editing something [14:39] oh, well, .~lock is probably not ignored yet :) [14:39] wonder why it has the ~ [14:49] * ari-tczew checks interesting merges available for natty. [15:05] didrocks: hey [15:05] didrocks: I have some time now to tackle bug 723782 [15:05] Launchpad bug 723782 in gnome-session "Finalize gnome-session fallback detection" [Medium,New] https://launchpad.net/bugs/723782 [15:05] didrocks: I can backport and test that d-bus session name property now [15:05] pitti: oh, I should have warned you last week that with latest loicm's change, it's not needed anymore [15:06] didrocks: you actually told me it's not necessary any more, but the bug is still open, so that's what I wanted to discuss with you now :) [15:06] pitti: if we keep the checks in compiz and in the helper tool in sync [15:06] which is the case right now :) [15:06] hope that we can keep it like that [15:06] didrocks: so is it totally obsolete, or we can work around it, or would it still be useful then? [15:07] IOW, should we just close the bug, or would having it be an enhancement? [15:09] pitti: I *think* we should close it and avoid adding a big regression right now. Then, testing to ensure that we don't drop the user on some corner cases in a "no panel" session is needed [15:09] (which means, compositor, but no panel) [15:09] that can be ensure by keeping the testing tool opengl tests in unity_support_tool and the test from the start in the unity plugin initialization in sync [15:10] didrocks: i. e. with the dbus property we wouldn't need to duplicate the code and run the tests twice? [15:11] pitti: the tests will be run twice anyway, as it seems some people try to run unity even if it's not supported (with the "unity") command [15:11] pitti: so, a test rather than a crash is in order at unity startup :) [15:12] didrocks: as long as this test gets reasonably cheap.. [15:12] didrocks: anyway, so I'll close the bug then, to get it off the radar? [15:12] pitti, seb128, So are you guys planning on taking the upower and gpm patches here? It doesn't make sense to take the indicator-session one without those. [15:12] bug 578542 [15:12] Launchpad bug 578542 in gnome-power-manager "resuming from S3 wrongly prompts for password" [Low,In progress] https://launchpad.net/bugs/578542 [15:12] pitti: yes, please :) [15:13] pitti: the tests are cheaps, it's reading in an array [15:13] pitti: and the array is initialized once opengl is initialized [15:13] tedg: looking [15:13] pitti, seb128, Some helpful discussion on them: http://lists.freedesktop.org/archives/devkit-devel/2011-March/date.html [15:13] didrocks: what tests are you doing? [15:13] Amaranth: look at unity_support_tool [15:13] didrocks: initializing GL and checking for supported extensions isn't all that cheap [15:13] tedg: ah, "Adding an argument to Sleeping signal"? [15:13] didrocks: Oh, that doesn't segfault anymore? :) === warp11 is now known as warp10 [15:14] pitti, Yup [15:15] didrocks: I don't seem to have a unity_support_tool anymore, didn't nux ship that? [15:15] tedg: will have a look and discuss with hughsie; as this changes the d-bus API, I won't apply it in Debian/Ubuntu only [15:15] pitti, Okay, it seems like he approves on the mailing list. [15:15] pitti, But good to double check. [15:15] I think that it's solving it in the right way. [15:16] Though, it seems that gss should listen for the signal not gpm. But, that's a minor optimization :-) [15:16] Amaranth: /usr/lib/nux/unity_support_test [15:16] Amaranth: talk to jay, he told that checking the extensions wasn't more expensive once opengl is activated. I think he knows a little on opengl so that I can trust him [15:17] tedg, seems a pitti thing, I will let him handle it [15:18] didrocks: Oh, sure, checking extensions is free once opengl is initialized [15:19] hrm, I seem to be stuck in a situation that makes compiz crash without triggering an apport dialog [15:20] weird, and it just stopped doing that [15:25] rodrigo_, hey [15:25] hey seb128! :) [15:25] rodrigo_, so one frequent issue users get in nautilus is that they right click on a directory, do open with and pick an application and associate the folder mimetype with the software they used [15:26] rodrigo_, we used the patch from https://bugzilla.gnome.org/show_bug.cgi?id=637264 to make less easy to run into the issue [15:26] Gnome bug 637264 in File and Folder Operations "The 'Remember this application for ..." option changes the default for both files and folders" [Normal,Resolved: obsolete] [15:26] * rodrigo_ looks [15:27] rodrigo_, that's sort of a workaround though (just toggle the default value), the issue is fixed in GNOME3 as well, cosimoc said he would welcome a 2.32 patch that hides the checkbox for directories though [15:27] rodrigo_, do you think you could work on that? [15:27] ok [15:27] is there a LP bug for it? === bjf is now known as bjf[afk] [15:29] rodrigo_, bug #662194 [15:29] Launchpad bug 662194 in nautilus "Nautilus: 'Remember this application for ..." option should be made inactive by default" [Low,Fix released] https://launchpad.net/bugs/662194 [15:29] ok [15:30] rodrigo_, I've reopened and assigned it to you [15:30] rodrigo_, thanks [15:30] ok thanks [15:31] rodrigo_, thank you! ;-) [15:31] bugs with GNOME3 from the PPA should be filed on ... ? [15:31] jcastro, good question :) [15:31] aha, I knew I would stump someone [15:32] jcastro, they should not be filed ;-) [15:32] jcastro: bugzilla gnome of course :D [15:32] jcastro, there is no ppa bug tracker [15:32] so far, people have been sending mail to me directly [15:32] right [15:32] jcastro, code issues should be filed upstream , packaging ones mentioned here [15:32] and the mailing list looks like lp build announcements [15:32] maybe just using the mailing list? I mean, it's there already [15:33] seb128: also, is there a way out for people if they decide to not use it [15:33] jcastro, ppa-purge? [15:33] because from looking at the packages, if I use natty, and I want to try gnome3, and it upgrades a ton of stuff [15:34] jcastro, what mailing list? [15:34] mterry: ok, I can add that to the instructions [15:34] seb128: gnome3-team@lists.launchpad.net [15:34] jcastro, oh the gnome3 team one on launchpad? [15:34] yeah [15:34] jcastro, yeah they can use that [15:34] I'm not sure anyone is reading it [15:34] or subscribed [15:34] but seems the right location [15:34] we can check the list every now and then [15:34] jcastro, downgrade ... I wouldn't recommend it [15:35] I'm subsucribed [15:35] mterry: I want to avoid "I tried this PPA and now my gnome is totally hosed wether it's 2.x or 3.x!" [15:35] like GNOME3 will migrate your users datas to gsettings etc [15:35] seb128, but it won't delete old stuff [15:35] there is no easy roll back [15:35] right, so really, this isn't "try gnome3!" this is a bit of a commitment? [15:35] no, you will just go back to the settings you had before upgrading [15:35] ok [15:35] downgrade are not handled packaging wise either [15:35] it's likely that ppa-purge will fail on conflicts etc [15:36] like Replaces: are not made for going this way [15:36] you can downgrade but I would said it's not something a normal user will be able to deal with [15:59] I'm giving another global call if anyone wants to leave comments on my in-progress core-dev application. https://wiki.ubuntu.com/mterry/CoreDev [16:01] mterry, when is your meeting? [16:01] seb128, haven't formally put myself in yet. Was waiting for a few comments [16:01] mterry, ok, I will do that tomorrow then ;-) [16:02] sweet [16:16] mterry, btw if you get borred and are interest it could be nice to make appmenu-gtk work on gtk3 if we can [16:16] interested === bjf[afk] is now known as bjf [16:27] good night everyone! have to leave a bit early today [16:28] pitti: cheerio [16:29] seb128: i have a new respect [16:29] seb128: it turns out i have fat fingers for packaging [16:29] hey desrt, new respect for who? ;-) [16:29] seb128: for you :) [16:29] lol [16:30] * desrt tried to repackage gnome-screensaver and failed spectacularly [16:30] the ..90->..91 transition is brutal [16:30] lots of vendor patches no longer applying, packaging broke in various other ways [16:30] i wanted to kill bzr by the end of it :) [16:31] you should produce (and blog?) a 'packaging for ubuntu with bzr' cheetsheet... after some googling i wasn't able to find one [16:31] basically the tips you gave me on IRC the other day, but expanded a bit [16:32] for example, i wasn't ever able to rediscover that command you told me that looked at the apt database to determine the bzr repository that the packaging for a specific source package was kept in and check it out with an appropriate name [16:32] desrt, debcheckout? [16:32]