[03:38] <openstackgerrit> Joshua Harlow proposed stackforge/cloud-init: Bring over the 'url_helper' module from bzr  https://review.openstack.org/170242
[10:08] <Odd_Bloke> smoser: Do you have any thoughts on moving cloud-init 0.7.x development to git in Launchpad?
[12:05] <openstackgerrit> Claudiu Popa proposed stackforge/cloud-init: Add the data source base classes and the HTTP OpenStack implementation  https://review.openstack.org/188327
[12:50] <smoser> i'm not really opposed to that.
[12:51] <openstackgerrit> Claudiu Popa proposed stackforge/cloud-init: Add the layout for a couple of Windows OS utils, especially networking  https://review.openstack.org/188361
[12:51] <openstackgerrit> Claudiu Popa proposed stackforge/cloud-init: Add the data source base classes and the HTTP OpenStack implementation  https://review.openstack.org/188327
[12:53] <Odd_Bloke> harlowja_: Do you know if we can get the bot to use notices rather than messages?
[13:16] <claudiupopa> hey guys. Short question, what exactly is cloudinit.sources.DataSource.ds_cfg?
[13:24] <Odd_Bloke> claudiupopa: It's generally used for configuring things that are specific to a datasource.
[13:24] <Odd_Bloke> claudiupopa: See Azure, for example.
[13:25] <Odd_Bloke> claudiupopa: Azure requires some DHCP hijinks on first boot, which are configured under the hostname_bounce key.
[13:25] <Odd_Bloke> It wouldn't make sense to have that for any other data source.
[13:25] <claudiupopa> it's taken from a config file or something?
[13:26] <Odd_Bloke> claudiupopa: I'm less sure about that (I've only ever really played with the built-in config for the Azure source), but line 70 of cloudinit/sources/__init__.py suggests that is the case.
[13:27] <Odd_Bloke> Presumably cloud.cfg.
[14:20] <openstackgerrit> Claudiu Popa proposed stackforge/cloud-init: Add the layout for a couple of Windows OS utils, especially networking  https://review.openstack.org/188361
[14:20] <openstackgerrit> Claudiu Popa proposed stackforge/cloud-init: Add the data source base classes and the HTTP OpenStack implementation  https://review.openstack.org/188327
[17:09] <harlowja_> Odd_Bloke don't think so, but not sure (as for notices rather than messages)
[17:10] <harlowja_> Odd_Bloke https://github.com/openstack-infra/gerritbot is the code for it
[17:11] <harlowja_> i've modified it somewhat previously (i have a internal version running on internal y! irc that notifies whenever a yahoo employee puts a review up)


[17:00] <qense> Hello, I'm Sense Hofstede -- https://launchpad.net/~qense -- and the next hour I'll be telling you a bit about Adopt-an-Upstream.
[17:00] <qense> Hello, I'm Sense Hofstede -- https://launchpad.net/~qense -- and the next hour I'll be telling you a bit about Adopt-an-Upstream.
[17:01] <qense> A notice for those testing Ubuntu Lucid: please don't click links in XChat (GNOME), but copy them to your browser instead; apparently clicking links makes XChat crash.
[17:01] <qense> I know from experience!
[17:02] <qense> Today's session is about Adopt-an-Upstream. But what is Adopt-an-Upstream?
[17:03] <qense> We all know there are different ways of contributing to a distribution. You can cherry pick work items you like, or you can choose to focus on a specific subset of the tasks.
[17:04] <qense> Everyone has got a different best approach. However, when you focus on something you like you are more productive.
[17:04] <qense> Adopt-an-Upstream is just this: you focus on a project you like and make sure it rocks in Ubuntu!
[17:07] <qense> Now, it is quite some work to focus on all facets of a project's existence in Ubuntu -- I'd say you're no longer focusing then, but it depends on the amount of time you're willing to spend on Ubuntu -- so you split it up in different tasks.
[17:07] <qense> When you've chosen a project to adopt the next thing you need to do is making up your mind on what you're going to work on.
[17:08] <qense> Because adoption of an upstream encompasses the following points:
[17:08] <qense> Communication
[17:09] <qense> both communicating Ubuntu schedules and announcements of importance to the upstream project to the upstream project, and communicating the project's schedules and announcement to the developers in Ubuntu that should know about it.
[17:09] <qense> Bug triaging
[17:09] <qense> or Adopt-a-Package
[17:09] <qense> You work on triaging -- processing -- the bugs reported against the adopted project. More on this later.
[17:10] <qense> Packaging
[17:10] <qense> Making sure the latest version of the package is available in Ubuntu, either by merging or syncing it from Debian, or by packaging it yourself.
[17:10] <qense> Forwarding patches upstream
[17:11] <qense> For some bugs there are fixes available that Ubuntu maintains as patches. It's the best for everyone if those patches are also sent upstream so they can be included in the code.
[17:11] <qense> and finally
[17:12] <qense> Representing the project in Ubuntu and Ubuntu upstream
[17:12] <qense> This means being the contact person of that project in Ubuntu and the Ubuntu contact person upstream.
[17:14] <qense> You can also organise a BugDay for the project -- more information about that at the wiki: https://wiki.ubuntu.com/UbuntuBugDay
[17:14] <qense> That sure are many things to do!
[17:15] <qense> It can happen that someone else is already working on one or more of the tasks I mentioned.
[17:16] <qense> In this case it would be best to first talk to that person to make sure you're not going to do duplicate work. And working together is of course much more efficient and productive than working alongside each other!
[17:16] <qense> Some people have formed a team for adopting a project.
[17:17] <qense> An example of this is the MozillaTeam: https://wiki.ubuntu.com/MozillaTeam
[17:18] <qense> Although that team was created before Adopt-an-Upstream was started it is still a very good example for people that actually want to adopt a package.
[17:18] <qense> Any questions so far?
[17:20] <qense> OK, lets take a closer look at connecting with the upstream.
[17:21] <qense> Because that's the most important thing of it all and that's what Adopt-an-UPSTREAM is actually about.
[17:23] <qense> First of all, please keep in mind that the upstreams are very important to Ubuntu -- without them we'd barely have anything in the repositories and nothing to run what we would have -- so please try treat them respectfully.
[17:23] <qense> Although I'm sure most of you will. :)
[17:24] <qense> There are a few actions you can take to make sure you don't miss anything you need to know.
[17:25] <qense> First of all, if you're often on IRC, it is strongly advised to join the project's channel as well; this makes it easier for the upstream developers to contact you when they need to ask you something and allows you to quickly ask them your questions.
[17:26] <qense> It's also a good idea to subscribe to the project's mailing list, or -- when there are multiple -- to the list that you'll most likely find the discussions on you need/want to follow.
[17:26] <qense> Some projects also have mailing lists that are only used for sending release announcements, often with the release notes.
[17:27] <qense> This is a valuable source of information and something you should pass on to the affected Ubuntu developers if it is interesting for Ubuntu.
[17:28] <qense> If the upstream project chooses to make a radical change you should warn Ubuntu on time.
[17:29] <qense> Example given: during the Ubuntu Developer Summit a collaborative text editor called 'Gobby' is used. A release or so ago, before the UDS for Ubuntu Lucid, a new version was released which changed the protocol.
[17:30] <qense> In order to make sure that everyone, even those that don't use the latest release of Ubuntu, can participate Ubuntu decided to stick to the old protocol.
[17:30] <qense> The new release of Gobby was packaged separately and the previous Gobby release was left in the repositories.
[17:31] <qense> This is something upstream adopters should work on.
[17:31] <qense> if it affects their project.
[17:32] <qense> Of course, when large changes are made in Ubuntu -- like the Application Indicator that were added to Ubuntu Lucid -- it is the task of the adopter to notify upstream and cooperate with them in adding support for it to the project.
[17:33] <qense> This could be done by helping an upstream developers by pointing her or him to the right documentation, wiki pages, mailing lists and IRC channels, but also by helping an Ubuntu contributor with writing a patch and making sure that patch gets sent upstream.
[17:34] <qense> If you've got a question, please ask!
[17:36] <qense> What's also an important task of making sure no data valuable to the upstream project remains locked away in Ubuntu is forwarding bugs upstream.
[17:36] <qense> This brings us to our next stop: Adopt-a-Package.
[17:37] <qense> This is actually a bit separate from Adopt-an-Upstream because of the amount of work required for keeping the bugs clean and tidy.
[17:38] <qense> General information about Adopt-an-Upstream page can be found at https://wiki.ubuntu.com/Upstream/Adopt
[17:38] <qense> However, Adopt-a-Package has a wiki page of its own, at https://wiki.ubuntu.com/BugSquad/AdoptPackage
[17:39] <qense> As you can see on that page there are already quite a few packages adopted by bug triagers that aren't adopted 'in general'.
[17:40] <qense> This is possible as well, and something you should check when you decide to adopt an upstream; if the bugs are already adopted, please profit from this and try to cooperate as much as possible.
[17:40] <qense> Just as with Adopt-an-Upstream you can also divide the tasks for adopting the bugs.
[17:41] <qense> At https://wiki.ubuntu.com/BugSquad/AdoptionTeam you can see an example of an 'Adoption Team', a group of people working on the bugs of a specific package.
[17:42] <qense> When dealing with projects that have many bugs reported against them on Launchpad it's often wise to divide the tasks and let one go through the newly reported bugs, whereas the other is responsible for forwarding bugs upstream.
[17:43] <ClassBot> hggdh asked: do I need to be a developer to adopt a package? Or an upstream? How much experience should I have, and in what?
[17:44] <qense> Adopting an upstream isn't something you should take lightly. Adopting an upstream means you want to invest time in the project and people will start to see you as the contact person for that project in Ubuntu, and vice-versa upstream.
[17:44] <qense> Therefore it's wise to only adopt an upstream after you've gained experience, both with the tasks you want to work on and with the upstream in general.
[17:46] <qense> I would strongly suggest to gain some experience with bug triaging before adopting a project's bugs, just as it is wise to learn how to package before taking up the responsibility for packaging a project.
[17:46] <qense> Respectively a membership of Ubuntu Bug Control and the Ubuntu MOTU is a big plus when doing those tasks.
[17:47] <qense> It is also good to take into account that every project has got its own way.
[17:47] <qense> Before you start you should learn how the project works, what its habits are, its customs.
[17:48] <qense> To loosely  quote the wiki page: "It's easier for an individual to adapt to a group than for a group to adapt to one individual."
[17:48] <ClassBot> enli asked: How do you exactly inform an up-steam and send bug fixes? (bug trackers i guess?) If forwarding patches, are there conventions to be followed for the topic title in upsteams bug tracker?
[17:49] <qense> enli: Nice question.
[17:49] <qense> The conventions differ per project.
[17:49] <qense> However, bugs and patches should be reported in the upstream bug tracker indeed.
[17:50] <qense> Patches should be attached to the bug report of the issue they're fixing.
[17:50] <qense> If the issue the patch is fixing isn't reported yet upstream, just report that bug and say someone provided a fix in Ubuntu and attach that patch.
[17:51] <qense> A good place to look for the conventions is the wiki of the upstream project, if they have any.
[17:51] <qense> GNOME has got its bug tracker at http://bugzilla.gnome.org/ and its developers wiki at http://live.gnome.org/
[17:51] <qense> When you've gather some information it's a good idea to document it on the Ubuntu wiki.
[17:52] <qense> This way you make sure Ubuntu and the upstream project won't suffer too much when you (suddenly) leave -- the so-called "hit by the bus" problem -- and you make it easier for other people to help or even just contribute one patch or bug report upstream.
[17:53] <qense> You should add a link to this information at https://wiki.ubuntu.com/Upstream/Workspaces
[17:53] <qense> You can find there is already one workspace for Banshee
[17:53] <qense> As you can see it uses this template: https://wiki.ubuntu.com/Upstream/AdoptingTemplate
[17:54] <qense> Please use that template when creating your project's workspace so readers can quickly find the information they were looking for.
[17:54] <qense> You could also add e.g. an item about the conventions for bug titles of forwarded patches here.
[17:55] <qense> If you take a look at Banshee's workspace you can see that it includes many information already https://wiki.ubuntu.com/Upstream/Banshee
[17:56] <qense> It lists to the main website, the most important mailing list for the adopters -- to which you subscribed, of course! -- the IRC channel and the location of the source code.
[17:56] <qense> But it also links to certain pages in Launchpad, like a PPA, bug reports and the status of the package in Debian.
[17:57] <qense> This is also what adopting an upstream is about: making information about the project accessible for Ubuntu contributors.
[17:57] <qense> And, of course, making information about Ubuntu accessible to the upstream project.
[17:57] <qense> With that I would like to end this session. Are there any questions?
[17:59] <qense> No? OK, in that case, thank you for attending. If you've got any questions about Adopt-an-Upstream or Adopt-a-Package or if you want to adopt an upstream or a package, please don't hesitate to ping either me or jcastro in #ubuntu-bugs or #ubuntu-devel
[17:59] <jcastro> or just send me a mail at<EMAIL_ADDRESS>[17:59]  * jcastro claps! Good job qense!
[17:59]  * qense bows


