[09:46] <k1l_> Hi, i got a question about the procedure of fixing a bug according to SRU: see bug https://bugs.launchpad.net/ubuntu/+source/corebird/+bug/1730927 The maintainer says he cant get a SRU since the final repos have different majorversions than bionic has got.
[09:48] <k1l_> but aiui this would make most packages unpatchable in final repos since the unstable version got a different major release most of the time?
[10:00] <rbasak> k1l_: can you ask in #ubuntu-devel please? This channel is for bug triage, and isn't read by all developers. I'll answer you in the other channel but this way others can pitch in too.
[10:01] <rbasak> Actually I can answer the bug.
[10:04] <k1l_> rbasak: ok, thanks. headed to #ubuntu-devel


[01:03]  * ogra_ wonders why grub-probe runs (and fails indeed) during the edubuntu builds
[01:05] <cjwatson> The kernel packages are being installed in the wrong phase
[01:05] <cjwatson> I haven't worked out why yet
[01:06] <cjwatson> Was vaguely on my list to care about tomorrow
[01:07] <ogra_> ah, its the first time i bothered to scroll down in the log :)
[01:07] <ogra_> they roll in since a while already
[01:07] <cjwatson> Yeah
[01:07] <cjwatson> I guess it's a new dependency somewhere or similar
[01:07] <cjwatson> But just a guess
[09:02] <ogra_> hmpf, so whats libcolorhug1 and why does it break all images for all arches :P
[09:04] <infinity> It's hugging your images until they suffocate?
[09:04] <ogra_> lol
[09:05] <ogra_> i see doko fixed anothetr issue with colord ... and RAOF before him ... neither of them seems to have touched that dep though
[09:05] <infinity> Nothing depends on libcolorhug...
[09:05]  * infinity goes to look at logs.
[09:08] <infinity> Oh, curious.  I guess colord did for a while.
[09:09] <ogra_> well, it surely did when the image builds ran :)
[09:11] <infinity> Hrm, yes, my laptop's living slightly in the past.
[09:12] <infinity> Then again, libcolorhug1 is now in main.
[09:13] <infinity> So, I guess that got fixed this morning.
[09:13] <infinity> Probably just more fallout from the override-loss-on-migration bug. :/
[09:14] <ogra_> ok
[11:12] <brendand> will there be a freeze this friday, or are things being modified for the rolling release?
[11:13] <tumbleweed> brendand: I have no idea
[11:13] <xnox> brendand: we will have uds tomorrow and on wednesday, i'd expect things to be cleared up by thursday.
[11:13] <ogra_> yeah
[11:13] <ogra_> UDS should tell
[11:13] <tumbleweed> xnox: there's no relevent discussion in the UDS schedule, though
[11:14] <xnox> hm?!
[11:14] <tumbleweed> am I blind?
[11:14] <ogra_> https://blueprints.launchpad.net/sprints/uds-1303 has things like monthly milestones etc
[11:14] <ogra_> which clearly is rolling related
[11:15] <seb128> monthly snapshot is wednesday at 2pm
[11:16] <tumbleweed> hrm, I swear it wasn't scheduled when I looked earlier
[11:16] <xnox> there is: foundations-1303-monthly-snapshots
[11:16] <xnox> and rolling-kernel spec.
[11:16] <ogra_> and "rolling kernel maintenance"
[11:16] <seb128> tumbleweed, yeah, I just did a bunch of scheduling, no client session was scheduled either
[11:16] <ogra_> heh
[11:16] <ogra_> snap
[11:16] <seb128> most of the sessions are on the schedule now
[11:16] <seb128> let me know if any is missing
[11:17] <Laney> I thought the rolling thing was officially still a proposal
[11:17] <tumbleweed> yet all the sessions on tuesday assume it's happening
[11:18] <smartboyhw> tumbleweed, what?
[11:18] <smartboyhw> hmm
[11:18] <smartboyhw> It should STILL be officially a proposal to the Ubuntu community....
[11:18] <seb128> it's a proposal
[11:19] <seb128> it doesn't prevent to discuss details of how things should be adapted to make that happen
[11:19] <Laney> I mean that I'd expect a session like "should we move to a rolling/LTS release model?"
[11:20] <seb128> is that really something that can happen in a session?
[11:20] <Laney> UDS is the typical venue for such discussions
[11:20] <xnox> proposals without action plans are not proposals but wishful thinking.
[11:20] <seb128> seems like an endless discussion with too many people having different opinions that will never give any concrete output
[11:20] <tumbleweed> given the limitations of G+ hangouts, I'm not too concerned about that possibility
[11:20] <seb128> Laney, well, UDS is the right venue, but you better want to split that in subtopics
[11:21] <Laney> anyway, we need to know by Thursday whether Feature Freeze is happening
[11:21] <seb128> right
[11:21] <tumbleweed> seb128: I'd have expected a session like Laney describes to be the first thing on the agenda, with split-out sessions being scheduled from it
[11:21]  * ogra_ only saw positive feedback for rolling everywhere ... apart from the flavours on ubuntu-devel
[11:21] <seb128> tumbleweed, anyone is welcome to create a blueprint
[11:21] <tumbleweed> we have, of course, already had a lot of discussion so we know many of the details we want to talk about
[11:22] <seb128> tumbleweed, seems like nobody did so far, that includes you ;-)
[11:22] <tumbleweed> fair, but I'm not the one driving this
[11:22] <seb128> e.g feel free to create one I would say
[11:22] <seb128> who is?
[11:22] <tumbleweed> rick?
[11:23] <seb128> right, maybe ping him when he gets online
[11:23] <tumbleweed> though, I guess if canonical is convinced that they aren't supporting non-LTS releases, there's not much to discuss
[11:24] <seb128> seems like it would be easy to add that session in the first foundation slot
[11:24] <seb128> and move the +1 one to 6pm
[11:25] <Laney> Riddell: are you going to be around for this UDS/
[11:25] <Laney> I think that it would be a really good idea to have a flavours/rolling session ...
[11:25] <ogra_> ++
[11:27] <Riddell> Laney: I guess so
[11:28] <Riddell> Laney: it's on my todo list for today to work out what session kubuntu needs
[11:28] <Laney> fair
[11:28] <Riddell> Laney: if you register one that'll shorten my todo list :)
[11:28] <Laney> I just expect it's something that would benefit from some pushing from your end
[11:28] <Laney> well I'd rather not as I'm not involved with any flavour
[11:29] <Laney> other than being concerned for their success ;-)
[11:29] <Riddell> fair enough
[13:15] <xnox> are the "daily CD heath check" mini-reports published on p.c.c/~ubuntu-archive/ somewhere? at least as a single file which gets updated similar to raring_probs?
[13:23] <ogra_> xnox, i think they are only maikled by default
[13:23] <ogra_> *mailed
[13:26] <xnox> ogra_:  it would be nice to "| tee somewhere/health-check.txt |" in whatever mails it ;-)
[13:26] <ogra_> livecd-rootfs, feel free to hack :)
[13:27] <ogra_> in the BuildLiveCD script
[13:49] <cjwatson> Eh, no, it's not in BuildLiveCD
[13:49] <cjwatson> it's in lp:ubuntu-cdimage bin/daily-checks
[13:50] <cjwatson> You're thinking of the livefs build failure mails
[13:54] <ogra_> cjwatson, oops, yeah, sorry
[15:00] <dobey> hi all. any chance we could get the tomboy SRUs for bug #1115460 pushed to updates today? i know it's not quite 7 days yet, but would be nice to get it pushed out to reduce the chances of people trying to set up notes sync with a server that won't exist in a couple days.
[15:00] <ubot2`> Launchpad bug 1115460 in tomboy (Ubuntu Quantal) "Ubuntu One notes sync is going away" [Undecided,Fix committed] https://launchpad.net/bugs/1115460
[17:15] <tseliot> infinity: hi, can you approve nvidia-graphics-drivers-313-updates and nvidia-settings-313-updates in NEW, please?
[19:47] <antarus> cjwatson: why do all the Ubuntu announcements make me a sad panda?
[20:46] <slangasek> any SRU members around who could look at the apt in precise?  It's needed to fix the mess that the lts-quantal stack made of things for multiarch
[20:47] <slangasek> (precise-proposed unapproved queue)
[20:59] <blitzkrieg3> Is anyone on the SRU team able to move bug 780602 to Fix Released?
[21:00] <ubot2`> Launchpad bug 780602 in OEM Priority Project precise "nm-applet leaks memory and stops functioning after a while" [High,In progress] https://launchpad.net/bugs/780602
[21:00] <blitzkrieg3> I've verified that the memory leak is plugged
[22:56] <infinity> slangasek: Accepted, and thanks for following up with the auto-remove fix, I was about to do the same thing. ;)
[23:02] <infinity> slangasek: I can haz the same upload to Q, or should I do that one myself when I wake up?
[23:03] <slangasek> infinity: well, I'm regarding it as lower priority for quantal
[23:56] <slangasek> blitzkrieg3: looking over the bug log for bug #780602, there's a comment from bdmurray about an NM crash that happens only with the precise-proposed version
[23:56] <ubot2`> Launchpad bug 780602 in OEM Priority Project precise "nm-applet leaks memory and stops functioning after a while" [High,In progress] https://launchpad.net/bugs/780602
[23:56] <slangasek> blitzkrieg3: so if there's a regression, we don't really want to publish it...
[23:56] <blitzkrieg3> slangasek: yes, but cyphermox says it's unrelated
[23:57] <blitzkrieg3> slangasek: if we can't publish it, can we pull it?
[23:57] <bdmurray> slangasek: I'm fine with publishing it
[23:57] <slangasek> blitzkrieg3: where has he said that?  it's not in the bug log
[23:57] <blitzkrieg3> slangasek: I know, it was over irx
[23:57] <blitzkrieg3> irc
[23:58] <slangasek> I would prefer to have these comments in the historical record :)
[23:59] <blitzkrieg3> slangasek: it's funny, I was just complaining earlier today how no one puts enough info into lp
[23:59] <blitzkrieg3> slangasek: if it makes sense I'll circle back with cyphermox and bdmurray and tell them to update the bug


[06:31] <LocutusOfBorg> ubottu, -->  /topic #ubuntu-release-party "Nope, it's not out yet.  Check back later today"
[06:31] <LocutusOfBorg> but dax is :)
[06:33] <dax> can't make the topic too specific, we'd miss out on all the people asking if it's out yet
[06:35] <el> topics don't get read though
[06:38] <valorie> amen to that
[06:39] <valorie> even when reminded!
[08:53] <LocutusOfBorg> topic? oh sorry
[08:53] <LocutusOfBorg> I was meaning ubottu answer
[08:54]  * LocutusOfBorg fixes that
[13:30] <popey> Speaking of topics. We should update the /topic in #ubuntu to add 17.10 now :)
[13:39] <LocutusOfBorg> Unit193, ^^
[14:18] <Pici> I guess I should poke ubottu
[14:26] <Pici> factoids updated
[14:26] <Pici> (and the channel topic)
[18:01] <ikonia> LocutusOfBorg: do you need anything from the ops team at the moment ?
[18:49] <el> ahoneybun: fix your autoidentify plz :P
[18:49] <el> irccloud does sasl afaik?
[18:56] <ahoneybun> why?
[18:59] <el> so you can have voice here
[19:00] <el> it'll also help for joining channels which require you to be identified, or have your account +I
[19:01] <el> most importantly you can't op yourself without identifying
[20:30] <LocutusOfBorg> ikonia, not anymore :)
[20:34] <krytarik> LocutusOfBorg: It's because this channel has a no-idle policy - unless you're an op. :P
[21:14] <LocutusOfBorg> sorry!
[21:14] <LocutusOfBorg> indeed, my client automatically connects me here until I part
[21:14] <LocutusOfBorg> sorry
[21:45] <ikonia> @mark TJ- #ubuntu really solid few hours effort helping in #ubuntu - work marking to show very positive contribution
[22:01] <valorie> ikonia: nice!


[11:58] <flocculant> cyphermox: thanks :) though both 32/64 bit hang on shutdown (VB)
[12:04] <DanChapman> \o/ i see some green https://jenkins.qa.ubuntu.com/view/Ubiquity/view/All/job/ubiquity_ap-ubuntu_devel_daily-test_english_default/ although it seems all the i386 tests failed :-/
[12:05] <flocculant> DanChapman: are the new running tests going to show up there?
[12:06] <flocculant> or is that just because the tests got fixed ?
[12:06] <DanChapman> flocculant: errm only for Ubuntu afaik. nuclearbob is going to put the flavours up somewhere else.
[12:06] <flocculant> ok
[12:07] <flocculant> obviously not interested in ubuntu results - just flavours :)
[12:07] <DanChapman> of course :-)
[12:07] <flocculant> and by flavours - obviously mean Xubuntu :D
[12:07] <flocculant> anyway - back of out for a while
[15:32] <DanChapman> nuclearbob, balloons hey! so i noticed the ubiquity jobs started running again \o/ but all the i386 tests failed. I just ran them locally and it seems there is no  unity7 or window decorations https://drive.google.com/file/d/0BwhxYaiA7z1qTzFyaU5LQ2s2RUE/view?usp=sharing
[15:33] <DanChapman> so the test fails when it hasn't got focus on a dialog
[15:33] <DanChapman> s/hasn't/can't
[15:33] <balloons> wild.. no decorations, but only on i386?
[15:33] <nuclearbob> DanChapman: that would explain the errors I saw. I ran the test, but hadn't actually watched the output yet
[15:33] <nuclearbob> yeah
[15:33] <DanChapman> now is that a unity7 or compiz issue
[15:33] <nuclearbob> either way it sounds like the automated tests found us a good bug?
[15:34] <balloons> it's possible to auto-take screenshots now with AP -- does this work out ok with these tests?
[15:35] <DanChapman> nuclearbob: Yep looks like it did find a good bug.
[15:35] <DanChapman> balloons: in the log i see ERROR testresult:44 - Binary attachment: "FailedTestScreenshot" (image/png) but i can't see it in the artifacts anywhere. Maybe the runner needs to learn it exists??
[15:36] <balloons> are you running with subunit streams?
[15:36] <DanChapman> balloons: and yes it is only on i386 todays amd64 seems fine
[15:36] <DanChapman> err not sure
[15:36] <balloons> you won't get binary on the console
[15:36] <balloons> :-)
[15:38] <balloons> just add -f subunit
[15:38] <balloons> and make sure you are writing results to a file
[15:38] <balloons> then use trv to view the file; and you'll get some sane viewing of the logs
[15:39] <balloons> bzr branch lp:trv
[16:28] <flocculant> balloons: ha ha
[16:28] <flocculant> we has good image - that fails to shutdown in virtual environment but is good on hardware
[16:31] <flocculant> gnome fails on shutdown too - not checked hardware
[16:31] <flocculant> would try ubuntu but that's still got the fubar ubiquity/nm thingy
[18:27] <nuclearbob> DanChapman, balloons: is anybody looking at the adt ubiquity tests, like this one: https://jenkins.qa.ubuntu.com/job/wily-adt-ubiquity/
[18:28] <balloons> that would be a question for pitti I think; I'm not sure what's in those tests atm actually
[18:29] <balloons> probably just build stuff
[22:00] <sethj> I found a bug in the Ubuntu Ubiquity's slideshow. Would that be filed against ubiquity itself or another package? I don't see the slideshow in the code anywhere..
[22:03] <knome> sethj, ubiquity-slideshow-ubuntu please
[22:04] <sethj> aha, thanks knome!
[22:05] <knome> np
[22:05] <knome> also, please link to the bug once you've filed and i'll look at it
[22:10] <sethj> knome, looks like someone beat me by a few days: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1495212, I guess the fix just hasn't made it into the daily image yet.
[22:11] <knome> yep, should be in tomorrows image
[23:34] <sak> Ok, looks like me and bazaar are becoming best of friends :)
[23:35] <sak> Just wondering, where there be any testcases for snappy?


[02:40] <bigjools> shadeslayer: your libdc1394 fix for digikam worked
[02:41] <bigjools> shadeslayer: I don't get anything in the device notifier when I plug in, FWIW (not related to this fix)
[08:06] <Riddell> bonjour
[11:10] <shadeslayer> bigjools: weird, I do get a notification
[11:11] <shadeslayer> /tmp/buildd/digikam-2.5.0/extra/kipi-plugins/advancedslideshow/widgets/slideshowgl.cpp:249:18: error: 'GL_PROJECTION' was not declared in this scope
[11:13] <shadeslayer> !find GL/gl.h
[11:31] <Riddell> shadeslayer: on arm?  arm doesn't do GL
[11:31] <Riddell> it does gles
[11:31] <Riddell> so kipi-plugins needs fixed to detect that and turn off GL upstream or just add a config option or patch to disable it downstream
[11:37] <shadeslayer> hmm
[11:39] <Riddell> shadeslayer: how does digikam-2.5.0/extra/kipi-plugins relate to kipi-plugins, is it a copy of the code?
[11:40] <shadeslayer> don't think so, lemme check
[11:45] <shadeslayer> heh
[11:45] <shadeslayer> Riddell: digikam is the source package that provides kipi-plugins
[11:45] <shadeslayer> there's no seprate kipi-plugins package
[11:45] <shadeslayer> s/package/source/
[11:45] <kubotu> shadeslayer meant: "there's no seprate kipi-plugins source"
[11:46] <Riddell> shadeslayer: oh ok
[11:47] <Riddell> so aye, fix it upstream or downstream-with-moaning-to-upstream as you see fit
[11:47] <shadeslayer> Riddell: uh, how would one go about doing that?
[11:48] <Riddell> shadeslayer: fixing it?  by adding a patch which only gets applied on arm that disables the advancedslideshow directory in CMakeLists.txt I expect is easiest
[11:49] <Riddell> although I don't think I've used platform specific patches with quilt
[11:50] <Riddell> or just set whatever variable advancedslideshow needs to compile to false, I expect there's a variable a bit like GL_ENABLED that can be set
[11:50] <Riddell> on arm
[11:50] <shadeslayer> I'll look into it
[11:57] <shadeslayer> Riddell: could you upload https://launchpad.net/~rohangarg/+archive/experimental/+files/libdc1394-22_2.1.3-4ubuntu1.dsc ?
[11:59] <tsdgeos> Riddell: http://codereview.qt-project.org/#change,19692 <-- real crash fix for the evil thai fonts stuff
[12:03] <BluesKaj> Hiyas all
[12:25] <shadeslayer> Riddell: dpkg-architecture -qDEB_HOST_ARCH would return 'armhf' on a armhf builder right?
[12:25] <shadeslayer> in which case, how does one use the or operator in debian/rules ? :P
[12:26]  * shadeslayer doesn't see a way to use the or operator in makefiles
[12:46]  * shadeslayer crosses fingers
[13:24] <agateau> Riddell: hey, it seems we have two different packages for zanshin
[13:24] <agateau> Riddell: one by you, updated by me, one by fabo
[13:29] <agateau> fabo: are you going to package zanshin 0.2.1? (I have it in my PPA right now)
[13:31] <shadeslayer> digikam building on ARM, and I'm going out for a while
[13:31] <shadeslayer> cya
[13:46] <apachelogger> shadeslayer: oh boy, you should have announced your dev interview on thursday, now I got too much time to come up with questions :P
[13:47] <apachelogger> they are the evil
[13:48] <ScottK> Did bulldog98_ decide if he wanted to piggyback onto the same kubuntu-dev meeting?
[13:48]  * ScottK recalls some discussion of it.
[13:51] <apachelogger> he'd better not, my questions are too dangerous this time around, could totally cause brain dmg
[14:02] <ScottK> As long as he goes second, you'll be too tired.
[14:15] <apachelogger> ScottK: well, I only have to paste questions, hardly tiresome ;)
[14:16] <ScottK> Well, if you aren't going to analyze the answers it'll go much easier on shadeslayer.
[14:16] <apachelogger> I trust others will do that for me
[14:18] <Riddell> agateau: ah zanshin is still on my todo list, let me know what you want done with it
[14:20] <agateau> Riddell: it's a bit weird: zanshin 0.2.0 is in universe, as a brand new package created by fabo, but I have 0.2.1 in my PPA, as an update to the Oneiric package you created... not sure what to do (other than putting 0.2.1 in universe)
[14:21] <Riddell> tsdgeos: ug remind me again how I recover my password for qt-projects?
[14:21] <Riddell> agateau: 0.2.1 in universe seems optimal :)
[14:22] <Riddell> shadeslayer: oh nice catch on the digikam fix
[14:22] <agateau> Riddell: we should merge the description from fabo package, it looks nicer, want me to do it?
[14:23] <Riddell> agateau: sure
[14:38] <agateau> Riddell: what should I do with zanshin changelogs? our package has history from 0.1+svn versions, fabo package has 0.2.0-1 as its initial release.
[14:39] <agateau> or rather: fabo package only entry in changelog is 0.2.0-1, initial release
[14:39] <fabo> agateau: Riddell: you've got the situation in good hand :)
[14:40] <agateau> fabo: ?
[14:40] <fabo> you don't need me anymore, right?
[14:41] <fabo> agateau: I can update to latest one and upload if you want
[14:41] <agateau> fabo: sounds good to me :)
[14:41] <fabo> agateau: deal :)
[14:51] <Riddell> ug, qt-project.org is too hard to use :(
[14:52] <Riddell> I've only been using the web for 16 years why is it hard to make a login I can use
[14:57] <Riddell> "The existing username and/or password you submitted are not valid" what does that even mean?
[14:57] <Riddell> does my username exist or not
[15:07] <ScottK> They won't tell you for sekurity reasons.
[15:17] <tsdgeos> Riddell: to be honest no idea how to get the password
[15:17] <tsdgeos> Riddell: you sure you had one?
[15:17] <Riddell> I think I'm nearly there
[15:17] <Riddell> no.  I'm not.
[15:17] <Riddell> I can log into https://qt-project.org/
[15:18] <Riddell> but not http://codereview.qt-project.org
[15:18] <tsdgeos> really?
[15:18] <tsdgeos> i think it's different stuff thouh
[15:18] <Riddell> could changing my password on https://qt-project.org/ mean I need to wait for it to be synced to http://codereview.qt-project.org ?
[15:18] <tsdgeos> codereview sahres the password with the bugtracker
[15:19] <tsdgeos> can you log into https://bugreports.qt-project.org ?
[15:21] <Riddell> yes but it's a different password right enough
[15:21] <Riddell> ooh and it works for http://codereview.qt-project.org
[15:21] <Riddell> phew
[15:22] <Riddell> I think I'll write those down for extra security
[15:22] <Riddell> tsdgeos: do you know if QWidget has a maintainer in qt-project now?
[15:22] <Riddell> fregl: does Qt have such a think as a designer? (query from canonical designer)
[15:23] <tsdgeos> Riddell: no idea
[15:23] <fregl> Riddell: Qt no, Nokia yes
[15:23] <Riddell> fregl: anyone suitable if canonical designers want to discuss the finer details of sliders and scrollbars?
[15:24] <fregl> Riddell: in qml or qwidget?
[15:24] <Riddell> fregl: qwidget
[15:25] <Riddell> qt dudes, what am I doing wrong here with git? http://paste.kde.org/439736/
[15:25] <Riddell> it's what codereview told me to do to get a patch
[15:25] <fregl> not sure anyone currently is up to the task. do they want the overlay stuff that they did to gtk?
[15:26] <fregl> Riddell: this needs to be done in an existing checkout of the git repo
[15:27] <Riddell> fregl: it wasn't clear but I think they're looking at changing single click to be "move to that point" not "move towards that point"
[15:28] <fregl> Riddell: why does that need designers talking to us? I guess none of us here is going to implement such a feature, so if canonical wants it, they'll most likely have to contribute it
[15:28] <Riddell> fregl: yes and they're wanting to know if it can go upstream
[15:28] <fregl> we are currently more than busy getting qt5 into shape...
[15:29] <fregl> ah, that is a valid concern, generally I think that is something we'd accept
[15:30] <Riddell> groovy, I'll tell them qwidget is not well maintained but if they submit it chances are someone will look at it
[15:30] <Riddell> I can't find a way to just download a patch from http://codereview.qt-project.org
[15:30] <fregl> yes, reviews will definitively be done
[15:30] <fregl> I don't think you can download just a patch
[15:31] <fregl> you can look at the diff and you can grab it with the fetch...
[15:31] <Riddell> hmm, that means keeping a large qt checkout around, ho hum
[15:31] <fregl> yes
[15:32] <fregl> but that's what everyone wants anyway, right :p
[15:32] <Riddell> it's your devious plan to turn us all into Qt hackers!
[15:33] <fregl> on a more serious note, I agree that it's silly that you can't download a patch
[15:34] <fregl> sounds like a missing gerrit feature
[15:35] <fregl> Riddell: you could grab the same patch from gitorious since that mirrors it anyway. of course only after it was approved. that is the right way to go anyway...
[15:35] <Riddell> fregl: oh?  it's this I'm after http://codereview.qt-project.org/#change,19692
[15:35] <Riddell> where can I get that in gitorious
[15:35] <Riddell> ?
[15:37] <fregl> Riddell: well, it says merged, since gitorious mirrors all commits... http://qt.gitorious.org/qt/qt but how to find a commit there is a mystery to me
[15:38] <fregl> http://qt.gitorious.org/qt/qt/commit/827e5c4c689d4ecb4f8c1ab48c9a7ab712fe2ca7
[15:38] <fregl> well, it was the newest commit
[15:39] <fregl> so qt-project == people actively working on patches => gitorious == read only mirror as soon as a patch is in, of course that doesn't have patches that are being reviewed
[15:52] <Riddell> lovely, thanks fregl
[15:52] <fregl> np
[16:27] <shadeslayer> apachelogger: nooooo
[16:27]  * shadeslayer is scared now
[16:28] <shadeslayer> something came up tomorrow night, which is why I chose Friday
[16:29] <shadeslayer> ScottK: see libdc1394-22 FFe + Sync bug
[16:29] <shadeslayer> bug 954154
[16:33]  * shadeslayer pokes pbuilder-dist to pick it up
[16:35] <ScottK> shadeslayer: Let's do it.
[16:35] <shadeslayer> :D
[16:37] <shadeslayer> can you close multiple bugs when syncing packages?
[16:55] <micahg> shadeslayer: yes, pass -b multiple times to syyncpackage
[16:55] <micahg> *syncpackage
[16:55] <shadeslayer> cool!
[16:55]  * shadeslayer doesn't have sync rights, was just interesting
[16:55] <shadeslayer> *interested
[16:56] <micahg> shadeslayer: you're not a kubuntu dev yet?
[16:56] <shadeslayer> *cough* nope *cough*
[16:56] <shadeslayer> micahg: I've applied, meeting on Friday
[16:57] <shadeslayer> *hopefully* apachelogger won't massacre me
[17:01] <Riddell> shadeslayer: just give him some jagermeister before the meeting
[17:01] <shadeslayer> Hmm, I guess I should start making arrangements for that :D
[17:08] <apachelogger> you'd better
[17:08] <apachelogger> also you should read the entire debian policy to prepare
[17:11] <ScottK> micahg: libdc1394-22 is core anyway, so kubuntu-dev wouldn't help this particular one.
[17:15] <shadeslayer> LS
[17:15] <shadeslayer> :S
[17:16] <apachelogger> shadeslayer: you realize that does not work with caps on? :P
[17:16] <shadeslayer> apachelogger: I meant to type :S
[17:16] <shadeslayer> and accidently hit L
[17:22] <ScottK> shadeslayer: That doesn't bode well for Friday.
[17:22] <shadeslayer> nah, just trying to multitask ...
[17:23] <shadeslayer> and stop scaring me!
[17:23] <ScottK> shadeslayer: Give me the syncpackage command that gives you credit for the sync and closes all the bugs and I'll run it.
[17:23] <shadeslayer> hehe
[17:23] <ScottK> shadeslayer: Where would be the fun in that.
[17:23] <ScottK> shadeslayer: Not kidding.
[17:23] <ScottK> (about the syncpackage thing)
[17:23] <ScottK> I'm too tired to look it up.
[17:23] <shadeslayer> yeah, give me a minute
[17:27] <ScottK> micahg: Who's responsible for the annoying popup about some test profile thing in FF in precise?
[17:28] <micahg> ScottK: which version are you running?
[17:28] <ScottK> Whatever is in the archive.
[17:28] <shadeslayer> simulating
[17:28] <micahg> it's chrisccoulson either way, but if it's on in precise ATM, that's a big bug I think, as we shouldn't be enabling that in the stable firefox releases
[17:29] <shadeslayer> ah
[17:29] <ScottK> OK.  I dismissed it.  We'll see if it comes back.
[17:29] <shadeslayer> seems like Riddell uploaded my package
[17:30] <ScottK> --force and you're done then.
[17:30] <shadeslayer> yeah
[17:31] <shadeslayer> ScottK: syncpackage -d unstable -V 2.2.0-2 -s rohangarg -b 947785 -b 835687 -b 462453 -b 379088 --force libdc1394-22
[17:31] <shadeslayer> oh
[17:31] <shadeslayer> need to add another bug to that
[17:31] <shadeslayer> ScottK: syncpackage -d unstable -V 2.2.0-2 -s rohangarg -b 947785 -b 835687 -b 462453 -b 379088 -b 947785 --force libdc1394-22
[17:32] <shadeslayer> ... added the same bug twice ... *headdesk*
[17:32] <shadeslayer> first command is good to go
[17:33] <shadeslayer> omg ... digkam arm build at 18%
[17:33] <micahg> umm, I've never seen -V used with syncpackage before
[17:33] <micahg> but it's a valid option
[17:33] <shadeslayer> micahg: I like to be verbose
[17:33] <shadeslayer> less prone to errors
[17:33] <micahg> shadeslayer: -v is for verbose :P
[17:33] <shadeslayer> nope
[17:33] <shadeslayer> well
[17:34] <shadeslayer> uh yeah ...
[17:34] <micahg> shadeslayer: :)
[17:34]  * shadeslayer goes back to code
[17:38] <apachelogger> shadeslayer: so you meant to type S?
[17:38] <shadeslayer> apachelogger: no, :S
[17:39] <apachelogger> so I don't get it, stop confusing me
[17:39] <shadeslayer> :>
[17:41] <ScottK> shadeslayer: Done.
[17:41] <shadeslayer> yay
[17:52] <apachelogger> shadeslayer: so you confuse apachelogger, use wrong options in syncpackage commands, what else?
[17:52] <shadeslayer> apachelogger: wrong options in syncpackage?
[17:52] <apachelogger> -V for verbose
[17:53] <shadeslayer> huh? -V is used for specifying a version
[17:53]  * shadeslayer does not follow
[17:53] <apachelogger> "I like to be verbose"
[17:53] <shadeslayer> yes, by that I meant, I like specifying which version to sync
[17:54] <apachelogger> yeah, right, easy to say now :P
[17:54] <shadeslayer> -.-
[18:53] <ScottK> Riddell: Would you please look at qscintilla2 in New.  It's my upload, so I can't.
[19:03] <Riddell> ScottK: ok
[19:04] <ScottK> Riddell: Thanks.
[22:01] <MountainX> a standard install of Kubuntu 12.04 beta 1 (via alternate installer) appears to be missing /usr/share/applications/mimeinfo.cache, /usr/share/applications/defaults.list and ~/.local/share/applications/mimeapps.list. Can anyone else confirm this?
[22:16] <ScottK> MountainX: Do you have desktop-file-utils installed?
[22:16] <MountainX> checking...
[22:17] <MountainX> ScottK: no. "Package `desktop-file-utils' is not installed and no info is available."
[22:17] <ScottK> It doesn't seem like there's anything Kubuntish that would pull that in.
[22:17] <ScottK> That's what provides /usr/share/applications/defaults.list
[22:18] <ScottK> It looks like .local/share/applications/mimeapps.list is a gdm thing.
[22:19] <MountainX> ScottK: do you recommend I install desktop-file-utils in Kubuntu 12.04?
[22:19] <ScottK> I don't know why you think you need the files you're missing.
[22:20] <ScottK> I am guessing mimeinfo.cache is generated on system.
[22:21] <MountainX> ScottK: I am trying to solve a problem where Firefox doesn't know how to open downloaded files (or containing folders). My best guess so far is that some mime-type info is missing.
[22:22] <ScottK> I'd install desktop-file-utils then.
[22:22] <MountainX> Rekonq has the same (or similar) problem on my system.
[22:22] <ScottK> Rekonq is probably broken for unrelated reasons that shadeslayer will claim aren't it's fault.
[22:22] <ScottK> He'll be wrong.
[22:23] <MountainX> haha. yes, yesterday's conversation clued me in that these may be two separate issues.
[22:25] <MountainX> # update-desktop-database returns Error in file "/usr/share/applications/kde4/ktp-send-file.desktop": "all/allfiles" is an invalid MIME type ("all" is an unregistered media type)
[22:27] <ScottK> Hmm.  Another shadeslayer special.
[22:28] <ScottK> Hopefully his ears are burning and he wakes up.
[22:28] <MountainX> ok. thanks


