[00:01] <rodrigo_> now I'm going to sleep, so good night all
[00:02] <robert_ancell> rodrigo_, later
[01:16] <lamalex> Horizontal scrolling isn't working on my thinkpad, it worked in 10.04. I enabled it in mouse prefs. Should I file as an X bug?
[01:20] <RAOF> Probably.
[01:29] <lamalex> I think it might be https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/661445
[01:29] <ubot2> Launchpad bug 661445 in xserver-xorg-input-synaptics (Ubuntu) "Horizontal scroll doesn't work in maverick in SynPS/2 Synaptics Touchpad (affects: 2) (heat: 14)" [Low,Confirmed]
[01:30] <lamalex> but I'm not sure how to tell what kind of touchpad I have
[01:30] <lamalex> dont see anything in lsusb or lspci
[01:31] <Sir_Konrad> lamalex, I'm pretty sure you have a Synaptics PS/2... A lot of Thinkpads do.
[01:38] <Sarvatt> lamalex: does synclient HorizEdgeScroll=1 enable it?
[01:40] <lamalex> lol now I can't find anything that needs to scroll horizontally :P
[01:41] <lamalex> Sir_Konrad, nope
[01:42] <Sir_Konrad> lamalex, you don't have a Synaptic one?
[01:45] <ajmitch> lamalex: I think /var/log/Xorg.0.log will show which touchpad type it is
[01:45] <ajmitch> not sure if there's a better way to see or now
[01:45] <ajmitch> s/now/not/
[09:06] <dpm> good morning pitti, I've added an action for you on http://is.gd/gEArp to update the text description on the langpacks PPA once we've got the schedule on the wiki and on the calendar - I just want to check you're ok with it
[09:07] <seb128> dpm, hey
[09:07] <dpm> heya seb128
[09:07] <seb128> dpm, he's in Boston for plumbers this week so probably sleeping
[09:07] <seb128> just for information
[09:07] <seb128> dpm, how are you? had a nice trip back?
[09:07] <dpm> aah, thanks seb128, yeah, now I remember he mentioned it. Thanks for the heads up
[09:08] <dpm> seb128, fine, thanks :) - but got caught by the infamous ubuflu, no doubt helped by the air conditioning in Orlando and in the plane
[09:09] <seb128> :-(
[09:09] <dpm> seb128, and you? Had a nice trip back and a nice Bank Holiday on Monday?
[09:10] <seb128> yes, and I managed to go back on local time after a night
[09:10] <seb128> without the ubuflu
[09:10] <dpm> nice :)
[09:10] <seb128> I can't complain this time ;-)
[09:10] <dpm> :)
[09:22] <huats> morning
[09:49] <seb128> lut huats
[09:49] <seb128> didrocks, is the new evo still on your to review list?
[09:49] <seb128> huats, ca va ?
[09:49] <didrocks> seb128: yes it is, there were still some issues with cyphermox latest proposal and he is fixing them
[09:50] <seb128> ok
[09:50] <seb128> I was reviewing versions and wondering if that one was still being worked
[09:50] <didrocks> yes, it's still, no worry on it, I'm following :)
[09:51] <seb128> ok
[09:55] <huats> seb128, I am fine thanks !
[09:55] <huats> appart from the fact that my office has been robbed last week...
[09:55] <huats> you ?
[09:56] <huats> (I have read that you avoided the ubuflu :) )
[09:58] <seb128> I'm fine thanks
[09:58] <seb128> yeah didrocks told me about your office
[09:58] <seb128> sorry about that
[09:59] <huats> seb128, thanks
[10:00] <huats> it is a bit annoying because it takes me a lot of time
[10:00] <huats> and quite some money...
[10:03] <huats> today the most annoying thing is that I haven't a spare PC to build... (and since I am doing a lot of squashfs it slow a lot my every day computer...)
[10:03] <huats> and since I have my credit card stollen...I can't order another one yet :(
[10:05]  * didrocks hugs huats
[10:05] <didrocks> :/
[10:06] <didrocks> did you get a lot of money, apart from ubuntu-fr's one?
[10:06] <huats> didrocks, nope
[10:06] <huats> nothing...
[10:07] <huats> just the ubuntu-fr one,  (that for the record I'll pay back myself...)
[10:07] <huats> didrocks, they took my passport, a credit card, my netbook and my build computer + the monitor :(
[10:08] <didrocks> huats: well, as said on the ML, don't worry, focus first on having your paper, cards and a computer to work
[10:08] <huats> didrocks, I will :)
[10:15] <bilalakhtar> mvo: Hello there! Free?
[10:46] <seb128> bilalakhtar, did you send that gtk patch upstream as well?
[10:46] <seb128> bilalakhtar, could you add the bug number on launchpad?
[11:05] <bilalakhtar> seb128: okay, doing that now
[11:05] <bilalakhtar> sorry for the delay, I was having lunch
[11:05] <bilalakhtar> forgot to put myself on /away
[11:06] <seb128> no worry
[11:11] <bilalakhtar> seb128: done
[11:38] <bilalakhtar> rodrigo_: Congrats on becoming a member of ~ubuntu-desktop
[11:38] <bilalakhtar> !
[11:38] <rodrigo_> thanks bilalakhtar
[11:38]  * bilalakhtar would apply soon, when seb128 would find him fit for the job
[11:39] <seb128> well ubuntu-desktop gives mainly access to things on the default desktop, you didn't worked on those much yet
[11:39] <bilalakhtar> papercuts?
[11:40] <seb128> keep contributing and do some updates this cycle
[11:40] <bilalakhtar> yup
[11:40] <bilalakhtar> will update when GTK3 gets into Ubutnu
[11:40] <bilalakhtar> *ubuntu
[11:40] <seb128> well you don't really need commit access to papercuts
[11:40] <seb128> but yeah, keep contributing and we will see ;-)
[11:40] <seb128> rodrigo got it mainly because he needs upload rights to the gtk3 ppa
[11:40] <bilalakhtar> ah
[11:41] <bilalakhtar> what do you mean by : You don't need commit access for papercuts?
[11:41] <bilalakhtar> ah, okay, I got what you meant
[11:44] <seb128> well you don't have upload rights for those components anyway
[11:44] <seb128> so having commit access wouldn't give you much
[11:44] <seb128> you would still need a sponsor
[11:47] <Laney> ubuntu desktop would give upload though no?
[11:47] <seb128> not the launchpad team
[11:47] <Laney> thought it did
[11:48] <Laney> Archive Upload Rights for ubuntu-desktop: archive 'primary', package set 'ubuntu-desktop' in natty
[11:48] <seb128> if it does I didn't know about it
[11:48] <seb128> hum, ok
[11:48] <Laney> I thought that was the main point of the team
[11:48] <seb128> we need to be careful who we add then
[11:48] <bilalakhtar> I think Laney is right
[11:49] <seb128> well the point is to have access to the vcs
[11:49] <bilalakhtar> I also thought that ~u-d gives access to the package set
[11:49] <seb128> I though somebody add to ack the upload rights as well for upload
[11:49] <Laney> in parallel to being able to upload, yeah
[11:49] <seb128> time to eat
[11:49] <seb128> bbl
[11:49] <bilalakhtar> bye, seb128
[11:50] <didrocks> reboot bbiab
[12:44] <rodrigo_> seb128, ok, libcanberra built now (had to patch it to build with GTK3)
[12:44] <seb128> rodrigo_, did you push your work somewhere?
[12:45] <rodrigo_> seb128, pushing now
[12:48] <rodrigo_> seb128, lp:~rodrigo-moya/ubuntu/maverick/libcanberra/ubuntugtk3
[12:48] <rodrigo_> seb128, should I push to the PPA, or wait for your review?
[12:50] <seb128> rodrigo_, wait
[12:50] <seb128> I will review it now
[12:50] <rodrigo_> ok
[12:57] <mvo> bilalakhtar: hey, sorry for the reply - now I have time :)
[12:57] <mvo> bilalakhtar: for the late reply
[12:57] <seb128> hey mvo
[12:57] <seb128> how are you?
[12:57] <bilalakhtar> mvo: no problem, How are you?
[12:58] <mvo> bilalakhtar: good, thanks!
[12:58] <mvo> bilalakhtar: a bit tired (jetlag)
[12:58] <mvo> seb128: hi!
[12:58] <bilalakhtar> mvo: then, rest a bit
[12:59] <bilalakhtar> mvo: I was asking about what would be the right time before u-m would say 'System may be up to date. Press the check button to check for available software updates' after an apt-get update. I am talking about bug #35009
[12:59] <ubot2> Launchpad bug 35009 in update-manager (Ubuntu) (and 2 other projects) "Says "System is up to date" when package lists not updated (affects: 7) (dups: 6) (heat: 102)" [Low,Triaged] https://launchpad.net/bugs/35009
[12:59] <bilalakhtar> A week should be enough
[12:59] <bilalakhtar> (IMHO)
[13:00] <pitti> dpm: of course, thanks
[13:00] <pitti> Good morning
[13:01] <seb128> hey pitti
[13:01] <dpm> hey pitti, thank you :)
[13:01]  * pitti -> sessions, &
[13:01] <mvo> bilalakhtar: let me have a look
[13:01] <didrocks> good morning pitti
[13:02] <mvo> bilalakhtar: from first glance the diff looks fine, I will merge now
[13:03] <bilalakhtar> mvo: you went as far as merging the branch!
[13:03] <bilalakhtar> What I asked was different
[13:03] <bilalakhtar> Since you just came from UDS I thought to not get you to sponsor right away
[13:03] <bilalakhtar> I was just asking whether 1 week would be the right time
[13:04] <bilalakhtar> though IMHO the branch is good, but its your wish
[13:07] <mvo> bilalakhtar: I think one week is fine
[13:07] <mvo> bilalakhtar: do you think its too long?
[13:07] <bilalakhtar> mvo: could be, but for stable Ubuntu releases it should be fine
[13:08] <bilalakhtar> And, I know many new users who don't like the idea of updating their systems more often than once a week
[13:10] <mvo> bilalakhtar: *nod*
[13:10] <bilalakhtar> mvo: so, I have to go now, sorry. BTW, you may be tired, so rest. I am in no hurry to get my changes in the archive
[13:10] <bilalakhtar> or in the trunk
[13:11] <bilalakhtar> so, merge whenever you have time
[13:11] <bilalakhtar> bye!
[13:11] <mvo> thanks bilalakhtar!
[13:12] <bilalakhtar> You're welcome
[13:15]  * rodrigo_ -> lunch
[13:24] <cyphermox> hmm... unity feels weird with two screens... I need to switch to the window on the second screen then head back to the first for the menus and then back to the second ...
[13:25] <didrocks> bug already filed FYI :)
[13:26] <cyphermox> ah, sweet
[13:26] <cyphermox> do you know the #?
[13:27] <cyphermox> I feel like extending or adding a top panel would probably be sufficient to get the right "feeling", unless it's just letting apps have their own menus if they aren't displayed on the first screen :P
[13:28] <didrocks> hum chromium is completely crazy when searching in the bar or use shortcut… will switch back to firefox soon…
[13:29] <didrocks> cyphermox: there are already a lot of discussion on it, but you can look for it (I already spent too much time on finding duplicates a day :))
[13:29] <didrocks> cyphermox: this kind of discussion should be on the ayatana ML I think
[13:29] <cyphermox> didrocks, ok.
[14:00] <nessita> hello humans! may I have a sponsorship for https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.6/+merge/39964 ?
[14:07] <seb128> nessita, hey robot
[14:07] <seb128> nessita, ok, can do that for you ;-)
[14:08] <nessita> seb128: awesome! and I was playing the monster role (too much disney world in me still)
[14:08] <seb128> nessita, ;-)
[14:10] <seb128> mterry, hey
[14:11] <jcastro> charlie-tca: if you have time we could use a hand confirming that this fix works: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/627744
[14:11] <ubot2> Launchpad bug 627744 in tomboy (Ubuntu Natty) (and 5 other projects) "Tomboy note names are blank in the Application Indicator fallback menu (affects: 14) (dups: 2) (heat: 151)" [High,Fix committed]
[14:12] <mterry> seb128, hello!
[14:12] <kenvandine> thx jcastro, charlie-tca
[14:12] <seb128> mterry, how are you?
[14:12] <seb128> mterry, not going to plumbers?
[14:12] <seb128> key kenvandine
[14:12] <kenvandine> hey seb128
[14:12] <mterry> seb128, good.  no, I've gone before, but it's too much kernel, not enough userspace for me
[14:12] <seb128> kenvandine, the x264 fix is still on my list so don't worry about it by maverick sru are frozen for linaro
[14:13] <seb128> mterry, ok
[14:13] <kenvandine> ah, ok
[14:13] <kenvandine> thx seb128
[14:13] <seb128> mterry, could you peer review lp:~rodrigo-moya/ubuntu/maverick/libcanberra/ubuntugtk3
[14:13] <seb128> mterry, I will review gtk in a bit ;-)
[14:13] <seb128> got busy with other things until now
[14:14] <mterry> seb128, sure
[14:14] <seb128> mterry, thanks
[14:28] <seb128> didrocks, you got bugs
[14:29] <seb128> I've just sent 2 evo bugs your way
[14:29] <seb128> calendar not respecting week days and timelines
[14:29] <seb128> it seems to be due to your une backports
[14:29] <seb128> I've rebuilt with 89* and 91* and it works fine
[14:29] <didrocks> seb128: please, can I have a puppy face as a notification when you say "you got bugs"? :)
[14:30] <seb128> didrocks, lol
[14:30] <didrocks> seb128: ok, let's have a look :)
[14:30] <didrocks> seb128 | I've rebuilt with 89* and 91* and it works fine
[14:30] <didrocks> -> you mean, "without"
[14:31] <seb128> yes
[14:31] <seb128> I just wanted to drop the express patch first
[14:31] <seb128> but it made other ones fail
[14:32] <didrocks> hum, I see that will be a joy to do, maybe not for today but will give it a look later
[14:34] <seb128> didrocks, no hurry, it's just that we got quite some duplicates and it's Ubuntu specific
[14:34] <seb128> so we should try to fix it
[14:35] <didrocks> seb128: btw, when you point to upstream bug report, do you look at bug reports "fixed" or at commits?
[14:35] <seb128> didrocks, you mean?
[14:35] <seb128> when I point who?
[14:36] <didrocks> seb128: like in https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/649543/comments/12
[14:36] <ubot2> Launchpad bug 649543 in evolution (Ubuntu Maverick) (and 2 other projects) ""work week" preferences do nothing - no effect (affects: 29) (dups: 7) (heat: 158)" [Low,Triaged]
[14:36] <didrocks> seb128: you look for bug report closed in bugzilla?
[14:37] <seb128> usually yes
[14:37] <seb128> but in this case I did type calendar on the git log
[14:37] <didrocks> ok :)
[14:37] <seb128> on git.gnome.org
[14:38] <seb128> that's because the guy who tested said it works in other distros
[14:38] <seb128> so I figured it has been fixed in git during the 2.32 cycle
[14:38] <nessita> mvo: ping
[14:47] <nessita> mvo: when you come back: hello! so, I've read your comment on bug #624065, and I have no so good news. We (desktop+) have no time allocated in the roadmap for that feature :-/ I will try to squeeze a fix before natty release, but if you want/can provide a patch we'll love you and you'll get your func in place :-)
[14:47] <ubot2> Launchpad bug 624065 in ubuntu-sso-client (Ubuntu) (and 1 other project) "Detect revoked SSO tokens (affects: 2) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/624065
[14:48] <didrocks> seb128: that patch is already in the tarball and not reverted by evo express, I will have a deeper look then
[14:48] <seb128> didrocks, ok, I found that patch before having finishing my build
[14:49] <seb128> it was a first guess before I figured the backport patch was the issue
[14:49] <didrocks> not a joy as a lot of items have been renamed in the express branch, so a signal should be missing
[14:49] <seb128> didrocks, did that code land in 2.32?
[14:50] <didrocks> seb128: yeah, but it has changed a lot since
[14:50] <seb128> didrocks, you might be able to find something in the diff between those
[14:50] <seb128> hum, ok
[14:50] <seb128> didrocks, or try watching the git you used for the backport, they might have fixed it there?
[14:51] <didrocks> seb128: already done :) and no activity since june
[14:51] <seb128> :-(
[14:52] <didrocks> I'll try first to remove the express tweak in calendar
[14:52] <seb128> didrocks, enjoy the debugging then ;-)
[14:53] <didrocks> seb128: well… yes :-)
[14:57] <mvo> nessita: thanks, I will see what I can do, should not be too much work actually
[14:57] <nessita> mvo: yeah, specially if you use the current code as example
[14:57] <nessita> I mean, as guideline :-)
[15:00] <jcastro> didrocks: do we ship upnp support in rhythmbox in 10.10 and earlier?
[15:01] <jcastro> I am wondering if feature parity means "banshee needs to support upnp" or "banshee needs to support upnp with what's on the CD and don't add anything else"
[15:01] <didrocks> jcastro: not by default in 10.10, it's a separate package
[15:01] <jcastro> ok so something in universe is fine?
[15:01] <didrocks> jcastro: it was before lucid IIRC
[15:01] <didrocks> yeah
[15:02] <seb128> jcastro, yes
[15:02] <seb128> the upnp code is shipped with rb but we install it in a different binary
[15:02] <seb128> which is not installed by default because it depends on coherence
[15:09] <seb128> mterry, did you push your gtk3 with gir somewhere?
[15:09] <mterry> seb128, yeah, lp:~mterry/+junk/ubuntugtk3
[15:09] <seb128> thanks
[15:12] <seb128> mterry, --enable-introspection=yes seems wrong in configure_flags
[15:12] <seb128> shouldn't it be to =no
[15:12] <seb128> then =yes for the shared flavor
[15:12] <seb128> you have it to =yes in shared_configure_flags
[15:12] <mterry> seb128, I wasn't sure about that.  I knew we wanted it for shared.  But wasn't sure about normal
[15:13] <seb128> seems it will be exercising some non standard build configuration
[15:13] <seb128> like gir in the static build
[15:13] <seb128> I think we should do it only for the shared flavor
[15:13] <seb128> would it only to reduce build time
[15:14] <mterry> k, easy to change
[15:14] <seb128> yeah
[15:16] <seb128> mterry, ok, seems ready for me otherwise, I'm doing a testbuild there to check as well
[15:19] <seb128> why the heck is bzr bd failing to download tarballs
[15:20] <seb128> or rather seems to be downloading for a while and then says tarball not found
[15:20] <mterry> seb128, uscan can't find the gtk3 tarballs
[15:20] <mterry> not sure why
[15:20] <seb128> is that the watch issue you fixed in some other sources?
[15:20] <seb128> ([\d\.])+[02468]
[15:20] <seb128> to  ([\d\.]+[02468])
[15:21] <mterry> seb128, maybe..?   yeah...  i think that all wants to be in the parens
[15:21] <mterry> seb128, oh also, that line only checks for stable releases
[15:21] <seb128> that's a valid point ;-)
[15:21] <seb128> wget -nv -T10 -t3 -O ../tarballs/gtk+3.0_2.91.3.orig.tar.gz http://ftp.gnome.org/pub/GNOME/sources/gtk+/2.91/gtk+-2.91.3.tar.gz
[15:21] <seb128> I've that in my log
[15:22] <seb128> so it seems it does figure the right location
[15:22] <didrocks> ../tarballs exists?
[15:22] <seb128> no
[15:22] <seb128> # create tarball dir
[15:22] <seb128> mkdir -p ../tarballs
[15:22] <seb128> wget -nv -T10 -t3 -O ../tarballs/gtk+3.0_2.91.3.orig.tar.gz http://ftp.gnome.org/pub/GNOME/sources/gtk+/2.91/gtk+-2.91.3.tar.gz
[15:22] <seb128> in fact
[15:22] <seb128> in the log
[15:23] <seb128> still seems to be a fail
[15:24] <seb128> it's using /usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk
[15:24] <seb128> not the watch
[15:26] <mterry> ah
[15:27] <mterry> rodrigo_, I'm looking at your canberra gtk3 branch
[15:27] <rodrigo_> mterry, ok
[15:27] <mterry> rodrigo_, you bumped compat to 7, but need to bump debhelper to >= 7 too then
[15:27] <rodrigo_> mterry, ah, ok, let me change it
[15:27] <seb128> why do you bump the compat?
[15:28] <mterry> rodrigo_, you switched from cdbs to quilt?  Surprised me that you would prefer that.  I think desktop packages are mostly on quilt
[15:28] <mterry> seb128, good point, I didn't see any changes that needed it
[15:28] <rodrigo_> ok, coming back to 5, not sure why I did
[15:28]  * mterry shudders at cdbs patches
[15:29] <mterry> rodrigo_, you dropped the gtk2 module's dbg package.  was that intentional?
[15:29] <rodrigo_> mterry, hmm, well, I prefer the cdbs patches, but I'm ok with switching to quilt if tha'ts better
[15:29] <rodrigo_> mterry, hmm, did I?
[15:29] <seb128> rodrigo_, we sort of standardized on quilt after a while
[15:29] <seb128> with edit-patch nowadays it's ok
[15:30] <rodrigo_> wasn't intentional, no, so re-adding it now
[15:30] <seb128> edit-patch understands quilt
[15:30]  * seb128 hugs mvo
[15:30] <mterry> :)
[15:30] <mterry> rodrigo_, you overrode DEB_DH_MAKESHLIBS_ARGS_ALL in debian/rules.  Did you mean +=?
[15:30] <chrisccoulson> oh, i've not used edit-patch yet
[15:30] <chrisccoulson> i just use quilt directly ;)
[15:30]  * mterry hugs quilt
[15:30]  * chrisccoulson hugs quilt too
[15:30] <chrisccoulson> :)
[15:30] <rodrigo_> mterry, yes
[15:30] <seb128> chrisccoulson, edit-patch is useful when you need things like running autoreconf or so
[15:31] <seb128> it avoids having to quilt add things
[15:31] <mterry> rodrigo_, and this is minor, but gtk3-dev has a different required version of gtk3 than the build-depends.  Probably not intentional?
[15:31] <mterry> seb128, oh, didn't know that, cool.  But as we discussed, I also hate autoreconf patches.  Go dh-autoreconf!
[15:31] <seb128> yeah ;-)
[15:32] <seb128> I still hate quilt for having to export QUILT_PATCHES
[15:32] <seb128> or to have to quilt add things you modify
[15:32] <seb128> I often forget the quilt add and edit the file
[15:32] <seb128> then I need to trash my work and start again
[15:32] <nessita> seb128: any news with the upload? if you haven't sponsored yet, I'd like to remove the proposal and make a new one
[15:32] <seb128> nessita, you can do a new one, I got sidetracked in the gtk review
[15:33] <seb128> nessita, you are next
[15:33] <mterry> seb128, I just hold down undo for a while, quilt add, then hold down redo.  :)
[15:33] <nessita> seb128: great! I'll remove the current one, so ignore until further notice
[15:33] <mterry> rodrigo_, so besides the gtk3-dev version, one last thing about debian/rules
[15:33] <seb128> mterry, ;-)
[15:34] <mterry> rodrigo_, did you really want to update dh_makeshlibs -V args to 0.26 from 0.24?
[15:34] <mterry> I get the /usr/lib/canberra-0.26 one, but the -V args, I'm not as sure about
[15:34] <seb128> rodrigo_, as a rules we usually try to not do changes over debian for packages come from there when not required
[15:34] <mterry> I believe that sets the required version of libcanberra for any reverse depends
[15:34] <didrocks> argh, I have to create a pbuilder for maverick. How come I don't have one?
[15:34] <seb128> like changing the patch system or bumping the compat version
[15:34] <seb128> come -> coming
[15:35] <seb128> mterry, rodrigo_: right the shlibs defines the current api version
[15:35] <seb128> ie the version anything building against the lib will depends on
[15:35] <seb128> urg
[15:35] <seb128> we scared him away? ;-)
[15:35] <mterry> seb128, right.  I'm not sure off the top of my head if 0.26 broke API
[15:36] <mterry> heh
[15:38] <mterry> seb128, rodrigo_, hrm, the API docs don't indicate anything even changed in 0.24, so probably don't need the bump to 0.26
[15:38] <seb128> I'm doing a 0.26 build to check
[15:38] <mterry> seb128, how do you check doing a build?
[15:38] <rodrigo_> mterry, that's the version there was in the ubuntu-desktop branch
[15:38] <rodrigo_> seb128, mterry: although I think 0.24 is not ready to build with GTK3
[15:38] <seb128> mterry, I still have 0.25 installed
[15:38] <mterry> rodrigo_, no, I mean as an argument to dh_makeshlibs -V
[15:39] <rodrigo_> mterry, ah
[15:39] <mterry> rodrigo_, in debian/rules, the -V argument specifies the last time the package broke API and reverse-depends need to depend on that version or greater
[15:39] <mterry> rodrigo_, you bumped that from 0.24 to 0.26, but probably didn't need to
[15:39] <seb128> mterry, I've small script which nm -D the installed version and the build one
[15:39] <seb128> and diff the lists
[15:39] <mterry> seb128 is checking
[15:40] <seb128> mterry, check-symbols in ubuntu-dev-tools does something similar
[15:40] <mterry> seb128, fancy.  isn't that what .symbols is for?
[15:40] <seb128> using the deb for each version rather than a build dir
[15:41] <seb128> mterry, right, I had mine years before .symbols though :p
[15:41] <mterry> rodrigo_, oh, speaking of, you need a debian/libcanberra-gtk3-0.symbols file
[15:41] <seb128> it still comes handy for things not using .symbols
[15:41] <rodrigo_> mterry, ok
[15:41] <seb128> which I just nothing libcanberra do
[15:41] <seb128> nothing -> noticed
[15:41] <seb128> why do we still have DEB_DH_MAKESHLIBS_ARGS_libcanberra0 calls?
[15:42] <seb128> the .symbols should be enough
[15:42] <mterry> seb128, oh really, dh_makeshlibs does that from symbols?  clever
[15:42] <rodrigo_> so, I can remove those lines then?
[15:42] <mterry> brb
[15:42] <seb128> rodrigo_, you can remove the -V
[15:43] <rodrigo_> ok
[15:43] <seb128> you might want to keep the -- -c<n>
[15:43] <seb128> that tells the build to stop if symbols are missing
[15:43] <rodrigo_> and leave the -- -c4?
[15:43] <rodrigo_> ok
[15:43] <seb128> yes
[15:46] <mterry> rodrigo_, that's all I had.  :)  if those are fixed, seems good, pending seb128's OK
[15:46] <rodrigo_> mterry, ok, building now, will push in a minute
[15:47] <seb128> mterry, <mterry> seb128, oh really, dh_makeshlibs does that from symbols?  clever
[15:47] <seb128> mterry, what is "that"?
[15:51] <mterry> seb128, I guess "that" is what dh_makeshlibs is supposed to do -- determine minimum requirements of packages.  :)  I just never thought about where it got the info from
[15:52] <seb128> mterry, ah ;-)
[15:52] <seb128> yeah it lists all the symbols used
[15:52] <seb128> read the version for those in the .symbols
[15:52] <seb128> and use that
[15:54] <rodrigo_> mterry, pushed
[15:54] <ricotz> hi, what is the reason for "debian/patches/01-build-with-gtk3.patch" in libcanberra, isnt it better to use the official 0.26 tarball?
[15:54] <rodrigo_> ricotz, are we not using the official one?
[15:54] <rodrigo_> ricotz, I got that fix from git
[15:54] <ricotz> 0.26 includes this patch
[15:55] <rodrigo_> not the one we have, it seems
[15:55] <ricotz> http://0pointer.de/lennart/projects/libcanberra/libcanberra-0.26.tar.gz
[15:55] <seb128> rodrigo_, your source seems to be 0.25
[15:55] <seb128> according to the configure
[15:55] <rodrigo_> hmm
[15:56] <rodrigo_> it is indeed, got confused by the previous entry in debian/changelog
[15:56] <seb128> where did you get the checkout from?
[15:56] <rodrigo_> ubuntu-desktop branch
[15:56] <seb128> I guess that's debian dir only though?
[15:57] <rodrigo_> hmm
[15:57] <seb128> we way we usually work there is debian dir only and tarball is automagically downloaded and used
[15:58] <rodrigo_> yes, but the branch I have is indeed ~ubuntu-desktop/libcanberra/ubuntu
[15:58] <rodrigo_> that's the correct one, right?
[15:58] <seb128> oh you are right it's full source
[15:58] <seb128> I bet robert_ancell got confused by the format
[15:58] <seb128> we usually use debian only format
[15:59] <rodrigo_> ok, so I bzr merge-upstream from the official tarball, or are you fixing the branch?
[15:59] <seb128> rodrigo_, so yeah, you are right, robert screwed it
[15:59] <seb128> rodrigo_, you need to merge-upstream
[15:59] <rodrigo_> ok
[15:59] <seb128> having 2 workflows is confusing
[15:59] <seb128> that's sort of what with discussed last week
[16:00] <seb128> mterry, rodrigo_: do you know if there is some documentation on the full source way to update?
[16:00] <seb128> http://wiki.ubuntu.com/DesktopTeam/Bzr
[16:00] <seb128> equivalent to that but with merge-upstream
[16:00] <mterry> seb128, https://wiki.ubuntu.com/DistributedDevelopment/Documentation/
[16:00] <mterry> rodrigo_, ^
[16:00] <rodrigo_> ok
[16:01] <seb128> mterry, thanks
[16:01] <seb128> hum
[16:01] <seb128> I wondering if we should switch to that
[16:01] <seb128> at least for things which don't take days to download ;-)
[16:02] <mterry> seb128, we can just ship gnome release sources to team members on a dvd  :)
[16:03] <seb128> lol
[16:03] <bilalakhtar> seb128: bzr merge-upstream works with debian folder only branches?
[16:03] <seb128> no
[16:04] <seb128> debian only uses tarballs
[16:09] <rodrigo_> hmm -> Unable to find the tag for the previous upstream release, 0.25...
[16:09] <rodrigo_> if I tag the branch, it still fails
[16:10]  * kenvandine upgrades to natty...
[16:10] <seb128> one other reason I don't like full source in bzr :p
[16:10] <seb128> you always have issues like that
[16:10] <seb128> where debian only is very low demanding
[16:10] <seb128> rodrigo_, james_w or didrocks or others might know
[16:11] <rodrigo_> yeah, I prefer debian only too
[16:11] <didrocks> when upstream uses bzr, merge-upstream is the best :)
[16:11] <kenvandine> it is definately much faster to push and pull
[16:11] <didrocks> rodrigo_: what do you try with mu?
[16:12] <rodrigo_> didrocks, merge-upstream libcanberra 0.26 on the ~ubuntu-desktop/libcanberra/ubuntu branch
[16:13] <rodrigo_> didrocks, it says 'unable to find the upstream-0.25 tag'
[16:13] <seb128> I guess the vcs in not on merge-upstream format
[16:13] <didrocks> rodrigo_: yeah, if nobody used it before, you should tag it manually
[16:14] <rodrigo_> ok, so bzr tag upstream-0.25 ?
[16:14] <didrocks> rodrigo_: yeah, look what commit you should add to it
[16:14] <didrocks> weird, you have in latest commit "New upstream release" with no upstream file changed…
[16:15] <seb128> didrocks, because robert_ancell used it as a debian only vcs
[16:15] <didrocks> seb128: not sure how it handles with file in the bzr tree :)
[16:15] <seb128> he doesn't
[16:15] <seb128> I doubt he is running into those often
[16:15] <rodrigo_> adding the tag fails also, in a different way though
[16:15] <seb128> I've to admit I don't really know how to deal with those either when upstream is not in bzr
[16:16] <rodrigo_> wouldn't it be easier to move that ubuntu.-desktop branch to debiabn-only again?
[16:16] <seb128> check with TheMuso
[16:16] <seb128> he's the one whoc was working on it until now
[16:16] <rodrigo_> TheMuso, ^
[16:16] <seb128> so he might have an opinion
[16:17] <seb128> rodrigo_, what error do you get after tagging?
[16:18] <rodrigo_> it says 0.26-ubuntu1 is less than 0.26-0ubuntu1~maverick~ppa1, but I'm doing this on a clean branch, without my changes, so not sure where it gets that from
[16:18] <rodrigo_> ah
[16:19] <seb128> yeah you might need to merge-upstream on the current version
[16:19] <seb128> then to apply your changes
[16:21] <rodrigo_> it removes the debian dir, when doing merge-upstream
[16:21] <didrocks> that's what it's doing on first merge-upstream
[16:21] <didrocks> you have to revert the first time
[16:21] <rodrigo_> http://pastebin.ubuntu.com/525150/
[16:25] <didrocks> rodrigo_: bzr revert debian/
[16:25] <tedg> bryceh, Have you played any with the GTG branch that adds an LP backend?
[16:25] <didrocks> rodrigo_: dch -v<blabla<
[16:25] <rodrigo_> didrocks, ok
[16:25] <didrocks> rodrigo_: only the first merge-upstream known and filed bug :)
[16:33] <rodrigo_> ok, I think I got it, it's building correctly now -> https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/maverick/libcanberra/ubuntugtk3
[16:33] <rodrigo_> mterry, seb128: do I do a merge proposal so that the diff is easier to look at?
[16:34] <mterry> rodrigo_, yeah, that is easier
[16:34] <rodrigo_> ok
[16:34] <seb128> the merge proposal diff are different from standard diffs?
[16:35] <rodrigo_> https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/maverick/libcanberra/ubuntugtk3/+merge/39990
[16:35] <rodrigo_> seb128, oh, no, it's just it's easier to look at, rather than seeing the revisions on my branch
[16:38] <rodrigo_> of course, my merge proposal includes all the upstream changes :(
[16:39] <rodrigo_> yeah, my diff is completely borked, seems the upstream tarball includes a debian dir
[16:39] <ricotz> rodrigo_, oh, is the drop of the sound-theme patch intended?
[16:40] <rodrigo_> no
[16:40] <ricotz> ok, so then it is missing
[16:41] <rodrigo_> ricotz, the diff is borked, it shows every file as being removed and added
[16:41] <seb128> rodrigo_, easier to review those by bzr diffing the debian dir between revisions
[16:41] <rodrigo_> yes
[16:41] <rodrigo_> I'll pastebin that, and remove the merge proposal
[16:41] <seb128> don't bother
[16:42] <seb128> we can do it locally
[16:42] <rodrigo_> ah, ok
[16:52] <didrocks> ahah, take that evolution! :)
[16:52] <seb128> didrocks, you got it?
[16:53] <didrocks> seb128: yeah, both bugs was the same cause :)
[16:53] <seb128> lacking an update?
[16:54] <didrocks> seb128: not really, the editor really changed the gconf key, but as the restruction of evolution is half finished in 2.30 and the express branch was relying on it, there were no parent listening to the change.
[16:54] <seb128> oh ok
[16:54] <didrocks> I had to minimize the change to add the part for listening the gconf key again as well adapting it with previous structure :)
[16:59] <bryceh> tedg, a while ago, not recently
[17:03] <tedg> bryceh, Was it reasonable stable, or should I avoid looking? :)
[17:05] <bryceh> tedg, avoid
[17:36] <rodrigo_> seb128, mterry, did you review my branch?
[17:37] <mterry> rodrigo_, oh no, I didn't.  didn't know you had gone back and actually requested a merge
[17:38] <rodrigo_> mterry, my branch is a bit borked, so I guess for a merge I'd need a cleaner one, but just need review to upload the package to the gnome3 ppa
[17:38] <rodrigo_> mterry, but no hurry, just wanted to know if there was something else wrong
[17:38] <mterry> Oh I see, you fixed the whole 0.25/0.26 thing
[17:38] <rodrigo_> yes
[17:40] <mterry> OK, looking now
[17:40] <pitti> seb128: do you think you can review/approve https://blueprints.edge.launchpad.net/ubuntu/+spec/performance-desktop-n-install-footprint this week?
[17:40] <seb128> pitti, yes
[17:40] <seb128> pitti, how is plumber?
[17:41] <seb128> pitti, I will review the spec in a bit or tomorrow morning
[17:42] <pitti> seb128: in one word: "enlightening" :) in fact there's quite some bits to discuss on our side, I'll follow up next week
[17:42] <pitti> seb128: cheers
[17:42] <pitti> seb128: sohuldn't take much work, you were in the session and there shouldn't be much surprise
[17:42] <seb128> right
[17:42] <seb128> pitti, lot of stack changes coming from plumbers?
[17:43] <pitti> seb128: one word: systemd :)
[17:44] <seb128> lol
[17:46] <mterry> rodrigo_, what happened in the 're-add debian directory' commit?  It makes bzr diff really hard to understand (every file is removed & added instead of being changed)
[17:46] <mterry> as well as losing bzr history for those files
[17:46] <rodrigo_> mterry, yeah, merge-upstream removed the dir so re-added it
[17:47] <mterry> rodrigo_, it deleted the debian/ directory? odd
[17:47] <rodrigo_> yes
[17:48] <mterry> rodrigo_, you can get it back by doing 'bzr revert debian' instead of re-adding them, though I'm not sure why it deleted it
[17:48] <rodrigo_> I think it's because the upstream tarball has a debian/ dir, let me check
[17:48] <rodrigo_> no, it doesn't
[17:49] <rodrigo_> so yeah, not sure why it did, I guess it got confused by the branch not having had a merge-upstream before
[17:49] <rodrigo_> I think we should fix the ubuntu-desktop branch to not have the source in it, shouldn't we?
[17:50] <mterry> rodrigo_, well...  there are two schools of thought on that, and I'm not sure where canberra falls (normal distro stuff is full-source, most desktop-team stuff has historically been debian-only)
[17:50] <rodrigo_> yeah
[17:50] <rodrigo_> I'll try fixing my branch for a better merge proposal
[17:51] <mterry> rodrigo_, thanks, the bzr history is important
[17:51] <rodrigo_> yeah
[17:52] <TheMuso> rodrigo_: Also be aware that there are unreleased changes in debian libcanberra git.
[17:52] <TheMuso> That we will likely need for GTK3.
[17:53] <seb128> why?
[17:53] <seb128> what sort of changes?
[17:53] <seb128> rodrigo_ got a gtk3 build without those
[17:54] <TheMuso> Gtk3 support was added, thast pretty much it.
[17:55] <rodrigo_> yeah, it builds the gtk3 module correctly
[17:55] <rodrigo_> mterry, forget my previous branch, removing it and submitting a new one
[18:00] <rodrigo_> mterry, https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/maverick/libcanberra/ubuntugtk3/+merge/39997 <- now it's ok
[18:01] <mterry> :)
[18:01]  * mterry looks
[18:03] <mterry> rodrigo_, I bet you thought this would be easier!  :)
[18:03] <rodrigo_> yeah, the previous branch's diff was completely messed up
[18:04] <seb128> 420	+ * debian/patches/01-build-with-gtk3.patch:
[18:04] <seb128> 421	+ - Add patch to make it build with GTK3
[18:04] <seb128> rodrigo_, ^ to clean?
[18:05] <rodrigo_> yeah
[18:05]  * rodrigo_ cleans
[18:05] <rodrigo_> pushed
[18:07] <mterry> rodrigo_, what's the src/sound-theme-spec.c about?  That was upstream?
[18:07] <rodrigo_> mterry, yes
[18:07] <rodrigo_> mterry, I just merge-upstream and then did changes in debian/
[18:07] <mterry> rodrigo_, weird.  I wonder how that affects us.  Also,  -gtk3-dev still depends on a different version of gtk3 than the Build-Depends
[18:08] <seb128> rodrigo_, you should document the rules changes in the changelog as well
[18:08] <rodrigo_> mterry, it's just a .spec file, not built it seems
[18:08] <rodrigo_> ah, sorry, it's a C file
[18:08] <mterry> rodrigo_, so what's the deal with the header files like libcanberra.h?  There's just one copy and whether you're building with gtk2 or gtk3, you use the same header?
[18:09] <rodrigo_> ok, fixing the -gtk3-dev
[18:09] <rodrigo_> mterry, seems so, you select which one to link to
[18:10] <mterry> rodrigo_, then gtk3-dev should probably depend on gtk-dev to pull in libcanberra-gtk.h
[18:10] <seb128> that seems suboptimal
[18:10] <mterry> rodrigo_, also, this isn't your fault, but /usr/bin/canberra-gtk-play should really not be in a library package
[18:11] <mterry> not worth fixing now though
[18:11] <seb128> sjoerd said he was interested to get the canberra update in debian
[18:11] <seb128> I will point him to the ppa version one uploaded
[18:11] <seb128> so we can sort with debian what to do for those
[18:11] <seb128> just to make sure we don't divert
[18:13] <rodrigo_> seb128, mterry, ok, pushed last 2 fixes
[18:13] <didrocks> ok, sport and dinner, see you tomorrow!
[18:13] <rodrigo_> bye didrocks
[18:13] <seb128> didrocks, have fun
[18:13] <didrocks> rodrigo_: seb128: enjoy your evening :)
[18:13] <rodrigo_> didrocks, you too :)
[18:15] <rodrigo_> seb128, so, what other libs do we need in the PPA? gtk-engines-3? what others?
[18:15] <mterry> rodrigo_, I think at-spi needs to ship a gtk3 module as well as gtk2 one
[18:16] <rodrigo_> right
[18:16] <rodrigo_> what about gtksourceview?
[18:16] <mterry> rodrigo_, did you do the gtk3-dev depends on gtk-dev change?
[18:16] <rodrigo_> do we want it in the PPA, or just when we package gedit?
[18:16] <rodrigo_> mterry, hmm, no
[18:17] <rodrigo_> mterry, shall I?
[18:17] <mterry> rodrigo_, I agree with seb128 that it's suboptimal, but we need some way to ship libcanberra-gtk.h when gtk3-dev is used.  We could split it into a common-dev package, or we could ship two copies of the header with namespaces...  or we could have one depend on the other
[18:18] <seb128> depends for now
[18:18] <seb128> we will not get ride of the gtk2 version in the next weeks
[18:18] <rodrigo_> can we have 1 file in 2 subpackages?
[18:18] <seb128> we can upload for now and sort that with debian
[18:18] <mterry> rodrigo_, only if they conflict&replace each other
[18:18] <seb128> sjoerd said he would review your work for debian in the next days
[18:18] <rodrigo_> ah, ok
[18:18] <rodrigo_> so, do I add the dependency then?
[18:22] <seb128> rodrigo_, yes for now
[18:22] <rodrigo_> ok
[18:22] <seb128> until we sort a better way
 seb128: in my local trial version i've got a libcanberra-gtk-common-dev, but that seems a bit suboptimal as well