[02:04] <HFSPLUS> phunyguy, hi
[02:04] <HFSPLUS> where can i download the ubuntu+1 iso?
[09:44] <lordievader> Good morning.
[09:46] <elfy> hi lordievader
[09:46] <lordievader> Hey elfy, how are you?
[09:46] <elfy> good thanks
[09:46] <elfy> mostly - managed to pick up a cough the last week :p
[09:47] <elfy> lordievader: and how are you?
[09:48] <lordievader> Meh, allright. Trying to figure out how I can get GCC compiled correctly.
[09:50] <elfy> :)
[10:13] <wolfheart> hello I am running Ubuntu 15.04 and I was wondering how do I install oracle java 7 please ?
[10:13] <lordievader> wolfheart: What do you run into?
[10:16] <wolfheart> lordievader : I get a 404 when trying to use the webup8date ppa
[10:17] <wolfheart> webupd8team *
[10:18] <lordievader> wolfheart: http://java.com/en/download/manual.jsp?locale=en
[10:41] <wolfheart> lordievader : any idea how I enable java for firefox please ?
[10:41] <wolfheart> as from what I can tell java is installed :- java -version
[10:41] <wolfheart> java version "1.7.0_65"
[10:41] <wolfheart> OpenJDK Runtime Environment (IcedTea 2.5.3) (7u71-2.5.3-1)
[10:41] <wolfheart> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
[10:45] <lordievader> wolfheart: http://askubuntu.com/questions/354361/how-to-install-java-plugin-in-firefox
[10:45] <lordievader> wolfheart: I'm starting to doubt if it is a good idea that you are running a development version, if I may be so honest.
[10:47] <wolfheart> lordievader : ok ty


