[05:54] <ashams> Hello everybody,
[05:54] <ashams> Any one knows how to get some code from git repo, then send it to bzr branch
[05:57] <RAOF> ashams: bzr branch git://wherever.the.git/is ; bzr push lp:wherever/you/want ?
[05:57] <ashams> RAOF: that easy?, thank you :)
[05:58] <wgrant> ashams: What exactly do you want to achieve here?
[05:58] <RAOF> You'll need bzr-git installed for that to work, but that's a quick apt-get away if you don't already have it.
[05:58] <ashams> I want to help with X org team
[05:58] <ashams> there's a lot of things to get from freedesktop
[05:59] <ashams> repos
[05:59] <ashams> to lp
[05:59] <RAOF> Ah.  Most of those should already be mirrored.
[05:59] <wgrant> But LP can do that sort of thing automatically.
[06:00] <RAOF> And we don't generally use Launchpad for hosting the X stuff; we use git.debian.org :)
[06:00] <ashams> wow, I've missed a lot :(
[06:00] <ashams> great, so no need for this now
[06:01] <ashams> Greatings :)
[06:02] <ashams> wgrant, RAOF, Thank you
[06:40] <dholbach> good morning
[06:51] <pmjdebruijn> mornin
[06:55] <micahg> bdrung: ping
[07:19]  * micahg fishes for an awake DMB member other than himself...
[08:02] <micahg> bdrung: unping
[09:52] <gaspa> hi, anyone knows if we can sync from unstable from launchpad? (I mean, here:  https://launchpad.net/ubuntu/precise/+localpackagediffs)
[09:53] <wgrant> gaspa: Not at the moment, unfortunately. The multi-parent support isn't quite finished enough yet.
[09:53] <gaspa> wgrant: k, thanks :)
[09:54] <Laney> use syncpackage for that
[09:55] <tumbleweed> gaspa: the LP web interface doesn't check things like sync blacklists or for ubuntu deltas that may be overwritten, so one should always use syncpackage
[09:55] <gaspa> uh, pity, I found it very attractive :D
[10:46] <Laney> http://paste.debian.net/137307/ ← here's my current lp-udd script, which ~works. I get EPIPE at line 136 though with py2.6 but not py2.7… why? :(
[10:58] <tumbleweed> Laney: maybe because you are trying to write to a /dev/null that was opened for reading?
[11:01] <Rhonda> A new, easier, procedure involving the Backports Tester Team PPA is in the works. Stay tuned for info.
[11:01] <Rhonda> That's from the UbuntuBackports wiki page - anything done along that lines already?
[11:03] <Rhonda> And when I do a test build, should I mark the backport bug as confirmed already myself, or is that only up to someone from the backports team?
[11:04] <Rhonda> What's the proper versioning for a backport again? :)
[11:06] <tumbleweed> Rhonda: backportpackage takes care of the versioning. AFAIK there is a PPA, andI can't remember the procedures.... /me waits for a backporter Laney? broder?
[11:07] <Rhonda> for i in lucid natty maverick; do sudo nice ionice -c3 cowbuilder --update --basepath /var/cache/pbuilder/cow/$i; sudo nice ionice -c3 cowbuilder --build --basepath /var/cache/pbuilder/cow/$i --pkgname-logfile tmux_1.5-1~$i~ppa1.dsc; dcmd mv /var/cache/pbuilder/result/tmux_1.5-1~$i~ppa1_i386.* .; done
[11:08]  * Rhonda hides for doing long commandline foo. :)
[11:08] <Rhonda> tumbleweed: I think only the backporters are allowed to upload to the backports PPA, it's only described under Source Change Backports anyway.
[11:09] <tumbleweed> Rhonda: well yes, you need to be in the team to upload to the PPA
[11:46] <Laney> Rhonda: the packages need source changes?
[11:47] <Laney> append ~release1
[11:47] <Laney> tumbleweed: no, it even happens if I don't redirect stderr
[11:48] <Rhonda> Laney: Nope, they don't.
[11:49] <Rhonda> I appended ~natty1~ppa1 for the time being.
[11:49] <Rhonda> … see my "oneliner" ;)
[11:49] <Laney> ok, well someone (can be the requester) needs to confirm it builds/installs/runs as well as any rdeps
[11:50] <Laney> of which there don't appear to be any
[11:51] <Rhonda> doh, error in there, not ~$i~ppa1 but ~${i}1~ppa1  :)
[12:12] <soren> Laney: http://bugs.python.org/issue10963 ?
[12:13] <Laney> hmm
[12:52] <Laney> is there a workaround for that?
[13:04] <tumbleweed> Laney: looks like catching the OSError would be a workaround
[13:04] <Laney> yeah I tried that, but parsed_changelog is unset
[13:06] <Laney> is there some fancy streaming to incrementally set it?
[13:07]  * Laney flails around
[13:09] <tumbleweed> oh, it wasn't that it failed, just *really* short lived
[13:09] <tumbleweed> run command; cat? :)
[13:10] <nigelb> tumbleweed / Laney - Either of you got a chance to propose a session about challenges?
[13:10] <nigelb> I won't be there or I'd have proposed one
[13:10] <soren> Laney: Yeah. Use Python 2.7.
[13:11] <tumbleweed> nigelb: challenges?
[13:11] <Laney> soren: I don't admin the box it will run on
[13:11] <nigelb> tumbleweed: The dev challenges which we tried to do this cycle but failed
[13:11] <Laney> nigelb: not if it's this week
[13:11] <tumbleweed> the box it will run on presumably runs squeeze
[13:12] <tumbleweed> I'm assuming he's talking about UDS
[13:12] <Laney> oh
[13:12] <nigelb> Yeah, I'm talking about UDS :)
[13:12] <Laney> not the open week?
[13:12] <nigelb> No :P
[13:12] <Laney> dunno, I can be there
[13:12] <nigelb> (sorry, I should've been clearer)
[13:12] <Laney> we should have one about recruitment
[13:12]  * tumbleweed can too, but I can't really drive any challanges next cycle. I'm spread too thin as it is
[13:13] <Laney> quite
[13:13] <nigelb> so we need to do a session about recruiting to recruit people to do recuriting?
[13:13] <nigelb> So meta.
[13:13] <Laney> like how do we make motu less dead
[13:14] <Laney> challenges are well and good but there needs to be people to do them
[13:14] <tumbleweed> we definitly need a session on that
[13:14] <tumbleweed> but I don't know what we'll get out of it...
[13:14] <Laney> :(
[13:14] <nigelb> we need more new blood to handle it.
[13:14] <nigelb> I'm spread thin as well.
[13:15] <tumbleweed> the QA session at debconf was also pretty sad, lots of "so this 1 persion is doing foo, who can help him/her", and nobody responds. Repeat 10 times
[13:15] <nigelb> :(
[13:15] <nigelb> Are we losing too many people to burn out?
[13:16] <tumbleweed> I don't know. This is partly why I did http://people.ubuntu.com/~stefanor/upload_activity/ this weekend. Which showed more activity in universe than I expected
[13:17] <nigelb> Neat.
[13:17] <Laney> what are the spikes?
[13:17] <nigelb> probably pre-freeze ;)
[13:17] <nigelb> or post freezes
[13:17] <tumbleweed> the y axis is uploads per week
[13:17] <Laney> transition uploads?
[13:18] <nigelb> tumbleweed: minus syncs?
[13:18] <tumbleweed> it should exclude syncs. Yes probably transitions
[13:18] <Laney> could be perl at the start of O
[13:18] <nigelb> There was a perl thing, a python thing, and an ftbfs thing.
[13:18] <nigelb> I wonder if the little activities that were planned had a good effect.
[13:18] <tumbleweed> if anyone knows a good way to exclude canonical, that would be interesting
[13:19] <tumbleweed> excluding cjwatson and doko would get us 50% there, though :P
[13:19] <nigelb> lol
[13:19] <Laney> is there an lp team?
[13:19] <nigelb> No
[13:19] <nigelb> you'd have to manually pick people out.
[13:19] <cjwatson> there is a ~canonical LP team, but it's private
[13:19] <cjwatson> (which doesn't help you)
[13:19] <nigelb> well, so we can get a canonical person to run the script :D
[13:19] <Laney> well, it's questionable how much value that would have anyway
[13:20] <tumbleweed> Laney: I'm just trying to see how dead MOTU actually is
[13:21] <Laney> just looking at the list would probably be ok
[13:21] <nigelb> ha, I just realized I did have 3 uploads to Oneiric.
[13:24] <mr_pouit> (you should probably exclude universe seeded packages if you want to know how dead motu is)
[13:24] <bdrung> micahg: pong; unpong ;)
[13:25] <tumbleweed> Laney: next job: import packagesets into udd:)
[13:26] <Laney> heh
[13:26] <Laney> should be easy
[13:27]  * tumbleweed doesn't even know how to examine packagesets (short of reading edit_acl.py)
[13:27] <Laney> stgraber wrote a script to list them all recently
[13:27] <tumbleweed> ah, that too
[13:28] <Laney> http://bazaar.launchpad.net/~developer-membership-board/+junk/packageset-report/view/head:/make_report.py
[13:29] <Rhonda> Laney, got lucid and natty test of tmux up and running, maverick still compiling, but I don't expect any issues. Set them both to confirmed already. If you are familiar with tmux, would be great if you could check: bug #876381 (natty) bug #876382 (maverick) bug #876383 (lucid)
[13:29] <Laney> Rhonda: nice, that's all the confirmation i need
[13:30] <tumbleweed> Laney: do we need something in u-d-t to query packagesets? I found myself running edit_acl a lot during final freeze, to verify that I could sync something
[13:30] <Laney> but we need to backport them in order, so i'll approve natty and then the others when maverick turns out to work
[13:31] <Laney> tumbleweed: maybe, don't know how often listing them is needed per se, rather than "can I upload x?"
[13:31] <Laney> release team requirements are a bit specialised
[13:31] <tumbleweed> maybe make syncpackage list the packagesets as well as the changelog?
[13:32] <Laney> "is this seeded?" is the more important question?
[13:32] <tumbleweed> yeah. But that's harder to determine...
[13:33] <Laney> mmm
[13:34] <tumbleweed> the sponsors page also equates packagesets with seeds
[13:35] <cjwatson> "can I upload this?" is a sensible question something in u-d-t should be able to answer
[13:35] <Laney> pretty sure it can
[13:35] <cjwatson> possibly followed by "who can upload this?"
[13:36] <tumbleweed> in freezes, there's also "I can upload this, but is it safe?"
[13:36] <cjwatson> true
[13:40] <Laney> I suppose listing (component, sets, seeded?) would be nice
[13:41]  * tumbleweed files a wishlist bug before he forgets
[13:42] <Laney> can you query LP to see if the archive is frozen?
[13:43] <tumbleweed> looks like distro_series.status can tell us that
[13:44] <Laney> could use that to enable some extra fear
[13:44] <Laney> like a small electric shock
[13:44] <tumbleweed> lol
[13:46] <bdrung> tumbleweed: should we wait six days for the distro-info 0.3 migration to testing?
[13:47]  * cjwatson pro-forma objects again to exposing the "seeded" concept anywhere that humans might be expected to understand it
[13:47] <Laney> but we already do expect people to understand it for freezes?
[13:48] <Laney> or do you think /that/ is a mistake?
[13:48] <cjwatson> yes, I do
[13:48] <cjwatson> it's a hopelessly ambiguous term
[13:49] <cjwatson> (a) actually listed in seed files (b) contained in the dependency-expansion of seeds (c) on some CD images (d) in some package sets ...
[13:49] <cjwatson> we should say whatever we actually mean
[13:51] <Laney> yes, I agree it needs defining. writing this code could actually prompt that...
[13:51] <tumbleweed> cjwatson: the most useful thing for freezes is "on some CD images", is there any reasonable way to query that?
[13:52] <tumbleweed> bdrung: yeah, I'm thinking we do a minimal SRU now, and copy-it-up. Then do the sync-from-testing-for-LTSs change when distro-info is available
[13:52] <bdrung> tumbleweed: copy-it-up?
[13:53] <tumbleweed> get the SRU copied from oneiric-updates to precise
[13:53] <Laney> proposed
[13:54] <tumbleweed> yeah, that
[13:54] <Laney> :-)
[13:58] <cjwatson> tumbleweed: in practice it's probably best to grep the .list/.manifest files
[13:58] <cjwatson> which is unfortunately not especially reasonable, but ...
[13:58] <cjwatson> precise already has a newer distro-info than oneiric
[13:58] <tumbleweed> that sounds out of the question for something we do regularly, but the way to go for a can-i-upload-this-during-freeze tool
[13:58] <cjwatson> including the packaging reorganisation
[13:58] <cjwatson> I doubt that a copy-up from oneiric-updates would work
[13:59] <tumbleweed> ah, copy-up of u-d-t, not distro-info. The change I want from there for the long term solution is only in git
[13:59] <cjwatson> ah, ok
[13:59] <cjwatson> sorry
[13:59] <tumbleweed> np, thanks for checking :)
[15:14] <jtaylor> this as-needed change is really screwing users ._.
[15:14] <jtaylor> all their crappy apps don't compile anymore ^^
[15:15]  * tumbleweed sees that as a good thing :P
[15:15] <jtaylor> almost a dozen threads in the ubuntu forums already and its not even a week released
[15:15] <gaspa> anyone can drive me a bit on a backport? (seems strange but I never did one)
[15:15] <gaspa> I'm after #858361, it is a no-source-change. may I upload by myself or should I subscribe some -backporter?
[15:15] <jtaylor> well gcc is a bit unfriendly in that respect, its counterintiutive to ahve stuff depend on ordering on command line
[15:15] <jtaylor> I don't really get why gcc can't do reordering itself by default
[15:16] <tumbleweed> gaspa: file a bug against $release-backports. Build it with backportpackge yourself, and test it. Report on the results in the bug
[15:16] <tumbleweed> then poke backporters here
[15:16] <Laney> and all rdepends
[15:16] <Laney> and no need to poke, i'm keeping up with it
[15:16] <Laney> (so far)
[15:16]  * tumbleweed is impressed :P
[15:17] <gaspa> Laney, tumbleweed: so we should not upload by ourselves, I guess. right?
[15:17] <Laney> no
[15:18] <gaspa> uh, it's already in.
[15:19] <Laney> that's happy
[15:20] <gaspa> ok, so it's all done.
[15:20]  * gaspa bows
[15:30] <geser> jtaylor: the problem is that gcc in the past the ordering could be ignored (by developers) as all libs got linked in (even the unused by the application) so all the symbols from the libs were available
[15:30] <jtaylor> yes I understand why as-needed is good
[15:31] <jtaylor> its just not really apparent why gcc can't just scan all files for needed symbols and then for libraries providing them, no matter what order they are
[15:32] <jtaylor> kind of what --start-group --end-group does
[15:32] <jtaylor> is performance really an issue nowadays?
[15:36] <geser> I guess this question is better asked the gcc/ld gurus
[15:37] <Laney> gaspa: you should use the new syncpackage (using LP API) for syncs
[15:39] <jtaylor> are autosyncs already running?
[15:39] <Laney> yep
[15:39] <jtaylor> nice
[15:40] <jtaylor> time to sync all as-needed fixes that are in debian now, too bad I did not keep proper track of them ._.
[15:40] <Laney> usertagged though?
[15:41] <jtaylor> yes
[15:41] <Laney> doable then
[15:41] <geser> jtaylor: the next time you will :)
[15:41] <jtaylor> yes but it would ahve been easier if I noted for each branch I made when it was fixed in debian :/
[15:47] <jtaylor> is the branch status selector in the personal code section on lp broken?
[15:49] <tumbleweed> "personal code section" ?
[15:49]  * tumbleweed made a rough first pass at affiliation, for everyone doing > 100 uploads in 'select count(*) as count, signed_by from ubuntu_upload_history group by signed_by order by count;' http://people.ubuntu.com/~stefanor/upload_activity/
[15:50] <tumbleweed> of  course, canonical hires community developers, which skews the numbers...
[15:51] <geser> the black lines are release dates and the red ones FF?
[15:51] <gaspa> Laney: ack. next time :P
[15:51] <tumbleweed> gaspa: yeah
[15:52] <tumbleweed> err geser
[15:53] <tumbleweed> err, that'll also be skewed by patch pilots
[15:53] <tumbleweed> I was looking at signed by, not changed by
[15:53] <geser> hmm, was oneiric so good that it didn't need many uploads since a couple of weeks before FF?
[15:53] <tumbleweed> oneiric was really quiet near the end
[15:53] <geser> in the previous release the amount of uploads was pretty constant even after FF
[15:54]  * tumbleweed probably granted less than 10 FFes
[15:56] <Laney> it'd be interesting to see the distribution of uploads
[15:56] <Laney> on an individual level
[15:56] <tumbleweed> run the query I just pasted
[15:56] <Laney> in a nice graph :P
[15:56]  * micahg didn't ask for as many this cycle :)
[15:56]  * Laney ties a bow around micahg
[15:57]  * micahg didn't sign up for the dog and pony show...
[15:58] <jtaylor> tumbleweed> "personal code section" ?    <  the code tab in your profile
[15:58]  * micahg hopes to do a lot of uploads at the end of precise to clean up stuff (had no time for oneiric)
[15:58] <jtaylor> I can't see any but those with active status :/
[15:58] <tumbleweed> jtaylor: aah, does branch status make sense for personal UDD branches?
[15:59] <jtaylor> yes merged and active
[15:59] <jtaylor> I set them all to merged when I'm done so they don't clutter the list
[16:00]  * Laney is in the list twice
[16:00] <Laney> (using changed_by)
[16:00] <jtaylor> with the side effect that I know can't reach any of them ._.
[16:01] <jtaylor> worked yesterday
[16:01] <jtaylor> should probably file a bug
[16:01] <tumbleweed> jtaylor: oh, I thought you were talking about the thing in the bzr client that telss you if a UDD branch is up to date
[16:02] <tumbleweed> Laney: you can get around e-mail address variance with changed_by_name
[16:02] <Laney> yep
[16:03] <Laney> haskell transitions: good for karma
[16:03] <tumbleweed> heh
[16:04] <jtaylor> ah its filed already :) bug 876533
[16:04] <Laney> if someone helps me (with a patch ...) to fix the problem I talked about ^ then I'll roll out the new importer ASAP
[16:05] <Laney> if DSA don't mind installing lplib that is
[16:06] <tumbleweed> Laney: lucas has root on it, IIRC
[16:06]  * Laney knows not how it works
[16:07] <Laney> i emailed d-admin last time
[16:07] <tumbleweed> ah, I did that too, and my request was never installed :)
[16:07] <lucas> tumbleweed: are you sure you are talking about the same UDD?
[16:07] <Laney> samosa
[16:07] <lucas> ah, ok
[16:08] <lucas> I don't have root, you need to go through DSA
[16:08] <tumbleweed> ah, sorry, misremembered
[16:08] <Laney> that is what i thought, np
[16:09] <pmjdebruijn> \3\\\\\/win 13
[16:09] <pmjdebruijn> sorry
[16:09] <Laney> nice!
[16:43] <tumbleweed> Laney: from the look of the patch against python, you can use process.stdout.read() to avoid .communicate() throwing the data on the floor
[16:48] <jtaylor> can we sync stuff from unstable when the reason for it not being in testing is that it does not build on e.g.hurd?
[16:48] <jtaylor> e.g. flightgear 2.4 is ~40 days in unstable but not in testing due to hurd
[16:49] <micahg> jtaylor: as long as it has no rdepends, sure :)
[16:52] <cjwatson> jtaylor: that can't possibly be the reason it isn't in testing; hurd-i386 isn't a Debian release architecture
[16:53] <jtaylor> hm maybe it needs some kind of hints
[16:53] <jtaylor> it built on all arches except hurd and has no rc bugs
[16:53] <jtaylor> neither do its rdeps
[16:53] <jtaylor> deps
[16:55] <cjwatson> simgear is marked as not considered, I believe due to simgear2.0.0 still being in the archive and out of date
[16:55] <cjwatson> which in turn appears to be because fgrun and fgfs-atlas are still built against it
[16:55] <c_korn> even if I have multiverse enabled apt-cache policy avidemux says there is no  such package. but it should be there: https://launchpad.net/ubuntu/+source/avidemux
[16:56] <cjwatson> c_korn: failed to build everywhere with new libav and nobody fixed it, so the binaries were removed.  bug 831096
[16:56] <micahg> c_korn: it's source only in precise
[16:56] <jtaylor> hm I'll wait for the maintainers to sort that out
[16:57] <cjwatson> c_korn: feel free to fix it in precise and SRU it to oneiric
[16:59] <c_korn> cjwatson: I see what I can do.
[17:08] <Laney> tumbleweed: how dirty is this? http://paste.debian.net/137409/ :-)
[17:08] <Laney> works ...
[17:35] <tumbleweed> Laney: err why do you need to echo the changelog?
[17:35] <tumbleweed> how about just using .stdout.read instead of .communicate?
[19:04] <tumbleweed> any opinions on bug 873984? I don't know anything about OpenSSL ABI stability...
[19:16] <micahg> tumbleweed: I was wondering about that, it seems weird that it would require a rebuild w/out a soname bump in openssl, but maybe proftpd is doing something it shouldn't or needs a stricter depends
[19:30] <tumbleweed> micahg: I suspect they just don't trust OpenSSL (or users who compile it themselves)
[19:39] <tumbleweed> micahg: I suppose a rebuild doesn't hurt...
[19:40] <micahg> tumbleweed: well, if it's not really needed, maybe that should be fixed, if it is needed, then either proftpd needs stricter depends or libssl needs a soname bump
[19:41] <tumbleweed> my thoughts too
[19:41] <tumbleweed> given the number of things that link to libssl, I'd have thought that its ABI was well understood...
[19:41] <micahg> indeed, although there was a change in 1.0.0e that wreaked havoc
[19:43] <tumbleweed> the SSLv2 drop?
[19:45] <micahg> tumbleweed: no, we did that in natty, I forgot what it was exactly
[20:06] <micahg> \o/ mass sync == mass build failures :)
[20:08] <ajmitch> the list grows long?
[20:08]  * ajmitch tries to recall where the graph of FTBFS numbers is
[20:10]  * tumbleweed is trying to persuade geser to merge it into the FTBFS table
[20:11] <geser> I really hope to find time to review it soon
[20:12] <cjwatson> most of the ones I've looked at so far have been gnutls fallout
[20:12]  * ajmitch should see if there are any merges he can do
[20:12] <tumbleweed> ajmitch: so far, it's flat: http://corelli.tumbleweed.org.za/ubuntu-qa/qa-ftbfs/precise-historical.html. Wait until it runs tonight...
[20:13] <jtaylor> so all syncs should be filed
[20:13] <tumbleweed> geser: it'll be nice if we can land it before doko kicks off any rebuilds, but besides that, there's no hurry
[20:13] <ajmitch> nice
[20:13] <jtaylor> not as many as hopped :/
[20:13] <micahg> cjwatson: so it's not 300 failures in universe ATM?
[20:14] <cjwatson> micahg: no, I gave back a load, haven't been keeping count
[20:15] <micahg> cjwatson: ok, that's a relief :)
[20:15] <Laney> tumbleweed: how do i pass the changelog in then?
[20:15] <Laney> it needs to go on stdin
[20:15] <Laney> or else i write it to a temp file
[20:16] <tumbleweed> Laney: stdin.write?
[20:16] <Laney> okies
[20:16]  * Laney somehow missed the python boat
[20:17] <ajmitch> what are you using that requires it goes on stdin?
[20:17] <Laney> easier than saving to a temporary file isn't it?
[20:17] <Laney> bah, that gets broken pipe again
[20:18] <tumbleweed> yeah, you'll need to catch that
[20:18] <tumbleweed> but you won't lose the output (as far as I can tell)
[20:19] <ajmitch> whatever you're doing, it looks interesting :)
[20:20] <Laney> i preferred the old way
[20:21] <Laney> aha, works
[20:21]  * ajmitch wants to look at the whole code for it now, got a branch?
[20:21] <Laney> will you promise not to be mean?
[20:21] <ajmitch> when am I ever mean?
[20:21] <Laney> and instead make improvements
[20:22] <Laney> it is pretty severely slow
[20:22] <ajmitch> yeah you said that yesterday, I'm sure I've written worse
[20:22] <Laney> http://paste.debian.net/137499/
[20:25] <ajmitch> what specifically do you need from dpkg-parsechangelog output? just the Launchpad-Bugs-Fixed & Closes?
[20:25] <Laney> yep
[20:25] <Laney> distribution is useful but you can reconstruct that
[20:25] <Laney> the commented out bit
[20:25] <tumbleweed> once you are already talking to launchpad, the overhead of shelling out to dpkg-parsechangelog is tiny...
[20:25] <Laney> indeed
[20:25] <ajmitch> right, it just looks messy
[20:25] <ajmitch> I'm just checking what python-debian can do
[20:25] <Laney> i think it's probably the duplicate checking
[20:44] <tumbleweed> geser: just realised a potential bug in the historical graph support. diff line 229 deletes data points within the last 12 hours. That won't work if it's cronned more frequently than that. How fast do you usually run it?
[20:46] <geser> wgrant runs it hourly on qa.ubuntuwire.com
[20:47] <tumbleweed> maybe I should store a date instead of a timestamp
[20:47] <tumbleweed> I think one graph point per day is sufficient
[20:48] <geser> do you store then the min or max or the last value per day?
[20:49] <tumbleweed> I want all the timestamps for a single run to be the same, so that we can use SQL GROUP BY easily, so I take the current timestamp before we start inserting rows
[20:49] <tumbleweed> I'll take the timestamp of midnight that day instead
[20:50] <tumbleweed> the reason I do the deletion is that I didn't want partial runs in the data
[20:51] <tumbleweed> actually, that's not a danger. I didn't want uneven datapoint frequency when it's occasionally run by hand
[20:54] <Laney> Rhonda: any news on maverick
[20:54] <Laney> ?
[20:55] <Laney> oh, the script finished
[20:55] <Laney> can't be /that/ slow then
[20:55] <tumbleweed> that was quick?
[20:55] <Laney> err
[20:55] <Laney> no, it's not right
[20:55] <tumbleweed> :)
[20:55] <Laney> no precise uploads
[20:57]  * ajmitch is fairly sure that people have been uploading to precise already
[20:58] <Laney> yes
[21:30] <Laney> wow
[21:30] <Laney> I made it even slower?
[21:33] <ajmitch> Laney: well done?
[21:34] <Laney> give me mboxes or give me death
[21:34] <ajmitch> https://lists.ubuntu.com/archives/precise-changes.mbox/precise-changes.mbox
[21:35] <ajmitch> there you go, have fun
[21:35] <ajmitch> that only works if all the changes that happen make it to the list, of course
[21:35] <Laney> :(
[21:35]  * cjwatson should probably wait for the world to build a bit better before trying to deal with NBS
[21:36] <cjwatson> or transitions for that matter
[21:36] <ajmitch> archive admins plan to be a bit more ruthless with purging packages for the LTS?
[21:39] <cjwatson> I have some plans to marshal people such that we hopefully won't need to
[21:45] <Rhonda> Laney: It's on my workplace computer, can tell you tomorrow :)
[22:45] <r3pek> guys, how to rename a file during the instalation of a deb?
[22:45] <r3pek> the source has it like "abcd.sh" but i want to install it as "abcd"
[22:51] <tumbleweed> r3pek: rename it during the build, after it's been installed to debian/packagename/usr/bin/abcd.sh
[22:51] <r3pek> so i have to put that path? the full path? starting with debina/<packagename> ?
[22:52] <StevenK> dh_install can do it too
[22:52] <r3pek> dh_install doesn't do renames afaik
[22:52] <Laney> no, it can't rename
[22:52] <tumbleweed> r3pek: well, that's where it gets installed to, so yes
[22:53] <r3pek> ok... i just didn't knew the correct path so my "mv"s were failling :)
[22:54] <r3pek> hummm :/
[22:54] <r3pek> still errored out :(
[22:55] <tumbleweed> that's when you go and see what it did and why it didn't work
[22:56] <r3pek> that's the easy part :P
[22:56] <r3pek> mv: cannot stat `debian/sispmctl/etc/bash_completion.d/gemplug-completion.sh': No such file or directory <--- :)
[22:57] <tumbleweed> so go and see what is there
[22:58] <r3pek> i can be doing something wrong on my rules file
[22:58] <r3pek> build/sispmctl:: <----
[22:59] <r3pek> ^^ i have that and then the mv
[22:59] <tumbleweed> r3pek: build is too soon
[23:00] <r3pek> so when? during install?
[23:00] <tumbleweed> you can't move it until it's there
[23:01] <tumbleweed> IIRC the cdbs manual gives a good description of the hook points
[23:01] <r3pek> hummm ok. one mor try :)
[23:01]  * cdbs has a manual?
[23:01] <cdbs> :)
[23:02] <ajmitch> cdbs: you're still using that nick? :P
[23:02] <cdbs> ajmitch: I really want to switch over, after a long legal (lol) battle I managed to win over the nick "bilal"
[23:02] <cdbs> feeling lazy to make another move
[23:03] <cdbs> since, I was "bilalakhtar" earlier, and since "bilal" was occupied I moved to "cdbs"
[23:03] <ajmitch> just use /nick :)
[23:03] <cdbs> ajmitch: Its not that easy, you need to tell everyone to call you by this nick
[23:03] <ajmitch> they'll manage
[23:04] <ajmitch> better than you getting highlights from people ranting about how cdbs sucks :)
[23:04] <cdbs> that's actually okay
[23:04] <cdbs> it gives me a chance to kick into the discussion
[23:04] <ajmitch> heh
[23:04] <cdbs> and then tell people to move to dh
[23:04] <cdbs> since /me hates cdbs
[23:04] <tumbleweed> lol
[23:05] <ajmitch> with that, I think I shall find lunch :)
[23:05] <cdbs> bye ajmitch
[23:05]  * tumbleweed gets hilighted when people notice channels are dead. Not sure which is more interesting :P
[23:06] <r3pek> i still don't reallu understand the debian packaging system :)
[23:06] <r3pek> from a user pov, it's cool. for a dev pov, looks a nightmare so far :X
[23:07] <tumbleweed> r3pek: it's actually pretty simple, but people have written some rather complex tools to automate most of it, and learning the tools and all their oddities ends up being the nightmare
[23:08] <RAOF> Also, cdbs *is* unnecessarily arcane.
[23:10] <tumbleweed> r3pek: http://cdbs-doc.duckcorp.org/en/cdbs-doc.xhtml#id465030 you'll notice that the hook you want is probably install/package
[23:11] <r3pek> tumbleweed, yes, it's working on install :)
[23:12] <r3pek> RAOF, i'm just upgrading a package. and trying to learn the package system along the way...
[23:12] <r3pek> but i'm not even aware what i'm using... cdbs or any other thing :X
[23:16] <r3pek> [PPA r3pek-sispmctl] [ubuntu/oneiric] sispmctl 3.0-nmu2 (Accepted)
[23:16] <r3pek> ^^ #win :)
[23:52] <cjwatson> back down to 72 build failures after the first day of autosyncs; not too shabby
[23:54] <wgrant> We can fix that by running add-missing-builds if you want :)


[00:00] <mrand> prozaconstilts: I've not tried it, but does xine --keymap=lirc produce anything?
[00:00] <prozaconstilts> one sec, let me try
[00:02] <prozaconstilts> it outputs an lirc button config
[00:03] <mrand> And do the names match up with what's in your .lirc?
[00:04] <prozaconstilts> in terms of the config= lines, the values there are correct
[00:04] <prozaconstilts> the remote and button lines just have "=xxx"
[00:06] <prozaconstilts> the mapping I have in place now worked fine for 9.04...
[00:06] <mrand> Right.  Normally you'd replace the xxx with various button names and such.
[00:07] <mrand> Yeah,, I'm sorry to say that I don't have a clue.  If superm1 has time, he might be able to suggest something else, but the fact that you appear to be the only one complaining about it either means no-one else has noticed (unlikely, but possible in my opinion), or there is something wrong on your particular system.
[00:07] <mrand> I suppose you could perhaps try dropping back to a previous version of xine.
[00:08] <superm1> the best thing to do is do a test run with ircat
[00:09] <superm1> rule out problems in the lirc conf files in your home directory
[00:09] <henrik__> superm1, I need your help. I have been asking in mythtv-users for several days and no one can help me..
[00:10] <superm1> henrik__, and you've posted several contentless pings to me.  post the actual question :)
[00:11] <henrik__> Problem 1. In mythweb when I do a free text search for a epg program, it shows the dates of when the shows are shown but not the day. ie. 8/12-2009 instead of mon 8/12 2009
[00:11] <henrik__> this worked in .21 but not in .22
[00:12] <mrand> prozaconstilts: The ONLY problem I've found mention of an lirc / xine problem on archlinux, where they needed to recompile xine. http://bbs.archlinux.org/viewtopic.php?id=82557
[00:12] <henrik__> and I have gone thru all my videos and added the number from http://www.themoviedb.org/ in metadata, and it downloaded the backgrounds and pictures perfectly. But next time I did a search of the movies in my movie dir all that information was removed, and even if I do a w in the directory or a fetch information in meta menu it does not come back.
[00:14] <prozaconstilts> mrand, i've read that post. I've confirmed lirc was compuled for 9.10 w/ lirc support...let me try ircat. I was unaware of that nice little tool
[00:15] <prozaconstilts> er,, xine was compiled*
[00:15] <superm1> henrik__, so are you sure that it's the action of the search making the metadata go away?
[00:15] <superm1> it can possibly be jamu mucking with things
[00:16] <henrik__> well, the way it turned out was that the next day all the information was there, and then when I had added information it just disapered..
[00:16] <superm1> prozaconstilts, the other thing to consider is that you can regenerate your lircrc for just xine (look at mythbuntu-lirc-generator --help)
[00:17] <superm1> henrik__, well what you want to do is make sure you can isolate what is doing that.  you can disable the jamu cron jobs temporarily to aide in verifying that's what's doing it
[00:17] <superm1> they're in /etc/cron.*/
[00:17] <henrik__> but right now I have no information
[00:17] <henrik__> in my video dir
[00:18] <henrik__> is it a known problem with the meta data utility?
[00:18] <prozaconstilts> superm1: I did that, and diff'd with the original. Aside from a few changes I made to map buttons to config actions, it looked the same.
[00:20] <prozaconstilts> superm1: ircat shows config strings outputting to the terminal for xine
[00:20] <mrand> henrik__: the meta data utility has had a number of recent updates... are you on autobuilds?
[00:22] <henrik__> I'm on avenard
[00:22] <superm1> why?
[00:22] <henrik__> cause I did not get vdpau working without it
[00:22] <superm1> our builds provide 185 and 190 nvidia too
[00:22] <superm1> not sure what benefit you get out of there instead
[00:22] <superm1> prozaconstilts, hmm.  okay next idea.  can you move the xine conf out of the way and let it regenerate?
[00:22] <henrik__> I'll be more then happy to go back
[00:23] <henrik__> now I'm on 190
[00:23] <superm1> perhaps there is sort of option for enabling / disabling remote that i'm not aware of
[00:23] <superm1> henrik__, well on avenard, what's the latest svn revno you're at?
[00:23] <superm1> the jamu updates have been backported in very recent commits
[00:23] <prozaconstilts> superm1: i tired that as well
[00:24] <prozaconstilts> xine config being ~/.xine
[00:24] <superm1> yeah
[00:24] <superm1> prozaconstilts, you've got me then.  if ircat shows it working, there's not much reason for it to not work directly in xine
[00:24] <prozaconstilts> :'(
[00:24] <henrik__> 2:0.22.0-fixes22952-0ubuntu2
[00:25] <superm1> prozaconstilts, i know it works in 9.10 with xine because i've been using it for xine up until last week
[00:25] <superm1> (i stopped because i'm now using a bluray player to upconvert dvds)
[00:25] <prozaconstilts> well, let me compile from source and enable debug. Maybe it'll show me something...or maybe it'll even work :P
[00:25] <henrik__> superm1, whats the svn that is in the org.
[00:26] <superm1> those are fairly recent.  the latest on mythbuntu autobuilds is 22957
[00:26] <superm1> but i think the jamu stuff went in about a week or two ago, so you should be fine there
[00:26] <superm1> go disable the cron jobs and see if the problem persists
[00:27] <superm1> if it does, then you've at least ruled one area out
[00:27] <henrik__> where in the crown can I find the jamu?
[00:27] <superm1> you'll have to run mythbackend with debug in that case
 they're in /etc/cron.*/
[00:28] <henrik__> and what is it called?
[00:29] <superm1> i don't know off hand
[00:29] <superm1> there's a few files there
[00:29] <henrik__> this one.. mythvideo??
[00:34] <superm1> sounds right
[00:34] <superm1> there's a few
[00:34] <henrik__> now i removed mythvideo from hourly daily and weekly
[00:40] <henrik__> you seem to be right
[00:41] <henrik__> Now when I removed that from my crown scripts
[00:41] <henrik__> and added them again..
[00:41] <henrik__> no problem..
[00:41] <henrik__> but as soon as I executed one of thouse scripts it erased all meta data
[00:52] <henrik__> superm1, I'm now going back to your repros..
[00:52] <henrik__> should I be using the PPA?? is there where the most recent version?
[00:52] <superm1> henrik__, they're mirrors
[00:53] <superm1> so you can get them anywhere
[00:53] <superm1> whatever's closest
[00:53] <superm1> so what you want to do is file a bug at svn.mythtv.org about this. file it against jamu, and RDV_Linux should be able to help figure out what's going wrong
[00:53] <henrik__> but where is the most recent version.. I know that the uk was days behind
[00:54] <henrik__> well superm1 just by removing the cron worked good for me..
[00:54] <superm1> PPA is the first place that they get uploaded to
[00:54] <superm1> but that means there is a bug in jamu
[00:54] <superm1> it's not supposed to be doing this
[00:54] <superm1> it's actually supposed to be doing $GOOD things
[00:55] <henrik__> should I active testing ppa?
[00:55] <henrik__> yes. but I will probelbly not be able to add all the info that the developers want :)
[00:56] <henrik__> I can never give enough information they ask for so much.. I would hoever happily give you a shell account..
[00:56] <superm1> RDV_Linux will ask you for whatever information is necessary
[00:56] <superm1> surely you're not the only one with the issue, so it's beneficial to everyone to file a bug about it
[00:56] <superm1> up to you on the testing ppa
[00:56] <henrik__> sure!
[00:57] <superm1> we dont use it as much as we should
[00:57] <henrik__> then i'll skip it..
[00:59] <henrik__> now I'm back to your autobuild
[01:00] <henrik__> superm1, the other question?
[01:13] <henrik__> superm1, a bug is filed..
[01:17] <henrik__> superm1, when you have the time please look at my other question i wrote to..
[04:36] <MistStlkr> hello all
[04:37] <MistStlkr> anyone else having an issue since taking the 2.6.31-16 kernel update?  I can now only boot in recovery mode for some reason.
[04:38] <tgm4883> MistStlkr, Linux ares 2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3 22:07:16 UTC 2009 x86_64 GNU/Linux
[04:38] <tgm4883> Have you tried booting an older kernel?
[04:39] <MistStlkr> I have tried -15 as well and get the hang at the same spot, but a -15 (recovery mode) also works
[04:39] <MistStlkr> and once booting into recovery mode, all I have to do is hit "resume normal" on the menu and it boots fine
[04:40] <tgm4883> MistStlkr, odd
[04:40] <tgm4883> any errors in syslog?
[04:40] <tgm4883> dmesg?
[04:40] <MistStlkr> I get what appears to be a white terminal window and a permanent "wait" icon
[04:41] <MistStlkr> The system can actually be used as long as I jump thru a few hoops, including changing the permissions on the sound card.. so each time I reboot I can tinker to get it working, but it seems awfully odd.
[04:42] <MistStlkr> perhaps the chmod on the audio is a result of having to boot in recovery mode?
[04:45] <MistStlkr> wife is watching a video at the moment, she got tired of not having it and jumped all over it once I got eh audio issue "fixed" LOL  I'll have to check the syslog later.  what might I be looking for?
[04:45] <tgm4883> anything with error, failed, etc
[04:45] <tgm4883> usual troubleshooting stuff like that
[04:46] <MistStlkr> alright, thought you had something specific in mind.  I'll have a look when I can kick her off :-P  at least i can have it functional as it is, which is a big step up from where it was for the past week or two
[04:47] <MistStlkr> thanks for the help
[07:08] <dtrott> Is it possible to do a text only install of mythbuntu (I have some issues with the GFX card and I need to get the system operation so I can install the proper drivers) ?
[07:55] <dtrott> ok i found the "safe graphics mode option" the latest version of mythbuntu doesn't detect the hard drives correctly thought (I have gone back to 9.04 which seems to be fine).
[08:21] <superm1> dtrott, can you file a bug about that?
[08:21] <superm1> dtrott, run ubiquity like this: "ubiquity -d"
[08:22] <superm1> dtrott, and then after you get to the screen that it tries to detect drives (and fails), you can close ubiquity out and file a bug like this: "ubuntu-bug ubiquity"
[08:22] <dtrott> K let me wrap up the install with 9.04 first then I will reboot to 9.10
[08:22] <superm1> great thanks
[08:31] <dtrott> Does mythbunu have a  runlevel that is not X11 ?
[08:32] <superm1> not during the live cd
[08:33] <dtrott> I have it installed on the drive now only I can't use RL 1 as the NVidia installer bitches and 2 is already at X11
[08:34] <superm1> dont use the nvidia installer
[08:34] <superm1> use the hardware drivers tool to enable the driver
[08:39] <dtrott> yea that did it i now have a console so I can install the nvidia driver (the stardard hardware tool boned X11).
[09:16] <dtrott> Sweet up an running watching tv ;-)
[09:20] <jussi01> Zinn: is a bot?
[09:48] <dtrott> am i right in thinking that mythbuntu 9.04 doesn't have VDPAU support compiled in ?
[10:03] <dtrott> superm1: Bug #  493977
[12:09] <eddie128> Hi,  I've been through a number of howtos on LCD proc and mythtv however I can't seem to get my LCD to do anything but display welcome , time and goodbye messages with MythTV.  I'm using an IMON device.   Can someone advise how I can test the connection between LCDproc and mythtv?
[15:13] <superm1> jussi01, yes Zinn is a bot
[15:13] <superm1> rhpot1991 maintains him
[15:14] <jussi01> superm1: ahh, great, thanks.
[15:14] <superm1> !hi | jussi01
[15:14] <Zinn> jussi01: Hi $nick, how are you?  Something we can help you with today?
[15:14] <superm1> :)
[16:28] <mishehu> is there a quick & easy way to set the cpufreq to be performance?
[16:32] <mishehu> nm
[16:32] <mishehu> I found that there was a script in /etc/init.d that ran it, so I removed the symlink from the /etc/rc?.d dirs
[17:04]  * jussi01 waves.
[17:05] <jussi01> Can someone point me to something in regards to setting up the remote for my anysee e 90 combo?
[17:10] <superm1> not even sure on that model.  who manufacturers the remote?
[17:17] <jussi01> superm1: not sure
[17:17] <jussi01> just says anysee on the remote, nothing in it at all...
[17:18] <superm1> jussi01, take a look through lsusb and lshal to see if you can find anything more informative about it.  if not, it's probably not going to be worth the effort to try to make work some third party rare remote.  probably just better off buying a mceusb based one
[17:18] <superm1> (which work OOTB perfectly)
[17:21] <jussi01> superm1: this any use to you? http://paste.ubuntu.com/337422/
[17:22] <superm1> jussi01, that tells me that the kernel might be able to handle it directly without LIRC
[17:22] <jussi01> oh? :D
[17:22] <superm1> see if the keys do anything when pressed (they might emit keypresses)
[17:22] <jussi01> how would I check that?
[17:22] <superm1> press a button on the remote and see if it does anythign to a terminal window
[17:23] <jussi01> oooh, I get numbers
[17:23] <jussi01> and volume
[17:23] <superm1> there you go
[17:23] <jussi01> so how do I then configure it?
[17:23] <superm1> well check xev and make sure that all the buttons put out some keycode
[17:24] <superm1> as long as they do, you can just map from within mythcontrols
[17:24] <jussi01> ahh, excellent. Now I just have to tell my lovely girlfrined that I need her pc for a day... :D
[17:25] <superm1> or you can map them from xmodmap too
[17:25] <superm1> or other similar standard key mapping tools
[17:25] <jussi01> superm1: is there a way to install mybuntu over the top of her kde environment?
[17:25] <jussi01> mythbuntu
[17:25] <superm1> jussi01, sure, visit http://mythbuntu.org/existing-ubuntu
[17:26] <superm1> as long as kde does apturl, you can click that right from the website to install things
[17:26] <jussi01> superm1: great, your a star. thanks very much. (it doesnt)
[17:26] <superm1> otherwise, go install the control centre in the kde equivalent of synaptic or software center
[17:34] <jussi01> superm1: 1 more quick q,
[17:34] <jussi01> I have to pass: jussi@galaxy:~$ sudo rmmod dvb_usb_anysee
[17:34] <jussi01> jussi@galaxy:~$ sudo modprobe dvb_usb_anysee delsys=1
[17:35] <superm1> jussi01, so put it in /etc/modprobe.d/blah.conf
[17:35] <jussi01> to it every time. (its a dvb-c and dvb-t and that swithces to the -t)
[17:35] <superm1> where blah.conf is your favorite file name
[17:35] <jussi01> oh, :)
[17:35] <jussi01> thanks
[17:45] <jussi01> hrm, what exactly do I need to put in my .conf file?
[17:47] <jussi01> ooh, thats cool, apt-url in chromium :D
[17:47] <superm1> i think it would be:
[17:47] <superm1> options dvb-usb-anysee delsys=1
[17:48] <jussi01> ooh, thats not giving me errors now, lets see...
[17:49] <jussi01> thanks again. Ill come bother you all later when ive set it all up... (or am having issues setting it all up.)
[17:50] <superm1> okay have fun!
[17:50] <superm1> noprob
[17:57] <jussi01> hrm, I only seem to have lirc remote stuff in the mybuntu control center - where was it that you meant for mapping?
[18:34] <superm1> jussi01, there's no support for the standard X mapping tools in MCC, only lirc as you say
[18:34] <superm1> you can go into mythcontrols to map inside myth though
[22:18] <map7_> can anyone help me with a frontend client connection problem?
[22:32] <henrik__> map7_, what is your problem?
[22:34] <henrik__> map7_, I se you are getting help from iamlindoro.
[22:34] <map7_> henrik__ i'm working through it with people on mythtv-users
[22:34] <henrik__> yes good luck with that
[22:34] <map7_> thanks


[11:42] <ubot4> In #ubuntu-ops, ubottu said: #ubuntu-in is the channel for Ubuntu in India
[13:58] <[NikO]> so usefull ubot4 :)
[14:08] <Odo> hi folks
[15:43] <MTecknology> When are hostmasks given to new members?
[16:42] <jussi01> MTecknology: as soon as they ask, provide link to LP profile, have their nick setup and a staff/GC is available to do it.
[20:03] <MTecknology> jussi01: so it's one of those "just wait for it" things?
[20:04] <jussi01> MTecknology: has the person in question asked?
[20:09] <MTecknology> I don't know
[20:10] <MTecknology> I haven't been asked about anything yet
[20:11] <MTecknology> I was added to the team, but that's about it
[20:13] <Myrtti> what is this about?
[20:13] <Myrtti> MTecknology: you got approved?
[20:13] <MTecknology> ya
[20:13] <Pici> MTecknology: So you're an Ubuntu Member?
[20:14] <MTecknology> yup
[20:14] <Pici> MTecknology: *you* need to request the cloak then
[20:14] <Myrtti> it's not given by default to all members
[20:14] <MTecknology> That's what I was asking
[20:15] <MTecknology> I didn't really ask it how I had it in my head
[20:15] <MTecknology> Who do I ask?
[20:15] <Myrtti> MTecknology: "hello I'm an ubuntu member, approved in the Loco council on the 19th, here's my launchpad page. Could I have a cloak, please?"
[20:16] <Pici> MTecknology: You can ask me and I can make sure that the basic steps are done and ask the group contacts to enable your cloak.
[20:16] <Pici> MTecknology: http://freenode.net/faq.shtml#nicksetup
[20:16] <Pici> MTecknology: Your lp page?
[20:16] <MTecknology> launchpad.net/~mtecknology
[20:18] <Pici> elky, nalioth, Pricey: ping, cloak for https://edge.launchpad.net/~mtecknology requested.
[20:32] <MTecknology> Pici: so I'll get it whenever one of them pops in here?
[20:32] <Pici> MTecknology: Indeedy.
[20:32] <Pici> MTecknology: Stick around though
[20:33] <MTecknology> yup, I'll be around for about 20min
[20:33] <MTecknology> then I need to go home and get ready for my LoCo meeting
[20:38] <Myrtti> MTecknology: they can set it up even if you're not here :-)
[21:10] <MTecknology> :D
[21:17] <nalioth> MTecknology: which is you, in your LP picture?
[23:04] <VicTheHunter> Hello
[23:05] <VicTheHunter> join #ubuntu-meta
[23:08] <Myrtti> what's that?
[23:15] <VicTheHunter> I was trying to join that channel
[23:15] <Myrtti> oh, ok
[23:15] <VicTheHunter> I need help troubleshooting video images, could you help me?
[23:16] <VicTheHunter> When I watch videos with Cheese, or totem-plugin-viewer 2.22.1, the images come out looking interleaved, and the bottom half is columns of solid colors.  How can I fix this?
[23:16] <Myrtti> have you asked in #ubuntu?
[23:16] <[NikO]> VicTheHunter, the channel support is #ubuntu
[23:16] <VicTheHunter> not yet, I didn't know. Thanks, I'll go there.