[18:22] <seb128>  seb128: (with the vapi and the .h)
[18:25] <rodrigo_> ok, pushed
[18:25] <seb128> sjoerd tried on that
[18:25] <seb128> rodrigo_, ok
[18:25] <seb128> if mterry is happy with the current version feel free to upload to the ppa
[18:25] <seb128> I will drop an email to sjoerd about your current work
[18:25] <rodrigo_> ok
[18:26] <seb128> so he can review and comment later on
[18:26] <seb128> I will Cc you on the email
[18:26] <rodrigo_> ok
[18:26] <seb128> rodrigo_, thanks for working on that ;-)
[18:26] <rodrigo_> you're welcome :)
[18:26] <seb128> rodrigo_, is there still anything we lack to build g-c-c after that?
[18:26] <mterry> rodrigo_, yeah, seems great!  push to the ppa and thanks
[18:26] <rodrigo_> mterry, ok
[18:26] <seb128> do we need that libsocial?
[18:26] <seb128> is somebody working on packaging it?
[18:26] <rodrigo_> seb128, I think not, but I'll try later on
[18:27] <rodrigo_> right, libsocial
[18:27] <rodrigo_> I'll look at packaging that
[18:27] <seb128> ok
[18:28] <seb128> rodrigo_, mterry: you guys have enough tasks to keep busy?
[18:28] <rodrigo_> seb128, I do, yes
[18:28] <rodrigo_> seb128, but if you want me to work on something, just tell me
[18:28] <mterry> seb128, I have stuff to work on, but I can take something
[18:28] <seb128> no, I'm just trying to make sure people don't waste time because they don't know what to do
[18:29] <seb128> rodrigo_, mterry: ok, great, so just keep on your current tasks ;-)
[18:30] <seb128> rodrigo_, btw you might want to hang on  oftc #debian-gnome
[18:30] <rodrigo_> ah, ok
[18:30] <seb128> we might have some of the gtk3 update discussions there with the debian guys over the cycle
[18:31] <seb128> it's usually very low activity
[18:31] <seb128> but being there is useful for such discussions
[18:31] <rodrigo_> here on freenode?
[18:31] <seb128> no, on oftc
[18:31] <seb128> irc.oftc.net
[18:31] <seb128> that's the irc debian is using
[18:32] <seb128> (yeah, yet another server to connect)
[18:33] <rodrigo_> :)
[18:33] <rodrigo_> ok, I'm in, but I'm leavbing now for some fresh air, so later all!
[18:35] <seb128> rodrigo_, have fun, see you tomorrow
[19:54] <kenvandine> tedg, i made some changes to the ubuntu-geoip package lp:~ubuntu-desktop/ubuntu-geoip/ubuntu
[19:54] <kenvandine> added description, bumped standards and set the desktop team as the package maintainer
[19:56] <tedg> kenvandine, Cool, I'll merge those.
[19:56]  * tedg is good at stealing other's work :)
[19:56] <kenvandine> i'll look for a sponsor soon, hacking up a test in python to make sure it behaves well without much installed :)
[20:00] <seb128> kenvandine, it's about time you run for motu rights
[20:00] <seb128> ;-)
[20:03] <kenvandine> seb128, yeah.. i know :)
[20:03] <kenvandine> i just need to ask for endorsements and get on the agenda for the next meeting
[20:03] <kenvandine> i keep forgetting about it
[20:03] <kenvandine> i guess that is the problem when most packages i touch i have upload rights for :)
[20:04] <seb128> we can fix that if you want ;-)
[20:04] <kenvandine> haha
[20:04] <kenvandine> although the other day i thought it would be fun to go do some sponsoring and help clean up the queue
[20:04] <kenvandine> but of course i couldn't :/
[20:05] <seb128> see
[20:05] <Laney> universe queue is pretty clean these days
[20:05] <Laney> you want main rights for that :P
[20:05] <seb128> you need motu first then you can get there ;-)
[20:05] <kenvandine> seb128, nope... dholbach told me to go ahead and ask for core-dev
[20:05] <seb128> better
[20:05] <seb128> go for it ;-)
[20:06] <seb128> so you can clean the sponsoring queue!
[20:06] <seb128> there is no way you will get out of your sponsoring duties :p
[20:06] <kenvandine> i'll make sure i am on the agenda for the next meeting
[20:06] <kenvandine> :)
[20:06] <seb128> thanks
[20:06] <dobey> has anyone here built natty packages in a ppa?
[20:06] <seb128> dobey, quite some people did that
[20:07] <seb128> we have a bunch of desktop ones
[20:07] <dobey> ok
[20:07] <seb128> why?
[20:07] <dobey> i guess it's just the source recipe builder stuff on launchpad that's not working for it
[20:08] <dobey> i get chroot errors when trying to build source recipes on lp for it
[20:08] <seb128> I guess you should ask the launchpad guys
[20:08] <seb128> works fine for normal uploads
[20:09] <dobey> yeah, that's why i asked if normal ppa uploads worked ok. :)
[20:10] <dobey> i'll bug the lp guys, thanks
[20:20] <cyphermox> guh, just finally made evolution-exchange 2.32 agree to compile on natty :)
[20:57] <kenvandine> tedg, so with geoclue, is should be able to set my accuracy and allowed resources and it will figure out the provider to use?
[20:58]  * kenvandine was looking at a plugin for GTG and they iterate over all the available providers and decide which to use
[20:58] <kenvandine> which seems silly to me
[20:58] <tedg> kenvandine, Yup.  I haven't tested that though.
[20:58] <tedg> kenvandine, The master client should be able to choose one for you.
[20:58] <kenvandine> ok
[20:58] <kenvandine> i actually think there is a bug in python-geoclue
[20:58] <kenvandine> which i have a fix for
[20:58] <tedg> kenvandine, You can look in indicator-datetime for how I do it.
[20:58] <kenvandine> but need to look at it with fresh eyes later :)
[21:39] <rodrigo_> kenvandine, any idea why I get this:
[21:39] <rodrigo_> Unable to find libcanberra_0.26.orig.tar.gz in upload or distribution.
[21:39] <rodrigo_> Files specified in DSC are broken or missing, skipping package unpack verification.
[21:39] <rodrigo_> when submitting from a source package branch?
[21:39] <rodrigo_> it seems it doesn't upload the tar.gz, why?
[21:40] <kenvandine> is the libcanberra_0.26.orig.tar.gz in the dir?
[21:40] <rodrigo_> yes
[21:51] <cyphermox> rodrigo_, is it a *ubuntu1 revision?
[21:52] <rodrigo_> hmm, no, it's 2
[21:52] <cyphermox> you might want to debuild -S -sa if it's for a PPA
[21:52] <rodrigo_> ok
[21:52] <cyphermox> (or the 'bzr bd -S -- -sa' equivalent)
[21:53]  * cyphermox -> eod
[21:54] <rodrigo_> right, that did it, it's uploading the tar.gz now
[21:56] <rodrigo_> hey robert_ancell
[21:56] <robert_ancell> rodrigo_, hey
[21:57] <robert_ancell> rodrigo_, hey
[22:11] <kklimonda_> rodrigo_: I like your host ;)
[22:11] <sarvatt> http://etherpad.osuosl.org/lpc2010-desktop  -- desktop discussions from today at plumbers, the death to distributions talk (aka gnome os) was especially interesting
[22:11] <kklimonda_> sarvatt: are the discussions and presentations recorded?
[22:12] <sarvatt> I dont believe so outside of the awesome non crashy gobby replacement etherpad notes
[22:13] <kklimonda_> bummer - topics that are being discussed on the plumber conference are really interesting :/
[22:28] <sarvatt> gnome 4.0 = the one distro to rule them all basically (pretty easy to guess what it would be based on)
[22:31] <kklimonda_> sarvatt: how are they planning to do that? it
[22:31] <kklimonda_> it's one thing to say that gnome is going to be the os itself, it's another thing to convince enough people of it.