[00:46] <bluesabre> flocculant: actually, indicator-sound also doesn't listen for new playlists, so will probably revisit this later :)
[06:06] <flocculant> Unit193: just go ahead :)
[06:06] <Unit193> :(
[06:13] <flocculant> ha ha
[06:13] <flocculant> not even sure what you're talking about - so even better from my point of view :D
[06:14] <Unit193> Xubuntu Core 17.10 release.
[06:15] <flocculant> oh right - yea go ahead, just don't mention the tracker
[06:15] <flocculant> cos it's not there
[14:55] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: thunarx-python 0.4.0 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-thunarx-python-0-4-0-released-tp50153.html (by Adam Plumb-2)
[21:42] <flocculant> bluesabre: perhaps I have one of those git things going on - but can't see anything playlisty at all ...
[22:54] <Unit193> bluesabre: https://packages.qa.debian.org/d/debian-policy/news/20171130T224907Z.html
[23:20] <Unit193> slickslickthequick: I did a once over on both ISOs, they boot to live and have fully functional networking.


[00:00] <apachelogger> LaserJock: rc1
[00:00] <apachelogger> coming up in about 2 days
[00:02] <LaserJock> apachelogger: I see a bzr revisioned tagged as 4.1.96-0ubuntu1, is that pre-emptive?
[00:03] <apachelogger> LaserJock: KDE releases the tarballs one week before release to packagers for additional QA, build checks and binary preparation
[00:05] <LaserJock> interesting
[00:05] <LaserJock> is it a public download but they don't announce it widely?
[00:05] <LaserJock> or do thet send them in the mail :-)
[00:06] <apachelogger> LaserJock: packagers get direct access to the internal KDE ftp server, only once the appropriate directory is made world readable the public ftp server can sync it
[00:07] <apachelogger> usually there are some modifications being done, or important last minute bug fixes that didn't make it in before tarball creation
[00:07] <apachelogger> not many, but it happens
[00:07] <LaserJock> right
[00:08] <LaserJock> do they do that even for Betas?
[00:09] <apachelogger> yep, IMHO it makes our lives easier since we have a good amount of time to prepare packages and deploy them at the same time KDE publishes the source
[00:09] <apachelogger> also makes the users happier I suppose :)
[00:10] <JontheEchidna> unless we're a week and a half late anyways, of course :P
[00:10] <apachelogger> not often, but it happens :P
[00:11] <apachelogger> that should also improve if/when we get a server where every ninja has access
[00:12] <LaserJock> so can you not upload the packages untill KDE officially releases the tarball
[00:12] <ScottK> Except when we do.
[00:12] <JontheEchidna> it is very strongly suggested that we don't, since fixes can be made at the last moment
[00:12] <ScottK> Debian uploaded 4.1.4 and it doesn't release until Monday.
[00:12] <ScottK> Monday, right?
[00:13] <apachelogger> depends on the timezone
[00:13] <apachelogger> Tue UTC
[00:13] <ScottK> Ah.
[00:13] <ScottK> Friday in .au.
[00:13] <ScottK> ;-)
[00:13] <apachelogger> lol
[00:13] <ScottK> Quassel git snapshot test building now.
[00:14] <apachelogger> LaserJock: we upload before the embargo ends to meet our own release schedule for example
[00:14] <LaserJock> ok, so if only a couple people in Kubuntu have access to the tarballs does it make it harder to collaborate on getting the packages ready?
[00:14] <ScottK> apachelogger: In KDE the quassel notifications only work if focus grabbing protection is disabled.  I'm wondering if we should make that the default?
[00:15] <ScottK> LaserJock: We have a process ....
[00:15] <JontheEchidna> LaserJock: apachelogger mirrors them on a non-publicly-disclosed-but-accessible-to-those-who-know server
[00:16] <LaserJock> ok, makes sense
[00:16] <apachelogger> you have no idea... in june I did a release on my own because Riddell was busy and I guess Riddell did pretty much the same for every release before
[00:17] <ScottK> Then suddenly he was in charge.
[00:17] <ScottK> Which was funny because he wasn't core-dev then.
[00:19]  * apachelogger certainly got a lot of the core-dev experience through being in charge though
[00:19] <LaserJock> yes, I can imagine
[00:20] <apachelogger> also we have come a long way, we started off by downloading stuff manually, now we just call a couple of scripts, do some changes and watch pbuilder build ;-)
[00:21] <nixternal> apachelogger: and you documented all of this on the wiki right? :p
[00:22] <ScottK> nixternal: You saw my reply to his latest proposal, right?
[00:22] <apachelogger> nixternal: actually I did, it's just not public :P
[00:22] <nixternal> hehe
[00:22] <nixternal> ScottK: yup :)
[00:23] <nixternal> I can haz wikipage or something
[00:23] <ScottK> Yep.
[00:23] <nixternal> I was going to respond with the same thing :)
[00:23] <nixternal> hrmm
[00:23]  * apachelogger will write something up once he is done with .96 reviews
[00:23] <ScottK> lolspeak and everything?
[00:24] <apachelogger> I was thinking about writing it in whitespace :P
[00:24] <apachelogger> also, it's actually all pretty straight forward if you know what all the scripts are doing ;P
[00:24] <JontheEchidna> black magic otherwise
[00:24] <JontheEchidna> "ZOMG! It makes teh packagez!"
[00:25]  * ScottK hands https://launchpad.net/ubuntu/hardy/i386/python-stepic/0.3-1 for his documentation project.
[00:28]  * ScottK tries to remember where to push the packaging branch for quassel ....
[00:29] <ScottK> Found it.
[00:33] <ScottK> Sput: It built and the depends are good now.  Thanks.
[00:33]  * ScottK tests....
[00:36] <ScottK> Note to self: Build for the release you're running.
[00:36] <Hobbsee> hah
[00:36] <Hobbsee> always a help
[01:01] <vorian> ScottK: ok, what version of mysqyl does amarok need? the ones i keep plugging in are failing in pbuilder
[01:01] <ScottK> 5.1
[01:01] <vorian> yes
[01:01] <apachelogger> JontheEchidna: trying resumes here
[01:02] <JontheEchidna> apachelogger: kquitapp plasma && plasma now?
[01:02] <ScottK> vorian: apachelogger knows the details.
[01:02] <apachelogger> JontheEchidna: yus
[01:02]  * vorian looks to apachelogger
[01:02] <vorian> again
[01:02] <apachelogger> vorian: more information required
[01:03] <vorian> remeber earlier today, i showed you the pbuilder failuer with mysql?
[01:03] <apachelogger> vorian: no universe?
[01:03] <vorian> i have universe
[01:03] <JontheEchidna> apachelogger: it wasn't default but it shows up now
[01:03] <apachelogger> vorian: post a complete build log then
[01:04] <apachelogger> JontheEchidna: ok, need a strace now
[01:04] <vorian> pfft
[01:04] <apachelogger> technically system.kdeglobals should override kdeglobals
[01:04]  * ScottK returns with his 45.0 ounce/1275.8gram bag of Peanut M&Ms.
[01:05] <JontheEchidna> apachelogger: what command?
[01:05] <JontheEchidna> nvm
[01:05] <apachelogger> strace plasma --nofork > ~/plasma-strace 2>&1
[01:07] <JontheEchidna> big file
[01:07] <apachelogger> gzip and send
[01:08] <JontheEchidna> oh, only line-wise though
[01:08] <ScottK-laptop> OK.  Here on the quassel git snapshot now.
[01:09]  * JontheEchidna uses signature volia misspelling
[01:09] <JontheEchidna> apachelogger: sent
[01:12] <apachelogger> ah
[01:12] <apachelogger> another wrong path
[01:12] <apachelogger> JontheEchidna: change your wallpaper to something else
[01:12]  * JontheEchidna changes to KDE 4.0 default
[01:12] <JontheEchidna> now restart plasma?
[01:13] <apachelogger> JontheEchidna: yah, best make sure that plasmarc-applets applied it
[01:14] <ScottK-desktop> ScottK-laptop: Hey.  This is a test to see if notifications work.
[01:15] <JontheEchidna> still no snow :(
[01:15] <apachelogger> JontheEchidna: nah, you need a new package
[01:15] <apachelogger> JontheEchidna: same url
[01:15] <apachelogger> then restart plasma and you should have snow
[01:15] <apachelogger> with a bit of luck at least
[01:15] <JontheEchidna> oh
[01:17] <JontheEchidna> no luck here
[01:17] <apachelogger> bleh
[01:18] <apachelogger> JontheEchidna: strace again please
[01:18]  * apachelogger reinstalls his jaunty vm to try for himself
[01:21] <JontheEchidna> apachelogger: sent
[01:23] <apachelogger> hm
[01:23] <apachelogger> are you sure you upgraded the package?
[01:24] <JontheEchidna> yes, wget, dpkg
[01:25] <JontheEchidna> oh, unless wget tried to be smart
[01:25] <JontheEchidna> and renamed the deb
[01:25] <JontheEchidna> :/
[01:25] <apachelogger> ^_^
[01:26] <JontheEchidna> still no snow, though
[01:26] <apachelogger> JontheEchidna: strace :P
[01:27] <apachelogger> ah well
[01:27] <apachelogger> JontheEchidna: grep the strace for /usr/share/kubuntu-default-settings/kde4-profile/default/share/config/system.kdeglobals
[01:27] <apachelogger> it shouldn't say (No such file or directory)
[01:29] <JontheEchidna> apachelogger: http://paste.ubuntu.com/103347/
[01:31] <apachelogger> JontheEchidna: grep for wallpaper-of-the-month-profile
[01:31] <JontheEchidna> nothing
[01:31] <vorian> http://machine-crusade.net/kubuntu-devel.html
[01:32]  * vorian retries amarok
[01:33] <apachelogger> hm, apparently I am speaking a lot
[01:33] <apachelogger> JontheEchidna: that is no good
[01:33] <apachelogger> JontheEchidna: anyway, thanks
[01:33] <JontheEchidna> yw
[01:33]  * apachelogger will have to look into this more closely
[01:33] <JontheEchidna> maybe if I removed the appletsrc...
[01:34] <JontheEchidna> haha @ my quote
[01:34] <vorian> apachelogger: http://paste.ubuntu.com/103348/
[01:37] <apachelogger> root@osiris:/# apt-cache show libmysqlclient-dev
[01:37] <apachelogger> root@osiris:/# apt-cache show mysql-server-5.1
[01:37] <apachelogger> W: Unable to locate package mysql-server-5.1
[01:37] <vorian> mrn
[01:37] <apachelogger> vorian: either these packages are stuck in new, or they are just not available
[01:37] <vorian> ah, that's prolly it
[01:38] <apachelogger> vorian: yeah, all in new launchpad sez
[01:38] <JontheEchidna> no luck with new appletsrc either
[01:38] <vorian> i just checked too :)
[01:39] <apachelogger> so, here is the question
[01:40] <apachelogger> another glass of bloody mary, or going to bed?
[01:40] <vorian> bloody mary
[01:40] <apachelogger> ok
[01:40]  * apachelogger opens another bottle of vodka
[01:43] <ScottK> apachelogger: Looks like your SSL cert magic works.
[01:43] <apachelogger> yay :)
[01:43] <ScottK> Couldn't sniff my own password this time.
[01:44] <ScottK> Sput: I'm here on the git snapshot with split client server.  The monolithic one works too.
[01:47] <ScottK> Sput: I'm about convinced this git snapshot is working.  Is there some upstream person that would be willing to subscribe to Quassel bugs in Ubuntu?
[01:47] <ScottK> apachelogger: Any reason I shouldn't upload this?
[01:48] <apachelogger> ScottK: unless I told you some earlier there is probably none
[01:48] <ScottK> Not that I recall.
[01:49]  * apachelogger is not 100% sober but thinks there was only some testing on the cert stuff to be done
[01:51] <JontheEchidna> kubotu: chat
[01:51] <kubotu> 08] <Tonio_> Riddell: I already packaged smb4d, and planing to prepare the wiki static?
[01:51] <JontheEchidna> whee, lag
[01:56] <apachelogger> who is lagging?
[02:03] <apachelogger> oh dear, my bf just fell a sleep watching television
[02:03] <apachelogger> hm
[02:03] <apachelogger> oh
[02:04] <apachelogger> JontheEchidna: please check if your .kde kdeglobals contains a Directories group
[02:04]  * ScottK wonders what decorations apachelogger has available.
[02:04] <apachelogger> ScottK: decorations?
[02:05] <ScottK> If it's a deep sleep you might decorate them with something.
[02:05] <apachelogger> rofl
[02:05] <ScottK> Shaving cream and lipstick are traditional.
[02:06] <ScottK> Nair is you've got a serious nasty streak.
[02:06] <ScottK> is/if
[02:06]  * apachelogger notes that decoration from the christmas tree is still somewhere *evilgrin*
[02:07] <JontheEchidna> apachelogger: no Directories group
[02:12] <apachelogger> JontheEchidna: hm, ok, I'll take a look at it
[02:13] <apachelogger> maybe we really need to edit kde4rc, altough I'd rather avoid that
[02:13] <torkiano> hello, I have a little problem with your KDE 4.2beta packages, Can I report a bug in launchpad?
[02:13] <torkiano> summarizing: http://imagebin.ca/view/Us-dl8.html
[02:15] <torkiano> the trash applet not shows its elements
[02:15] <apachelogger> torkiano: if you are on jaunty you can report a bug, if you are on intrepid this issue might very well be caused by the fact that we don' t deploy updated localization for it
[02:15] <torkiano> ok apachelogger, I'm in intrepid
[02:15] <vorian> torkiano: that should be fixed when RC1 comees out next week
[02:16] <apachelogger> vorian: are you sure?
[02:16] <vorian> or that
[02:16] <torkiano> vorian: grear news, thank you vorian
[02:16] <vorian> apachelogger: it's connected to the kdm.init bug
[02:16]  * apachelogger is wondering how that connects to kdm
[02:17] <vorian> it doesn't
[02:17] <apachelogger> Oo
[02:17] <apachelogger> you are not making sense :P
[02:17] <vorian> yeah, i'll stop talking now
[02:17] <apachelogger> lol
[02:17]  * apachelogger continues decorating and then goes to bed, still a lot of reviewing to do tomorrow
[02:19] <ScottK> apachelogger and Sput: quassel uploaded.
[03:07] <ScottK> seele: There is now a git snapshot of quassel with KDE integration enabled in Jaunty and on my PPA for Intrepid https://launchpad.net/~kitterman/+archive/
[03:08] <ScottK> seele: This is, less one small commit, the current state of the development tree. It might be worth a quick relook to see if any new usability things pop up.
[03:12]  * ScottK discovers there is a "Emoticons Themes Manager" and despairs.
[03:26] <torkiano> ScottK: Wow, Kvirc4 is very impressive, thank you for the PPA
[03:27] <ScottK> torkiano: You're welcome.  I think it's a bit much for newbies, so not great for our default, but it's a good client.
[03:27] <ScottK> I should probably upload that to the archive too.
[03:31] <torkiano> Maybe, quaseel is a little confusing, too. Mainly because of its distributed architecture
[03:31] <torkiano> but as dar as I Know they are working in it
[03:32] <ScottK> Yes.  The client/core is.  We're intending the monolithic client as the default.
[03:35] <torkiano> I wonder if you mind if I put links to your PPA in this thread in kde forum: http://forum.kde.org/kde4-qt4-replacements-for-konversation-t-23842.html
[03:36] <ScottK> No.   I'll wait until you upload kvirc4 to the archive
[03:53] <ScottK> It may be awhile.  I built my package on work rgreening did and I'd rather let him finish it and get the credit if he's interested.
[04:13] <rgreening> hry
[04:14] <rgreening> hey even
[04:14] <rgreening> ScottK: Im around... I have been a bit tied up with $work :)
[04:15] <rgreening> + holidays... I should have some time starting Monday...
[04:15] <ScottK> rgreening: I updated your kvirc package to a newer snapshot and then played with it some.
[04:15] <rgreening> That's cool
[04:16] <ScottK> rgreening: I think it's good enough to put in the archive as kvirc (modulo fixing the comments I gave you).
[04:16] <ScottK> rgreening: So would you be up for updating it next week then (as kvirc, not kvirc-kde4)?
[04:16] <rgreening> awesome
[04:16] <ScottK> I take it that's a yes?
[04:16] <rgreening> sure nthing.
[04:17] <rgreening> thing...
[04:17] <ScottK> Great.
[04:17] <rgreening> :P
[04:17] <ScottK> rgreening: Ping me when you need a sponsor.
[04:17] <rgreening> ok. ty.
[04:19] <ScottK> torkiano: ^^ Next week some time.
[04:20] <rgreening> Scott: what changes besides the -kde4 do I need? Obviously update the tar.gz to current snapshot/release/ver
[04:20] <rgreening> ScottK^
[04:21] <ScottK> rgreening: Do you still have my comments in your IRC logs?
[04:21] <torkiano> ScottK: I upgrade the post when that happens ;-)
[04:22] <ScottK> Well grep kvirc * acrosss my IRC logs tells me who uses kvirc.
[04:22] <rgreening> probably. If those are the ones, I am pretty sure I did those..
[04:22] <ScottK> I didn't see an upload after I gave you the comments.
[04:22] <rgreening> hmm...
[04:23] <rgreening> let me look
[04:25] <rgreening> ScottK: https://launchpad.net/~roderick-greening/+archive
[04:25] <ScottK> rgreening: That's after I gave you comments.
[04:25] <ScottK> So I guess you did.
[04:26] <rgreening> :)
[04:27] <rgreening> ScottK: If you have a look and see any glaring bad things... feel free to let me know. I'll update hte package next week without the -kde4 extension.
[04:27] <ScottK> OK.  If I get motivated I will.
[04:27] <ScottK> rgreening: Since it's a Universe package, when you ask me, ask me in #ubuntu-motu.
[04:28] <rgreening> kk.
[04:28] <ScottK> When you apply for MOTU we want these people to know who you are.
[04:28] <rgreening> for sure
[04:28] <rgreening> ty
[04:28] <ScottK> No problem.  The more people who know what they are doing and have upload rights, the less for me to do ...
[04:29] <rgreening> true dat
[04:29] <Tm_T> (:
[04:30] <ScottK> Man with one big eyebrow and no mouth?
[04:30] <ScottK> or nose
[04:30] <rgreening> ahaha
[04:30] <Tm_T> left-handed smiley
[04:30] <rgreening> tim-may!
[04:31] <Tm_T> rgreening: ?
[04:31] <rgreening> nvm
[04:32] <Tm_T> nevervontermights?
[04:32] <vorian> wow
[04:32] <rgreening> lol
[04:32] <rgreening> nwn
[04:32] <vorian> you can put a sftp address in folderview :D
[04:32] <rgreening> hahah
[04:32] <vorian> that is awesome
[04:32] <rgreening> oh I need sleep
[04:32] <Tm_T> vorian: sure
[04:33] <vorian> i'm always the last to notice things :)
[04:33] <Tm_T> vorian: well there will be thousands of people noticing after you so no worries
[04:34] <vorian> hehe
[04:34] <ScottK> That's one of the things I love about KDE is you can pretty much to that anywhere.
[04:34] <ScottK> Gnomish stuff seems to fall over and get upset.
[05:36] <LaserJock> vorian: that rocks
[05:37]  * LaserJock comes late to the "sftp in folderview" party
[07:22] <torkiano> Sckott: I have problems with your quassel packages: dpkg: error processing /var/cache/apt/archives/quassel-client_0.4.0~git090110-0ubuntu1~intrepid1~ppa2_i386.deb (--unpack):
[07:22] <torkiano>  trying to overwrite `/usr/share/kde4/apps/quassel/quassel.notifyrc', which is also in package quassel
[07:54] <Tm_T> Riddell: knew this? http://www.nytimes.com/2009/01/11/business/11ubuntu.html?_r=1
[09:51] <briseight> Hi
[09:51] <briseight> I'm building digikam
[09:52] <briseight> from svn
[09:52] <briseight> I need libkipi
[09:52] <jussi01> briseight: you do realise there is a recent version in ppa?
[09:53] <briseight> no
[09:53] <jussi01> briseight: deb http://ppa.launchpad.net/digikam-experimental/ubuntu intrepid main
[09:53] <briseight> but I would like to build it from svn
[09:53] <briseight> thx
[09:53] <jussi01> briseight: thats just a few days old
[09:53] <briseight> there are a lot of libkipi version
[09:54] <briseight> libkipi5 libkipi6 libkipi0
[09:54] <briseight> what is the difference?
[09:56] <jussi01> no idea tvh
[10:51] <Tonio_> hi there ;)
[10:51] <Tonio_> finally got internet at home !!!
[10:51] <smarter> hey toma
[10:51] <smarter> woops
[10:51] <smarter> hey Tonio_
[10:51] <Tonio_> Riddell: I'll push some packages today... they're offline for a moment right now
[10:51] <smarter> toma: sorry :p
[10:51] <Tonio_> hi smarter
[10:52] <Tonio_> 7 month without internet connection at home..... so goot to be connected outside of work
[10:52] <Tonio_> is jaunty usable right now ? I'm currently upgrading....
[10:53] <Tonio_> smarter: any info about it's status ? I've been offline those last weeks so I have no idea wether it works or not :)
[10:54] <smarter> Tonio_: didn't try to upgrade, imho it's not really useful at the moment
[10:54] <Tonio_> smarter: hum, well to test latest kde packages, it is imho
[10:54] <Tonio_> we'll see if it reboots or not :)
[10:55] <smarter> Tonio_: we backport everything to intrepid
[10:55] <smarter> good luck :p
[10:55] <smarter> I just have a jaunty schroot set up
[10:55] <Tonio_> smarter: hum, yeah, but backports are generally poorly maintained and don't receive lots of fixes...
[10:56] <smarter> that's what we try to avoid
[10:56] <Tonio_> it's the very first time I have a 3.5 MB/s upload speed at home... impressive...
[10:56] <Tonio_> that'll be usefull :)
[10:56] <smarter> wow
[10:57] <Tonio_> and 50 MB/s download (theorically 100 but hard drive + wifi is the limit !!)
[10:57] <Tonio_> Mb, not MB, sorry :)
[10:58] <Tonio_> anyway that's still pretty good :)
[10:58] <smarter> yup
[11:02] <Tonio_> smarter: do you know if guidance replacement by powerdevil was discussed recently ?
[11:02] <smarter> yes
[11:02] <Tonio_> smarter: I need to get infos on what's going on now I'm really back ;)
[11:03] <smarter> iirc, it was decided to keep guidance in the repo, but to switch to powerdevil by default
[11:03] <danimo> moin
[11:03] <Tonio_> smarter: okay
[11:03] <Tonio_> hey danimo !! long time no see !!
[11:03] <smarter> not sure how we'll handle the transition
[11:03] <Tonio_> smarter: what about pataching the powerdevil applet so that it goes in the systray in the first place ?
[11:03] <danimo> question:does anybody know if the gtk-qt-kde4 theme is finally good enough to make firefox look good?
[11:04] <danimo> hi Tonio_ :)
[11:04] <Tonio_> smarter: to many applets in the bar take up to much space....
[11:04] <danimo> the one in 8.10 has a quite some issues
[11:04] <Tonio_> smarter: better have them in the systray imho, as for networkmanager too
[11:04] <Tonio_> danimo: yeah, but that's a long time plan discussion :)
[11:04] <smarter> Tonio_: this should be discussed with the plasma devs, I think the idea is to get the plasmoids in the systray
[11:05] <Tonio_> danimo: also, I hope the kde crew will do something with notification... there are WAY to much of them right now
[11:05] <Tonio_> smarter: should probably be an option btw...
[11:05] <danimo> Tonio_: it mostly annoys me with kopete
[11:05] <Tonio_> danimo: and what about file copy :)
[11:06] <danimo> Tonio_: well, I never liked that anyway
[11:06] <Tonio_> danimo: have you tried to load ktorrent with a bunch of torrents loaded ?
[11:06] <Tonio_> your screen get full of notifications :)
[11:06] <smarter> Tonio_: report bugs everytime you see them when you shouldn't, the devs need to specify it explicitely in the code so that they don't appear
[11:06] <danimo> Tonio_: the problem is that kio does not distinguish between downloads and file copy operations
[11:06] <Tonio_> smarter: yep, that's probably a ktorrent issue
[11:06] <smarter> and the fix should be easy
[11:07] <Tonio_> smarter: I think so...
[11:07] <Tonio_> danimo: interesting...
[11:07] <Tonio_> what about the policykit applet ?
[11:07] <Tonio_> last time I tried it didn't work at all...
[11:07] <danimo> Tonio_: you can make them silent, e.g. if you  know the operation is probably local, but nobody seems to do thgat
[11:08]  * danimo goes for breakfast
[11:08] <Tonio_> danimo: I'll check if that can simply be kiosk configured for the softwares causing problem...
[11:17] <danimo> Tonio_: I doubt it
[11:17] <danimo> Tonio_: about the policykit applet: no idea. I'm still not very involved in KDE dev again
[11:18] <danimo> Tonio_: you can now ask me all about Qt Creator though :)
[11:18] <Tonio_> danimo:  :)
[11:18] <Tonio_> the problem is that whenever you need to take a break..... everything changes so fast....
[11:21] <danimo> Tonio_: tell me about it
[11:21] <danimo> Tonio_: I finished studies and suddenly everything's changed
[11:21] <danimo> which is good to see, since there is progress
[11:21] <danimo> but well, it's quite some effort to get going again
[11:24] <Tonio_> true that....
[11:24] <Tonio_> danimo: running through personal issues, I couldn't contribute much for 7 month... alike
[11:29] <danimo> Tonio_: last thing I heard about you was getting married and stuff
[11:35] <Tonio_> danimo: that's old stuff :)
[11:35] <Tonio_> danimo: we split....
[11:35] <Tonio_> danimo: in fact she had another guy for month when we where planning to get married....
[11:35] <Tonio_> danimo: pretty rude :)
[11:36]  * Tonio_ crosses fingers and reboots.... jaunty please, give me a good feeling !
[11:44] <Tonio_> re
[11:44] <Tonio_> hum it works surprisingly well....
[12:12] <wesley> ive reported more bugs for 9.04
[12:52] <apachelogger> ScottK: seeing torkiano's error I would suppose share/kde4/apps/quassel also ought to go to quassel-data
[12:53] <apachelogger> headache--
[12:55] <apachelogger> wesley: reporting bugs against kde*-kde4 products doesn't make much sense because we don't monitor them anymore
[12:56] <apachelogger> wesley: apt-cache show juk | grep Source
[12:56] <apachelogger> that should spitout the appropriate source package to report the bug against
[13:29] <wesley> ow though that already, but some are distro related
[13:30] <wesley> gues the problems will be fixed in kde4.2 final
[13:32] <wesley> going see if in kde4.2 rc is the problem, if not its fixed within kde
[13:34] <wesley> https://bugs.launchpad.net/~velroy1
[13:35] <apachelogger> wesley: that has nothing to do with distro related or not, it's about reporting bugs against the right package
[13:36] <apachelogger> usr/bin/juk was never created by kdemultimedia-kde4
[13:37] <wesley> which package is it then? kdemultimedia ?
[13:38] <apachelogger> aye
[13:39] <wesley> kdemultimedia-kde4 is from 8.04 isnt it ?
[13:39] <apachelogger> wesley: https://wiki.kubuntu.org/Bugs/FindRightPackage
[13:39] <apachelogger> yes, -kde4 is from hardy
[13:45] <wesley> You know that people por linux drivers to osx ?
[13:46] <apachelogger> wesley: I suppose you mean port?
[13:46] <wesley> yeah port
[13:47] <apachelogger> didn't know that
[13:47] <apachelogger> but I imagine that would be rather pointless
[13:47] <apachelogger> osx is based on bsd, now while both linux and bsd are posix compatible the way their driver stacks are quite different AFAIK
[13:48] <wesley> its not really for legal purpose but its nice to see such a commiuty, it reminds me about Linux :)
[13:49] <apachelogger> wesley: well, they make use of the linux driver's implementation details, so they don't have to analyze the hardware themselfs, so one could say they only "borrow" knowledge ;-)
[13:50] <apachelogger> something not possible for most linux drivers though
[13:52] <wesley> yeah, they doing pretty well if you ask me, i dont get why osx wont be there for the pc, but those drivers that people make should be in handy for say external wlan devices
[13:53] <apachelogger> wesley: apple would loose it's main advantage if osx was available for anything but macs
[13:53] <wesley> say is juk unmainted ?
[13:53] <apachelogger> anyway
[13:53] <apachelogger> off-topic
[13:53] <apachelogger> wesley: again
[13:53] <wesley> juk is ontopic
[13:53] <apachelogger> not so much either :P
[13:53]  * apachelogger knows no one who actually uses juk
[13:53] <Tm_T> apachelogger: I do
[13:54] <Tm_T> when Amarok fails that is
[13:54] <apachelogger> Tm_T: mom, then I would have to use juk all the time :P
[13:54] <wesley> is it maineted by kde? because there are no responds on my bug reports
[13:54] <Tm_T> apachelogger: I don't, as my amarok is just fine
[13:54] <Tm_T> wesley: ot
[13:54] <wesley> i prefer juk over amarok
[13:54] <Tm_T> wesley: gah, sorry
[13:55] <wesley> ot ??
[13:55] <Tm_T> wesley: it's part of kdemultimedia
[13:55] <wesley> oh, doesnt really seem to be maintned if you ask me
[13:55] <apachelogger> wesley: help -> about juk
[13:56] <apachelogger> and just because you didn't recive a reply on your bugs doesn't mean it's unmaintained
[13:56] <apachelogger> Riddell, JontheEchidna: did anyone fix bindings?
[13:56] <JontheEchidna> apachelogger: kdepimlibs bug which was fixed, it builds fine without any modification to Riddell's first package
[13:58] <apachelogger> ok
[13:58] <apachelogger> Riddell: I'll mark it reviewed
[13:59] <wesley> https://bugs.launchpad.net/ubuntu/+source/guidance-power-manager/+bug/269592 i think this is fixed in 9.04 ?
[14:01] <apachelogger> we don't use guidance-power-manager by default anyway
[14:02] <wesley> yeah found another bug, this time in package usb-creator
[14:05] <wesley> apachelogger , gues that solved the problems, because in 8.04 and 8.10 it wasnt working like i wwanted
[14:05] <wesley> how do i find package detalil ?
[14:07] <wesley> ubuntu is hard working on the intel issues ???
[14:07] <apachelogger> what kind of package detail?
[14:07] <apachelogger> and for which package
[14:07] <wesley> usb-creator
[14:08] <wesley> and how can i report against 9.04? i always fill this in [ Kubuntu 9.04 Alpa 2 ]
[14:11] <apachelogger> wesley: you should stop that
[14:11] <apachelogger> a bug affects all series unless someone proofs it is only vaild for 9.04 or 8.10 ...
[14:11] <apachelogger> wesley: usb-creator is an ubuntu thing, so you might want to ask in #ubuntu
[14:12] <wesley> i have found the info, why not use tags like which branch i am uing? i though that would be better for developers
[14:12] <apachelogger> JontheEchidna: join ##club-ubuntu for bug squashing purpose :P
[14:14] <wesley> so if i get it right, its better to report without pointing which branch i use?
[14:14] <JontheEchidna> my dog is chewing on my dad's beard...
[14:14] <wesley> i only have cats
[14:15] <Nightrose> apachelogger: another 2 hours to release I hope - getting started on the announcement now
[14:15] <wesley> apachelogger what if i know sure its related to 9.04 ? because ive used usb creator on 8.10 and it worked
[14:16] <apachelogger> Nightrose: packages for intrepid are ready
[14:17] <Nightrose> excellent
[14:17] <wesley> http://paste.ubuntu.com:80/103538/
[14:17] <apachelogger> wesley: that doesn't mean it can be fixed for 9.04, so it might as well affect 9.10
[14:18] <wesley> oh okay, anyway if i spit the file, see this ImportError: No module named gnomevfs
[14:18] <wesley> should i name that in my title ?
[14:18] <apachelogger> yeah, probably a dependency issue in sub-creator
[14:18] <apachelogger> wesley: for example
[14:19] <apachelogger> the triagers will change the title to the most productive form anyway if necessary
[14:19] <wesley> okay, then, i going test maby to on my acer machine
[14:20] <wesley> its better to test on more machines isnt it ?
[14:20] <apachelogger> yes
[14:21] <wesley> then i going run unstable on both
[14:22] <apachelogger> wesley: having a virtualmachine ought to be enough in most cases
[14:24] <wesley> ive something must better, i have a stable osx on my machine so i dual boot with osx and ubuntu is unstable
[14:30] <ScottK> apachelogger: I agree I put the notify thing in the wrong package for quassel.
[15:02] <wesley> cant i help on lauchpad for people who want to ask something about kde4 in there dutch laugugae?
[15:11] <apachelogger> wesley: https://answers.edge.launchpad.net/ubuntu/+source/kdebase
[15:11] <apachelogger> it's organized by source package, so you might want to subscribe to more than just kdebase
[15:11] <apachelogger> it's like subforums for every source package
[15:12] <wesley> you added me :) thanks,
[15:13] <wesley> i can answer also in dutch
[15:26] <wesley> !kdenlive
[15:39] <JontheEchidna> !info kdenlive
[15:39] <JontheEchidna> !info kdenlive jaunty
[15:42] <seele> ScottK: which one do i want? quassel or quassel-client?
[15:42]  * seele waves to jjesse
[15:42] <seele> 'morning
[15:42] <jussi01> seele: quassel for the monolithic build
[15:42] <seele> jussi01: thanks
[15:43] <jjesse> monring
[15:51] <wesley> I need someone with a credit card to pay some flight tickets
[15:52]  * seele blinks
[16:02] <jussi01> err, what?
[16:28] <doc__> hi there
[16:50] <alleeHol> \sh: mhmm, happy birthday \o/
[16:56] <torkiano>
[16:57] <torkiano> Hello, what is the kubuntu policy with KDE3 bugs?
[16:58] <ScottK> torkiano: Depends on the package.
[16:58] <torkiano> For triaging this: bug 47429
[16:58] <torkiano> is kopete
[16:58] <ScottK> Also I'm fixing the quassel conflicting file problem right now.  Thanks.
[16:59] <torkiano> You are welcome
[16:59] <ScottK> torkiano: Does the KDE4 version do it?
[16:59] <torkiano> As far as I know, no
[16:59] <ScottK> The it's still a valid bug.
[17:01] <torkiano> Then, this is not a valid response: http://pastebin.ca/1305993
[17:03] <ScottK> apachelogger: Do I need to conflict/replace or just conflict when I shuffle files from package to package?
[17:03]  * ScottK didn't get enough sleep in the last few days to remember.
[17:03] <apachelogger> ScottK: replace
[17:03] <ScottK> apachelogger: Thanks.
[17:03] <apachelogger> both only when the package completely replaces another one
[17:05] <ScottK> Right.
[17:06] <ScottK> torkiano: I'm not a fan of such replies.  I tend to believe it's a bug until someone has reason to believe it's not.  Can you try it with a proxy?
[17:07] <ScottK> But that's just me.  Asking everyone to reproduce every bug in every release and invalidating the bug is all the rage these days in bugsquad.
[17:07] <ScottK> JontheEchidna: Weren't you working on updating kdenlive to a new version or something?
[17:08] <JontheEchidna> I don't think I was
[17:08] <torkiano> ScottK: not here, I try tomorrow in the work
[17:09] <ScottK> torkiano: I think that's a much more useful triaging action.
[17:09] <ScottK> Thanks.
[17:11] <torkiano> ScottK: And if tomorrow I can't reproduce the bug with my KDE4, what is the next step?
[17:11] <ScottK> If you can connect via a proxy, then the bug is fixed.  Just mark it fix released.
[17:12] <ScottK> Generally you invite the reporter then to try it in a new release and reopen the bug if it still doesn't work for them.
[17:16] <ScottK> apachelogger: Please double check me on this...  For quassel-data:
[17:16] <ScottK> Conflicts: quassel-client (=< 0.4.0~git090110-0ubuntu1), quassel (=< 0.4.0~git090110-0ubuntu1)
[17:16] <apachelogger> ScottK: ah, I am being silly as well
[17:16] <apachelogger> yo need a replaces
[17:16] <apachelogger> *you
[17:16] <ScottK> OK.
[17:17] <ScottK> That's the correct syntax though, right?
[17:17] <apachelogger> nah <= not =<
[17:17] <ScottK> OK.
[17:17]  * ScottK fixes
[17:17] <ScottK> Thanks.
[17:18] <apachelogger> and I thought my hangover had bad influence on my work :)
[17:22] <apachelogger> oh
[17:22] <apachelogger> my
[17:22] <apachelogger> god
[17:22] <apachelogger> it's 11th again
[17:22] <apachelogger> ~order birthday package for \sh
[17:22]  * kubotu is running to the corner shop to get a birthday present.
[17:22]  * kubotu slides a birthday cake and a present down the bar to \sh and gives everyone a nice frosty mug of beer.
[17:22] <kubotu> Happy birthday to you, happy birthday to you, happy birthday \sh, happy birthday to you!!!! - Wooooho!
[17:22] <kubotu> Happy Birthday \sh :D
[17:22] <kubotu> To your health!
[17:22] <Tm_T> ok
[17:22] <apachelogger> \sh: happy bday *hug*
[17:23]  * apachelogger hands \\sh a box of cookies
[17:23] <Tm_T> Kubuntu Kookies!
[17:23] <apachelogger> ah
[17:23] <apachelogger> bad!
[17:23] <apachelogger> that makes KK
[17:23] <apachelogger> you don't want to have KK, really
[17:23] <Tm_T> Kool Kubuntu Kookies then
[17:23] <apachelogger> K3
[17:23] <ScottK> No, that's worse.
[17:23] <Tm_T> how so?
[17:24] <ScottK> KKK is a severely racist organization in the US.
[17:24] <apachelogger> so
[17:24] <apachelogger> why do your racist organizations have K's in their names?
[17:24] <Tm_T> oh I know, and we have big crocery stores called KKK-Supermarket here
[17:24] <apachelogger> in europe they at least use something with N
[17:24] <apachelogger> Tm_T: oh dear
[17:25] <Tm_T> well K KK KKK and biggest ones are KKKK
[17:25] <apachelogger> we should just use kenji signs instead
[17:25] <Tm_T> apachelogger: why not Kubuntu signs?
[17:25] <ScottK> Well it's ~ a century and a half old, so I think they got there first.
[17:25] <apachelogger> Tm_T: because we only have one :P
[17:26] <Tm_T> apachelogger: but that's enough!
[17:26] <apachelogger> if you say so :P
[17:26] <apachelogger> we need a font though
[17:26] <apachelogger> and make it default, otherwise we can't use the sign on IRC
[17:26] <Sput> happy birthday \sh!
[17:27] <Sput> \sh: we shall have a (two, three, many) beer(s) as soon as I've started drinking again :)
[17:27] <apachelogger> Sput must be sober, he is so unproductive :P
[17:27] <Sput> I am :(
[17:27]  * ScottK points out http://techbase.kde.org/Development/CMake_KDE_4_2
[17:27] <apachelogger> back in the days you broke and rewrote quassel in one day
[17:28] <Sput> I'm busy figuring out why QFormLayout sucks in Oxygen theme
[17:28] <Sput> can't give seele her middle alignment stuff with that bug :/
[17:28] <apachelogger> ScottK: something interesting about it?
[17:29] <ScottK> It summarizes build system changes 4.0/4.1 -> 4.2
[17:32] <ScottK> Sput: Did you see the minimize bug discussions from last night on #quassel?
[17:33] <Sput> ScottK: yeah, didn't get around to look at it though
[17:33] <nixternal> do we have the <IP_ADDRESS> amarok in intrepid yet?
[17:33] <ScottK> nixternal: vorian was working on it yesterday.
[17:33] <nixternal> groovy
[17:33] <ScottK> Sput: OK.  As long as it goes on the list.
[17:33] <ScottK> nixternal: It's punted to Universe so mere MOTU can deal with it.
[17:33] <ScottK> ;-)
[17:34] <nixternal> looks like there is an amarok-kde4 update in intrepid already :)
[17:34] <ScottK> Yes, but it doesn't use the official mysql 5.1 packages, so there's more work for Jaunty to get it more right.
[17:35] <apachelogger> ScottK: he worked on jaunty
[17:35] <apachelogger> also for jaunty 5.1 is still in binary new
[17:35] <ScottK> apachelogger: Right.  You did the Intrepid one.
[17:35] <ScottK> That too.
[17:35]  * ScottK wonders if Riddell can find a moment to fix that (get mysql 5.1 out of binary New)?
[17:36] <apachelogger> Riddell: what does one have to do to become archive admin? :P
[17:45] <ScottK> Working for Canonical helps a lot.  AFAIK, Hobbsee is the only exception, but has limited access as a result.
[17:47] <nixternal> Hobbsee: no more Vista for me! Windows 7!!! :P
[17:47] <ScottK> Nightrose: So Amarok works with Audible?
[17:47] <Tm_T> nixternal: 7lover!
[17:47] <nixternal> hahahaha
[17:47]  * Tm_T hides
[17:47] <Tm_T> nixternal: damn you, we have to change all factoids
[17:47] <nixternal> don't know yet...they opened up beta testing to everyone...so I am going to see if it is all people are saying it is
[17:47] <nixternal> I will give an un-biased report of course :p
[17:48] <Tm_T> !nixternal
[17:48] <Nightrose> ScottK: it did in 1.4 - i don't think Alejandro got around to making it work in 2
[17:49] <ScottK> OK.
[17:49] <Nightrose> but it is planned
[17:49] <ScottK> Nightrose: Audible is the thing that stands between my wife and being Windows free ...
[17:49]  * ScottK is interested ...
[17:49] <Nightrose> *nod*
[17:49] <Nightrose> xevix and aumuell are the guys to talk to about it
[17:50] <Nightrose> aumuell being the guy who did it for 1.4
[17:50] <nixternal> !nixternal
[17:50] <nixternal> hahahahahahahha
[17:50] <Nightrose> *lol* nixternal
[17:50] <Nightrose> so you love it, he?
[17:50] <Tm_T> sorry, had to fix that
[17:50] <nixternal> Nightrose: haven't even tried it yet, downloading it now
[17:50] <Nightrose> ;-) ok
[17:50] <nixternal> I need to go get another hard drive
[17:51] <Nightrose> tell us how much you love it once you tried
[17:51] <Nightrose> :P
[17:54] <Nightrose> apachelogger: JontheEchidna: can one of you update http://amarok.kde.org/wiki/Download:Kubuntu please?
[18:01] <nhandler> What is the best way to test out the latest kde on intrepid? I'm still getting used to not running the Development version of Ubuntu
[18:01] <apachelogger> nhandler: kubuntu-experimental PPA
[18:01] <apachelogger> nhandler: also I think JontheEchidna could use some help with backporting
[18:01] <nhandler> Thanks apachelogger
[18:01] <nhandler> apachelogger: What is he backporting?
[18:01] <apachelogger> nhandler: 4.1.96
[18:02] <nhandler> To intrepid?
[18:02] <apachelogger> or at least I am hoping he started backporting already :)
[18:02] <apachelogger> nhandler: yes
[18:03] <nhandler> Sure, I could give him a hand. Is the progress being tracked anywhere? Or should I just ask him what he has done?
[18:09] <seele> ScottK: i saw you made a comment about notifications in quassel, is it using knotify now?
[18:09] <ScottK> seele: Now it is.
[18:09] <ScottK> It wasn't before.
[18:09] <seele> ScottK: ok great
[18:09] <ScottK> It was actually better before.
[18:10] <seele> ScottK: i didnt get to install .4 yet (i'll get to it in about 30 minutes after i finish emails).. but does Quassel have an option to run in the systram without having an entry in the task panel?
[18:10] <seele> ScottK: i'm annoyed with the plasma notifications, but i forget if they were improved for rc1.  theyre too big and block too much of my work area
[18:10] <ScottK> seele: It does, but it's currently bugged.  Sput's aware of it.
[18:10] <seele> ScottK: ok.. as long as it's planned.
[18:11]  * ScottK is using it with 4.1.3, so dunno what it's like with 4.2.
[18:11] <ScottK> It'd be handy if someone running 4.2 would take a screenshot of a quassel notification using the Jaunty package or the one from my PPA?
[18:11]  * ScottK looks around.
[18:12] <Sput> ScottK: actually, close-to-tray seems to work fine here
[18:12] <ScottK> Sput: Clost to try works.  It's minimize to try that was the problem.
[18:12] <ScottK> Was/Is.
[18:12]  * ScottK needs more coffee
[18:13] <jussi01> ScottK: I can take a screenie of git +4.2 if you like?
[18:13] <ScottK> jussi01: With the KDE integration enabled?
[18:13] <jussi01> ScottK: yeah
[18:13] <Sput> ScottK: that works here too :(
[18:14] <ScottK> Yes.  Please.
[18:14] <jussi01> ScottK: please hilight me then :)
[18:14] <ScottK> Sput: With KDE integration.
[18:14] <Sput> ScottK: yes of course.
[18:14] <ScottK> jussi01: Hello from #kubuntu-devel
[18:14] <ScottK> Sput: Dunno what to say then.  Definitely no workee here.
[18:15] <Sput> ScottK: I have tried both checking and unchecking the box, and Quassel minimizes fine with both minimize and close button
[18:15] <Sput> I'm running KDE trunk though
[18:15] <ScottK> Maybe that's it.
[18:15]  * ScottK looks at jussi01 to try it too.
[18:15]  * Sput updates and restarts quassel just in case
[18:16] <Sput> ScottK: so you have both options checked?
[18:16] <ScottK> Sput: I've tried it with both and only one.
[18:16] <jussi01> ok, hilight again? (sorry)
[18:16] <ScottK> jussi01: Does minimize-to-tray work for you?
[18:17] <ScottK> Sput: It did not work both with both options checked and with just minimize-to-tray checked.
[18:17] <jussi01> minimize to tray doesnt work here
[18:17] <ScottK> minimize-to-try-on-minimize
[18:18] <jussi01> just remaximises
[18:18] <ScottK> Same here.
[18:18] <ScottK> Sput: close-to-tray works fine.
[18:19] <jussi01> ScottK: this is annoying, cant seem to get a screen - the notifications disapear on me. can you hilight me a few times in a row?
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <Sput> ScottK: I can't reproduce :(
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <ScottK> jussi01: Sure.  Repeated notifications here we come ....
[18:19] <nhandler> Riddell: ping
[18:19] <ScottK> Sorry everyone else.
[18:20] <ScottK> I hope that was enough.
[18:20] <ScottK> Sput: What KDE are you  running?
[18:20] <Sput> minimize on minimize, minimize on close, tray icon all work fine
[18:20] <Sput> 4.2.60
[18:20] <Sput> but I couldn't reproduce that issue last time I tried either
[18:20] <ScottK> Odd.
[18:21] <Sput> which makes fixing a bitch, obviously... I'd need somebody who can reproduce who is willing to have a look at our code and can debug this
[18:22] <ScottK> Unfortunately that would not be me.
[18:22] <ScottK> willing/able
[18:22] <jussi01> Sput: I can give you vnc to my machine...
[18:23] <Sput> jussi01: that might be an option, not right now though (have some other things cooking in my workdir currently)
[18:23] <ScottK> jussi01: Was that enough notifications?
[18:23] <Sput> plasma's notifications are broken still, they seem to ignore the "persistant" flag
[18:23] <jussi01> ScottK: yeah, ive got it... (though with my other client - stole the wifes lappy fo a min)  1 sec
[18:24] <ScottK> OK.
[18:24] <ScottK> jussi01: Did you have to disable focus stealing protection?
[18:24] <ScottK> One does on 4.1.
[18:24] <Sput> on 4.2 as well, afaics
[18:24] <ScottK> OK.
[18:25] <Sput> KNotification has a flag to raise the window on click, with a TODO: No working yet
[18:25] <jussi01> ScottK: I just had another app running next in line (terminal) http://omploader.org/vMTQ5YQ
[18:25]  * ScottK looks
[18:26] <ScottK> jussi01: Looks much better than what I get in 4.1.
[18:26] <jussi01> ScottK: yeah, MUCH bettefr :D
[18:26] <Sput> ah, 4.1 still had those ugly rectangles
[18:27] <jussi01> 4.2 does on occaision still
[18:28] <nixternal> seele: you tweeted to me about "browser stats" being misleading...please explain, because I am quite confused right now...this was from jan. 8
[18:29] <ScottK> jussi01: Here's my recursive look at it: http://kitterman.com/kubuntu/notify.notify.png
[18:29] <seele> nixternal: i posted a message on one of your articles and it said i was on XP.  i assume that is because i set my user agent to XP so i can view websites which check for Windows
[18:29] <nixternal> ahhhh
[18:30] <jussi01> ScottK: heh... I like the look of my setup much better... ;)
[18:31] <jussi01> anyone tried the new network manager plasmoid in the last few days? (updating mine now)
[18:31] <apachelogger> ScottK: problem is the positioning of the passive popup?
[18:31] <apachelogger> jussi01: it looks better :P
[18:32] <jussi01> apachelogger: usable yet?
[18:32] <apachelogger> no :P
[18:32] <apachelogger> not for me anyway
[18:33] <apachelogger> 2 packages to go
[18:39] <ScottK> seele: Did you get the updated quassel working OK?
[18:39] <ScottK> torkiano: I just uploaded the fix for the conflicting packages.
[18:42] <torkiano> ScottK: downloading...
[18:42] <ScottK> Given the huge amount of change in the quassel package from 0.3.1 (thanks again apachelogger), if that's the only thin that's bugged in the packaging, I'm pretty pleased.
[18:42] <ScottK> thin/thing
[18:42] <torkiano> ScottK: Works fine now, thanks
[18:42] <ScottK> torkiano: Great.  Sorry for the trouble.
[18:43] <torkiano> I'll try it, see you soon ;-)
[18:45] <seele> ScottK: sorry.. still going through a pile of emails.  as soon as i finish this one i plan on installing .4
[18:45] <ScottK> OK.
[18:45] <seele> sometimes i think i work hard on kde than the job that pays me
[18:45] <seele> *harder
[18:45] <Sput> seele: why do I know that feeling :)
[18:47] <torkiano> mmmm
[18:47] <torkiano> I  believe i found a little bug XD
[18:48] <torkiano> in help->about quassel
[18:48] <torkiano> show 0.3 version
[18:49] <ScottK> torkiano: It's not a 0.4 release yet, just a git snapshot, so it's up to Sput when he wants to change that.
[18:49] <Sput> yeah, probably gonna take a couple weeks until we release 0.4 proper
[18:50] <torkiano> ScottK: I know, forget what I said then
[18:50] <ScottK> But please test and file bugs.
[18:52] <torkiano> ScottK: ok, but in the quassel tracker or here (they are your packages)
[18:52]  * Sput wonders if launchpad can relay to redmine
[18:53] <ScottK> Sput: I don't think so.  If you have a launchpad account it's easy enough to subscribe and get the bugmail.
[18:53] <ScottK> torkiano: The easy answer is if it's a packaging problem put it in Launchpad and if it's a quasell problem put it in their Redmine.
[18:54] <ScottK> Of course knowing the difference isn't always easy.
[18:54]  * Sput will subscribe to launchpad if redmine can't be integrated
[18:54] <ScottK> Sput: I'm sure it can't.
[18:54] <seele> Sput: is there a changelog thusfar?
[18:55] <nhandler> Is there a better way to setup multiple pbuilders than the way mentioned here: https://wiki.ubuntu.com/PbuilderHowto#Multiple%20pbuilders
[18:55] <ScottK> nhandler: You can do it with pbuilder-dist very easily.
[18:56] <Sput> seele: there is one, but it just contains major features (and I don't think it's quite up to date currently)
[18:56] <torkiano> ok ScottK, thank you for the information. I'll do the best we can
[18:56] <nhandler> ScottK: Will that work with k-d-t ?
[18:56] <Sput> seele: there is git log, of course.
[18:57] <ScottK> Dunno
[18:57] <Sput> http://bugs.quassel-irc.org/repositories/revisions/quassel-irc
[18:58] <ScottK> seele: The current snapshot we have packaged includes the commit from 01/10/2009 06:42 PM, but nothing after.
[18:59] <seele> ok thanks
[18:59] <Riddell> nhandler: you pinged?
[18:59] <apachelogger> nhandler: you can override pbuilder in kdt using the env var $PBUILDER
[18:59] <apachelogger> nhandler: smarter knows more about that
[19:00]  * smarter switched to sbuild, pbuilder-dist sucks :p
[19:00] <apachelogger> nhandler: also, I prefer to have multiple .pbuilderrcs for different series
[19:00] <Riddell> apachelogger: to become archive admin you need to hang around on #ubuntu-release and express and interest, I'm not sure what's available through launchpad these days (hobbsee will know), I use the command line but that needs ssh to datacentre so Canonical only
[19:01] <apachelogger> so ultimately I need to become canonical employee first -.-
[19:01] <Riddell> apachelogger: I think most stuff is available through launchpad now
[19:01] <apachelogger> Riddell: do you think they need someone to cleanup canonical tower? ;-)
[19:02] <nhandler> Riddell: Could you add me to k-u-t
[19:02] <Riddell> nhandler: updates-testing?
[19:02] <apachelogger> hm, hold on
[19:02] <Riddell> nhandler: what's your LP id?
[19:02] <nhandler> nhandler
[19:02] <apachelogger> Riddell: we could make -ninjas a member of it?
[19:03]  * apachelogger thins it would make much more sense to have all ninjas be member of -ninjas and indirect member to all the other teams we have
[19:03]  * nhandler likes that idea
[19:06] <apachelogger> Riddell: please make ninjas a member of kut
[19:06] <apachelogger> or make me admin and I make ninjas a member :P
[19:07] <vorian> ScottK: nixternal, waiting for mysql5.1 to get through new first
[19:10] <nixternal> groovy
[19:11] <nhandler> Thanks Riddell
[19:12] <Riddell> "Kubuntu Ninjas (kubuntu-ninjas) has been invited to join this team.
[19:14] <Riddell> vorian: mysql 5.1 accepted
[19:14] <vorian> Riddell: AWESOME!
[19:14] <vorian> thanks so much
[19:14] <Riddell> kubuntu-ninjas accepted
[19:31] <apachelogger> is it me or is rsync borked?
[19:32] <apachelogger> from the cdimage server
[19:33] <apachelogger> hm, now it works
[19:42] <Sput> seele: I think you had the great idea of replacing the giant Quassel logo by some sort of welcome page where users can choose to edit network/identity and/or connect to a (possibly predefined) network
[19:42] <Sput> seele: Would you like to provide a mock-up (either as .ui or a graphics file) how that could/should look like?
[19:52]  * ScottK wonders how much more junk mail these team changes will get him.
[19:52] <apachelogger> lol
[19:52]  * ScottK is not kidding.
[19:53] <apachelogger> ScottK: you should see what I get at releases
[19:53]  * ScottK can imagine.
[19:53]  * ScottK would really like for the entire concept of merge notifications to just die and go away.
[19:54]  * ScottK could really care less if some mozillathingy has a branch that wants merged.
[19:56] <apachelogger> I am not sure but I think you can unsubscirbe $team from the branch ;-)
[19:56] <ScottK> apachelogger: Unfortunately those branches are owned by ubuntu-dev.
[19:57] <ScottK> So that might not make everyone happy.
[19:57] <ScottK> They need to disambiguate 'can commit to the branch' from 'cares if it wants merged'.
[19:58] <apachelogger> *nod*
[20:00] <apachelogger> ScottK: https://wiki.kubuntu.org/Kubuntu/Ninjas/ReleasePackaging
[20:00] <apachelogger> enough information?
[20:00]  * ScottK guesses too much before he looks.
[20:00] <apachelogger> oi vei
[20:02]  * apachelogger burns jaunty
[20:03] <ScottK> apachelogger: The only thing that leaps out as missing is where/how one gets the correct batrc.
[20:03] <ScottK> Is that automagic now?
[20:03] <apachelogger> the idea is that that is private :P
[20:04] <ScottK> OK.
[20:04] <ScottK> Fair enough.
[20:04] <apachelogger> ScottK: you just need to download the .batrc_path which defines where exactly the .batrc lives ... if no .batrc is around the batscritps will try to download one via the url in .batrc_path
[20:54]  * JontheEchidna tries quassel
[20:55]  * JontheEchidna purges config for pure experience
[20:57] <JontheEchidna> meh, gotta go
[21:23] <torkiano> bug 201291
[21:24] <torkiano> my ogv video appears without its video icon
[21:25] <torkiano> is it a bug in kubuntu-default-settings?
[21:25] <torkiano> I use KDE4.2 4.1.85
[21:27] <torkiano> if I change the extension to ogg, I get the correct video icon
[23:00] <ScottK> kdesvn could really use a merge from Debian Experimental if someone were in the mood.
[23:01] <ScottK> We're quite behind.
[23:58] <Nightrose> cheaters (@ amarok screenshot in the <IP_ADDRESS> news) ;-)
[23:59] <Nightrose> that is clearly an old beta screenshot
[23:59] <Nightrose> thx for the story though


[07:28] <eckert> bonjour youtube bloque avec firefox et chromim ne s'installe pas merci
[07:30] <diogenes_> eckert,
[07:30] <diogenes_> !fr
[07:33] <eckert> please youtube in firefox is no possible toheart
[08:20] <samuel> spick spanish
[08:20] <alkisg> !es
[08:52] <jaga__> hi
[08:52] <diogenes_> hi
[08:54] <jaga__> when i compile a program it tell that couldn't connect to docker daemon is not running
[08:58] <alkisg> jaga__: I don't think this is related to ubuntu-mate, so maybe it'll be better to find a more appropriate channel, like #programming or #docker, depending on which of those is your issue
[08:58] <diogenes_> jaga__, I've never done that but you might try something like: systemctl status docker
[22:57] <PlainDave> how do I change the cursor blinking speed when it's in an edit field?
[23:20] <PlainDave> My problem is solved. Just thought you should know.
[23:21] <omgwtf> and the solution was?
[23:21] <PlainDave> in the keyboard preferences
[23:21] <PlainDave> I was looking in the mouse preferences
[23:22] <omgwtf> didn't even know that was a thing?
[23:22] <PlainDave> Yeah, I had a hard time finding it because the default was a pretty slow blink