[12:19] <crimsun> 'lo raphink :)
[12:24] <raphink> hi crimsun
[12:25] <LaserJock> hi raphink
[12:25] <raphink> hello LaserJock
[01:18] <tomveens> hi
[01:21] <tomveens> what about the wired package
[01:21] <LaserJock> what about it?
[01:21] <tomveens> the progress
[01:22] <tomveens> I'ts almost impossible to compile it for my ubuntu amd64
[01:22] <LaserJock> hmm, well I have no idea what you are talking about, unfortunately
[01:22] <LaserJock> so I can't give you any info
[01:22] <tomveens> you know wired?
[01:22] <tomveens> thats a new DAW for linux
[01:23] <tomveens> Digital Audio Workstation
[01:23] <tomveens> looks great
[01:23] <tomveens> works! I don't know?
[01:23] <LaserJock> has somebody been working on it?
[01:24] <tomveens> I thought it was a release candidate in you're list but I can not figure out what is the progress. Or is there any progress, what are the problems?
[01:25] <crimsun> I don't see 'wired' at all on REVU, and it's not in the repos.
[01:25] <crimsun> [wired.sf.net]
[01:25] <crimsun> or [wired.is.free.fr]
[01:25] <LaserJock> it's on Candidates
[01:26] <LaserJock> and there is a Debian ITP
[01:26] <LaserJock> debian bug #372849
[01:26] <Ubugtu> Debian bug 372849 in wnpp "Subject: ITP: wired -- music production and creation software" [Wishlist,Open]  http://bugs.debian.org/372849
[01:26] <tomveens> there I saw it yes
[01:26] <tomveens> was only for 386
[01:27] <LaserJock> yeah, so I don't know if anybody is working on it in Ubuntu
[01:27] <crimsun> wired-daw seems like a suitable srcpkg name.
[01:27] <tomveens> what is that?
[01:27] <LaserJock> yeah, wired is a very vauge name
[01:27] <tomveens> you mean source package
[01:27] <LaserJock> yeah
[01:27] <crimsun> not to mention the clash with the other wnpp
[01:27] <tomveens> yes
[01:28] <tomveens> It is almost impossible to compile
[01:28] <LaserJock> "Notice that there is already an RFP (#353608) for a completely different
[01:28] <LaserJock> program also named wired. One of us will have to change its upstream name..."
[01:28] <LaserJock> :-)
[01:28] <tomveens> change to wired-daw is okay!
[01:29] <tomveens> you know something about the blender 2.42 package?
[01:29] <Toadstool> yay! cdbs updated in sid! who wants to request an uvf exception? :)
[01:29] <Toadstool> hi everybody
[01:30] <tomveens> hi
[01:30] <slomo> Toadstool: what was updated?
[01:30] <crimsun> Toadstool: but we already have a delta, so I don't know if it's really worth it ;)
[01:30] <tomveens> or cinelerra package?
[01:30] <crimsun> (meaning a delta prior to ogra's upload yesterday)
[01:30] <Toadstool> :)
[01:31] <Toadstool> slomo: er, a few bashism removed, a big fix in python-distutils.mk and... some other things
[01:31] <Toadstool> *bashisms
[01:32] <LaserJock> tomveens: hmm, blender 2.42 just hit Debian not too long ago
[01:33] <tomveens> you mean a package?
[01:34] <LaserJock> yeah
[01:34] <shawarma> Any takers of a really simple merge? http://www.linux2go.dk/edgy-merges/dietlibc-merge.diff
[01:34] <tomveens> amd64?
[01:34] <LaserJock> and cinelerra seems to be a work in progress
[01:35] <tomveens> what are the problems for cinelerra, you know?
[01:36] <LaserJock> tomveens: it seems like a yes on blender for amd64
[01:36] <LaserJock> I don't know
[01:36] <tomveens> I just saw it
[01:36] <tomveens> and i've got the deb
[01:36] <tomveens> thank you
[01:37] <LaserJock> tomveens: it just says that Rodrigo Belem is working on it (https://wiki.ubuntu.com/RodrigoBelem)
[01:37] <LaserJock> tomveens: I suppose you could email him and ask him how it is progressing if you feel the need
[01:38] <tomveens> I will
[01:38] <crimsun> shawarma: sure, sec.
[01:38] <tomveens> thanks
[01:40] <shawarma> crimsun: er... hang on.
[01:40] <crimsun> shawarma: (too late)
[01:40] <tomveens> blender 2.42 is not satisfied with my libavcodecs
[01:41] <shawarma> crimsun: I got my build logs messed up. It appears to ftbfs.
[01:42] <LaserJock> tomveens: what are you running?
[01:42] <tomveens> blender 2.41 (is that what you mean?)
[01:43] <LaserJock> tomveens: no what release of what
[01:43] <LaserJock> distro
[01:43] <tomveens> ubuntu dapper
[01:44] <crimsun> shawarma: that may be unrelated to dietlibc, though, noting make[1] : *** [bin-x86_64/elftrunc]  Segmentation fault
[01:44] <crimsun> I haven't looked more closely yet.
[01:44] <LaserJock> tomveens: and what are you trying to install?
[01:44] <LaserJock> blender 2.42?
[01:45] <tomveens> yes
[01:45] <tomveens> what is you're point?
[01:46] <LaserJock> tomveens: well, Debian's blender 2.42 package is built using different packages then Dapper
[01:46] <LaserJock> so you could have problems
[01:46] <tomveens> I know that, but I hoped because it is family, that it was possible
[01:47] <tomveens> I realy want to try the new blender
[01:47] <LaserJock> then you could build it on your dapper box using the Debian source
[01:47] <tomveens> I want to use openexr, and my timeline is shit
[01:48] <tomveens> that is an option
[01:48] <LaserJock> !info blender edgy
[01:48] <ubotu> blender: Very fast and versatile 3D modeller/renderer. In repository main, is optional. Version 2.41-1ubuntu5 (edgy), package size 4797 kB, installed size 12744 kB
[01:49] <tomveens> You think it is easy to make the debian source a ubuntu package?
[01:49] <shawarma> crimsun: I'm quite sure it's dietlibc.
[01:49] <shawarma> crimsun: I'm looking at it now.
[01:50] <LaserJock> tomveens: hmm, looking at the current edgy package it looks like it might need a little tweaking
[01:50] <LaserJock> tomveens: you could try it I guess
[01:51] <tomveens> is the blender 2.42 already in the edgy package list?
[01:51] <LaserJock> no
[01:51] <LaserJock> it would need an upstream version freeze (UVF) request
[01:51] <LaserJock> since Ubuntu's Main repo has frozen
[01:51] <tomveens> why?
[01:52] <tomveens> and what is an uvf request?
[01:53] <LaserJock> well, right now the Main repo is under a freeze which mean you need to get permission to update a package to a newer version
[01:53] <lfittl_> LaserJock: are you still talking about blender? (ogra is working on it)
[01:54] <LaserJock> so it can be requested, but it isn't going to be automatically included
[01:54] <LaserJock> lfittl_: yeah
[01:54] <LaserJock> ah, excellent
[01:55] <tomveens> can I help?
[01:55] <lfittl_> LaserJock: problem is they added ffmpeg export/import, and we are not sure yet if we simply compile it without it, or solve it otherwise (e.g. by making a blender-ffmpeg package available)
[01:56] <LaserJock> ah, :/
[01:56] <lfittl_> tomveens: thanks, but there is not much you can do, it's complicated because we don't have ffmpeg in main, and blender needs it
[01:57] <lfittl_> tomveens: just wait for ogra, he will work on it
[01:57] <tomveens> How does the package procedure work?
[01:58] <lfittl_> what exactly do you mean?
[02:05] <tomveens> how does a new package begins and how does it ends?
[02:05] <tomveens> do you need to inform canonical for some packages?
[02:05] <tseng> you need to inform MOTU here
[02:05] <tseng> you upload your packages to REVU for... review
[02:06] <tseng> with enough votes someone will upload it for you
[02:17] <LaserJock> hmm, anybody know of any good documentation for uscan and uupdate?
[02:18] <LaserJock> I think I've got an ok watch file, I'm just not sure what to do with it
[02:18] <slomo> LaserJock: what exactly do you want to know?
[02:19] <slomo> run uscan -v to see whether your watch file works ;)
[02:19] <shawarma> crimsun: I found the error in dietlibc. I'll fix it tomorrow. Sorry.
[02:20] <shawarma> must... have... sleep.... Zzzz....
[02:20] <shawarma> G'night, guys!
[02:21] <LaserJock> slomo: ok, so the watch file works. uscan gave me a new upstream tarball
[02:22] <slomo> LaserJock: if you add "debian uupdate" at the end of the url-line of the watch file uscan will automatically run uupdate on the new upstream tarball
[02:22] <LaserJock> ahh
[02:24] <shawarma> crimsun: Arh, heck. Here's the new patch: http://www.linux2go.dk/edgy-merges/dietlibc-merge.diff
[02:24] <shawarma> crimsun: And that one actually builds.
[02:24] <shawarma> crimsun: Hmm... if you actually uploaded the other one I sent will something go bad since this is the same ubuntu revision?
[02:26] <slomo> it won't work... you have to make a new revision
[02:27] <slomo> (unless you upload before some script that runs all 5 minutes gets the upload)
[02:56] <LaserJock> hi imbrandon
[02:56] <imbrandon> heya LaserJock
[03:04] <LaserJock> imbrandon: how's it going?
[03:05] <imbrandon> good good, just wakin up , getting some coffee^mt dew in me ;)
[03:06] <LaserJock> wakin up?
[03:06] <imbrandon> out of bed
[03:07] <imbrandon> kinda a late start ;)
[03:08] <LaserJock> imbrandon: I'll say. :-)
[03:08] <imbrandon> heh ok brb afk ~20 minutes , breakfast^Wdinner , shower and other morning type things , bbiab
[03:09] <Toadstool> 3am... time to go to bed :)
[03:09] <Toadstool> g'night
[03:16] <zul> er....ok...
[03:16] <zul> http://www.youtube.com/watch?v=kBVmfIUR1DA
[03:17] <bddebian> Heya gang
[03:26] <LaserJock> hi bddebian and zul
[03:26] <zul> hi LaserJock
[03:26] <bddebian> Heya LaserJock
[03:27] <bddebian> Anyone know autoconf very well?
[03:37] <bddebian> What utility is it to read the packages file and rip out reverse build depends?
[03:37] <ajmitch> you don't
[03:37] <ajmitch> you read the sources file
[03:37] <bddebian> That's what I meant but what do I use?
[03:38] <slomo> grep-dctrl
[03:38] <bddebian> Thanks slomo
[03:38] <slomo> grep-dctrl -FBuild-Depends -FBuild-Depends-Indep $package /var/lib/apt/lists/*_Sources
[03:39] <zul> didnt we go through this before?
[03:39] <bddebian> Yep, and will probably go through it again.  I'm brain dead
[03:40] <zul> yes we know :)
[03:40] <bddebian> Love you too honey
[03:40] <LaserJock> bddebian: that's what sticky notes are for :-)
[03:40] <zul> or you just remmember :)
[03:41] <bddebian> slomo: Isn't AC_CHECK_HEADERS[]  supposed to be [header, if yes, if no]  ?
[03:41] <bddebian> zul: Well we all can't be as good as you
[03:41] <ajmitch> slomo: I tried out metacity with its compositing manager
[03:41] <ajmitch> slomo: it's not going to be on by default in edgy, I'd say
[03:49] <bddebian> la la la
[03:52] <bddebian> Is this valid?
[03:52] <bddebian> grep-dctrl -FBuild-Depends -FBuild-Depends-Indep $package /var/lib/apt/lists/*_Sources
[03:52] <bddebian> Gah, damnit
[03:52] <ajmitch> no
[03:52] <ajmitch> use cat
[03:52] <bddebian> AC_CHECK_HEADERS([linux/videodev2.h] , [v4l2=yes] , [v4l2=no] ,
[03:52] <bddebian>     [#include <linux/types.h>] )
[03:53] <bddebian> Is the 4th param valid?
[03:55] <bddebian> LaserJock: What about the Policy?
[03:56] <LaserJock> bddebian: I'm just upgrading gausssum in Debian
[03:56] <LaserJock> I'd like to make sure I do it right the first time
[03:56] <bddebian> Ah :-)
[03:57] <LaserJock> so apparently the Debian maitainer of debhelper doesn't much care for the new policy
[03:58] <LaserJock> it has to be NMU'd
[03:58] <LaserJock> that's interesting to me
[03:58] <bddebian> :)
[03:59] <bddebian> ajmitch, slomo, anyone know my AC_CHECK_HEADER thing?
[04:04] <LaserJock> darn, how are you supposed to know what to version these python deps?
[04:05] <zul> anyone seen this before? dpkg-shlibdeps: warning: format of `NEEDED libxenstore.so' not recognized
[04:06] <LaserJock> hi tritium
[04:06] <tritium> hi LaserJock
[04:06] <bddebian> LaserJock: You don't need to, that's the beauty of it
[04:06] <bddebian> Heya tritium
[04:06] <tritium> heya bddebian
[04:07] <LaserJock> bddebian: right now it looks like I need debhelper (>= <IP_ADDRESS>), python (>= 2.3.5-7), python-all-dev, python-central (>= 0.4.17)
[04:08] <LaserJock> but I think python (>= 2.3.5-10) would work too
[04:08] <LaserJock> do you really have to crawl through the changelog of every dep to find these things?
[04:08] <LaserJock> anybody know of an email or something  that says what to use?
[04:14] <bddebian> LaserJock: Hang on
[04:14] <bddebian> http://wiki.debian.org/DebianPython/NewPolicy
[04:14] <bddebian> http://wiki.debian.org/DebianPythonFAQ
[04:15] <LaserJock> bddebian: thanks!
[04:16] <bddebian> Well transcode's wiki page sucks
[04:20] <LaserJock> bddebian: sounds good
[04:22] <bddebian> w00t, axiom built
[04:22] <bddebian> On all archs I might add (except possibly sparc)
[04:23] <zul> whee
[04:24] <zul> that reminds me i need something to drink
[04:27] <LaserJock> *-o-*
[04:27] <LaserJock> *-o/*
[04:27] <LaserJock> *\o/*
[04:28] <LaserJock> my cheerleading skills stink
[04:28] <fowlduck> is that a cheerleader?
[04:28] <fowlduck> haha :)
[04:28] <zul> whee...got it
[04:29] <bddebian> LaserJock: :-)
[04:32] <LaserJock> goooooooo BDDEBIAN!
[04:33] <bddebian> Well I'm doing much worse on slomo's list :-(
[04:46] <bddebian> autoreconf runs aclocal right?
[05:23] <bddebian> @$%$^2456
[05:23] <bddebian> slomo: Still around?
[05:24] <tseng> wish he was
[05:24] <tseng> but it seems not
[05:24] <bddebian> Heya tseng
[05:24] <tseng> hi
[05:38] !lilo:*! Happy Sunday afternoon.... reminder to Aus users: freenode's unofficial channel for its Australian users is ##australia .... please feel free to stop by :)
[05:58] <LaserJock> \o/
[05:59] <bddebian> LaserJock: ?
[06:00] <LaserJock> I think my gausssum package is ready to go
[06:00] <LaserJock> it's very nearly lintian clean
[06:01] <bddebian> Sweet, congrats!
[06:05] <LaserJock> I think everybody should maintain at least one package in Debian
[06:07] <bddebian> No way ;-P
[06:09] <Yagisan> LaserJock, I'm personally not intrested in that. While there are some good areas (-mentors, -games, the people that also work on ubuntu) where people act decent,
[06:10] <Yagisan> I just found that there far to many hostile, technocrats that I probally would not be able to work with. I looked at joining 4 times, and each time, those people put me off, so I've no intention of considering it again
[06:10] <bddebian> Yagisan: Sounds familiar :-)
[06:12] <Yagisan> bddebian, I admire the work that many of them do, but, the bulk either don't encourage new developers, or show apathy towards it by not reigning in the jerks.
[06:14] <bddebian> Aye, that is what brought me to Ubuntu
[06:14] <bddebian> Though I suppose many in Ubuntu aren't necessarily happy about that either ;-P
[06:15] <Yagisan> bddebian, well, that I suppose is another thing we have in common
[06:15] <bddebian> :-)
[06:23] <Hobbsee> hi all
[06:25] <Yagisan> G'day Hobbsee
[06:25] <Hobbsee> hi Yagisan
[06:27] <LaserJock> Yagisan: well, I never said that you had to become a DD
[06:28] <bddebian> Heya Hobbsee
[06:29] <Hobbsee> hi bddebian
[06:29] <Hobbsee> hey LaserJock
[06:29] <Yagisan> LaserJock, To be honest, not being a DD is a very much second class status there. Not being an ubuntu member here is far less so, and does not prevent me from getting what I think is important from being done.
[06:34] <Yagisan> hmm. Do we have any live-USB verision of ubuntu ?
[06:35] <LaserJock> hi Hobbsee
[06:35] <LaserJock> Yagisan: I know. I just like getting to know a package like you get to do in Debian
[06:37] <Yagisan> LaserJock, that I agree with. I maintain my own packages, that one day will be in Ubuntu. I should send the latest version to revu for comments on my packaging of it.
[06:55] <ajmitch> afternoon
[06:55] <bddebian> Heya ajmitch
[06:56] <bddebian> ajmitch: Hey, what do I do if running autoreconf causes unrepresentable changes to source?
[06:56] <ajmitch> autoreconf --install
[06:56] <ajmitch> otherwise it'll usually symlink which breaks things
[06:57] <bddebian> Frick.  So I'm screwed now?
[06:57] <ajmitch> no
[06:57] <bddebian> I mean I have to re-pull and reapply all my fixes?
[06:57] <bddebian> Then autoreconf?
[06:58] <ajmitch> whatever works
[06:58] <ajmitch> find the symlinks, remove them, rerun autoreconf
[06:58] <bddebian> Ah
[06:59] <bddebian> Isn't -i the same as --install?
[06:59] <bddebian> Ah, yes.  I did autoreconf -f -i -s
[06:59] <bddebian> But still get that error
[07:02] <bddebian> ajmitch: Should I not have done -f ?
[07:02] <ajmitch> bddebian: -s is symlink
[07:02] <ajmitch> I told you not to do that
[07:02] <bddebian> Oh, I meant that's what I ran the first time
[07:02] <ajmitch> and -i by default doesn't symlink
[07:03] <zakame> hi all
[07:04] <bddebian> Heya zakame
[07:04] <zakame> heya bddebian, playing with autotools huh?
[07:04] <zakame> hmm why is my LP karma getting higher andhigher? :/
[07:05] <bddebian> zakame: Just breaking stuff as usual :-)
[07:09] <crimsun> shawarma: changelog tweaked, interdiff(1) output applied, uploaded.
[07:10] <bddebian> Hi crimsun
[07:10] <zakame> hello crimsun
[07:10] <Hobbsee> hi crimsun
[07:10] <crimsun> 'lo bddebian, zakame, Hobbsee, ajmitch
[07:11] <zakame> crapbroken spacebar
[07:11] <bddebian> hehe
[07:12] <ajmitch> hi crimsun
[07:12] <zakame> hi ajmitch
[07:12] <zakame> how's NetworkAuth going?
[07:13] <bddebian> ajmitch: I love you man! :-)
[07:14] <ajmitch> no you don't
[07:14] <ajmitch> zakame: going alright :)
[07:14] <ajmitch> how's your project?
[07:14] <bddebian> ajmitch: I do
[07:15] <zakame> ajmitch: quite ok too ow completing the unit tests for integration :)
[07:15] <ajmitch> great :)
[07:25] <zakame> bug 54520
[07:25] <Ubugtu> Malone bug 54520 in robotour "[Edgy MoM]  Please sync robotour 3.2.1-3 from Debian unstable" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/54520
[07:42] <bddebian> Gnight folks
[08:54] <TheMuso> Hobbsee: I feel your pain.
[08:54] <TheMuso> I remember the hassles I went through.
[08:54] <Hobbsee> eek, yeah, yours were likely even worse.
[08:55] <TheMuso> Yeah.
[08:55] <Hobbsee> yay.  it now says i'm doing the proper 4 subjects this semester, instead of three.
[08:55] <TheMuso> I tried dealing with the disabilities services, but they sucked.
[08:55] <Hobbsee> they usually do.
[08:55] <TheMuso> So I found out.
[08:55] <TheMuso> I ended up not using them, and dealt directly with lecturers.
[08:56] <TheMuso> Worked much better.
[08:56] <Hobbsee> yep
[08:56] <Hobbsee> oh yay.  it now even shows that i'm doing the advanced computing.
[08:56] <TheMuso> heh
[08:57] <Hobbsee> now if i can just get it to *print*, then i'll be happy.
[08:57] <TheMuso> What sort of timetable do you have?
[08:58] <Hobbsee> TheMuso: not such a great one as semester 1, unfortunately - 9am classes almost every day.
[08:58] <ajmitch> lucky you
[08:59] <Hobbsee> HAH!
[09:00] <imbrandon> hehe Hobbsee still got a question
[09:00] <imbrandon> off the phone / vnc now
[09:00] <imbrandon> sorry heh
[09:02] <Hobbsee> TheMuso: bleh.  got a three hour break each wednesday.  yuck.
[09:02] <TheMuso> That sucks.
[09:02] <TheMuso> My first semester, I had a 5 hour break on Wednesdays.
[09:02] <Hobbsee> ouchy
[09:03] <TheMuso> Every week I told myself I would do something ulseful in that time, but 95% of the time, I didn't.
[09:03] <Hobbsee> heh
[09:04] <Hobbsee> apart from that, my timetable isnt so evil.
[09:04] <Hobbsee> 6 hours straight will be fun though
[09:04] <TheMuso> Yuck.
[09:04] <TheMuso> What day is that?
[09:05] <Hobbsee> oh, wait, i can make it less evil.
[09:05] <Hobbsee> TheMuso: that's each monday
[09:05] <Hobbsee> no, i can kill the 3 hour break - yay1
[09:05] <TheMuso> Cool.
[09:08] <Hobbsee> right...that timetable is decidedly Less Evil (tm) than it was before.
[09:10] <TheMuso> heh
[09:25] <Yagisan> then reality crashes down around him
[09:25] <Hobbsee> heh
[09:26] <Yagisan> as it really menas 11~12pm to 4am
[09:53] <luks> hi, any revu admins around?
[09:53] <luks> i'm trying to recover my password<EMAIL_ADDRESS>says "Now paste the text below, and enter EOT<return>", but there is no text below
[09:53] <luks> is this a known bug?
[09:58] <Hobbsee> luks: your key is on the keyserver, right?
[09:58] <luks> yes
[09:58] <luks> at least used to be :)
[09:59] <Hobbsee> ajmitch: ping?
[10:00] <ajmitch> yes?
[10:00] <Hobbsee> ajmitch: ^ revu stuff
[10:01] <ajmitch> luks: have you uploaded a package that appears on REVU?
[10:01] <luks> yep
[10:01] <ajmitch> which one?
[10:01] <luks> http://revu.tauware.de/details.py?upid=2331
[10:01] <luks> and http://revu.tauware.de/details.py?upid=2252
[10:02] <ajmitch> with that same gpg key?
[10:02] <luks> yes
[10:04] <ajmitch> are you currently in the ubuntu-universe-contributors group on launchpad?
[10:04] <luks> no
[10:04] <ajmitch> please join it
[10:04] <ajmitch> keyring is synced from that group, so revu isn't able to find your key
[10:05] <luks> ah
[10:06] <ajmitch> once you've joined, tell me, I'll approve membership for that group & sync the keyring
[10:06] <luks> i've already joined
[10:08] <ajmitch> ah right, it's open membership now
[10:09] <luks> okay, thanks
[10:13] <ajmitch> ok, try again now
[10:37] <luks> works
[10:37] <luks> thanks again
[10:51] <slomo> somebody awake? :)
[10:57] <ajmitch> slomo: hi
[10:57] <slomo> hi ajmitch :)
[10:58] <slomo> i'm searching for someone who wants to improve his karma for all the forum users... by updating xgl :P i took a short look and it seems to be not much work
[10:58] <ajmitch> already done it
[10:58] <ajmitch> it just needs uploaded
[10:58] <slomo> ?
[10:58] <slomo> nice :)
[10:59] <ajmitch> I also tested out metacity with compositing, which didn't work so well
[10:59] <slomo> because of nvidia drivers?
[10:59] <slomo> or something else too?
[10:59] <ajmitch> yeah
[10:59] <ajmitch> crashed on nvidia drivers, gave artifacts on intel
[10:59] <slomo> ok, so get xgl/compiz uploaded and be the hero of the day? :)
[11:00] <ajmitch> compiz is a different matter ;)
[11:00] <slomo> why?
[11:00] <ajmitch> should I upload upstream, or the fork that everyone uses?
[11:01] <slomo> who did the fork?
[11:01] <ajmitch> quinnstorm
[11:01] <slomo> take upstream ;)
[11:02] <ajmitch> then all the users will complain :)
[11:02] <slomo> what exactly did he do to poor compiz?
[11:03] <ajmitch> patched the hell out of it, added a bunch of new features
[11:03] <slomo> hm, maybe upload upstream for now and then add the useful parts of his stuff as a patchset
[11:04] <imbrandon> and alot of kde fixes iirc
[11:04] <ajmitch> I suppose I could
[11:04] <ajmitch> I don't use it myself
[11:05] <imbrandon> ajmitch: or do upstream and poke quinn to patch and submit
[11:05] <ajmitch> heh
[11:05] <imbrandon> to the official repo
[11:05] <imbrandon> ;)
[11:05] <ajmitch> of course, I'd put the version number I upload higher than the fork's
[11:05] <slomo> ajmitch: just do it :) it can't be worse than what we have now and finally users will stop complaining
[11:07] <slomo> ajmitch: and for f-spot... shall i already upload a mono that has sqlite2 in recommends instead of depends?
[11:07] <ajmitch> I'll do that, I'd prefer to upload to debian & sync for now
[11:07] <slomo> i mean mono itself, not f-spot
[11:08] <slomo> libmono-sqlite*-cil depends on both sqlite libs
[11:08] <ajmitch> ah ok
[11:08] <ajmitch> go ahead & do that
[11:08] <slomo> (i.e. you don't have to depend on that yourself :P )
[11:08] <ajmitch> I'll drop the explicit deps
[11:08] <ajmitch> since they used to be needed
[11:08] <slomo> yes, until the large mono split :)
[11:08] <slomo> i wonder why beagle still depends on old sqlite lib
[11:08] <slomo> tseng: ^--- ?
[11:09] <ajmitch> do I still need to depend on libmono0?
[11:10] <slomo> nope
[11:10] <slomo> mono-jit depends on that
[11:10] <ajmitch> great
[11:10] <slomo> all dependencies are fine now (well, libsqlite0 isn't anymore in some minutes ;) )
[11:12] <slomo> ajmitch: what do you think? libsqlite0 to recommends or to suggests?
[11:12] <ajmitch> suggests
[11:12] <ajmitch> I might hold off uploading f-spot to debian for about 2 days
[11:12] <ajmitch> Too young, only 8 of 10 days old
[11:12] <ajmitch> it's 2 days off going into testing
[11:13] <slomo> hmm, i would really prefer it if you could upload f-spot to ubuntu first then... then we could already add it to the seed, get it moved into main by that and have it on the knot2 cds
[11:13] <slomo> knot2 is next week afaik
[11:13] <ajmitch> hm ok
[11:13] <ajmitch> that shouldn't be a problem
[11:14] <ajmitch> it's just filing a sync bug
[11:14] <ajmitch> & 1 extra changelog entry
[11:14] <ajmitch> ok, changed -4 to -3ubuntu1 :)
[11:14] <slomo> thanks :)
[11:14] <slomo> will you write the MIR and add it to the seed? :)
[11:15] <ajmitch> I can
[11:15] <ajmitch> though pitti should approve the MIR before adding
[11:15] <Lathiat> is there a fix for this broken text stuff?
[11:15] <slomo> ajmitch: the kubuntu seeds had some stuff in that wasn't in main yet too... it only speeded up the review of the MIR ;)
[11:16] <ajmitch> Lathiat: Option "RenderAccel" "0"
[11:16] <Lathiat> ah
[11:16] <ajmitch> doesn't seem to affect desktop performance much that I can see
[11:16] <ajmitch> slomo: naughty
[11:17] <slomo> ajmitch: or just upload f-spot for now and ask pitti by mail to look at it asap because you like to have this on knot2 ;)
[11:19] <ajmitch> heh
[11:19] <ajmitch> pitti is just online now :)
[11:20] <ajmitch> and of course it's being argued on the mailing list
[11:21] <slomo_> ajmitch: or just upload f-spot for now and ask pitti by mail to look at it asap because you like to have this on knot2 ;)
[11:22] <slomo_> ok... i didn't know when my connection silently dropped ;)
[11:23] <slomo_> mono uploaded
[11:25] <ajmitch> f-spot uploaded
[11:26] <slomo_> cool... so world domination is near now :)
[11:26] <imbrandon> hehe
[11:27] <imbrandon> ajmitch: did that gnome-control-center for ppc stuff works its self out that you know of ?
[11:29] <ajmitch> imbrandon: it should have
[11:30] <imbrandon> kk
[11:41] <slomo_> ajmitch: hmm, really beagle uses sqlite0... do you know whether there is still a reason? or whether i can simply change that now? ;)
[11:41] <ajmitch> you'll have to ask tseng
[11:42] <slomo_> at least this explains why beagle can't search f-spot fotos
[11:42] <ajmitch> users will have to remove their index
[11:42] <ajmitch> hm, I thought I'd patched that properly to use sqlite3 if the f-spot db was sqlite3
[11:42] <slomo_> nope
[11:42] <slomo_> it uses the same version of sqlite as beagle uses for the f-spot helper
[11:46] <slomo_> ajmitch: will it remove the old index automatically?
[11:48] <ajmitch> I don't know
[11:49] <slomo_> i'll test it
[11:49] <Nafallo> IIRC you changed it to use the new sqlite if there wasn't an index already and use the old one if there was...
[11:50] <slomo_> Nafallo: nope, it uses whatever version configure finds
[11:50] <Nafallo> so auto-converting the old index then?
[11:50] <slomo_> don't think so... it will probably drop the old index and create a new one
[11:51] <Nafallo> ouch.
[11:53] <slomo_> it's only an index ;) not a database that can't be easily automatically created like in f-spot
[11:55] <ajmitch> which is why I've got to get that sqlite2->3 convertor working properly
[11:55] <ajmitch> which is easier said than done, since it doesn't like having both in a single process, it seems
[11:55] <slomo_> why btw? the symbols are prefixed with the sqlite version
[11:56] <ajmitch> I know, but it stops reading very quickly if I try to read from the old db & write to the new in a loop :)
[11:58] <slomo_> so try the read all && write all approach :)
[12:00] <ajmitch> will do, I just need time to sit & do it :)
[12:00] <ajmitch> not too hard, since you can get the aql to create the tables out of the existing table
[12:00] <Nafallo> woha! what happened to the deskbar-applet? :-P
[12:00] <ajmitch> s/aql/sql/
[12:01] <ajmitch> Nafallo: it got an upgrade?
[12:01] <Nafallo> seems like it. the textfield has an orange border now :-)
[12:10] <slomo_> ajmitch: Warn: Likely sqlite database version mismatch trying to read from /home/slomo/.beagle/TextCache/TextCache.db.  Purging.
[12:10] <slomo_> ajmitch: so it only drops the index ;)
[12:11] <ajmitch> oh good
[12:11] <ajmitch> at least it doesn't bail out & die straight away
[12:11] <Lathiat> is gnome-panel eating cpu & the applications menu flickering constantly a known probleM?
[12:12] <slomo_> ajmitch: i guess i'll upload this later after tseng showed up :) i've fixed the bashism bugs too now
[12:12] <slomo_> Lathiat: yes
[12:12] <Lathiat> ok
[12:12] <slomo_> Lathiat: bug 52405
[12:12] <Ubugtu> Malone bug 52405 in gnome-panel "gnome-panel eats 50% cpu for half an hour and flickers" [Untriaged,Confirmed]  http://launchpad.net/bugs/52405
[12:13] <slomo_> ajmitch: seems to be a bit faster too
[12:14] <Lathiat> cheers
[12:19] <Toadstool> hey everybody
[12:19] <Hobbsee> hi Toadstool
[12:19] <Toadstool> hi Hobbsee
[01:20] <Amaranth> what helper installs dbus conf files?
[01:46] <Hobbsee> Amaranth: got a path to one of the conf files?
[01:47] <Amaranth> Hobbsee: /etc/dbus-1/system.d/
[01:47] <Hobbsee> Amaranth: looked for that file path on packages.ubuntu.com?
[01:47] <Amaranth> it goes in your package as debian/<package>.dbus-conf
[01:47] <Hobbsee> Amaranth: in the second section, about the files/directories?
[01:47] <Hobbsee> oh, which helper, not which package...dont mind me
[01:47] <Amaranth> Hobbsee: I'm trying to figure out which debhelper script installs these files
[01:48] <Hobbsee> ah
[01:48] <Amaranth> *smack*
[01:48] <Hobbsee> hmm?
[01:49] <Amaranth> I dunno, it's 7am and I haven't gone to bed yet.
[01:49] <Hobbsee> ouch
[01:50] <Amaranth> Yeah. :P
[01:50] <Amaranth> I can't get my daemon and client to speak dbus to each other.
[01:55] <Amaranth> meh, it can wait until afternoon :P
[02:40] <slomo_> Gloubiboulga: ping?
[02:48] <Gloubiboulga> slomo_, hello
[02:48] <slomo_> Gloubiboulga: hi :) do you have clearlooks window manager decorations in xfce?
[02:48] <Gloubiboulga> slomo_, yes
[02:49] <slomo_> you might want to get the ones from http://www.stellingwerff.com/?p=16
[02:49] <slomo_> they fit much better with the current clearlooks gtk2 engine
[02:51] <Gloubiboulga> slomo_, thanks, I'll test this right now :)
[02:51] <Hobbsee> how do i make a file executable in debian/rules with debhelper?  pastebin of rules file is at http://rafb.net/paste/results/VplRFC53.html
[02:51] <slomo_> Gloubiboulga: np :) gnome uses them already with the latest gnome-themes upload
[02:52] <slomo_> Gloubiboulga: and if you need a sponsor for main for this (and janimo isn't there) feel free to ping me
[02:52] <Gloubiboulga> slomo_, thanks again ;)
[02:53] <Gloubiboulga> Hobbsee, with chmod?
[02:54] <Gloubiboulga> it'll work
[02:55] <Hobbsee> Gloubiboulga: i'd used the command on the second line to make it work for amarok, which uses cdbs.  unfortunately, you cant chmod +x a file in the source, and then expect it to be copied over as an exectable
[02:55] <Hobbsee> Gloubiboulga: and the idiot question of where do i actually put the command, of course
[02:56] <Hobbsee> i wonder if it's being stripped later with dh_strip
[02:56] <Gloubiboulga> Hobbsee, line 75,5
[02:57] <Hobbsee> Gloubiboulga: right, and i got the syntax right, as it installs in chmod a+x /usr/share/doc/libdvdread3/install-css.sh?
[02:58] <Gloubiboulga> Hobbsee, yep
[02:58] <Hobbsee> Gloubiboulga: yay!
[02:59] <Gloubiboulga> :)
[03:00] <Hobbsee> Gloubiboulga: still didnt work.
[03:00] <Gloubiboulga> :(
[03:00] <Hobbsee> Gloubiboulga: i'm assuming it is chmod a+x, as it is in amarok
[03:01] <Gloubiboulga> well, the line 65 should change the permissions already
[03:03] <Hobbsee> Gloubiboulga: oh, the 755 means executable?
[03:03] <Gloubiboulga> yes
[03:05] <Hobbsee> hmmm.
[03:08] <ivoks> anyone familiar with python? :)
[03:09] <slomo_> ivoks: depends on what you want to know ;)
[03:09] <ivoks> slomo_: i have a string, that looks like tuple
[03:09] <ivoks> slomo_: i just want to convert it to tuple
[03:09] <slomo_> no idea then ;)
[03:09] <ivoks> :)
[03:10] <slomo_> ivoks: "".join(x) maybe?
[03:10] <slomo_> if x = ('a', 'b', 'c') this does what you want
[03:10] <luks> that converts a tuple to string :)
[03:11] <ivoks> :)
[03:11] <ivoks> :*
[03:11] <luks> "a, b, c".split(", ")
[03:11] <luks> ?
[03:11] <slomo_> that makes an list
[03:12] <ivoks> i have
[03:12] <luks> tuple("a, b, c".split(", "))
[03:12] <ivoks> result=('keyword', 'not-attempted')
[03:12] <ivoks> and this is a string
[03:13] <ivoks> "".join(result) results in string too :/
[03:14] <luks> you mean you have "result=('keyword', 'not-attempted')" as a string?
[03:14] <luks> if yes, then simply exec it
[03:14] <ivoks> no ('keyword', 'not-attempted') is a string
[03:14] <ivoks> result is variable
[03:19] <ivoks> eh :)
[03:24] <Hobbsee> Gloubiboulga: GOT IT!!!!  :D
[03:25] <Gloubiboulga> Hobbsee, YAY! :)
[03:25] <Gloubiboulga> Hobbsee, what is the solution?
[03:25] <slomo_> Gloubiboulga: what do you think about the theme? do you have an screenshot? i have no idea how it looks on xfce :)
[03:25] <Hobbsee> Gloubiboulga: dh_fixperms automatically strips all executable permissions off anything in /usr/docs - so you have to exclude that file.  it's in man dh_fixperms
[03:26] <Gloubiboulga> slomo_, I'm fighting to make it work...
[03:27] <Gloubiboulga> Hobbsee, damn, it's something I have to remember of :)
[03:27] <Hobbsee> Gloubiboulga: :)
[03:27] <Hobbsee> Gloubiboulga: i'd already checked dh_strip, it's listed in debian maintainers guide. you've got uploads to main, dont you?
[03:28] <Gloubiboulga> Hobbsee, nop
[03:28] <Hobbsee> Gloubiboulga: didnt you go for them in the last meeting?
[03:28] <Gloubiboulga> Hobbsee, no, I'll go for core-dev at next TB
[03:29] <zul_> heh heh...
[03:29] <zul_> good luck
[03:29] <Hobbsee> Gloubiboulga: nice :)
[03:29] <Hobbsee> as for zul_...
[03:29] <Gloubiboulga> Hobbsee, sorry, you'll have to find someone else to sponsor your upload ;p
[03:29] <Hobbsee> Gloubiboulga: yeah, that's harder than it used to be
[03:30] <zul_> Hobbsee: why dont you go for core-dev at the next tb meeting?
[03:30] <Gloubiboulga> zul_, you'regoing for core-dev too? you're not already?
[03:30] <Hobbsee> zul_: havent done enough?
[03:30] <zul_> ah
[03:30] <Hobbsee> zul_: well, i dont think i've done enough.  but then you can see how long it took me to go for motu.
[03:31] <zul_> it could make your stop pestering people ;)
[03:32] <Hobbsee> zul_: well, yeah, exactly.  unfortunatly, the core-dev is smaller, so i have to pester the same people more often
[03:32] <zul_> true
[03:32] <slomo_> Gloubiboulga: for gnome it was just "cp foo bar" ;)
[03:32] <Gloubiboulga> slomo_, it should be the same for Xfce...
[03:45] <tuxmaniac> guys
[03:46] <tuxmaniac> Is launchpad and malone gonna be open sourced in the near future ?
[03:46] <Hobbsee> hi tuxmaniac
[03:46] <tuxmaniac> Hobbsee> hi howdy you
[03:46] <Hobbsee> tuxmaniac: good, fixing bugs
[03:47] <bddebian> Heya gang
[03:47] <tuxmaniac> Is launchpad and malone gonna be open sourced in the near future ?
[03:47] <bddebian> Hi Hobbsee
[03:47] <bddebian> tuxmaniac: Not that I know of
[03:47] <tuxmaniac> bddebian> so malone will still continue to store things in its own format?
[03:48] <Gloubiboulga> slomo_, http://tiber.tauware.de/~gauvain/Screenshot.png
[03:50] <slomo_> Gloubiboulga: looks good... only that the gnome version has a stronger and not so dark blue... you don't use the latest gtk2-engines, do you?
[03:51] <Gloubiboulga> slomo_, the one in the edgy repos
[03:51] <Gloubiboulga> hum, wait
[03:52] <slomo_> 2.7.6 is what you want
[03:52] <Gloubiboulga> it's 2.7.4
[03:52] <Gloubiboulga> 2.7.6 is in the gtk2-engines package now, right?
[03:52] <slomo_> then update please :)
[03:52] <slomo_> yes
[03:54] <Gloubiboulga> hum, a little mcs bug... some Widgets have not been refreshed
[03:55] <slomo_> hm, restart your session ;) but you have a lighter, stronger blue too now?
[03:55] <Gloubiboulga> yep
[03:55] <Gloubiboulga> brb
[03:58] <Gloubiboulga> slomo_, you can refresh the screenshot :)
[03:58] <slomo_> Gloubiboulga: right... that's how it should look like :)
[03:59] <Gloubiboulga> it's nice :)
[04:00] <slomo_> Gloubiboulga: metacity themes seem to have hardcoded colors... your xfce theme seems to take the colors from the gtk theme, right?
[04:00] <slomo_> in that case it's not that important to update the theme... but nice nonetheless :)
[04:00] <Hobbsee> Gloubiboulga: FYI:  you use dh_fixperms --except /path/to/file/file
[04:01] <bddebian> slomo_: I got transcode working and uploaded but I'm not sure why it's dep-wait
[04:01] <slomo_> bddebian: that's in the build log
[04:01] <Gloubiboulga> slomo_, I have to admit that I don't really know... :)
[04:01] <bddebian> slomo_: I know but what I am saying is that It build locally :-)
[04:01] <Gloubiboulga> I haven't touched all the artwork stuff yet
[04:02] <slomo_> bddebian: liba52-0.7.4-dev | liba52-dev would be the correct way
[04:02] <slomo_> bddebian: the buildds sometimes have problems with virtual packages it seems
[04:02] <bddebian> Oh
[04:03] <slomo_> just reupload with that small change :)
[04:03] <Gloubiboulga> Hobbsee, thanks :)
[04:04] <Hobbsee> Gloubiboulga: :)
[04:05] <bddebian> slomo_: OK
[04:05] <slomo_> bddebian: you missed "* moved libxvidcore4 to Recommends rather than depends."
[04:06] <slomo_> other than that it seems to be fine :) good work :)
[04:06] <bddebian> Doh, I suck :-(
[04:06] <slomo_> no, you rock :)
[04:09] <bddebian> Bah :-)
[04:24] <Gloubiboulga> archive.ubuntu.com is slow today... might be because today's sunday
[04:28] <Riddell> how do I enable universe in my pbuilder?
[04:30] <Hobbsee> Riddell: got a pbuilderrc?
[04:30] <Riddell> yep
[04:30] <Hobbsee> Riddell: usually in /etc/pbuilderrc?
[04:30] <bddebian> Riddell: Edit pbuilderrc
[04:30] <slomo_> Riddell: OTHERMIRROR="deb http://archive.ubuntu.com/ubuntu edgy universe multiverse restricted"
[04:30] <Hobbsee> there
[04:31] <Riddell> and then I need to re-create it?
[04:31] <bddebian> Nope just pbuilder update
[04:32] <Hobbsee> Riddell: sudo pbuilder-update --override-config
[04:32] <Hobbsee> dotn forget the overriding of the config
[04:34] <bddebian> Oh aye
[04:34] <Riddell> that seems to have done it
[04:35] <Riddell> we should change the default pbuilderrc to have that in it (commented out)
[04:35] <bddebian> Talk to the "powers that be" ;-)
[04:35] <bddebian> Err slave
[04:36] <bddebian> yes massa
[04:36] <Hobbsee> bddebian: massa?
[04:37] <bddebian> massa == master
[04:37] <Hobbsee> bddebian: ahhh...
[04:37] <Hobbsee> i suppose that's still better than being called mistress :)
[04:38] <zul> i choosed to hold my tongue
[04:38] <Hobbsee> zul: s/choosed/chose :)
[04:38] <zul> meh..
[04:38] <Hobbsee> zul: where are you from, btw?
[04:39] <zul> in canada or as some people call it canuckistan
[04:39] <Hobbsee> zul: ahhh...right
[04:47] <luks> edb
[04:47] <Hobbsee> night all
[04:53] <bddebian> slomo_: libxvidcore4 must be getting picked up by shlib depends.  If I make it a recommends does that override it?
[04:53] <slomo_> bddebian: nope... then don't change it
[04:53] <bddebian> OK
[04:54] <bddebian> Uploaded
[04:54] <bddebian> OK, shower time, bbl
[05:51] <bddebian> slomo_: If/when transcode succeeds, I will throw up gtranscode
[05:52] <slomo_> bddebian: perfect :)
[06:31] <siretart> slomo_: I'm just looking at transcode, but I'm failing at the libavcodec build-dep
[06:31] <siretart> slomo_: what else did you say needs a newer ffmpeg as well?
[06:31] <siretart> slomo_: and did you manage to reach sam?
[06:32] <slomo_> siretart: bddebian already did it... and works fine with our libavcodec it seems
[06:32] <slomo_> no he didn't answer yet :(
[06:32] <slomo_> and mplayer needs a newer ffmpeg... it likes to segfault with our current version
[06:32] <siretart> bddebian: my hero! :)
[06:34] <bddebian> :-)
[06:47] <bddebian> w00t transcode built on i386, PPC, and amd64
[06:48] <hub> hi
[06:48] <bddebian> Hello hub
[06:48] <hub> I need and advocating for hugin http://revu.tauware.de/details.py?upid=2808
[06:48] <hub> so I can upload it
[06:48] <hub> this time the license of vigra should be OK
[06:54] <bddebian> OK, swim time again, later folks
[07:09] <Spec> I can't 'pbuilder create' my pbuilder environment :-/, it keeps stalling after getting 2-5 packages :-/
[07:11] <slomo_> Riddell: what is "qt4-x11-kdecopy"? a copy of qt4-x11? ;)
[07:12] <Riddell> yes
[07:12] <Riddell> specifically it's the copy from kde's SVN
[07:13] <slomo_> hmm... what's the difference between the two?
[07:13] <Riddell> qt4-x11 is qt 4.1, qt4-x11-kdecopy is qt 4.2 preview plus some patches
[07:14] <slomo_> ok, sounds sane then :) this is needed for kde4? i guess kde4 will be the next kde version which i'll test :)
[07:18] <Riddell> slomo_: yes, it's what kde 4 needs, so the package is intended for people building kde 4
[07:18] <Riddell> any volunteers to package kdelibs trunk welcome :)
[07:30] <Linuturk> where would I begin to build and contribute a package installer of www.aptana.com ?
[07:34] <Linuturk> i'd like to start contributing to ubuntu with this good program, but I don't know where to start
[07:42] <Gloubiboulga> Linuturk, you can start with https://wiki.ubuntu.com/MOTU
[07:43] <Linuturk> yes, i've been reading that
[07:43] <Linuturk> thanks
[07:43] <Linuturk> i'm going to school
[07:43] <Gloubiboulga> nice :)
[07:43] <Linuturk> #ubuntu-motu-school that is
[07:44] <Gloubiboulga> did you look at the packaging guide to start with aptana?
[07:45] <Linuturk> packaging guide?
[07:45] <Spec> ubotu! ubugtu! whaa
[07:45] <Gloubiboulga> http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html
[07:47] <Linuturk> thanks
[07:47] <Linuturk> that helps
[07:47] <Gloubiboulga> cool :)
[08:30] <bddebian> re
[08:33] <Gloubiboulga> re bddebian
[08:33] <bddebian> Heya Gloubiboulga
[08:36] <Gloubiboulga> there's absolutely no documentation
[08:38] <bddebian> So what else is new? :)
[08:41] <Gloubiboulga> in pyxfce? everything is new :)
[08:41] <bddebian> No, I meant no documentation :)
[08:47] <Gloubiboulga> bddebian, I must be tired, I don't understand :s
[08:48] <Gloubiboulga> (heh, I usually speak french ;) )
[08:50] <Gloubiboulga> anaway, I'm off, see you later
[08:50] <bddebian> I am saying that it is common that there is no documentation :-)
[09:00] <Ademan> is there a compiz development channel?
[09:19] !lilo:*! We're going to be doing some pruning of bot klines. Please be aware that some spambots etc. may momentarily reappear.
[09:20] <Riddell> nixternal: ping
[09:20] <Riddell> doing UWN this week?
[09:23] <Riddell> Ademan: yes
[09:23] <Riddell> although I can't remember what it's called
[09:24] <Riddell> probably something obvious
[09:24] <Ademan> lol
[09:24] <Ademan> its not compiz though
[09:34] <toma> qquestion reguarding pbuilder: it requires a dsc to build, but what if i changed the changelog. Then there is no valid dsc.
[09:34] <bddebian> Toma: you need to rebuild the package with debuild or dpkg-buildpackage to generate the new .dsc
[09:37] <toma> bddebian: just an ordary dpkg-buildpackage is enough to create it?
[09:37] <bddebian> Toma: dpkg-buildpackage -S if you want it to sign the changes
[09:37] <bddebian> add -sa if you need to include the source
[09:38] <toma> *sigh*
[09:39] <toma> i want to use the pbuilder environments i created
[09:39] <bddebian> ?
[09:39] <bddebian> You can try pdebuild too but I don't know much about it
[09:40] <toma> i can not get pdebuild to use a dapper or breeze tgz
[09:48] <toma> ok dpkg -b creates the dsc and diff.gz
[09:48] <toma> ok
[09:49] <bddebian> Shit, someone screwed up the versioning for serpento
[10:11] <Sp4rKy> hi
[10:12] <Sp4rKy> i need some help with audacious
[10:13] <Sp4rKy> E: libaudacious: ldconfig-symlink-referencing-wrong-file usr/lib/libaudacious.so -> /tmp/buildd/audacious-1.0.0/debian/tmp/usr/lib/libaudacious.so.2.0.0 instead of libaudacious.so.2.0.0
[10:13] <Sp4rKy> what can i do for this error ?
[10:16] <Sp4rKy> hi mr_pouit :)
[10:16] <mr_pouit> hi Sp4rKy ^^
[10:16] <Sp4rKy> i think MOTUs are sleeping :/
[10:17] <mr_pouit> UTC-6 i think, and we are on UTC+2, so ^^...
[10:17] <mr_pouit> ((no that's stupid ^^)
[10:18] <Sp4rKy> :D
[10:19] <slomo_> Sp4rKy: run lintian with -i... it will explain this better to you
[10:19] <Sp4rKy> slomo_, i've done it , and look at the section of debian policy
[10:21] <slomo_> Sp4rKy: ok, i assume the link is to the full path of the library instead of using a relative path
[10:21] <slomo_> which then obviously breaks after installing the because
[10:21] <slomo_> s/the because//
[10:21] <Sp4rKy> yes
[10:21] <Sp4rKy> and so ...
[10:21] <Sp4rKy> what's wrong
[10:21] <slomo_> the build system of the package
[10:21] <Sp4rKy> because this link seems done with dh_link
[10:21] <slomo_> oh
[10:22] <slomo_> are you sure? then dh_link was used wrong ;)
[10:22] <slomo_> where is this package?
[10:22] <Sp4rKy> audacious
[10:22] <Sp4rKy> i'll dput it now
[10:26] <mr_pouit> Sp4rKy: why is there another Makefile in the package ?
[10:26] <slomo_> Sp4rKy: can you give me the url?
[10:26] <mr_pouit> because in this makefile is made another call to ldconfig...
[10:27] <Sp4rKy> mr_pouit, there is 2 Makefile in 2 rep
[10:27] <Sp4rKy> http://revu.tauware.de/details.py?upid=2609
[10:30] <slomo_> Sp4rKy: http://revu.tauware.de/revu1-incoming/audacious-0607051625/audacious-1.0.0/libaudacious/Makefile.in
[10:30] <slomo_> the post-hook is wrong
[10:30] <slomo_> install-posthook:
[10:30] <slomo_> this creates the ugly links
[10:33] <Sp4rKy> so i need make a patch
[10:34] <slomo_> yes
[10:35] <Sp4rKy> k
[10:36] <Sp4rKy> so i must delete the posthook entry ?
[10:38] <slomo_> no... patch it and make it right
[10:38] <slomo_> i.e. make relative links instead of absolute ones
[10:44] <Sp4rKy> but what's worng in this :
[10:44] <Sp4rKy>  @if test `whoami` = 'root' && test -z "$(DESTDIR)"; then \
[10:44] <Sp4rKy>    echo "[running ldconfig to update system library cache] "; \
[10:44] <Sp4rKy>    /sbin/ldconfig; \
[10:44] <Sp4rKy> echo "[system library cache updated] "; \
[10:44] <Sp4rKy>  fi
[10:48] <slomo_> nothing... but the install-posthook target in libaudacious/Makefile.in creates
[10:48] <slomo_> the links wrong
[10:49] <Sp4rKy> ok !
[10:53] <^ohoel> where can I find buildlogs again?
[10:54] <slomo_> https://launchpad.net/distros/ubuntu/edgy/+source/libgnomeui/2.15.90-0ubuntu2
[10:54] <slomo_> i.e. https://launchpad.net/distros/ubuntu/edgy/+source/$package/$version
[10:54] <slomo_> leave out the version and you can select one
[10:55] <^ohoel> ah, thanks slomo :)
[11:08] <crimsun> Sp4rKy: be aware of http://www.gentoo.org/security/en/glsa/glsa-200607-13.xml
[11:09] <Sp4rKy> crimsun, so i only need use the last version ?
[11:09] <crimsun> Sp4rKy: apparently, but I don't follow audacious development so I'm not the best person to ask.
[11:10] <Sp4rKy> ok
[11:10] <Sp4rKy> thx
[11:10] <crimsun> np
[11:40] <bmonty> we can drop the "c2" in the end of C++ packages for an unstable merge to edgy, right?
[11:41] <slomo_> no
[11:42] <doko> bmonty, slomo_ : if the soname in unstable did change, yes, if not: no
[11:42] <bmonty> soname didn't change
[11:42] <slomo_> doko: right, i didn't think about that case
[11:42] <bmonty> thanks doko


[03:36] <RadioZen>  Hello I have a question about installing .patch I googled it but I can't seem to figure it out. I downloaded https://patchwork.kernel.org/patch/7919851/ but I am such a newb that I don't know what to do... $ patch  PATCH doesn't work.
[03:40] <tsimonq2> RadioZen: #ubuntu is for support, please go there :)
[03:44] <RadioZen> thank you!
[16:30] <tyhicks> hello
[16:30] <tyhicks> #startmeeting
[16:30] <meetingology> Meeting started Mon Feb  6 16:30:54 2017 UTC.  The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:30] <meetingology> Available commands: action commands idea info link nick
[16:31] <tyhicks> The meeting agenda can be found at:
[16:31] <tyhicks> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:31] <tyhicks> there are no announcements today
[16:31] <tyhicks> [TOPIC] Weekly stand-up report
[16:31] <tyhicks> jdstrand: you're up
[16:31] <jdstrand> hi!
[16:31] <jdstrand> - several big PR reviews, in particular around Personal (unity8, maliit), but also others
[16:31] <jdstrand> - continue with seccomp arg filtering snappy policy (6 were sent up, more to come)
[16:31] <jdstrand> - various other snappy policy updates
[16:31] <jdstrand> - move to miscellaneous review tools updates as have time
[16:31] <jdstrand> mdeslaur: you're up
[16:32] <mdeslaur> I'm i the happy place this week
[16:32] <mdeslaur> I'm working on some updates
[16:32] <mdeslaur> I'll pick more from the list after that
[16:32] <mdeslaur> that's about it, sbeattie?
[16:32] <sbeattie> I'm also in the happy place this week.
[16:32] <sbeattie> I'll be focusing on updates this week.
[16:33] <sbeattie> That's pretty much it for me.
[16:33] <sbeattie> tyhicks: you're up
[16:33] <tyhicks> I'm on community this week
[16:33] <tyhicks> I need to prepare an apparmor SRU for bug 1661406
[16:34] <tyhicks> that's the only regression, due to the big SRU, that I'm aware of on Trusty but let me know if you want me to include any other changes in my upload
[16:35] <tyhicks> it looks like I have a few good security sponsorings to do this week
[16:35] <tyhicks> I'd still like to upload apparmor 2.11 to zesty
[16:35] <tyhicks> I expect to have some followup discussions and some libseccomp work fall out of the seccomp kernel patches that I sent up last week
[16:36] <tyhicks> I have a little bit of libvirt apparmor research to do around what it would take to dynamically update the policy when someone adjusts the disk image path via `virsh edit`
[16:36] <tyhicks> that's it for me
[16:36] <tyhicks> jj is out
[16:37] <tyhicks> sarnold: you're up
[16:37] <sarnold> I'm on bug triage this week, working my way down the MIRs; I'm very nearly finished with the mellon apache auth module, so advice on next one to start would be appreciated
[16:37] <sarnold> that's it for me, chrisccoulson?
[16:38] <chrisccoulson> I'm hoping to publish oxide updates this week. I was hoping to do it last week but they're blocked because I have to wait for the stable overlay PPA to be updated first
[16:38] <chrisccoulson> I'll also probably have to do a firefox update again (there's another point release)
[16:39] <chrisccoulson> I need to figure out why firefox crashes on arm, which currently prevents the build from completing
[16:39] <jdstrand> tyhicks: talk to me about virsh edit. this sounds like something that libvirt should be handling already
[16:40] <chrisccoulson> Other than that, I'll be working on bug 1638852
[16:40] <jdstrand> tyhicks: (ie, outside of this meeting)
[16:40] <tyhicks> jdstrand: will do - thanks
[16:40] <chrisccoulson> And no doubt I'll spend a bit of time crying about rust
[16:40] <chrisccoulson> That's me done
[16:40] <chrisccoulson> oh no
[16:40] <ratliff> I'm on CVE triage this week
[16:40] <tyhicks> chrisccoulson: looks like you're still expecting chromium-browser updates too
[16:40] <chrisccoulson> 1 more thing
[16:40] <chrisccoulson> Firefox/GCC4.9 on trusty doesn't run either, so I need to figure that out
[16:41] <chrisccoulson> Really done now :)
[16:41] <chrisccoulson> sorry
[16:41] <ratliff> :-)
[16:41] <ratliff> I'm triaging CVEs this week.
[16:41] <chrisccoulson> tyhicks, ack
[16:41] <ratliff> And still recovering from being sick.
[16:41] <ratliff> I am still working on updates for core (15.04) and touch.
[16:42] <ratliff> I will be out for 1/2 day on Friday.
[16:42] <ratliff> back to you, tyhicks
[16:43] <tyhicks> thanks
[16:43] <tyhicks> [TOPIC] Highlighted packages
[16:43] <tyhicks> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:43] <tyhicks> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:43] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/lib3ds.html
[16:43] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/hesiod.html
[16:43] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/newlib.html
[16:43] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/teeworlds.html
[16:43] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/libssh2.html
[16:43] <tyhicks> [TOPIC] Miscellaneous and Questions
[16:43] <tyhicks> Does anyone have any other questions or items to discuss?
[16:44] <tyhicks> jdstrand, mdeslaur, sbeattie, sarnold, ChrisCoulson, ratliff: Thanks!
[16:44] <tyhicks> #endmeeting
[16:44] <meetingology> Meeting ended Mon Feb  6 16:44:48 2017 UTC.
[16:44] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-02-06-16.30.moin.txt
[16:45] <sbeattie> tyhicks: thanks!
[16:45] <sarnold> thanks tyhicks!
[16:45] <ratliff> thank you, tyhicks!
[16:47] <mdeslaur> thanks tyhicks
[16:50] <jdstrand> thanks tyhicks :)


[09:35] <smartboyhw> knome: Are you here?
[09:35] <ochosi> hey smartboyhw
[09:35] <ochosi> (i'm not knome though)
[09:35] <smartboyhw> ochosi: Hey
[09:36] <ochosi> just wanted to ask you 'bout lightdm greeter quickly
[09:36] <ochosi> there were discussions with folks from lubuntu on cooperating on the greeter and its design
[09:36] <ochosi> one guy created a wiki page with a few of the specifications
[09:36] <ochosi> https://wiki.ubuntu.com/frankbooth/lightdm-gtk-greeter
[09:36] <smartboyhw> ochosi: What do you mean?
[09:37] <smartboyhw> OK, looking at it now
[09:37] <ochosi> there are a few things i like about it, but others i rather dislike
[09:37] <smartboyhw> Ha, good sketch
[09:37] <ochosi> anyway, the main question was when approximately you would have time to work on it
[09:37] <ochosi> just to know when mockups etc should be in palce
[09:37] <ochosi> place
[09:38] <smartboyhw> OK.
[09:41] <ochosi> to get a plan, since UI freeze is pretty soon
[09:41] <smartboyhw> ochosi: Is it in a weel?
[09:41] <ochosi> and whatever we can get out the door before makes our lives easier
[09:41] <smartboyhw> *week
[09:41] <ochosi> yeah, approx
[09:41] <ochosi> i think thursday
[09:42] <ochosi> (off the top of my head)
[09:42] <smartboyhw> Hmm....That's a disaster.
[09:42] <ochosi> heh
[09:42] <ochosi> no worries
[09:42] <ochosi> we can file exceptions
[09:42] <smartboyhw> ochosi: :)
[09:42] <ochosi> what seems realistic for you
[09:42] <smartboyhw> ochosi: What do you mean?
[09:43] <ochosi> well i'm not sure what you discussed with mr_pouit, but i assumed you would work on implementing changes to the lightdm-gtk-greeter
[09:44] <smartboyhw> ochosi: :)
[09:48] <ochosi> soo?
[09:48] <smartboyhw> I think I'll work on it:)
[09:48] <ochosi> mkay
[09:48] <ochosi> timeframe? :)
[09:50] <Unit193> mr_pouit: Put package too https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Quantal/SettingsManagerApps
[09:52] <smartboyhw> ochosi: Hi, I'm back
[09:53] <ochosi> smartboyhw: okies
[09:53] <ochosi> actually i have to leave in 4mins or so
[09:53] <smartboyhw> :)
[09:54] <ochosi> so, what would be a realistic timeframe/plan for you?
[09:54] <ochosi> (or is it too early to say because you haven't looked at the code)
[09:54] <smartboyhw> Hmm, I'm getting the source code first:)
[09:55] <ochosi> sure sure
[09:55] <ochosi> not sure what you've worked with, but most requests will involve tinkering with the .ui file (aka gtkbuilder aka glade-successor)
[09:55] <smartboyhw> :)
[09:56] <ochosi> e.g. moving the computer-name from the login-box to the top panel
[09:57] <smartboyhw> OK
[09:58] <ochosi> ok, gotta go now
[09:59] <smartboyhw> Bye
[12:48] <knome> pleia2, i bolded those sections/subpages that i consider "checked out"
[13:12] <ochosi> knome: i'm considering to skip "Find unnecessary icons and remove"
[13:12] <ochosi> it's really the hardest part of iconing, to find unused ones
[13:12] <ochosi> you never know what icons are in use by what obscure app...
[13:12] <knome> yeah, feel free to mark that as POSTPONED
[13:12] <smartboyhw> Yo ochosi: How to edit the .ui file?
[13:13] <ochosi> unless we decide to just trim down the icon-theme to a more minimal state
[13:13] <ochosi> smartboyhw: install glade or with a text-editor
[13:13] <smartboyhw> OK
[13:18] <smartboyhw> ochosi: Working on it now:)
[13:18] <ochosi> smartboyhw: ok, good luck :)
[13:20] <smartboyhw> :)
[13:49] <smartboyhw> knome: If you are here, I want to tell you a fact: The 12.10 ubiquity in Xubuntu, it sucks...
[13:49] <knome> smartboyhw, justify
[13:49] <ochosi> it will get better :)
[13:49] <ochosi> right now it's a lot of black on black
[13:49] <smartboyhw> ochosi: I agree
[13:50] <ochosi> because greybird wasn't working right i think
[13:50] <knome> okay. in that case it doesn't "suck", it has a bug
[13:50] <smartboyhw> It;s full of black:(
[13:51] <smartboyhw> Well, it looks it sucks. Sorry for using a nonsense word, it did look like that..
[13:51] <knome> one of the best qualities when filing bugs or problems is to know how to describe the problem
[13:52] <knome> "X isn't working" or "X sucks" is as helpful as nothing
[13:52] <smartboyhw> Sorry: So should I file a bug on Launchpad?
[13:52] <knome> probably not, since it's known, and people are working on it
[13:52] <smartboyhw> I apologise
[13:52] <smartboyhw> :)
[13:52] <knome> np, just trying to not waste anybody's time
[13:54] <elfy> talking of which - how to describe this one ... parole opens like this here http://imgur.com/8xTg1
[14:07] <smartboyhw> Hi I am back. Ochosi, you still here?
[14:07] <knome> smartboyhw, is there a problem?
[14:07] <smartboyhw> I want to find ochosi.
[14:08] <knome> for what reason?
[14:08] <smartboyhw> knome: BTW, status report: Testing a Quantal build of Xubuntu now
[14:08] <knome> okay
[14:08] <smartboyhw> Anyway, I recalled he has left, Find
[14:08] <smartboyhw> *Fine
[14:09] <bluesabre> elfy, what's wrong with parole?  That image looks spot-on.
[14:09] <elfy> really?
[14:09] <elfy> never used to look like that
[14:10] <bluesabre> Yeah, that's the new parole
[14:10] <bluesabre> 0.3.x
[14:10] <bluesabre> :)
[14:10] <elfy> oh wow LOL
[14:10] <elfy> I thought it was some graphic card glitch :)
[14:10] <bluesabre> lol
[14:10] <bluesabre> I think knome made that awesome background
[14:11] <bluesabre> or ochosi
[14:11] <bluesabre> One of those two
[14:11] <knome> i did
[14:11] <elfy> I almost reported a bug :)
[14:12] <elfy> this morning - then thought I'd wait till I asked someone how to describe it - glad I did
[14:12] <bluesabre> Glad I caught you
[14:12] <bluesabre> :D
[14:12] <elfy> lol
[14:12] <elfy> knome: now I know it's supposed to look like it - it's ok
[14:13] <knome> ;)
[14:13] <knome> we thought that was a cool idea
[14:13] <smartboyhw> OK, I need to add a bug to the ISO QA Tracker: VM does not reboot after installation:(
[14:14] <elfy> missed that meeting :)
[14:14] <knome> heh, that was at #shimmer i think
[14:15] <elfy> anyway - me wanders off again now - thanks for catching that bluesabre :)
[14:15] <elfy> cya all
[14:15] <knome> see you
[14:27] <smartboyhw> knome: Reported a pass for the Quantal Daily Build amd64 (but with a VM reboot bug)
[14:27] <knome> smartboyhw, ok, thanks. but please just report, no need to specifically tell me you did.
[14:28] <smartboyhw> :)
[20:15] <knome> pleia2, morning? :)
[20:17] <knome> mr_pouit, micahg: can you drop synaptic off of our seed? ta
[23:20] <pleia2> knome: hello
[23:21] <knome> hai
[23:21] <knome> you have a few mins?
[23:23] <pleia2> sure
[23:23] <knome> great!
[23:23] <knome> so
[23:23] <knome>   * Remove (or archive) xubuntu-website, rename xubuntu-website-wordpress to replace
[23:23] <knome> thoughts?
[23:23] <knome> should we just do that?
[23:24] <pleia2> I don't know precisely how to go about it, the never-delete-anything part of me sort of wants to keep the code around even though it's for drupal5 ;)
[23:24] <pleia2> but I don't know how we could do that, if we could
[23:24] <knome> if we'd archive it, how would you like to go about it?
[23:24] <knome> new branch under the other website code?
[23:24] <pleia2> yeah
[23:25] <knome> ok
[23:25] <knome> i suppose we can do that if we ask LP admins nicely enough
[23:25] <pleia2> so pull it down, delete the project, move the other, and push it up as a new branch?
[23:25] <knome> yeah
[23:25]  * pleia2 nods
[23:25] <knome> ok, good, i'll look at that at the beginning of next week
[23:25] <knome> then
[23:25] <knome>   * Review ~xubuntu-docs (Is it technically required? Which access/permissions does it have since it's a subteam of ~ubuntu-doc?)
[23:25] <pleia2> thanks
[23:25] <pleia2> that one I don't know
[23:25] <knome> me neither
[23:26] <knome> do you know somebody who does?
[23:26] <knome> i tried shouting at #ubuntu-docs earlier, but no response
[23:26] <pleia2> would also be worth figuring out exactly what we need to do to get a couple xubuntu folks access to upload our docbook stuff once it's done
[23:26] <pleia2> I can ask on the list
[23:26] <pleia2> phillw is good about replying to me
[23:26] <knome> though i think i have a better idea now who are the people we should accept to the team, even if that team had some access
[23:27]  * pleia2 nods
[23:28] <knome> if you ask a bit more about it, let's get back to that when you've had replies
[23:28] <knome> another one:
[23:28] <knome>  [lyz] Cleanup and review community wiki: INPROGRESS
[23:28] <knome> should we do that now?
[23:29] <pleia2> I was working through it last night, have some comments, let me dig up
[23:30] <knome> got an email from elfy for improvements on making the xorg/help page better
[23:30] <knome> tbe, the forums part
[23:30] <pleia2> oh yes, I saw that, that would be great
[23:31] <knome> i'll push the changes soon
[23:31] <pleia2> I've edited the forums section a couple of times based on random feedback from people, more coherent feedback from a FC member would be win \o/
[23:31] <knome> hehe
[23:31] <pleia2> right, so I think we should mark everything for deletion (maybe english "Installing" can just link to Ubuntu installing docs
[23:32] <pleia2> except https://help.ubuntu.com/community/CompizConfiguration/Cube/And/Effects/Ubuntu/Xubuntu/Lubuntu/Kubuntu/Edubuntu
[23:32] <pleia2> which we should test
[23:32] <knome> there was some discussion about that already
[23:32] <knome> but i can't remember which channel
[23:32] <pleia2> and we should talk about what to do with the XubuntuPanels page
[23:32] <knome> probably -offtopic
[23:32] <pleia2> yeah, I said I'd look a bit deeper to make sure it's what we really wanted
[23:33] <pleia2> I think XubuntuPanels is actually useful, and we would benefit from a community wiki of tips as people find them (so, not move to website)
[23:34] <knome> hmph.
[23:34] <knome> xubuntupanels was created for a factiod
[23:34] <knome> !panels
[23:34] <knome> !panels-#xubuntu
[23:34] <knome> that
[23:34] <knome> it's not a "community-written" page
[23:34] <pleia2> yeah, well that's good
[23:34] <pleia2> ah, but it could be!
[23:34] <knome> that's to say i don't have much hopes of having many of those
[23:35] <pleia2> well at least I know it exists now ;) I can help fix it too
[23:35] <knome> and either our rewritten offline documentation of the app-specific docs should make community-docs extinct ;)
[23:36] <pleia2> I don't love the idea of just removing them all because we can, I like to have a few around so people see they can make more if they want
[23:36] <knome> do you know of the processes in the community wiki?
[23:36] <pleia2> then maybe we can pull more into official docs
[23:36] <knome> would it be ok to just delete, not propose for deletion
[23:36] <pleia2> some, only admins can delete pages for instance so they have a whole tagging system
[23:36] <knome> aha
[23:37] <pleia2> https://help.ubuntu.com/community/Tag
[23:37] <knome> ok, do we know who the admins are?
[23:38] <knome> so, leave XubuntuPanels and the reference on Compiz
[23:38] <knome> and propose everything else for deletion?
[23:39] <pleia2> yeah, that's my assessment
[23:39] <pleia2> there are a few wiki admins, you can email -doc list if you want them immediately attended to after tagging them
[23:39] <pleia2> cprofitt, phillw
[23:39] <knome> okay
[23:39] <knome> i'm okay with those actions
[23:39] <knome> will you proceed with them?
[23:39] <pleia2> alright cool, I'll get that done today
[23:40] <knome> great :)
[23:40] <knome>  [lyz] Define target marketing audience: TODO
[23:40] <knome> what about that? :)
[23:41] <pleia2> I can finish that today too, I actually did it once and then the wiki didn't save my edits and I have been too upset for a month to redo it :)
[23:41] <knome> aww
[23:43] <knome> new wallpaper before UIF
[23:43] <knome> bleh
[23:43] <knome> :)
[23:44] <pleia2> :D
[23:44] <knome> http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-xubuntu.html
[23:44] <knome> burndown looks better though
[23:44] <knome> we've been keeping the reds below the mainline
[23:44] <pleia2> :)
[23:44] <pleia2> gold stars all around!
[23:45] <knome> hehe
[23:47] <knome> so, is there something else we can make happen today? :P
[23:48] <pleia2> hehe


 ~/ … not .~/ … This stands for home directory
 You can easily symlink your app to /usr/local/bin or any directory in PATH
 Like ln -s /path/to/app /usr/local/bin/
 You can also add the directory that contains your app to PATH environment variable
[07:44] <mono> hi
[07:44] <mono> im using a imac with kubuntu at the moment. The Imac is from 2017 an the audio is not working. I installed it yesterday and since installing its not working. Can anybody help?
[08:22] <guiverc> mono, kubuntu's support room is #kubuntu , you're also allowed to use #ubuntu (as all official flavors can)
 It is good enough to run lubuntu well
 I would gpo for the latest lubuntu 20.04 LTS
 @Emily Petrisor [Hi, … A kid cannot participate in online lectures because of lack of a laptop or …], 18.04
[22:34] <kanliot> I remember some of the LXQt devs using a new language based on C++, but with much better integration with Qt and object oriented.   What was the name?  Was it dolphin something?
 I don’t know about that dev team, but was it D?
 https://dlang.org
 @Emily Petrisor [Hi, … A kid cannot participate in online lectures because of lack of a laptop or …], I did exactly that same thing last week, on an acer aspire one notebook (probably worse than your laptop). … It works okay, but loading up Firefox to log in to a company specific zoom, takes at least a minute. … The zoom instal
[23:05] <genii> Perhaps rust
[23:06] <genii> ( or go )
 Also, I have to reboot the notebook multiple times a day or it slows down and then crashes. Not sure why.
 Often I have to hard shutdown because the menus are taking so long to load.
 And the mouse won’t move properly.
 I’m pretty sure that doesn’t happen if I haven’t launched zoom at all, so it’s probably zoom causing it.


[20:31] <ChinnoDog> crickets
[20:42] <ChinnoDog> kenvandine: I saw there is a hackerspace in Durham. Been to it?
[20:42] <kenvandine> ChinnoDog, i haven't
[20:43] <kenvandine> i keep wanting to go
[20:43] <kenvandine> just never have the time
[20:43] <ChinnoDog> I know how that is. I joined the hackerspace in DC when I lived in VA but it was too far away. I never had the time to commute there.
[20:44] <ChinnoDog> I want to move to Durham. If the hackerspace is cool I want to live in walking distance of it.
[20:45] <ChinnoDog> I could 3D print some boat parts. :D
[20:48] <kenvandine> lol


[03:20] <MTecknology> newz2000: I still haven't found a copy of everything - but I can look more later


[00:09] <infinity> tjaalton: Around?
[04:16] <tjaalton> infinity: off this week. xorg metapkg isn't uploaded yet btw..
[05:21] <infinity> tjaalton: xorg-lts-vivid, you mean (which is in the queue), or something else?
[05:21] <infinity> tjaalton: Also, I rejected one of your uploads, would be nice if you could look at that, despite the VAC.
[05:28] <tjaalton> infinity: oh i uploaded it? ok.. i'll check the other one
[05:40] <tjaalton> infinity: looks like -qxl doesn't follow the same packaging as rest, so there's some tarball diff
[05:40] <tjaalton> or such
[05:42] <infinity> tjaalton: That crufty weirdness didn't happen between utopic and lts-utopic, FWIW.
[05:42] <infinity> tjaalton: And nothing in the utopic->vivid diff would have caused that.
[05:42] <infinity> tjaalton: So, I assume it was just a dirty tree when building lts-vivid.
[05:43] <tjaalton> weird
[05:43] <tjaalton> i use the source from apt get
[05:43] <infinity> tjaalton: Err, wait.  WAT?
[05:43] <tjaalton> pulled the source package from vivid
[05:44] <tjaalton> renamed
[05:44] <infinity> tjaalton: qxl is native in utopic/lts-utopic, and vivid.  Where did that orig magically come from for lts-vivid?
[05:44] <tjaalton> debuild
[05:44] <tjaalton> oh
[05:44] <tjaalton> grr
[05:44] <infinity> tjaalton: That orig is likely the culprit. :P
[05:44] <tjaalton> shitfuck
[05:44] <tjaalton> ok i'll delete the orig then
[05:45] <infinity> Where did it even come from? :)
[05:45] <infinity> Given that there's no orig in vivid... So confused.
[05:46] <infinity> But yeah, I'd assume unpacking vivid, running rename mojo on it, and building source withut the orig should give you a nice, small diff.
[05:46] <infinity> tjaalton: And assuming xorg-lts-vivid is the last piece of the puzzle, then you can rest without me bugging you.
[05:46] <infinity> tjaalton: And I might have functional dailies for you to test when you get back.
[05:46] <tjaalton> and now the debdiff makes sense
[05:47] <tjaalton> the rename script was buggy for a reason then!
[05:48] <tjaalton> it would happily build the source for you without a proper tarball
[05:48] <tjaalton> qxl uploaded again
[05:49] <tjaalton> infinity: yeah apparently i uploaded the metapkg at some point, so it should be all good then
[05:50] <infinity> tjaalton: Alright, lemme quickly re-review this.
[05:51] <infinity> tjaalton: That looks much saner, thanks.
[05:51] <tjaalton> cool
[05:52] <tjaalton> time for bf ->
[11:04] <sil2100> Hello everyone! I would need to disable the importer on nusakan again for a while
[15:45]  * Laney looks at stgraber
[15:46] <Laney> iso tracker halp? :)
[15:48] <stgraber> Laney: hey
[15:48] <stgraber> Laney: what's up?
[15:48] <stgraber> (sorry, been taking some days off this past week so may have missed some pings)
[15:48] <Laney> no worries
[15:49] <Laney> how can I add a new 'owner' team?
[15:51] <stgraber> Laney: is that for a new product?
[15:51] <Laney> no, I want to set one for desktop-next
[15:52] <stgraber> ok, it's not exactly the easiest thing in the world :)
[15:52] <stgraber> first you have to go create a new role, that's in the admin interface under user IIRC
[15:52] <Laney> I see a list here: http://iso.qa.ubuntu.com/admin/config/services/qatracker/products/363/edit
[15:52] <stgraber> once done, go to the permissions tab and make sure that the permissions for the new role matches that of a similar product owner team
[15:53] <Laney> ah, that'll get it in there I suppose
[15:53] <stgraber> once that's done, go to the LP team module configuration and setup a new mapping between the LP team and the role you created
[15:53] <stgraber> once you've done that, you can go and edit the product to assign it the role
[15:53] <Laney> I don't have user in there
[15:53] <stgraber> oh, you're probably not admin enough :)
[15:54] <Laney> oh man, there are higher levels of power?
[15:54] <stgraber> and stupid 3G here has busted routes to SSO
[15:54] <stgraber> let me proxy through a server somewhere so I can actually login
[15:58] <stgraber> ok, I'm logged in
[15:59] <stgraber> Laney: what's the LP team?
[15:59] <Laney> ~ubuntu-desktop-next-release
[16:05] <stgraber> Laney: role should be setup now
[16:05] <stgraber> Laney: I'm EODing now and about to leave till Monday, do you need anything else from me?
[16:06] <Laney> stgraber: not if it works
[16:06] <Laney> happy holidays!
[16:06] <Laney> and thanks
[16:07] <Laney> ah wait, it's not posting to the tracker it seems
[16:08] <stgraber> Laney: btw, those with admin access for that kind of stuff are ~ubuntu-qa-website-devel
[16:08] <Laney> ah, maybe it doesn't have to be
[16:08] <stgraber> No iso.qa.ubuntu.com product found for ubuntu-desktop-next/daily-preinstalled/wily-preinstalled-desktop-next-i386; skipping.
[16:08] <stgraber> No iso.qa.ubuntu.com product found for ubuntu-desktop-next/daily-preinstalled/wily-preinstalled-desktop-next-armhf; skipping.
[16:08] <Laney> etc/qa-products?
[16:09] <stgraber> yep
[16:09] <Laney> k, will fix
[16:09] <Laney> will that break triggering the rebuild?
[16:09] <stgraber> qa-products is used both by the build script and process-rebuilds so yeah, you need to fix this
[16:10] <Laney> ok then
[16:10] <Laney> I'll hassle you on monday if it doesn't work by then
[16:10] <stgraber> ok :)
[16:10] <stgraber> rebuild-requests can be run in dry-run and verbose mode to see if the change works
[16:10] <stgraber> as for publishing, look at the end of the build log: http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-desktop-next/wily/daily-preinstalled-20150611.log
[16:17]  * Laney tries a test build
[16:18]  * stgraber -> out
[17:01] <sil2100> I'll have to disable the importer again...
[17:01] <sil2100> ...or maybe not
[17:36] <coreycb> hello, can we have python3-tempest-lib and python3-paramiko promoted to main please?
[17:39] <infinity> coreycb: I don't see anything on my reports indicating that they're being pulled in.
[17:40] <coreycb> infinity, do I need an MIR for them?  the python 2 binary packages are in main.
[17:41] <infinity> coreycb: No, you don't need an MIR.  But you need something uploaded that depends on them, or to have them explicitly seeded with a rationale.
[17:41] <infinity> coreycb: If your intent was the former, please upload, and we'll clean it up.
[17:42] <coreycb> infinity, ok I still need to get the package in that depends on python3-tempest-lib, but there's already a dep on python3-paramiko:  https://launchpad.net/ubuntu/+source/python-tempest-lib/0.5.0-1/+build/7528029
[17:43] <infinity> coreycb: You do, however, need an MIR for python-ddt.
[17:44] <coreycb> infinity, we have one somewhere, lemme find it
[17:44] <infinity> And I'm very confused about why none of this is showing up on my mismatches reports.  Hrm.
[17:44] <coreycb> infinity, bug 1459151
[17:44] <infinity> coreycb: Ta.
[17:51] <infinity> coreycb: Should all be promoted.
[17:51] <coreycb> infinity, great, thanks!
[17:51] <infinity> coreycb: Or, will be once a publisher cycle happens.
[17:52] <infinity> coreycb: By "all", I mean the two packages in that MIR, and paramiko.
[17:52] <infinity> coreycb: tempest will want love after you upload something else that needs it.
[17:52] <coreycb> infinity, yep, got it
[19:37] <infinity> coreycb: tempest still has an issue.
[19:38] <infinity> coreycb: It build-depends on python3-oslo.log and python-oslo.log, but those don't actually exist.  They're -log, not .log
[19:39] <infinity> coreycb: Oh, nevermind, the new .log just hasn't built yet.
[19:39] <infinity> La la la.
[19:39] <infinity> This namespace renaming is such a mess.
[19:42] <coreycb> infinity, yeah jamespage worked through a bunch of those to rename them back to .log recently.  anything needed from us?
[19:42] <infinity> coreycb: Not yet.  I'll keep babysitting and see where it ends up.
[19:43] <coreycb> infinity, ok thanks
[19:44] <infinity> coreycb: Oh, filling in all the MIR info for LP: #1464158 would help.  That seems to be the next snag.
[19:51] <coreycb> infinity, ok I'll do that
[21:28] <coreycb> infinity, I've updated that MIR bug for  python-debtcollector and python-wrapt
[21:29] <infinity> coreycb: Thanks.


[00:03] <TheNewAndy> hey, is there a way to get launchpad to not send me an email notifying me of a comment on a bug, when it was me that made the comment?
[00:57] <TheNewAndy> am I likely to run into any problems following the instructions at https://wiki.ubuntu.com/ARM/RootfsFromScratch
[00:57] <TheNewAndy> ... sorry. wrong channel :)
[01:46] <maxb> TheNewAndy: Regarding self-comments: No, sadly, that is not configurable.
[01:46] <TheNewAndy> maxb: ok thanks for that
[12:41] <bdrung> against which lp project should i file design bugs in the launchpad website?
[12:44] <geser> if you don't know the sub-project file them against launchpad and it should be moved to the correct one during triage
[12:54] <bdrung> geser: thanks
[20:46] <pkern> Why do translations uploaded need review?  Could one be whitelisted for that project-wise?
[20:47] <wgrant> pkern: Unless you're doing something strange, it should only need approval once.
[20:50] <pkern> wgrant: Once for what?  I get this needs review everytime I try to import stuff while doing upstream release work.
[20:51] <wgrant> pkern: I don't know translations that well. But most projects only need approval for the initial upload of each template or translation.
[20:51] <wgrant> Subsequent uploads are automatically approved.
[20:59] <pkern> wgrant: Just tried again on https://translations.edge.launchpad.net/net6/1.3/+imports and they're all on needs review.
[20:59] <pkern> While automatic bazaar imports are auto-approved.
[21:00] <wgrant> Right, bazaar imports are auto-approved.
[21:00] <wgrant> And you should use them if possible.
[21:01] <pkern> wgrant: Well, I do for one project now, but that doesn't change my point that it should be possible for others to get approved imports automatically.
[21:01] <pkern> The other dev refused to put in the .pot as auto-generatable data into the repository, but we "solved" that now.
[21:02] <wgrant> There should be auto-generation of .pots within LP in a few months, I suspect.
[21:02] <wgrant> But I don't know enough about Translations to help with your other point.
[22:22] <qnix> Hi... emm... what can I do if a source package "software-version.tar.gz" is already on the server ?
[22:22] <qnix> Is there a way to delete that tar.gz on the server? (I'm the original uploader)
[22:23] <nigel_nb> hi folks, is loggerhead down?
[22:23] <wgrant> qnix: You cannot ever upload the same filename again. Why has it changed?
[22:24] <wgrant> nigel_nb: It looks like it might be.
[22:24] <nigel_nb> wgrant: ah, planned downtime?
[22:24] <wgrant> nigel_nb: No.
[22:24] <wgrant> More likely just broken.
[22:24] <wgrant> Ah, no, not broken.
[22:24] <wgrant> Just slow.
[22:24] <wgrant> Tried refreshing a couple of times?
[22:25] <nigel_nb> wgrant: lemme try again
[22:25] <qnix> wgrant: The software developers found a very important security problem. Since the package was not published public (only between devs), they decided to re-do the package.
[22:26] <nigel_nb> but when its broken, *that* happens
[22:26] <wgrant> qnix: That's awful and wrong.
[22:26] <wgrant> qnix: You'll need to add something to the upstream version number.
[22:28] <qnix> wgrant: I see, like 5.6.0-1 ?
[22:28] <qnix> emm, no, wont work
[22:28] <wgrant> qnix: Avoid using - in the upstream version. It will work, but it's inadvisable.
[22:28] <wgrant> +1, perhaps.
[22:28] <wgrant> +badupstreamisbad, maybe.
[22:30] <qnix> will try that
[22:31] <nigel_nb> wgrant: are there anyone around who could look the loggerhead issue?
[22:31] <nigel_nb> do I need to log a bug, call or something?
[22:31] <wgrant> nigel_nb: It works OK for me.
[22:32] <nigel_nb> wgrant: oh
[22:32] <nigel_nb> lemme look it up again
[22:32] <wgrant> It just takes a couple of refreshes for each branch.
[22:32] <wgrant> Which sucks, but it at least works a bit.
[22:32] <nigel_nb> ah, a couple of refreshes does do wonders
[22:32] <nigel_nb> but I guess someone will read the logs and look into it later on
[23:16] <qnix> wgrant: Isn't there any way to replace a upstream version on the server ? I mean... the package is not good.. I can fix that for my package... but this can affect other user packages or even a future universe/multiverse package.
[23:38] <wgrant> qnix: The file only lives within your PPA.
[23:38] <wgrant> qnix: It will not affect anything else.