[00:01] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: SuperTuxKart Devs Detail Several Upcoming Improvements @ https://www.omgubuntu.co.uk/?p=133983 (by Joey Sneddon)
[02:44] -SwissBot:#ubuntu-news- ::Planet:: Benjamin Mako Hill: I have no friends or colleagues @ https://mako.cc/copyrighteous/i-have-no-friends-or-colleagues
[11:44] -SwissBot:#ubuntu-news- ::Planet:: Valorie Zimmerman: Going to Akademy! @ http://linuxgrandma.blogspot.com/2018/08/going-to-akademy.html (by<EMAIL_ADDRESS>(Valorie Zimmerman))
[13:11] -SwissBot:#ubuntu-news- ::Softpedia:: LibreOffice 6.0.6 Office Suite Released with 55 Bug Fixes, Download Now @ https://news.softpedia.com/news/libreoffice-6-0-6-office-suite-released-with-55-bug-fixes-download-now-522212.shtml (by Marius Nestor)
[13:28] -SwissBot:#ubuntu-news- ::Softpedia:: Ubuntu 16.04.5 LTS (Xenial Xerus) Released as Last in the Series, Download Now @ https://news.softpedia.com/news/ubuntu-16-04-5-lts-xenial-xerus-released-as-last-in-the-series-download-now-522213.shtml (by Marius Nestor)
[13:35] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Opera Browser is Now Available in the Ubuntu Snap Store @ https://www.omgubuntu.co.uk/?p=133991 (by Joey Sneddon)
[13:41] -SwissBot:#ubuntu-news- ::Softpedia:: Opera Web Browser Is Now Available as a Snap on Ubuntu, Other Linux Distros @ https://news.softpedia.com/news/opera-web-browser-is-now-available-as-a-snap-on-ubuntu-other-linux-distros-522215.shtml (by Marius Nestor)
[14:09] -SwissBot:#ubuntu-news- ::Softpedia:: Arch Linux 2018.08.01 Out Now with Linux Kernel 4.17.11, Latest Security Updates @ https://news.softpedia.com/news/arch-linux-2018-08-01-out-now-with-linux-kernel-4-17-11-latest-security-updates-522216.shtml (by Marius Nestor)
[14:29] <guiverc> https://lists.ubuntu.com/archives/ubuntu-announce/2018-August/000235.html
[14:30] <guiverc> I'm putting it up on fridge - yell now if it's a no...
[14:34] <guiverc> the notice mentions 'Ubuntu team is pleased to announce' -- this is usually Ubuntu Release team  --- leave as Ubuntu team??
[14:34] <pleia2> yeah, you don't want to edit their words
[14:36] <guiverc> :)   [my preference anyway; less likely to make a mistake when I don't touch...]
[14:36] <guiverc> thanks pleia2 :)
[14:44] <guiverc> (turns out I have a choice; once as Ubuntu Release Team, once as Ubuntu team)
[14:48] <guiverc> http://fridge.ubuntu.com/2018/08/02/ubuntu-16-04-5-lts-released/
[15:07] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Ubuntu 16.04.5 LTS Released, Available to Download Now @ https://www.omgubuntu.co.uk/?p=133896 (by Joey Sneddon)
[15:17] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu 16.04.5 LTS released @ http://fridge.ubuntu.com/2018/08/02/ubuntu-16-04-5-lts-released/
[16:39] -SwissBot:#ubuntu-news- ::Fridge:: Ubuntu 16.04.5 LTS released @ http://fridge.ubuntu.com/2018/08/02/ubuntu-16-04-5-lts-released/ (by guiverc)
[19:31] -SwissBot:#ubuntu-news- ::Softpedia:: GNOME and GIMP Receive $400K from Handshake Decentralized Certificate Authority @ https://news.softpedia.com/news/gnome-and-gimp-receive-400k-from-handshake-decentralized-certificate-authority-522218.shtml (by Marius Nestor)
[21:30] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Podcast from the UK LoCo: S11E21 â The Twenty-One Balloons - Ubuntu Podcast @ http://ubuntupodcast.org/2018/08/02/s11e21-the-twenty-one-balloons/
[21:30] -SwissBot:#ubuntu-news- ::Planet:: Lubuntu Blog: Lubuntu 16.04.5 has been released! @ https://lubuntu.me/xenial-5-released/
[23:15] <Bashing-om> guiverc: Had a death in the family last night - I may be scarace this week end . No details yet .
[23:17] <guiverc> sorry to hear that Bashing-om - forget UWN & deal with family (and your own grief); do the things that matter to you, and in your own time...
[23:21] <Bashing-om> well, he "was' married to my middle daughter, and the father of 2 of my grand kids . I personally had little use for him while they were marrierd .. and even less now . But of course the kids and ex are taking it hard .
[23:22] <Bashing-om> guiverc: As you say UWN: 20 minutes here and there :)
[23:33] -SwissBot:#ubuntu-news- ::Softpedia:: GNOME 3.30 Desktop Environment Enters Beta, Final Release Arrives September 5 @ https://news.softpedia.com/news/gnome-3-30-desktop-environment-enters-beta-final-release-arrive-september-5-522221.shtml (by Marius Nestor)
[23:48] <guiverc> it doesn't matter much what you felt for him, but you'll emotional-hurt.. because you feel for your daughter & grand-kids, and you'll feel her pain (even if unrecognized at times)..  thanks for telling me, but you do what's best for you & your family (when you need to..)
[23:50] <Bashing-om> guiverc: Ack .. appreciate the sentiments .


