[00:50] <phillw> Hello good people, is there someone about who could look into bug 964705 ? It has fix released by others, could it be 'cherry picked' for ubuntu?
[01:03] <sarnold> phillw: it might be worth pointing out the specific patches used to fix the problem
[01:04] <sarnold> (fwiw, the bug report comments just seem to be a pile of ranting about various things; it'd probably be worth explaining what specific feature / bug those patches address..)
[01:05] <phillw> sarnold: that is beyond my knowledge... it 'seems' ubuntu' do not rate it highly, but others have rated it, and more importantly have a fix released?
[01:06] <phillw> sarnold: https://bugzilla.novell.com/show_bug.cgi?id=731812
[01:07] <phillw> Ahh... I've seen this bug elsewhere.. it is polkit and sudo gremlin
[01:10] <phillw> yeah, there are several bugs open. All roads lead to Rome. polkit.
[01:12] <sarnold> wow, that novell bugreport is fun reading.
[01:15] <phillw> yup, back to polkit... which is an issue with other bugs I see cross my mailing list.
[01:37] <phillw> sarnold: having had fun reading... your thoughts?
[01:38] <sarnold> phillw: no ideas, I couldn't figure out what might be applicable to ubuntu vs applicable to world at large.. my eyes glaze over when polkit and consolekit and soforth get involved.
[01:41] <phillw> yeah, I know what you mean. I see 'chatter' about using polkit Vs looking up admin on the system... I do feel we need someone from 'above' to sort this out, as it would squish lots of different bugs.
[01:46] <phillw> Thanks for you time, I'll try to grab someone to see where the rules of polkit is going.
[01:48] <sarnold> agreed completely re "someone from above"
[02:02] <Bluefoxicy> huh apt-cacher is interesting
[02:03] <Bluefoxicy> here's a question:  why aren't there a few main mirrors, with the rest being cachers that don't bother downloading packages unless someone tries to get it from that mirror?
[02:06] <sarnold> a few thoughts: (a) if the main repo goes down and a cache doesn't yet have the package, it must either return failure or get the package from a peer. that's complicated. (b) how often should the caches check if a newer package is available from the main repos? pushing packages as they change is probably less traffic overall than having an expiry scheme
[02:06] <Bluefoxicy> uh
[02:06] <Bluefoxicy> why would it check for a new version?
[02:06] <Bluefoxicy> don't you bump the version number in the file name?
[02:07] <sarnold> .. how would the clients know to request the newer version?
[02:07] <Bluefoxicy> because you push updates to the Packages.gz file
[09:08] <dkessel> i have a question. i just tried: bzr branch ubuntu:webkit
[09:08] <dkessel> and it says: Packaging branch status: OUT-OF-DATE
[09:09] <dkessel> i have checked the package import status site and there is a bug for it. is there anything i can do to get the current version?
[09:10] <dkessel> bug: 653810
[09:54] <infinity> dkessel: If you want the current version, "pull-lp-source webkit" (from the ubuntu-dev-tools package) or just "apt-get source webkit" to get the source that matches your currently installation.
[09:54] <infinity> s/currently/current/
[10:03] <dkessel> infinity: thanks, pull-lp-source did it
[10:08] <dkessel> infinity: if i do any changes and upload that as a personal bzr branch on launchpad - would a ubuntu developer have any problems merging the changes into the current version?
[10:09] <infinity> You'd likely want to talk to Laney or micahg.  Depends on what the changes are, and why.
[10:09] <infinity> (What are you changing?)
[10:12] <dkessel> I will try to get a simple compile/link/run autopkgtest to work for the package libwebkitgtk-3.0-dev . normally i do this using bzr to create a branch of the current version, commiting my changes and then the changes get reviewed
[10:13] <infinity> Oh, sure, I imagine an autopkgtest case would be something we'd be interested in merging.  You could just file a bug with a diff attached, there's no reason it needs to be a bzr branch.
[10:13] <infinity> (And, in fact, a branch with no sane parent is just a pain to merge anyway)
[10:14] <dkessel> oh ok - i will do it this way then
[10:15] <dkessel> inifinity: thanks and bye
[10:27] <Laney> dkessel: You should look into running the gtk tests too (Tools/Scripts/run-gtk-tests)
[10:27]  * Laney disappears for the rest of the day with a flourish
[10:59] <gotwig> cjwatson, hey there
[11:01] <cjwatson> gotwig: on vacation.  occasionally happen to look at irc but I'm not going to look at any bugs 'til the new year.  sorry.
[11:01] <gotwig> cjwatson, no problem. Have a nice time :D
[11:22] <chilicuil> hi, good morning, sry to bother, what's the correct behaviour in case I want to change a line to fix a bug which was introduced by a patch living in /debian?, should I edit the patch file or provide another?
[11:24] <infinity> chilicuil: If the patch is something like a pull from an upstream VCS, stacking another on top (and submitting it upstream) is sane.
[11:24] <infinity> chilicuil: If it's a local patch, then just fixing it makes more sense than appending to it.
[11:25] <chilicuil> infinity: it was introduced by the debian maintainer, so I suppose that qualifies as a local change, right?
[11:25] <infinity> chilicuil: Yeah, though you'd also want to forward your fix to Debian.
[11:25] <infinity> (which patch is this?)
[11:26] <chilicuil> infinity: yep, it's just that the package in debian is orphaned, however I'll try, it's a little problem in html2text, #586279
[11:26] <chilicuil> bug #586279
[11:28] <infinity> chilicuil: Ahh, fair enough.  If it's orphaned, want to bug me about it $later (or provide a patch and /msg me about it), and I'll fix it in Debian with a QA upload and sync to Ubuntu?
[11:28] <infinity> chilicuil: (I only request later because I'm heading to bed)
[11:28] <chilicuil> infinity: sure, I'll do it, thanks
[11:53] <ricotz> infinity, hi :), any news on eglibc?
[12:04] <chilicuil> he went to sleep half an hour ago ricotz =)
[12:12] <ricotz> chilicuil, ah, i see
[16:08] <pigna_colada> hello :(
[16:08] <pigna_colada> I just downloaded this ubuntu 12.10 cd
[16:09] <pigna_colada> and booted my laptop using the "try" selection
[16:09] <pigna_colada> but now it asks for a username
[16:09] <pigna_colada> and password
[16:09] <pigna_colada> what do i have to put??
[16:20] <penguin42> pigna_colada: Please try #ubuntu for general help
[16:23] <pigna_colada> thanks
[21:54] <slangasek> mlankhorst: hi, I see you're involved in maintaining the wine1.5 packages in the ~ubuntu-wine ppa - are there any plans for this to land in raring?
[21:55] <slangasek> mlankhorst: also, do you know if anyone's working on audio device enumeration in wine using the pulse driver?
[21:57] <mlankhorst> I maintain winepulse
[21:57] <mlankhorst> and ask next year please
[21:58] <slangasek> heh :)
[21:58] <slangasek> mlankhorst: but I have an app I want to use it for over vacation, and time to spend hacking wine... if I wait until next year, it might be too late :-)
[21:59] <mlankhorst> I maintain winepulse in ubuntu-wine
[22:02] <paultag> jbicha: poke
[22:03] <paultag> jbicha: sorry about that bug, but I'm a bit swaped -- the issue stems from SFTP not meaning a user account on the system (or even a $HOME), so using "~" in SFTP is a bit odd
[22:03] <paultag> jbicha: if you find out what legacy dput does, I'd be happy to add a shim, but parimiko has no idea what's going on otherwise
[22:04] <paultag> one idea we were throwing around was just ditching the "~", which seems like it'll do the trick (but I'm not sure)
[22:05] <mlankhorst> slangasek: so wine is actually ok, just dont ask about upstream, dont want to work :P
[22:17] <jbicha> paultag: thanks, it's fairly easy for me to switch back to classic dput when needed
[22:20] <paultag> jbicha: righto. In the meantime, patches welcome, otherwise it's on my queue for some downtime during my vacation
[22:21] <paultag> or not :)
[22:25] <paultag> 17:20 < paultag> jbicha: righto. In the meantime, patches welcome, otherwise it's on my queue for some downtime during my vacation
[22:25] <paultag> jbicha: in case you missed it :)
[22:25] <paultag> I'll have to take a closer look, sorry for the bumpy ride, but this was something we were trying to work out for a while now without putting it on the fire