[06:23] <superfly> Zzzzz
[07:27] <gremble> Good morning
[13:30] <squish102> i'm struggling to get a kernel > 2.6 on a VPS. Anyone can give some help?
[13:31] <squish102> grub-mkconfig errors with: grub-probe: error: failed to get canonical path of `/vz/private/14025'
[13:58] <inetpro> good mornings
[14:01] <inetpro> squish102: maybe related to http://askubuntu.com/questions/254491/failed-to-get-canonical-path-of-cow ?
[17:33] <squish102> is it worth me setting up an unotelly like thing for people?
[18:23] <Cryterion> squish102??
[18:42] <inetpro> .
[23:05] <squish102> Cryterion: untotelly.com
[23:05] <squish102> unotelly.com


[08:46] <Walex> what does 'juju sync-tools' do? Is it related to 'juju upgrade-tools'?
[08:48] <Walex> my issue is: I upgraded the Juju packages 1.23.3 to 1.24.5 on the "control" node but the '/var/lib/juju/tools/' directories on the state nodes are not being updated
[10:47] <luqas> hi, I might be hitting https://bugs.launchpad.net/juju-core/+bug/1417875 on juju-core 1.24.5
[10:47] <mup> Bug #1417875: ERROR juju.worker runner.go:219 exited "rsyslog": x509: certificate signed by unknown authority <canonical-bootstack> <logging> <regression> <juju-core:Fix
[10:47] <mup> Released by wwitzel3> <juju-core 1.21:Fix Released by wwitzel3> <juju-core 1.22:Fix Released by wwitzel3> <https://launchpad.net/bugs/1417875>
[10:48] <luqas> wwitzel3: I'm trying your manual workaround but I can't find the "good" certificate
[15:49] <ssmoCoffee> We are installing Openstack per the single installer guide ubuntu-cloud-installer.readthedocs.org/en/latest/single-installer.guide.html.  Bootstrapping Juju fails with an error message about kvm-ok and cpu-checker packages needing to be installed.
[15:50] <ssmoCoffee> The packages cpu-checker and qemu-kvm are installed on both the host server and the bootstrap container.
[15:50] <ssmoCoffee> Anyone run into the same issue?
[15:51] <ssmoCoffee> I reproduce the error attaching the bootstrap container and running juju --debug bootstrap -e local
[15:52] <ssmoCoffee> ERROR juju.cmd supercommand.go:430 there was an issue examining the environment: failed verification of local provider prerequisites: kvm-ok is not installed. Please install the cpu-checker package.
[16:11] <firl> anyone able to possibly help me diagnose why my landscape isn’t installing via the openstack-install? I am looking in the JuJu files and I can’t seem to figure out which error to try to research.
[16:33] <lazyPower> dpb1_: ping
[16:33] <lazyPower> ssmoCoffee: thats... odd. Which version of ubuntu/openstack installer?
[16:34] <lazyPower> Walex: Did you get an answer out of band?
[16:36] <ssmoCoffee> lazyPower: OpenStack Installer v0.99.19
[16:38] <lazyPower> firl: i'm pending a response from a landscape charmer, however - if you could send over the juju log from that landscape node we should be able to track down whats happening
[16:39] <lazyPower> ssmoCoffee: is this on trusty?
[16:39] <ssmoCoffee> lazyPower: running kvm-ok from the bootstrap container fails
[16:39] <ssmoCoffee> vivid
[16:39] <lazyPower> @ddellav - can you check on this? kvm-ok on a bootstrap node in vivid?
[16:39] <lazyPower> ssmoCoffee: which version of juju?
[16:39] <firl> lazyPower: sure will do. I tried on 2 different systems, and a VM with embedded. Do you know if I deploy landscape automatically ( not openstack-installer ) if I get the openstack-beta tab still?
[16:40] <lazyPower> firl: i'm not positive, but i would *think* so
[16:40] <sparkiegeek> firl: you do :)
[16:40] <ssmoCoffee> 1.24.5-vivid-amd64
[16:40] <lazyPower> perfect, latest stable. thanks ssmoCoffee
[16:40] <firl> lazyPower: sparkiegeek: so the openstack-installer is just a “nice” wrapper so you don’t have to create your own juju file and environment?
[16:41] <lazyPower> 1 sec while i poke around and try to get some output.
[16:41] <sparkiegeek> firl: that and setting up of MAAS
[16:41] <firl> which can be done post install
[16:41] <firl> kk
[16:41] <sparkiegeek> (which is the hard part that the installer automates [some of] for you)
[16:41] <firl> that makes me feel a little better
[16:41] <sparkiegeek> so if you're comfortable getting MAAS setup, you can quite easily deploy Landscape using Juju
[16:41] <firl> lazyPower: http://pastebin.com/U8TeqYAK
[16:41] <sparkiegeek> https://help.landscape.canonical.com/LDS/JujuDeployment15.01
[16:42] <firl> nice, yeah I will do that
[16:42] <ssmoCoffee> lazyPower: thanks.  Should /proc/cpuinfo be empty on the bootstrap contianer?
[16:42] <lazyPower> ssmoCoffee: not at all
[16:42] <lazyPower> the /proc/cpuinfo should be filled out always due to procfs
[16:43] <lazyPower> and thats part of ubuntu core
[16:43] <firl> sparkiegeek: do you know if the openstack-beta installer has been upgraded to vivid/kilo?
[16:44] <ssmoCoffee> lazyPower: on the host /proc/cpuinfo is populated and kvm-ok returns that KVM acceleration can be used
[16:44] <sparkiegeek> firl: there's Work In Progress on trusty/kilo - we don't target the interim releases (vivid, wily ...)
[16:44] <firl> kk
[16:45] <firl> I just liked the idea of lxc containers that came with vivid
[16:45] <sparkiegeek> what do you mean? LXD?
[16:45] <ssmoCoffee> lazyPower: so the lxc bootstrap container isn't valid
[16:46] <firl> ya LXD sorry
[16:46] <firl> https://insights.ubuntu.com/2015/04/22/here-comes-kilo-15-05-containers-will-never-be-the-same-again/
[16:47] <sparkiegeek> firl: ah, containers in your OpenStack - right we're excited by that too, but you'll have to wait for 16.04 (next LTS) before we integrate it
[16:47] <sparkiegeek> (in the autopilot I mean)
[16:47] <firl> I figured :)
[16:47] <firl> are the openstack charms also only targetted for lts?
[16:47] <sparkiegeek> there's some rounding out of nova-compute-lxd that still needs to happen - an LTS is the best place to do that :)
[16:48] <sparkiegeek> no, the charms will support vivid/kilo
[16:48] <sparkiegeek> s/will/do/
[16:48] <firl> oh really?
[16:48] <firl> I can deploy via the juju ui and get vivid/kilo right now?
[16:51] <sparkiegeek> beisner: ^^ do you guys have a bundle somewhere for vivid/kilo?
[16:52] <beisner> sparkiegeek, firl - while there isn't an official V:K bundle published in the charm store, we do have test bundles which exercise that.  it would need to be tailored to you desired topology and machine/service placement, however.
[16:53] <sparkiegeek> beisner: sure, I expect firl could start with them as a drag/drop into Juju GUI and then tailor from there?
[16:53] <sparkiegeek> machine view for placement + any other tweaks
[16:54] <firl> beisner,sparkiegeek: yeah that doesn’t scare me. I ran into an issue last month where I had to commit the ceph config before adding the units because of having to specify all the drives
[16:55] <firl> I am using a custom deployed openstack bundle on my machines at home
[16:55] <beisner> sparkiegeek, firl - i'm not as familiar with the gui.  i generally tune the yaml in advance, with the desired deployment completely described before even bootstrapping.
[16:55] <beisner> but, i think you can do some pretty cool things like that in the gui
[16:55] <firl> beisner: that would work great actually for the deployment I am going for
[16:55] <sparkiegeek> beisner: sure
[16:55]  * beisner fetches a ymmv bundle as a starting point for ya
[16:57] <firl> :)
[16:59] <beisner> flir - caveat - these aren't vetted for production, they are the topologies we test with in charm and package development.
[16:59] <beisner> http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/baremetal/7-default.yaml
[17:00] <beisner> juju-deployer --bootstrap -c default.yaml -d vivid-kilo
[17:00] <beisner> rather
[17:00] <beisner> juju-deployer --bootstrap -c 7-default.yaml -d trusty-juno
[17:00] <beisner> ah bugger
[17:00] <beisner> copy paste fail
[17:00] <firl> haha
[17:00] <sparkiegeek> 7-default.yaml, vivid-kilo :)
[17:00] <beisner> juju-deployer --bootstrap -c 7-default.yaml -d vivid-kilo
[17:00] <beisner> yagotit
[17:00] <beisner> lol
[17:00] <beisner> thankfully, it is friday
[17:01] <firl> beisner: thanks! I will definitely be trying this later, there is a 40 node maas cluster I am trying to work with currently
[17:02] <sparkiegeek> firl: so not sure how familiar you are with Juju + bundles, but that one is a v3 bundle format (contains multiple targets) the latest/greatest format that the GUI supports is v4 so you'll have to use juju-deployer to ... deployt it :)
[17:02] <firl> sparkiegeek: I can still manage it post install via the juju-gui right?
[17:02] <sparkiegeek> firl: sure
[17:02] <firl> very cool
[17:03] <beisner> firl, sparkiegeek - ++caveat:  there is a known issues with pxc (percona-cluster) on vivid.   you can substitute lp:charms/trusty/mysql
[17:03] <beisner> bug 1481362
[17:03] <mup> Bug #1481362: pxc server 5.6 on Vivid and Wily does not create /var/lib/mysql <amulet> <openstack> <uosci> <percona-xtradb-cluster-5.6 (Ubuntu):New> <percona-cluster (Juju Charms Collection):New> <https://launchpad.net/bugs/1481362>
[17:04] <beisner> oh wait
[17:04] <beisner> i already did that via inheritance in the bundle :-)
[17:04] <beisner> http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/baremetal/7-default.yaml#L314
[17:04] <firl> haha
[17:11] <beisner> firl, ah cool 40 nodes.  happy deploying!
[17:11] <firl> beisner: haha thanks should be fun
[17:12] <beisner> o/ thanks sparkiegeek lazyPower
[17:13] <firl> and whoever set the title of the room scared me, the dates seem to be 17-18
[17:14] <sparkiegeek> firl: 10 points for attention to detail
[17:14] <sparkiegeek> lazyPower: ^^ topic has wrong dates for the summit :)
[17:14] <firl> haha, well I am about to book travel so I got scared
[17:19] <firl> beisner: do you have a help article on how to get the new environment ready for juju as well? I had quite a pain prepping my environment, and that is one thing I liked that landscape did
[17:20] <beisner> firl, you already have maas with machines enlisted and ready to go to work?
[17:20] <firl> ya
[17:20] <firl> I meant the vivid/kilo OS prepped for juju deployments
[17:21] <sparkiegeek> ah, Juju on the inside?
[17:21] <firl> yeah
[17:21] <firl> that’s one thing landscape did, deployed tools, and prepped the juju
[17:21] <beisner> oh to use juju with the openstack provider on the deployed cloud
[17:21] <firl> ya
[17:22] <sparkiegeek> https://jujucharms.com/docs/stable/howto-privatecloud is the documented way
[17:23] <firl> yeah … I am very familar with that page, hope it works out better than last time haha
[17:23] <beisner> also https://jujucharms.com/docs/devel/config-openstack  for the openstack-provider specific environment.yaml options
[17:24] <firl> thanks, yeah I’ve been through it. I will try again, hopefully with the latest juju it’s a little easier now
[17:25] <firl> 1.24 caused issues / frustrations
[17:29] <beisner> firl, as reference, my environments.yaml looks like this, sanitized:  http://paste.ubuntu.com/12215832/
[17:30] <firl> beisner: thanks, I appreciate it
[17:31] <sparkiegeek> firl: FWIW in my experience you don't have to put tools in to your OpenStack - what the Autopilot does is "just" put things in Swift to tell Juju where to find the Ubuntu images (e.g. Glance)
[17:31] <beisner> firl, you're welcome
[17:33] <sparkiegeek> i.e. just the Image Metadata Contents section of that doc page
[18:41] <pmatulis> does 'enable-os-upgrade' affect just 'apt upgrade' or 'apt full-upgrade'?
[18:41] <pmatulis> lazyPower, wallyworld, marcoceppi: ? ↑
[18:42] <lazyPower> pmatulis: that stops the apt-get update && apt-get upgrade when spinning up a new instance iirc.
[18:42] <pmatulis> lazyPower: ok, so just upgrade and not full-upgrade
[18:42] <lazyPower> aiui, correct
[18:43] <pmatulis> thanks
[22:16] <bdx> core, dev: Does anyone here know how to add custom cloud-config to maas provisioning....i.e. curtin_userdata preseeed or custom preseed??


[03:24] <ojeq> @find ubuntu
[03:24] <meetingology> ojeq: Error: "find" is not a valid command.
[03:24] <ojeq> !triger
[20:28] <clausen> about once per day, my gnome-shell goes black (login screen, bars on the top/bottom, activities screen, everything)
[20:29] <clausen> I can still use it, just things aren't drawn properly, so I have to guess where to click
[20:29] <clausen> any ideas?
[20:40] <clausen> changing theme doesn't help -- the only solution is to log out and in again
[22:10] <darkxst> Noskcaj, can you file a MIR for grilo-plugins, for bug 1393067


[00:23] <joaopinto> sistpoty,
[00:23] <joaopinto> notecase (1.9.8-0ubuntu3) karmic; urgency=low
[00:23] <joaopinto>   * FTBFS: Added include <stdio.h> to IniFile.h (LP: #447628)
[00:23] <joaopinto> like this ?
[00:23] <sistpoty> joaopinto: that's excellent!
[00:23] <joaopinto> ok, goind go attach the debdiff now
[00:23] <joaopinto> going to
[00:24]  * funkyHat hasn't found any other FTBFS that aren't C or C++ problems :(
[00:24] <joaopinto> hum, there is a change which was not done by me
[00:24] <joaopinto> -Architecture: i686
[00:24] <joaopinto> +Architecture: amd64
[00:24] <joaopinto> oh, deb dir
[00:25] <joaopinto> this is some temporary dir as part of the building process
[00:25] <joaopinto> notecase-1.9.8/deb/control
[00:26] <joaopinto> sistpoty, the package building source touchs a deb dir, it was no my change, i'll keep it in in the debdiff
[00:27] <sistpoty> sure thing, amd64 does make more sense imho ;)
[00:28] <joaopinto> done, bug 447628
[00:33] <sistpoty> joaopinto: the changed file doesn't seem to be one I'd worry about. patch looks good :), test-building
[00:37] <joaopinto> I would like to update a package to a newer version: http://icculus.org/referencer/ChangeLog, the new version is from August and it's mostly bugfixes
[00:43] <joaopinto> well, maybe is to late for that
[00:43] <joaopinto> I hate fixing problems on out-dated packages
[00:45] <sistpoty> joaopinto: sorry, was afk for a minute, and notecase failed to build for me (not your fault, problems with mirror on my side, retrying)
[00:45] <joaopinto> I did a test build on a karmic schroot
[00:47] <sistpoty> joaopinto: yes, as I wrote it's not your fault (my pbuilder failed to download build-deps, due to 403 on my mirror, grmpf)
[00:47] <sistpoty> ah, better now, compiling :)
[00:52] <sistpoty> joaopinto: in regards to referencer, imo it makes sense to file a FFe if it builds fine and subscribe seb128 (his terrain)
[00:52] <sistpoty> at least from a quick read of changelog
[00:53] <joaopinto> I am not experienced in those processes, i will just fix the ftbfs for now
[00:54] <sistpoty> !FFE
[00:54] <joaopinto> if the new version was not request, is because no one care about it until now
[00:54] <joaopinto> requested
[00:55] <sistpoty> joaopinto: gnome is a little bit special due to its release cycle being coordinated with Ubuntu's
[00:55] <joaopinto> there are some bugs reported about referencer, they would need to be checked and validated against the new version
[00:55] <sistpoty> joaopinto: question is if it's a package fallling under that release cycle
[00:55] <sistpoty> joaopinto: btw: notecase uploaded, thanks again!
[00:56] <joaopinto> yw :)
[00:56] <joaopinto> I am just test building referencer now
[01:02] <captivus> Hello.  I have, embarrassingly, forgotten my passphrase for the OpenPGP key I created when I created my LP account a few months back.
[01:02] <captivus> (I've clearly not used it since then.)
[01:03] <captivus> Anyone have any suggestions?
[01:03] <sistpoty> captivus: revoke that key and create a new one?
[01:03] <captivus> Ok.  How do I do that?
[01:04] <captivus> Oh, wait -- I'd have had to have created a revocation key, right?
[01:04] <captivus> How do I know if I created one?
[01:04] <captivus> (I don't recall doing that.)
[01:04] <sistpoty> captivus: using your revocation certificate that you've printed on paper and stored in your treasury once you generated the old key?
[01:04] <captivus> Oh, well that would be sensible ...
[01:04] <captivus> ... I definitely didn't do that.
[01:05] <sistpoty> captivus: then do that for the key you generate now ;)
[01:05] <captivus> sistpoty: LOL!  I'm going to be forever haunted by the ghost of this old key.  It's going to be lingering out there associated with my name forever.
[01:05] <captivus> God, that's so embarrassing.
[01:06] <sistpoty> captivus: yes, happened to me as well :(
[01:06] <joaopinto> sistpoty, bug 447659
[01:08] <sistpoty> joaopinto: looking
[01:09] <sistpoty> joaopinto: that's c++?
[01:09] <sistpoty> joaopinto: if so the really correct header is <cstdint>
[01:09] <joaopinto> siretart, yes, it's c++
[01:09] <joaopinto> ops :\
[01:09] <joaopinto> used the C header
[01:10] <sistpoty> joaopinto: I'll fix this before uploading, ok?
[01:10] <joaopinto> ok
[01:11] <joaopinto> sistpoty, it fails to compile if you include <cstdint>
[01:11] <joaopinto> /usr/include/c++/4.4/c++0x_warning.h:31:2: error: #error This file requires compiler and library support for the upcoming ISO C++ standard, C++0x. This support is currently experimental, and must be enabled with the -std=c++0x or -std=gnu++0x compiler options.
[01:12] <sistpoty> joaopinto: ah, crack, that that was solved with -4.4 now
[01:12] <sistpoty> thought that... even
[01:13] <sistpoty> joaopinto: another tiny change: I've updated the maintainer field... ok?
[01:14] <joaopinto> ok
[01:15] <sistpoty> argh, me hates de.archive.ubuntu.com today. mirrors don't seem to be in agreement depending which ip resolve to the name
[01:15] <sistpoty> (and one constantly says 403)
[01:18] <joaopinto> lighttpd looks another candidate for FFe
[01:18] <joaopinto> but that should be requested by someone really using it
[01:22] <joaopinto> argh, lighttpd calls automake, it produces a big debdiff, is that ok to fix FTBFS ?
[01:25] <sistpoty> joaopinto: sure, if it's only autotools files there's no problem
[01:27] <sistpoty> joaopinto: hm, you're fixing faster than I can sponsor :P (referencer uploaded, thanks!)
[01:27] <joaopinto> sistpoty, bug 447672
[01:27] <joaopinto> I only changed debian/control and added the changelog entry, all the other diff is autotools
[01:31] <sistpoty> joaopinto: patch is ok, but debian/changelog is erm, very brief. can you be a little bit more verbose there? ;)
[01:32] <joaopinto> erm, more verbose how ? I just noted it needed automake1.10 because configure invoked aclocal-1.10 :P
[01:34] <sistpoty> joaopinto: as in * debian/control: change build-dependency of ... * rerun autotools
[01:34] <jbernard_> i just posted a patch for Bug #447677, if anyone has a sec to review
[01:35] <sistpoty> <- out for 5 minutes, will continue reviewing then
[01:35] <quidnunc> When trying to run sudo do-release-upgrade -d I get "Building old list of packages... errors present. Is apt/dpkg running?" Anyone know what the problem is?
[01:35] <joaopinto> well, rerun autotools was not an explicit action, actually I could just trim dow the diff
[01:35] <quidnunc> Or, how can I run do-release-upgrade with debug logging on?
[01:36] <joaopinto> quidnunc, this channel is not for support, try #ubuntu or #ubuntu+1
[01:36] <quidnunc> Sorry
[01:39] <joaopinto> sistpoty, i will be attaching a new diff, without the autotools changes
[01:39] <sistpoty> joaopinto: thanks!
[01:44] <sistpoty> jbernard_: excellent, thanks! can you forward the patch to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549778 please?
[01:45] <joaopinto> brb
[01:45] <jbernard_> sistpoty: yep, im working on it right now
[01:45] <jbernard_> sistpoty: i crosslinked to the deb bug in LP
[01:45] <sistpoty> :)
[01:46] <sistpoty> jbernard_: uploaded, thanks!
[01:47] <jbernard_> sistpoty: awesome! thanks man
[01:50] <joaopinto> sistpoty, https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/447672
[01:51] <sistpoty> joaopinto: looks great, test-building again
[02:03] <sistpoty> joaopinto: lighttpd uploaded, thanks!
[02:04] <superm1> sistpoty, re bug 432678 there is a kernel component that needs to be updated too
[02:04] <superm1> it's been on my TODO for the last week or so to fully investigate
[02:04] <superm1> but it's a daunting task.  i always shrug whenever i need to touch LIRC
[02:05] <superm1> if you can make a call in terms of the FFe, i'll sort out the technical details if you lean towards yes though
[02:05] <sistpoty> superm1: thanks for the info
[02:05] <sistpoty> superm1: basically having you sort out details is what makes me lean very much towards it
[02:06] <sistpoty> superm1: the FFe only sounded as if we'd need to make changes to the stock kernel of which noone is aware yet ;)
[02:06] <superm1> which is true
[02:07] <superm1> there is a LIRC patchset that sits on top of the kernel
[02:07] <sistpoty> superm1: will that patchset work with an older lirc?
[02:07] <superm1> no it won't
[02:08] <superm1> so it's either new LIRC + new patches to kernel
[02:08] <superm1> or stay with the current stuff
[02:08] <sistpoty> superm1: hm, are you ok if I'll elevate this to ubuntu-release then?
[02:09] <superm1> sistpoty, yeah however you'd like to do it.  i'll clone a kernel and try to look into the technical details over the weekend
[02:09] <sistpoty> superm1: excellent, thanks!
[02:10] <superm1> it's worth mentioning the patches apply directly to a lirc/ directory and don't hurt anything else ever
[02:10] <superm1> so as long as they're verified to compile, they're harmless
[02:12] <sistpoty> <- doesn't know much about the kernel and certainly doesn't feel qualified to decide about kernel matters :P
[02:16] <joaopinto> sistpoty, check bug 447701 please , and now i am going to bed
[02:54] <sistpoty> <- falls into bed now.. gn8 everyone
[04:39] <mzz> How do I get debuild (or dpkg-buildpackage, or whatever's actually doing this) to show me the commandline used for "Now running lintian..."? I'm getting a complaint there (bad-ubuntu-distribution-in-changes-file unstable) that lintian -iIE --pedantic does not give me.
[04:43] <mzz> ah! I need to run it on the changes file, not on the dsc
[04:44] <mzz> (I'm guessing that always runs more checks?)
[11:36] <surfzoid> Hi, after a build package request at bugzilla, it took usually long time to see it in ubuntu ?
[11:37] <surfzoid> oups sorry, i mean launchpad not bugzilla :-)
[11:45] <av`> surfzoid, package name?
[11:45] <surfzoid> MonoOSC,  day ago :-)
[11:45] <surfzoid> https://bugs.launchpad.net/bugs/443398
[11:46] <surfzoid> 5 days ago
[11:46] <surfzoid> av`: not so long :-)
[11:46] <av`> surfzoid, give me a sec and I have a look at it, finishing something
[11:46] <surfzoid> hey, oki, very nice :-)
[11:48] <joaopinto> surfzoid, not goind to happen for this release
[11:48] <joaopinto> ops, gone
[11:51] <slacker_nl> i'm reading some of the chat logs of ubuntu developer week, why does dholbach installs some of the packages with no-install-recommends? apt-get install --no-install-recommends bzr ubuntu-dev-tools devscripts dpkg-dev cdbs
[12:15] <Laney> motu-release folks: would http://projects.qnetp.net/versions/show/9 get a FFe you think?
[12:35] <joaopinto> can someone check and upload the fix for bug 447933 ?
[12:37] <Laney> joaopinto: is the patch upstream?
[12:37] <joaopinto> no, I am going to send it now
[12:38] <Laney> ok
[12:46] <joaopinto> report upstream now
[12:46] <joaopinto> reported
[12:46] <joaopinto> who should I subcribe when no one is available for FTBFS bugs ?
[12:52] <Laney> this package takes ages to build
[13:01] <joaopinto> Laney, it does :P
[13:02] <jbernard_> joaopinto: i've been subscribing 'universe sponsors' to my FTBFS bugs
[13:02] <Laney> oh there it's finished
[13:03] <joaopinto> jbernard_, ok tks, Laney you are working on it right ?
[13:03] <Laney> joaopinto: uploaded
[13:04] <joaopinto> Laney, tks
[13:05] <Laney> please could you send it to debian too?
[13:14] <joaopinto> Laney, I have sent it to the upstream authors, it will land into debian on the next update
[13:16] <Laney> joaopinto: they might want to fix the ftbfs more immediately
[13:19] <joaopinto> ok
[13:25] <av`> jbernard_, did you do any FTBFS fix recently?
[13:25] <joaopinto> Laney, bug 447967
[13:26] <av`> joaopinto, the LP: xxxx field is broken
[13:27] <joaopinto> ops, forgot to update the source diff
[13:27] <ari-tczew> aloha
[13:28] <joaopinto> av`, fixed
[13:28] <av`> joaopinto, where did you grab that patch from?
[13:29] <joaopinto> av`, from myself
[13:34] <joaopinto> and yes, I have sent it upstream and to debian which is the same
[13:47] <mok0> Oh great, karmic upgrade  broke my sbuilder :-(
[13:49] <joaopinto> Laney, looking at 447967 or should I subscribe universe sponsors ?
[13:49] <joaopinto> that one is an easy build
[13:49] <joaopinto> it's a text game :P
[13:57] <hyperair> anyone from motu-release here? i'd like to inquire whether i can just upload a snapshot of banshee for the time being, and then get 1.5.1 uploaded post-release?
[13:58] <hyperair> from 1.4.3 to 1.5.0 there are approx 139 bugfixes (grepped the BGO keywords from git log)
[13:58] <hyperair> and from 1.5.0 to date is 84 bugfixes
[13:58] <hyperair> s/is/are/
[13:59] <hyperair> and while they say 1.5.1 is going to be released really soon, they haven't yet and won't give a date.
[13:59] <sistpoty> hyperair: you mean to get 1.5.1 in via an sru?
[14:00] <hyperair> yes
[14:00] <sistpoty> hm...
[14:00] <hyperair> well, i'm not sure whether 1.5.1 is going to arrive before or after karmic
[14:00] <hyperair> if before, then sru not needed, i suppose
[14:01] <sistpoty> directhex: what's your opinion wrt. banshee?
[14:02] <joaopinto> sistpoty, when you have some please check 447967
[14:02] <sistpoty> joaopinto: funny, actually I'm already looking at it ;)
[14:02] <joaopinto> I have a FTBFS for a game that will break the -data dependency rule, is there a proper fix apart from replaceing SourceVersion with an hardcoded version ?
[14:03] <joaopinto> otherwise it would require a -data reupload with the newer version
[14:04] <sistpoty> joaopinto: which one is it?
[14:04] <joaopinto> ceferino
[14:04] <joaopinto> ceferino_0.97.8-2.dsc -> ceferino_0.97.8-2ubuntu1.dsc
[14:05] <joaopinto> hum, maybe I can use UpstreamVersion instead ?
[14:05] <ari-tczew> if you want new upstream, you need open a ffe request
[14:06] <joaopinto> it's not a new upstream version
[14:06] <joaopinto> it's a FTBFS fix, which requires a debian version bump, which breaks the depend rule for -data
[14:09] <joaopinto> I beleive there is an UpstreamVersion macro, which could be a solution
[14:12] <ari-tczew> give bug's number
[14:13] <joaopinto> ari-tczew, bug 447994, but I don't need help with the bug per si, just how to address the -data depend change :)
[14:14] <sistpoty> joaopinto: bombardier uploaded
[14:14] <joaopinto> sistpoty, tks
[14:14] <sistpoty> joaopinto: there should be a macro for the upstream version, let me look
[14:15] <joaopinto> tried ${source:UpstreamVersion}, is not it :\
[14:15] <sistpoty> joaopinto:  source:Upstream-Version
[14:16] <sistpoty> joaopinto: see deb-substvars manpage
[14:16] <joaopinto> ops, was missing the -
[14:18] <joaopinto> erm, wait, I am nuts, -data is also built from this source package
[14:18] <sistpoty> that simplifies things ;)
[14:21] <joaopinto> sistpoty, bug 447994
[14:25]  * sistpoty reads the c++ iso spec to find out if that is indeed a bug in ceferino
[14:30] <joaopinto> bbl
[14:30] <sistpoty> yes, looks like grafico overrides the type name in the declarator list, so a bug in ceferino (at least from my interpretation of the c++ spec)
[15:27] <pkern> sistpoty: Hi.  So there is indeed a file conflict on gnome-audio vs. ubuntu-sounds AFAICS (card_shuffle.wav).  How to proceed from there, considering that ubuntu-sounds is in main whereas gnome-audio is not?
[15:27] <sistpoty> pkern: hm... let me recheck
[15:28] <pkern> sistpoty: https://bugs.edge.launchpad.net/ubuntu/+source/ubuntu-sounds/+bug/343288 fwiw
[15:29] <sistpoty> pkern: indeed didn't see card_shuffle.wav
[15:32] <pkern> sistpoty: Shipping the file in the package would of course also fix the problem, but I guess we don't really want that.  Or reusing a sound file from ubuntu-sounds if there's something suitable.
[15:32] <pkern> sistpoty: However in the long term that should be fixed.  \-:
[15:34] <sistpoty> pkern: I guess the best fix would be to move card_shuffle in ubuntu-sounds to the subdirectory.. though I'm not sure what uses the file and would need to be adjusted
[15:38] <sistpoty> pkern: maybe a dirty hack would be to declares replaces on ubuntu-sounds/gnome-audio w.o. conflicts?
[15:39] <sistpoty> pkern: I guess you could also ask seb128 for directions
[15:40] <pkern> sistpoty: Then it would be semi-random, though, who'll own that file.
[15:40] <sistpoty> pkern: yes, that's why I wrote dirty hack
[15:51]  * sistpoty is off again, cya
[15:59] <pkern> TheMuso: ^^
[16:12] <captivus> Hello.  How do I know if a package I am building will need the .ex and .EX files?
[16:15] <hyperair> erm experience?
[16:15] <hyperair> probably
[16:15] <hyperair> heheh
[16:16] <hyperair> well some of them are documented in comments inside them
[16:19] <captivus> Yes, well I was hoping that there was a comprehensive explanation of the files and their use somewhere, but I can't seem to find one on the wiki
[17:02] <directhex> someone rang?
[17:19] <soc> hi
[17:19] <soc> how can i see which libraries are used by an executabke?
[17:19] <directhex> soc, assuming it's an ELF binary, with "ldd"
[17:20] <Laney> directhex: re: uploading a git snapshot of banshee
[17:20] <soc> ldd /usr/bin/hp-setup
[17:20] <directhex> Laney, then SRU to 151?
[17:20] <Laney> yes
[17:20] <soc> not a dynamic executable
[17:21] <directhex> soc, no, it's not. it's a python script.
[17:21] <soc> ah thanks
[17:22] <directhex> Laney, if we can SRU to 1.5.1, do you think a git snapshot is better than 1.5.0?
[17:22] <Laney> yeah for sure
[17:22] <Laney> I've been running the dailies for ages
[17:23] <directhex> either is better than 1.4.3. i just have a general gut reaction to snapshots
[17:23] <Laney> cody-somerville, jdong: Would you agree in principle to a Karmic SRU from a git snapshot of Banshee to the release if it happens after release?
[17:24] <Laney> I reckon that head currently is pretty much what 151 will be anyway
[17:24] <directhex> i think that's quite possibly the case. mac bugs causing delays, isn't it?
[17:24] <Laney> not sure
[17:25] <jdong> Laney: well I would like to see at that point the diff and also what Ubuntu bugs it'd close, but in principle I see nothing wrong with that
[17:25] <funkyHat> nooo inkscape I need you to work properly -.-
[17:26] <directhex> jdong, can you REJECT something from NEW?
[17:26] <jdong> hahaha I'm not that magical :)
[17:27] <Laney> cool beans
[17:27] <Laney> directhex: yay or nay?
[17:28] <Laney> also, did you do it again?
[17:28] <Laney> hahaha
[17:28] <directhex> Laney, i fixed my dput.cf! on, erm, my office pc. then i did it again at home :(
[17:28] <Laney> amazing
[17:29] <jdong> directhex: HAHAHAHA
[17:29] <directhex> Laney, on a related note, i feel *way* more sleepy & headachey than i did when attacking the archive with bad uploads. so better if you coordinate my "yay" with hyperair
[17:29] <sebner> directhex: you should really hide somewhere
[17:29]  * jdong can totally see the archive admins chasing after directhex with a bat
[17:30] <directhex> jdong, apparently slangasek expects beer. beer is an acceptable penance
[17:35]  * james_w takes his archive admin bat and applies it to clr-wallpapers
[17:35] <james_w> and it is out of here!
[17:35] <directhex> ta james_w
[17:35] <directhex> going to the karmic release party in london?
[17:36] <james_w> I reckon you are just trying to catch someone asleep at the wheel so that it ends up in karmic
[17:36] <james_w> not sure
[17:36] <james_w> I have to head down sometime that week
[17:36] <directhex> 'cos i owe you a beer now
[17:36] <james_w> but we haven't arranged the meeting yet
[17:36] <james_w> hah
[17:36] <james_w> clicking a button != a beer
[17:36] <hyperair> directhex: what?
[17:37] <directhex> hyperair, "yes" to banshee snapshot in karmic, but i'm too headachey to check it
[17:37] <hyperair> ah
[17:37] <hyperair> i see
[17:39] <hyperair> well then i'll work on it
[17:41] <hyperair> so.. first step is to file a bug i suppose... what information should i include? diff (debdiff?), list of bugs it'd fix, what else?
[17:42] <hyperair> also, is there an easy way to get the bug # of a launchpad bug linked to a certain BGO bug#?
[17:42] <hyperair> as in, i have the BGO bug #, and i'd like to get the launchpad bug # linked to it
[17:44] <directhex> i don't know if launchpadlib can search on that
[17:46] <hyperair> hmm
[17:53] <ari-tczew> james_w: could you review again drupal's security bug #431080 ?
[18:59] <LtWorf> hello
[19:00] <LtWorf> i am the debian mantainer of a package, and i was sent here from #ubuntu to ask how could it be inserted in ubuntu's repositories too
[19:01] <azeem> it's a pretty bad time right now because AFAIK the Ubuntu repository is frozen for the 9.10 release
[19:01] <azeem> however, in general you can file a sync request bug I guess and it will be acted upon after release
[19:01] <Laney> we'll get it automatically after Karmic releases
[19:02] <Laney> if it's a new package
[19:02] <mok0> LtWorf: it will be sync'ed automatically for lucid
[19:02] <mok0> LtWorf: no need to do anything
[19:02] <LtWorf> mh ok... i'll try to figure out what a sync request bug is :)
[19:03] <mok0> LtWorf: It's just a bug that says: please sync ... blah blah ... from unstable
[19:03] <mok0> LtWorf: but you only need that after "Debian Import Freeze"
[19:05] <LtWorf> mok0: and what "Debian Import Freeze" is?
[19:05] <azeem> the end of automatic syncs
[19:05] <mok0> right
[19:05] <LtWorf> ok thanks to everybody.. goodbye
[19:06] <mok0> LtWorf: In the beginning of a cycle, there are regular imports of packages from unstable
[19:06] <mok0> Bye :-)
[19:48] <RoAkSoAx> ScottK, ping?
[19:48] <RoAkSoAx> ScottK, could you please take a look to bug #430913
[19:59]  * jdong takes a look
[20:02] <jdong> looks good to me
[20:07] <jdong> RoAkSoAx: sponsored
[20:15] <RoAkSoAx> thanks jdong :)


[02:13] <FloatingGoat> hello?
[03:57] <fisch246> it's nice to know Ubuntu doesn't recycle OPs >.>
[03:58] <fisch246> at least not all the time
[03:58] <fisch246> the fact that the same OPs are in basically every channel concerns me -__-
[03:59] <fisch246> especially when all the OPs in the Ubuntu Community have an extreme distaste for me >.>
[04:00] <fisch246> possibly rww and tonyyarusso are the only OPs i actually get along with
[04:02] <fisch246> non-OP love + easy tongue + willing to stand up for one self + talkative = not a single authority figure will ever respect you
[19:31] <FloatingGoat> hellooooo


[09:27] <maria26> hey guys...anyone knows about a wacom-grafictablett problem in dualmonitor use? Even if i assign my laptopscreen to the tablet, in the mainsettings, the mice is 5cm away from my pen, cause it thinks the whole desktop is my screen..the changed settings are never saved. when i close and open the settings again they are restored. using updatet ubuntu 12.04 on a lenovo x61t.thx4 reading...doubble thx4help :)
[09:34] <popey> maria26, you're probably better off asking in #ubuntu
[09:35] <MrChrisDruif> I agree with popey
[09:35] <maria26> ok...thx
[09:39] <MrChrisDruif> Btw popey, how is the tablet development going?
[09:39] <popey> what tablet development?
[09:43] <MrChrisDruif> Well, getting the software ready for tablets
[09:44] <MrChrisDruif> Or has that become a little "stagnant"?
[09:55] <popey> MrChrisDruif, well, we're just investigating ubuntu on tablets really.


[00:55] <jalcine> Merry Christmas to those who celebrate!
[00:59] <SonikkuAmerica> :)
[02:12] <goaw> hello, I just upgraded my system to 12.10 & the upgrade caused a malfunction in the usage of the language tools. Furthermore I'm now not able to login to my primary user login
[02:12] <goaw> :)
[02:12] <goaw> any helps would be truly appreciated
[02:34] <FloodBotK1> !netsplit
[04:36] <glenrock> is there a setting to control how long a taskbar item flashes when there is new activity in the window?
[09:10] <apb1963_> anyone know how to get plasma desktop weather wallpaper to work?  kubuntu 12.04
[10:53] <sasdani> Hi All! :)
[11:29] <BluesKaj> Hiyas all
[11:38] <user__> привет всем
[11:38] <user__> как можно в проводнике добраться до программ, поставленных через Wine?
[11:39] <user__> Эй, мужики!
[11:42] <BluesKaj> !ru | user__
[11:44] <user__> ah, so it is english channel)
[11:45] <user__> How can i run programs installed using wine?
[11:45] <user__> How can i find them in Nautilus?
[13:00] <dheeraj> How to configure cdma dongle in Ubuntu.?
[13:25] <Guest67317> türkçe bilen varmıdır?
[13:41] <ed765432345> please help, is there another vpn client for kubuntu? the default  one doesnt have the option to reconnect after connection is dropped
[13:42] <lordievader> Good afternoon.
[14:09] <chachan> ed765432345, http://forum.kde.org/viewtopic.php?f=18&t=102188
[14:09] <chachan> hope that helps
[14:53] <amichair> ever since I upgraded KDE to 4.12.0, the panel freezes several times a day (rest of desktop, alt-tab etc. are ok), then after a few minutes it unfreezes and goes back to normal. Is this a known issue?
[15:13] <ice9> when installing kubuntu-desktop on Ubuntu, does it install any kind of codecs?
[15:53] <vmusr> how to enable my bluetooth adapter? I can see it in lsusb, but there's no bluetooth in the OS
[16:07] <ovidiu-florin> vmusr: do you have bluetooth in System Settings?
[16:08] <vmusr> yes, but no adapters - however dmesg and lsusb seem fine
[16:15] <vmusr> also I have proper rfkill output
[16:21] <smurf> hello averybody
[17:04] <rcw2> what are the main differences between running ubuntu on a mac vs pc
[18:26] <abu_sado> is precise not getting the 4.11.4?
[19:49] <jdoles> Which versions of X, the kernel and radeon am I supposed to use together?
[19:49] <jdoles> The combination I am using now doesn't work.
[21:12] <valorie> jdoles: are you using packages as provided?
[21:13] <valorie> via muon or apt-get, aptitude, etc.
[21:13] <skreech_> jdoles: What versions do youhave?
[21:17] <ice9> I can't type with keyboard and window titles disappeared
[21:17] <ice9> also when I open the main menu and click anywhere on the desktop, the menu didn't hide, I have to click on it again
[21:17] <ice9> I installed kubuntu-desktop on ubuntu
[22:00] <skreech_> ice9: Got help?
[22:05] <uBUXUBu> hi
[22:21] <skreech_> HI
[22:21] <skreech_> uBUXUBu: Hello
[22:22]  * uBUXUBu offers skreech_ some pistachios...
[22:22] <skreech_> Thanks
[22:52] <uBUXUBu> does kubuntu offer an application that will take the place of my home phone?
[22:54] <uBUXUBu> i d like to get rid of my phone
[23:00] <valorie> uBUXUBu: there are some SIPP clients, yes
[23:02] <uBUXUBu> can i ditch my mphone
[23:02] <valorie> https://wiki.kubuntu.org/Kubuntu/KubuntuDocs/Software/Internet
[23:03] <valorie> if you find a provider willing to accept your old phone number, sure
[23:04] <valorie> I went the easy way and just bought a vonage box
[23:04] <valorie> hardly any fuss at all from the old phone company
[23:04] <uBUXUBu> what is a vonage box
[23:05] <valorie> and since it's hooked to the cable line through the cable box, it's rarely down
[23:05] <uBUXUBu> so u can make and recieve phone calls right
[23:06] <valorie> http://vonage-info.com/?kw=gvi1+vonage&gclid=CLPEtJaAz7sCFU9ffgodOgkAGg
[23:06] <valorie> commercially available in lots of places
[23:06] <uBUXUBu> is it cheaper
[23:07] <valorie> yes, make and receive phone calls, and they have a free message service as well
[23:08] <valorie> I just didn't want to take the time to set up something and leave a computer on all the time to host it
[23:08] <skreech_> !sip
[23:08] <skreech_> ha
[23:08] <skreech_> valorie: Vonage only works in  America I guess?
[23:09] <valorie> if we still had our own server set up in the back bedroom, we could have gone with ekiga instead, I guess
[23:09] <valorie> skreech_: dunno
[23:09] <valorie> I can make and get international calls
[23:09] <valorie> from the US
[23:10] <valorie> whether people can sign up outside the country, I don't know
[23:11] <valorie> I assume their website says!
[23:11] <skreech_> :-)
[23:11] <valorie> uBUXUBu: yes, quite a bit cheaper
[23:12] <valorie> $10/mo rather than about $30
[23:12] <valorie> I switched when they charged me about $25 for a 2 minute long distance call (which should never have been made in the first place)
[23:13] <valorie> that was the last month/last bill with ma bell
[23:15] <uBUXUBu> so i wonder if i can go to my cable company and do it
[23:16] <valorie> you don't have to tell your cable company unless you want to use their service
[23:16] <valorie> which IMO is more expensive and more sucky
[23:17] <valorie> but we should go to #kubuntu-offtopic for this
[23:17] <valorie> please
[23:17] <valorie> sorry for the off-topic, folks
[23:17] <uBUXUBu> ok ill go to offtopic i need more info im getting ripped off bad
[23:21] <Guest82894> can anyone here help me out with a sound problem i'm having, in windows i can plug my guitar in the audio input and have the sound come out of my speakers, i was wondering if i can do the same in kubuntu, i can't figure out how to do it thanks very much for your time
[23:24] <skreech_> Guest82894: As like a passthrough?
[23:25] <Guest82894> well in windows, there's an option i can select to listen to device and the sound then comes out of my speakes, is there a way to do that in kubuntu
[23:29] <Guest82894> would i need to install jack to get that working
[23:32] <valorie> I think pulseaudio should do that for you
[23:32] <valorie> you might want to install the pulseaudio volume control widget
[23:32] <Guest82894> can you tell me what to do exactly, i'm new to linux and wanting to get away from winblows
[23:33] <valorie> in the tabs there are all kinds of controls
[23:33] <Guest82894> thanks for your help valorie
[23:33] <valorie> well, you should experiment with the settings
[23:33] <valorie> you should be able to do as you wish
[23:33] <Guest82894> thanks very much for your help
[23:35] <valorie> have fun!
[23:40] <skreech_> Yeah I've not done that but I think that would work
[23:42] <Guest82894> i just wee veronix volume control in the widgets oh well, back to winblows i guess, thanks anyway
[23:42] <skreech_> Guest82894: I would guess you can try #pulseaudio
[23:43] <Guest82894> thanks
[23:44] <valorie> veromix seems buggy lately
[23:44] <valorie> the pulseaudio volume control seems to work fine
[23:51] <Guest82894> it's just a bunch of zombies in pulseaudio channel  :)
[23:52] <valorie> Guest82894: it is the day after christmas!
[23:52] <valorie> and boxing day where the most active devel is living
[23:52] <valorie> errr, maybe the morning after by now
[23:52] <Guest82894> true sorry
[23:52] <valorie> ok, going afk
[23:53] <Guest82894> wanna skype valorie
[23:53] <valorie> try again with the pulseaudio volume control widget
[23:53] <valorie> no skype here, sorry
[23:53] <valorie> bye for now
[23:53] <Guest82894> where do i get it
[23:54] <Guest82894> ok found it, happy  boxing day


[00:16] <rs2009> could someone run the ISO build for https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu-unity? (the generated ISO should also be our first completely functional ISO)
[00:16] <rs2009> ^ vorlon
[00:34] <bdmurray> rs2009: vorlon is out for a couple of days
[00:35] <rs2009> bdmurray: ah, wasn't aware of that
[00:35] <bdmurray> let me see what I can do
[00:38] <bdmurray> rs2009: I think I've started the ISO build but its my EOD but I'll come back and look at it
[00:38] <bdmurray> Boy, double buts its really my EOD
[00:49] <sergiodj> hi, can a moderator approve my message to ubuntu-devel-announce, please?
[00:49] <sergiodj> TIA
[01:12] <bdmurray> rs2009: it looks like it built https://cdimage.ubuntu.com/ubuntu-unity/daily-live/20220915/
[01:13] <rs2009> bdmurray: yep, thanks :)
[01:13] <rs2009> just noticed gnome-control-center was getting installed due to a dependency of unity-control-center, so was fixing that
[01:14] <bdmurray> sergiodj: approved
[01:15] <sergiodj> bdmurray: thanks
[01:55] <rs2009> jbicha: was wondering if it would be possible for you to move gnome-control-center from Recommends to Suggests in gnome-online-accounts (u-c-c depends on it, which is resulting in gnome-shell being pulled in)
[09:15] <LocutusOfBorg> mwhudson, FYI I syncd dh-lua, the Debian patch for the same glibc related issue avoids usage of catchsegv, making useless the extra glibc-tools dependency :)
[09:55] <jbicha> rs2009: let me try adding an alternate recommends first
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted mmdebstrap [source] (jammy-proposed) [0.8.4-1ubuntu0.1]
[11:16] -queuebot:#ubuntu-release- Unapproved: qreator (jammy-proposed/universe) [16.06.1-7 => 16.06.1-7ubuntu1] (no packageset)
[12:42] <seb128> could someone from release review https://code.launchpad.net/~seb128/britney/+git/britney/+merge/429834 ?
[12:43] -queuebot:#ubuntu-release- Unapproved: nfs-utils (jammy-proposed/main) [1:2.6.1-1ubuntu1 => 1:2.6.1-1ubuntu1.1] (core, i386-whitelist)
[13:53] <tumbleweed> seb128: merged
[13:53] <seb128> tumbleweed, thanks!
[14:11] -queuebot:#ubuntu-release- Unapproved: sosreport (bionic-proposed/main) [4.3-1ubuntu<IP_ADDRESS> => 4.4-1ubuntu<IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[14:11] -queuebot:#ubuntu-release- Unapproved: sosreport (focal-proposed/main) [4.3-1ubuntu<IP_ADDRESS> => 4.4-1ubuntu<IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[14:43] <Eickmeyer> sil2100: Hi! Left a comment for you! https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/comments/7
[15:01] <sil2100> Eickmeyer: thanks! Will try to take a look and follow up today, but ugh
[15:01] <sil2100> Busy busy
[15:13] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (focal-backports) [1:7.3.6-0ubuntu<IP_ADDRESS>~bpo20.04.1]
[15:20] <ricotz> tumbleweed, thank you
[15:57] <xnox> sil2100:  can we release gcc-12 gcc-12-cross gcc-12-cross-ports SRU from jammy-proposed to jammy-updates? it is non-default kernel and nothing uses it yet in jammy. (cc: doko) or is it waiting on something? (archive rebuild?)
[16:00] <sil2100> xnox: yep! I think it's fine! I simply had no cycles!
[16:01] <xnox> sil2100:  it would help us a lot; as gcc-12 in jammy-release is quite an old snapshot.
[16:02] <sil2100> Ok, let me try looking at those and releasing in the next minutes
[16:15] -queuebot:#ubuntu-release- New: accepted ntirpc [amd64] (kinetic-proposed) [4.0-2]
[16:15] -queuebot:#ubuntu-release- New: accepted ntirpc [armhf] (kinetic-proposed) [4.0-2]
[16:15] -queuebot:#ubuntu-release- New: accepted ntirpc [riscv64] (kinetic-proposed) [4.0-2]
[16:15] -queuebot:#ubuntu-release- New: accepted ntirpc [arm64] (kinetic-proposed) [4.0-2]
[16:15] -queuebot:#ubuntu-release- New: accepted ntirpc [s390x] (kinetic-proposed) [4.0-2]
[16:15] -queuebot:#ubuntu-release- New: accepted ntirpc [ppc64el] (kinetic-proposed) [4.0-2]
[16:24] <sil2100> xnox: hhmmm, so the gcc-12 bug is not verified, but maybe it could be released as-is - doko already did an archive rebuild with the gcc-12 binaries IIUC
[16:24] <sil2100> ginggs: do you know by any chance if there's some additional testing that doko wanted to do for the gcc-12 jammy SRUs still?
[16:27] <sil2100> I usually considered the test rebuild + autopkgtest + manual test as sufficient
[16:27] <ginggs> sil2100: no more tests needed, they are good to go!
[16:34] <sil2100> ginggs: thanks!
[16:35] <sil2100> Okay, I'm considering gcc-12* verified, releasing those
[16:38] <ricotz> hello ubuntu-release, libreoffice 7.3.6 in jammy-proposed is good to transition to -updates :)
[17:57] <Eickmeyer> sil2100: I'm fearing the worst for audacity. :(
[18:02] <dbungert> Eickmeyer: looking
[18:02] <Eickmeyer[m]> dbungert: Thanks
[18:26] <Eickmeyer> dbungert: It's in my PPA, do you need a link?
[18:28] <dbungert> Eickmeyer: I tracked it down, I'm taking a look at what the compiler is mad about.  I fixed the first build failure and am working on the next one done the line.
[18:28] <Eickmeyer> dbungert: Awesome, thanks. I don't know c++ well enough to know what is going on there, so I appreciate it.
[18:55] -queuebot:#ubuntu-release- Unapproved: autopkgtest (jammy-proposed/main) [5.20 => 5.20ubuntu1] (core)
[19:44] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.4.2-0ubuntu3 => 2:16.4.2-0ubuntu4] (openstack, ubuntu-server)
[21:43] -queuebot:#ubuntu-release- New source: plasma-distro-release-notifier (jammy-proposed/primary) [20220915-0ubuntu<IP_ADDRESS>]
[21:46] -queuebot:#ubuntu-release- New source: plasma-distro-release-notifier (focal-proposed/primary) [20220915-0ubuntu<IP_ADDRESS>]
[22:31] -queuebot:#ubuntu-release- New binary: ubuntu-settings [amd64] (kinetic-proposed/main) [22.10.1] (ubuntu-desktop)


[00:01] <Chipaca> tedg: yes, i did get the 'no qt installation'
[00:01] <Chipaca> tedg: you're using the qtchooser
[00:01] <Chipaca> tedg: use qmlscene directly
[00:01] <Chipaca> tedg: or, put the right qt config in your xdg config dir
[00:02] <Chipaca> tedg: poke me if you want the latter
[03:12] <tedg> Chipaca, Ah, I got it together. I have the qml plugin building the Qt configuration now.