[00:17] <sarnold> bdmurray: my guess is that should be on python-apt instead of apt; I wonder what else this'll break though...
[02:08] <arraybolt3> Just making sure that there's not something I don't know about here. I believe that Doxyfiles (Doxygen configuration files) that have the usual commented "how to use this file" stuff in them are always under the GPLv2, as the license states "Permission to use, copy, modify, and distribute this software and its documentation under the terms of the GNU General Public License is hereby granted."
[02:08] <arraybolt3> Since some of the software's documentation is put into the Doxyfile, I think that makes it GPLv2.
[02:09] <arraybolt3> However, at the same time, it says "Documents produced by doxygen are derivative works derived from the input used in their production; they are not affected by this license." I don't know if this seemingly template-based Doxyfile I'm seeing in a package I'm working on is the output of Doxygen or not. What license is this under - the package's main license, or the GPLv2 of Doxygen?
[02:09] <arraybolt3> (This is the Doxyfile for libfm-qt.)
[02:12] <arraybolt3> FWIW I looked through the source code of Doxygen in GitHub and could not find the documentation I was seeing in the Doxyfile, though I saw others had suspiciously similar-looking Doxyfiles.
[02:12] <arraybolt3> I *did* find the documentation on the Doxygen website though.
[06:52] <tsimonq2> #pilot in
[06:52]  * tsimonq2 figures out the correct syntax these days...
[06:53] <arraybolt3> tsimonq2: Oh nifty, now you can maybe help me with my Doxygen question :P
[06:55] <tsimonq2> arraybolt3: I'd be interested in where you find "Documents produced by doxygen are derivative works derived from the input used in their production; they are not affected by this license." and under what context
[06:55] <arraybolt3[m]> Simon Quigley: Under the "Doxygen license" section of this page: https://www.doxygen.nl/manual/index.html
[06:56] <tsimonq2> So, libfm-qt doesn't have a code copy of Doxygen itself right, just a document produced by Doxygen?
[06:56] <arraybolt3[m]> I don't know.
[06:56] <tsimonq2> In that case I'd say it's pretty explicitly "under whatever license the input data comes from"
[06:57] <arraybolt3[m]> The code is the configuration file, which appears to have been built from a template and manually edited.
[06:57] <arraybolt3[m]> I would think yes because I've not been able to find the code in question in Doxygen's code, but I also don't know where people get the template from.
[06:58] <arraybolt3[m]> I'd think that I would at least have found the snippet within the code of the project in strings if it was generated, so the fact that I couldn't find it in the code leads me to believe that maybe the template is somewhere else and is under Doxygen's GPL-2 license.
[06:59] <tsimonq2> @pilot in
[06:59] <tsimonq2> darn, maybe the bot is broken, I won't spam too much :/
[07:00] <arraybolt3[m]> Perhaps !pilot in?
[07:00] <arraybolt3[m]> (Bot commands in Ubuntu rooms usually start with !)
[07:00] <tsimonq2> meh I'm not too worried about it
 "The code is the configuration..." <- I would have to see it to make a complete decision, but I'm thinking you're likely fine - if it started in the Doxygen source code and was not *produced* by Doxygen, I'm willing to bet it needs to be GPL-2 with proper attribution
[07:03] <tsimonq2> Hard to say without looking at the file you're talking about ;)
[07:03] <arraybolt3[m]> I can show it easily enough, one moment...
[07:04] <arraybolt3[m]> Simon Quigley: https://termbin.com/kp3t
[07:04] <arraybolt3[m]> (It wouldn't fit in a Matrix message :( )
[07:04] <arraybolt3[m]> Filename is "Doxyfile.in".
[07:05] <arraybolt3[m]> s/./ dot /
[07:07] <tsimonq2> https://www.doxygen.nl/manual/config.html -> "To create the layout file that represents doxygen's defaults, run doxygen with the -l option." -> This is a file produced by Doxygen, or at least one that *can* be produced by Doxygen -> It's covered under the exception
[07:08] <arraybolt3[m]> Gah, that's even the same page I looked at! Just didn't dig deep enough I guess. Alright, thank you!
[07:08] <tsimonq2> No worries, and if I'm wrong someone tell me please ;)
[08:07] <cpaelzer> athos: PG-15 itself was resolved, you can start the related no change rebuilds
[10:55] <rbasak> Where is the magic autopkgtest behaviour that translates "triggers" into apt pinning implemented? I'm looking at a case that succeeds locally but fails due to uninstallable test deps in infrastructure, so I'm trying reproduce the pinning exactly. I see that the autopkgtest-cloud worker sets ADT_TEST_TRIGGERS, but I can't find where that's actually picked up.
[10:57] <rbasak> eg. https://git.launchpad.net/autopkgtest-cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker#n546
[10:58] <rbasak> https://git.launchpad.net/autopkgtest-cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker#n654 looks like it might do it, but I don't see the result in the autopkgtest command line
[11:00] <rbasak> eg<EMAIL_ADDRESS>has ADT_TEST_TRIGGERS set but nothing added to --apt-pocket=proposed
[11:32] <rbasak> It looks like it is supposed to happen via the --apt-pocket flag, but for some reason I haven't figured out, it didn't happen in that test.
[11:36] <laney> rbasak: In autopkgtest itself. autopkgtest-cloud constructs the commandline for that, and then autopkgtest realises it as apt pinning.
[17:28] <bdmurray> Boy, this new desktop installer had me clicking around to see if I could get my exact city.
[17:34] <Eickmeyer> bdmurray: I know your exact city. That's a stretch. XD
[17:38] <bdmurray> Eickmeyer: I managed to click Battle Ground, Washougal, and Salmon Creek...
[17:39] <Eickmeyer> bdmurray: Wasougal surprises me. I might have to download to see if I can find Black Diamond.
[17:40] <Eickmeyer> (not my current town, but where I grew up)


[12:22] <jenda> mdke: ping?
[12:45] <jenda> mdke: ping?
[01:12] <mvirkkil> mdke: I've been away a couple of days. You wrote about running tidy on the docbook. Would you like to elaborate?
[01:19] <robotgeek> mvirkkil: is that after commit?
[01:28] <mvirkkil> robotgeek: What do you mean?
[01:28] <mvirkkil> robotgeek: I'm working on automagic moinmoin->docbook stuff.
[04:43] <robotgeek> mvirkkil: oh great, the SOC project?
[04:44] <robotgeek> mvirkkil: anyways, all the best with it, and hope you all success. It will make our lives much easier :)
[07:11] <nixternal> anyone know who i need to contact to get information about creating a mailing list for a LoCo?
[07:13] <linuxmonkey> Local's Only Crazy Orginization :)
[07:13] <linuxmonkey> lol
[07:16] <robitaille> nixternal:  talk to jdub for mailing lists
[07:16] <nixternal> thx robitaille
[07:17] <Madpilot> hi all
[07:17] <nixternal> hey Madpilot
[07:17] <robitaille> Hi Madpilot
[07:17] <nixternal> didn't see you sneak in
[07:17] <Madpilot> I'm very stealthy sometimes :)
[07:18] <nixternal> ok bye
[07:18] <nixternal> ;)
[07:18] <nixternal> trying to get all this stuff for a Chicago LoCo Team together
[08:37] <mdke> mvirkkil: elaborate how?
[08:45] <mdke> mvirkkil: I just mean that the output xml is rather ugly and hard to work with, if you use tidy to clean it up, it would avoid the user having to do it.
[08:49] <mdke> jenda: pong, pong
[08:50] <jenda> mdke: ah great :) now to remember what I wanted :)
[08:50] <jenda> There's a forums section on ubuntu.com - and I'd like to see the Czech forum there.
[08:50] <mdke> sure
[08:51] <mdke> can you email me?
[08:51] <jenda> yuppers
[08:51] <mdke> thanks
[08:57] <jenda> mdke: sent.
[08:57] <jenda> Thanks
[08:58] <mdke> nixternal: there is an email address on the LoCoTeamHowto page
[08:58] <mdke> nixternal: in fact, all information you ever need is, or should be, there
[08:58] <nixternal> thx mdke
[08:59] <mdke><EMAIL_ADDRESS>[08:59] <nixternal> i think i hit that one also
[08:59] <nixternal> ya..i hit that one also...
[08:59] <nixternal> thx
[09:12] <mvirkkil> mdke: I mean how is it ugly? What would the tidy program do? Usually when I hear people saying that the xml is ugly they mean it's cluttered with namespace declarations, possibly invalid etc. This is not the case here.
[09:23] <mpt__> The element names are longer than in HTML :-)
[09:23] <mpt> Does that count as ugliness?
[09:23] <rob> can the element names be shorten and still mean the same thing?
[09:24] <mvirkkil> rob: nope
[09:24] <rob> icky
[09:25] <rob> how long are we talking?
[09:25] <mvirkkil> rob: <para> instead of <p> ?
[09:26] <mvirkkil> But you could always create a shorter version and convert it.
[09:26] <rob> thats the actual docbook markup, no it can't be shorten without a lot of work (afaik)
[09:26] <rob> yep
[09:26] <rob> but why not then create your own schema?
[09:26] <mvirkkil> But I'm pretty sure  mdke didn't mean this.
[09:27] <rob> Gentoo uses a really simple markup
[09:27] <rob> for its docs
[09:28] <mvirkkil> rob: Well, the idea is to use the moinwiki in the future, and then convert that to docbook. That's what I'm working on.
[09:28] <rob> are you the one working on the SoC project?
[09:28] <mvirkkil> rob: Yup.
[09:29] <rob> ah cool, I was actually going to submit something similar myself, but lack of spare time killed me
[09:30] <mvirkkil> rob: Close to killing me too. Sent it it on the 11th hour.
[09:30] <rob> GuideXML, thats what Gentoo uses, its much simpler and has less tags then docbook
[09:30] <rob> http://www.gentoo.org/doc/en/xml-guide.xml
[09:31] <rob> I think its pretty cool, but its not docbook, so yeah :)
[09:31] <mvirkkil> rob: Quickly browsed through it.
[09:32] <mvirkkil> rob: I see very little sence in using it.
[09:32] <mpt> and then there's MAML
[09:33] <rob> mvirkkil, it is much simpler, thus much easier to learn
[09:33] <mvirkkil> rob: I wouldn't say much, it looks a bit simpler. But not much.
[09:33] <rob> thats the only major benefit
[09:34] <mpt> MAML is crack because it includes built-in support for FAQs, which, almost by definition, you won't know exist until after the help has shipped
[09:34] <rob> mpt, so does docbook (we used it in the first version of the Desktop Guide)
[09:35] <mpt> Well, we already know docbook is crack :-)
[09:35] <mpt> It's just the least evil
[09:35] <rob> heh
[09:35] <rob> yep
[10:14] <mdke> mvirkkil: I mean it isn't nicely laid out with a line per element and indented
[10:49] <mvirkkil> mdke: Ahh.. Pretty printing.
[10:55] <froud> man Dapper is solid
[03:39] <CarlFK> before I create a new wiki page - anyone know of one that talks about upgrading an existing app using apt-get source/wget newwer source... ?
[03:40] <linuxmonkey> CarlFK: we stay away from specific install apps.
[03:40] <linuxmonkey> :)
[03:41] <CarlFK> huh?
[03:41] <CarlFK> I meant a generic version of https://help.ubuntu.com/community/BuildingWineFromSource
[03:42] <linuxmonkey> lol yeah all those  "sudo apt-get build-dep wine" will have to get changed im preaty sure..lol
[03:43] <linuxmonkey> nvm
[03:43] <linuxmonkey> i just read what it was.. brain fart
[05:16] <CarlFK> wget https://help.ubuntu.com/favicon.ico 404 - who's 'problem' is that?
[05:29] <nixternal> CarlFK: seems as if it isn't there at all
[05:29] <jjesse> i think mdke can fix that problem CarlFK
[05:30] <CarlFK> where/how should something like that be reported?  launchpad?
[05:30] <CarlFK> or do I just start shouting about it in -dev? :)
[05:31] <nixternal> lol
[05:31] <jjesse> mdke in this channel is responsible for help.ubuntu.com
[05:31] <jjesse> i don't know if there is something you can file a bug against or not, but ping him and help can fix it
[05:33] <CarlFK> i'll post to u-doc mailist
[06:56] <jjesse> .
[06:56] <nixternal> ..
[06:58] <LaserJock> ...
[06:58] <nixternal> jjesse: kubuntu team has a meeting today..i will be there to listen in...do you want to check it out concerning information for the switching documentation?  maybe see if Riddell has any ideas he might want to add?
[06:59] <jjesse> would love to how 21:00 is just when i'm leaving work today  and i can't stay late due to a softball game
[07:00] <nixternal> ok..did you mean 21:00?  the meeting is 16:00 for me and 17:00 for you...i will be there, so if there is anything you want me to add to their agenda, i can do that and then report it back to you
[07:01] <jjesse> yup 17:00 is when i leave work
[07:01] <nixternal> ahhh
[07:01] <jjesse> i would like to hold off on discussing the switching guide until the three of us can get some more concrete information put together, i'll update a subpage of my wiki page tongiht
[07:01] <nixternal> ok...i can do some reporting or whatever if you need it
[07:02] <jjesse> sure
[07:03] <nixternal> if you want...you can add something to https://wiki.ubuntu.com/Kubuntu/Meetings   agenda, and i will be more then happy to cover the points if needed
[07:03] <jjesse> sure, let me think if there is anything i need
[07:04] <nixternal> great..i am here if needed...drinking coffee and listening the weather report ;)
[07:04] <jjesse> and how is the wheather across the pond?
[07:05] <nixternal> nice today so far...stormed like crazy last night
[07:05] <jjesse> it was windy last night here, cool but windy
[07:05] <nixternal> it is cool today
[07:06] <nixternal> Current weather for Chicago / West Chicago, Dupage Airport : Few clouds at 1800 feet, Temperature: 66F, Pressure: 30.02" Hg, Wind: 12 MPH NE
[07:10] <nixternal> sudo apt-get update | sudo apt-get upgrade    << gnupg update to patch vulnerability
[09:08] <ompaul> jjesse, ahhhh there you are
[09:08] <ompaul> :-)
[09:08] <ompaul> hehe
[09:09] <ompaul> I knew I recognised the name but was not sure from where
[09:11] <jjesse> grin
[09:11] <jjesse> trying to figure why the sparc guide is not on help.ubuntuc.om
[09:22] <ompaul> well I stopped lurking and clicked on docs to ask that question, guess I can say it is in safe hands ;-)
[09:23] <jjesse> yup it is
[09:42] <nixternal> jjesse: you have roxy burger by you at all?
[09:43] <jjesse> nixternal: nope
[09:43] <nixternal> roxies, the outdoor burger joint..
[09:43] <nixternal> i gotta get into benton harbor to get me one...and soon
[10:09] <nixternal> alrighty..got get me some ice cream and snacks b4 the meeting starts...the old !ping !pong is in effect..bbiaf ;)
[10:52] <nixternal> mdke: it seems that an agenda item for the Kubuntu Meeting in 10 minutes is suggesting a KDE/Kubuntu theme and redirectors for doc.kubuntu.org and help.kubuntu.org, whatever they mean by the last..i will be partaking in this meeting...any items need to be suggested or conversed about..and what is the status of the kde theme?
[10:52] <nixternal> i know there is a kde theme in the making
[10:53] <jjesse> i think that was my idea nixternal
[10:53] <nixternal> it has imbrandon's name on it
[10:53] <jjesse> i was hoping we could get the same themes for the help.ubuntu.com wiki
[10:53] <jjesse> and also get a redirect from help.kubuntu.org to help.ubuntu.com
[10:53] <nixternal> i believe they are in the process of porting the themes
[10:53] <jjesse> i think that was the big suggestion and you are correct they are
[10:53] <jjesse> mdke and i spoke about it
[10:53] <nixternal> how did imbrandon's name get on it ;)
[10:54] <nixternal> ok..
[10:54] <jjesse> maybe he suggested it to the agenda
[10:54] <nixternal> i will relay that info during the meeting when that topic comes up
[10:54] <jjesse> thanks
[10:54] <jjesse> getting ready to leave
[10:54] <jjesse> but i know mdke is on top of those issues
[10:55] <nixternal> alright...good luck with the game btw
[10:55] <jjesse> thanks hoping it doesn't rain, looks like it out side
[10:55] <nixternal> it stopped raining here and became really nice outside
[10:55] <jjesse> nice
[10:56] <jjesse> i love that therer are 48 updates to a fresh install of xp service pack 2
[10:56] <nixternal> lol
[10:56] <nixternal> i wouldn't know..i haven't booted xp in a long time
[10:57] <jjesse> i work on it every day
[10:57] <nixternal> hehe
[10:57] <nixternal> as i am sure i will be too just as soon as I decide to start working and stop enjoying the summer ;)
[10:57] <jjesse> grin
[10:57] <jjesse> ok work's over :(


[15:38] <OvenWerks> re: backporting to 14.04... I can't think of anything I would do that with (jackd maybe). I would rather take the line: finish things started with 14.04 with 14.04 as is, but start new projects with 16.06 please.
[15:38] <OvenWerks> The list of known things not right in 14.04 (off the top of my head):
[15:39] <OvenWerks> Calf plugins (there is at least one bug that can destroy speakers)
[15:40] <OvenWerks> EQ10Q plugins, the GUI was broken
[15:41] <OvenWerks> jackd2
[15:41] <OvenWerks> Ardour has 1000s of bug fixes since then
[15:43] <OvenWerks> qjackctl has a new gui that is much more newby friendly as it hides parameters that can get new people in trouble (system not working)
[15:46] <OvenWerks> zynaddsubfx should be added to 16.10 for sure, even in it's present state, it is a better plugin than yoshimi as it is properly set up to have more than one instance running at a time.
[15:46] <OvenWerks> By 16.10 the new version might be out too.
[15:51] <OvenWerks> Most of the things for 14.04 if we were going to do backports... should have been done a year ago. If 14.04 has gotten along with out them so far, no need to start now. I would suggest put that energy into 16.04. The testing will be easier with people here (hopfully) running 16.04 day by day. Testing 14.04 backports will not get done well, just a quick opens,runs does not show any breakage deeper in.
[16:36] <zequence> OvenWerks: Our users are not used to backports, since they aren't getting any
[16:36] <zequence> but, it is actually something you can choose
[16:36] <zequence> It would be good for us to educate our users about that
[16:36] <zequence> So, that they don't update to backports by mistake, if they were not willing to do that
[19:49] <trebmuh> OvenWerks, reading at one of your email on a US ML, you might be able to +1 this : https://github.com/calf-studio-gear/calf/issues/22