[00:00] <Fujitsu> sistpoty: Ubuntu sbuild resolves very similarly, if not identically, to Soyuz sbuild.
[00:03]  * sebner will continue tomorrow with MD. Good night folks :D
[00:06] <albert23> Scottk2: please ignore the debdiff for enthought-traits. I will complete that tomorrow.
[00:09] <sistpoty> Fujitsu: ah, cool... switching to sbuild is still on my todo list though :/
[00:11] <sistpoty> Fujitsu: btw.: does "done" mean, that the publisher has already run? (I forgot the url to the actual page again)
[00:14] <ScottK2> albert23: OK.  Please delete it from the bug.
[00:14] <Fujitsu> sistpoty: It means that the publisher has started and picked up the package. It won't be available from a.u.c until about 43 past that hour.
[00:14] <sistpoty> Fujitsu: and for the buildds?
[00:15] <Fujitsu> sistpoty: Probably a few minutes earlier, but I'm not entirely sure.
[00:15] <sistpoty> Fujitsu: ah, k. thanks!
[00:15] <sistpoty> Fujitsu: when would it show up in binary new? about the same time? (imho hscolour/lpia would need to go through binary new, but I might be wrong)
[00:16] <Fujitsu> sistpoty: They'll hit binary NEW seconds after they build.
[00:16] <sistpoty> Fujitsu: thanks. seems like I'm wrong then on hscolour needing to go through binary new :)
[00:17] <Fujitsu> And you'll see `Successfully built (NEW)' rather than `Successfully built (ACCEPTED)'
[00:17] <sistpoty> cool :)
[00:17] <sistpoty> thanks!
[00:20] <sistpoty> Fujitsu: oh, if https://launchpad.net/ubuntu/hardy/lpia/hscolour/ writes "published", it's already available for the buildds, I assume?
[00:21] <Fujitsu> sistpoty: Not for about half an hour, probably.
[00:21] <sistpoty> ok, /me is now confused
[00:21] <sistpoty> but thanks Fujitsu for the insights
[00:23] <Fujitsu> sistpoty: That's just the date that publisher picked it up. It then has to actually be written out by apt-ftparchive, and mirrored.
[00:23] <sistpoty> ah, k
[00:25] <_MMA_> Hmm... Sorry for the probably basic question here but how do I find a changelog for an app? Something has changes either with Audacious or todays updates that have really screwed up it's sound.
[00:26] <pochu> night all!
[00:26] <sistpoty> gn8 pochu
[00:26] <pochu> _MMA_: aptitude changelog <package>
[00:26] <_MMA_> Thanx
[00:27] <sistpoty> _MMA_: trouble with audacious (on hardy)? meh... that's not good, as we shoved through a FFe
[00:28] <_MMA_> sistpoty: Its hard to explain. It all the sudden sounds like the preamp is up too high. Like the gstreamer EQ issue. Except it doesnt clip.
[00:30] <sistpoty> _MMA_: can you report a bug on lp against audacious and subsribe sebner and myself (lpid: sistpoty)?
[00:31] <bddebian> Heya gang
[00:31] <_MMA_> sistpoty: Well wait. Lemmie see what you think. The volume in Audacious controls the PCM volume. Correct? (does here anyway) :P
[00:32] <_MMA_> So, if I enable the EQ I have to now push the preamp to the floor. Otherwise I get sound that has a "overdriven" sound to it.
[00:32] <_MMA_> Static but doesnt clip.
[00:32] <sistpoty> _MMA_: not too sure actually, I've only tried audacious recently but not in depth with the EQ
[00:33] <sistpoty> _MMA_: what output plugin are you using (we dropped a pulseaudio-by-default patch, wich wasn't working properly)
[00:34] <_MMA_> Lemmie look.
[00:34] <_MMA_> ALSA
[00:34] <sistpoty> hm...
[00:35] <sistpoty> can you try pulseaudio and see if things improve?
[00:35] <_MMA_> SUre
[00:35] <sistpoty> thanks
[00:35] <sistpoty> (brb, out for a smoke)
[00:35] <_MMA_> bah.. Froze up on me.
[00:39] <_MMA_> sistpoty: Well same behavior with PA but at least now I can use PA. Before it wasn't working. :P
[00:41] <_MMA_> sistpoty: Just turn the EQ. Set some curve to it. I import my settings from Winamp. (rock preset) Then enable. I have to move the preamp slider to the bottom.
[00:44] <sistpoty> _MMA_: hm... I guess I'm not really the right person to ask about audio stuff. maybe persia would have some clue? (others than that I guess that filing a bug on LP against audacious might still make sense)
[00:44] <_MMA_> sistpoty: Ok. Ill try to dig a bit before I run to LP.
[00:45] <sistpoty> _MMA_: thanks (oh, /usr/share/doc/audacious should contain an upstream changelog, might be worth looking at)
[00:45] <_MMA_> Thanx. pochu also showed me.
[02:05] <persia> _MMA_: Do you have Master or Front volume controls as well?  It may be that your computer can overdrive your speakers, and something is being set high.
[02:06] <sistpoty> very cool, ghc6 on lpia is already in needs-building state :)
[02:06]  * sistpoty crosses fingers
[02:07] <persia> nenolod: Are you about?  Do you know how SSE2 support might cause clipping?
[02:15] <_MMA_> persia: Ill look now. Though I can't dig too much tonight or the wife is gonna kill me. :P
[02:16] <_MMA_> persia: Hmm... I also no longer get the little sound at GDM. Uses aplay/gdmplay or something.
[02:19] <nenolod> persia, SSE2 support uses a different dithering engine when converting audio to your set format
[02:19] <persia> nenolod: So the resulting gain may well be different.  Thanks.
[02:19] <nenolod> persia, it's a bug at any rate
[02:20] <nenolod> persia, this is aud 1.5 right?
[02:20] <persia> _MMA_: sounds like you've some complexity with your current configuration, which exacerbates the audacious change.  As nenolod suggests, best to file a bug.
[02:20] <_MMA_> persia: No matter the the Master or PCM volume, if the EQ is enabled, and the preamp isnt floored I gets tons of static.
[02:21] <persia> nenolod: 1.5.0-2, I believe
[02:21] <nenolod> _MMA_, probably a bug in the new EQ code
[02:21] <persia> _MMA_: And only for audacious, right?
[02:21] <nenolod> looks like the preamp gain is too way much
[02:22] <nenolod> way too much*
[02:22] <_MMA_> persia: Well there a simular isue with the gstreamer EQ but this is certinally new in audacious.
[02:22] <nenolod> please file a bug about this at http://bugzilla.atheme.org
[02:22] <_MMA_> nenolod: Noted.
[02:22] <nenolod> don't bother with launchpad triage, it's not needed in this case -- it can go directly to upstream
[02:23] <_MMA_> k
[02:23] <nenolod> persia, we have pkg-audacious in debian now for audacious packaging btw
[02:23] <persia> nenolod: Thanks both for the pointer, and the help.  I'll not poke you next time something comes up.
[02:23] <nenolod> but i've been busy, so haven't had time to transition the package yet
[02:26] <nenolod> persia, nah, feel free to poke me any time :)
[03:04] <lifeless> there will be a short outage to the wiki and bazaar.launchpad.net, to hoepfully address the bazaar.launchpad.net performance problems
[03:41] <sistpoty> damn, I want a lpia as well, ghc6 build took only an hour on the buildd *g*
[03:41] <sistpoty> :)
[03:41] <bddebian> heh
[03:41] <bddebian> persia: You still around?
[03:41] <Fujitsu> sistpoty: The lpia are just fast x86s.
[03:41] <Fujitsu> *lpia buildds
[03:41] <persia> bddebian: somewhat
[03:42] <sistpoty> Fujitsu: but must be damn fast boxes (my amd64 takes s.th. like two hours for the build, but it's a different arch of course)
[03:42] <bddebian> persia: *SHOULD* be a quick question if you have a minute?
[03:42] <persia> !ask
[03:42] <ubotu> Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-)
[03:42] <Fujitsu> It's a very similar arch.
[03:43]  * persia pokes bddebian, to see if that helps elicit a question
[03:43] <bddebian> persia: Sorry, too many channels, I have to get to the code quick
[04:27]  * sistpoty goes to bed
[04:27] <sistpoty> gn8
[06:47] <Fujitsu> Wow, dpkg doesn't like me:
[06:47] <Fujitsu> dpkg: too many errors, stopping
[06:47] <Fujitsu> dpkg: ../../src/packages.c:252: process_queue: Assertion `!queuelen' failed.
[06:48] <Fujitsu> Aborted
[06:48] <mbt> eep.  never seen that before
[06:49] <jdong> Fujitsu: that's a frightening one
[06:49] <Fujitsu> Oh my.
[06:50] <Fujitsu> Python is exploding.
[06:50] <Fujitsu> (this is a dapper->hardy upgrade blowing up)
[06:50] <Fujitsu> Ah, all python-central's fault:
[06:50] <Fujitsu> Setting up python-central (0.6.1ubuntu1) ...
[06:50] <Fujitsu> pycentral: pycentral pkginstall: not overwriting local files
[06:50] <Fujitsu> pycentral pkginstall: not overwriting local files
[06:50] <Fujitsu> What on earth is it trying to do?
[07:35] <Fujitsu> I don't particularly like how fragile python-central is.
[07:36] <Fujitsu> I shouldn't be able to hugely kill an upgrade just because python-opengl doesn't conflict with python2.4-opengl.
[07:36] <Fujitsu> Because of that, python-central tries to overwrite other files, so won't configure. launchpad-integration depends on python-central, and lots of things depend on the launchpad-integration libraries. Thus most of GNOME also fails to configure.
[07:37] <Fujitsu> dpkg then does ugly things like the above, causing update-manager to die a horribly painful death.
[07:37] <Fujitsu> All because somebody left a line out of one universe debian/control
[07:57] <cody-somerville> :(
[08:07] <eddyMul> Is there an easy way to reverse an individual cdbs simple-patchsys patch? Or do I have to issue the patch command myself?
[08:08] <persia> eddyMul: You'll want to call patch directly.
[08:09] <eddyMul> persia: I see. thanx.
[08:15] <warp10> Good morning
[08:46] <Iulian> G'morning.
[08:48] <eddyMul> g'morning
[09:10] <AnAnt> Hello, I need help with creating a cursor (pointer) theme
[09:10] <AnAnt> can it inherit from another cursor theme ?
[11:28] <Hobbsee> evening
[12:07] <pwnguin> so at this point, if there's a patch and an upstream new release that fixes a bug, the patch is the preferred approach?
[12:12] <persia> pwnguin: Unless the upstream release only contains that patch, or there is some other really good reason it should be included.
[12:13] <pwnguin> apparently MOTU's traditional xournal shepard it out of town =/
[12:15] <pwnguin> persia: the package in question has no patch system, and the patch in question is already applied upstream. i assume in this case it would be unreasonable to add a patch system to the package
[12:16] <persia> pwnguin: In general, I'm opposed to adding a patch system to a package.  If there is already one in place, it should be used.  If there is none, I presume that matches the maintainer's preference.
[12:16] <persia> You may want to add a note that the applied patch has been applied upstream and can be dropped when the new upstream is available.
[12:16] <pwnguin> where?
[12:17] <persia> Depending on length, I typically recommend either the changelog or debian/README.Debian-source.  Some people have talked about using a debian/README.Ubuntu-source, but I have yet to see a package using this.
[12:18] <pwnguin> what happens on autosync from unstable with -ubuntu versions?
[12:18] <persia> It doesn't autosync.  The package gets listed on merges.ubuntu.com, and someone reads your note, and drops your patch.
[12:20] <pwnguin> this changelog is confusing =/
[12:20] <pwnguin> unstable -> feisty -> unstable -> feisty -> gutsy
[12:21] <pwnguin> man. xournal hasnt been touched since gutsy at all =/
[12:21] <persia> That usually means someone applied a patch in feisty, someone merged a later version in feisty to get a fix, and someone merged to gutsy.
[12:25] <POX_> ScottK, albert23: .pth files can be safely removed if you use standard location for .py files
[12:37] <albert23> POX_: Thanks. Is it still necessary to remove those .pth files?
[12:37] <POX_> necessary? probably not, but they're useless
[12:37] <POX_> well, unless your package will not work without this file :)
[12:38] <POX_> anyway, I'm 90% sure you don't need it (without looking at the package)
[12:39] <albert23> POX_: OK, http://python-modules.alioth.debian.org/python-central_howto.txt says they must be removed, but that is probably just cleaner, not really necessary.
[12:40] <POX_> I wrote that howto :)
[12:40] <albert23> Ah, nice
[13:38] <emgent> hello
[13:38] <RainCT> hi emgent
[14:35] <bddebian> Heya gang
[14:35] <Iulian> Hi bddebian
[14:35] <bddebian> Hello Iulian
[15:00] <jdong> ugh I just had the worst dream last night
[15:00] <jdong> my EE test was administered over Launchpad
[15:01] <jdong> and every time I typed in an answer it dropped down like a page of suggested similar answers
[15:03] <bddebian> haha
[15:03] <jdong> that's probably a sign I should leave more time between eating dinner and falling asleep....
[15:39] <geser> Hi bddebian
[15:39] <protonchris> Hello
[15:41] <bddebian> Heya geser, protonchris
[15:57] <protonchris> slangasek: any luck with the sparc buildd admins yesterday?
[16:09] <zul> jdong: its also a sign to get out of the house more :)
[16:11] <protonchris> ScottK: ping
[16:29] <Mirv> could someone consider sponsoring this: http://ppa.launchpad.net/timo-jyrinki/ubuntu/pool/main/c/compizconfig-settings-manager/compizconfig-settings-manager_0.7.2-0ubuntu2.dsc ? the only changes are two new patches under debian/patches affecting only Finnish translations.
[16:31] <RainCT> Mirv: do you have a debdiff?
[16:40] <Mirv> RainCT: there you go: http://users.tkk.fi/~tajyrink/ccsm/compizconfig-settings-manager_0.7.2-0ubuntu2.debdiff
[16:41] <Mirv> the second patch is big, since almost the whole fi translation is broken
[16:51] <ScottK> protonchris: Pong
[16:52] <protonchris> I was taking a look at wxglade from unstable.  One question, it depends on  python-wxgtk2.6 are we prefering  python-wxgtk2.8?
[16:54] <ScottK> protonchris: We aren't particularly caring, but it has to work if both are installed.  You can look at spe as an example of a package designed to work with 2.6 in Debian and 2.8 in Ubuntu.
[16:55] <protonchris> ScottK: thanks.  looking.
[16:57] <protonchris> ScottK: the current version of wxglade in ubuntu depends on 2.8 while the debian unstable depends on 2.6.  Am I safe in assuming that we need 2.8 so we have consistancy?
[16:58] <ScottK> protonchris: Reasonably safe.  I've never actually looked at the package.
[16:59] <protonchris> ScottK: ok.  I will upload a diff.gz to the bug for a debian unstable merge.
[17:02] <protonchris> ScottK: uploaded to bug.
[17:04] <ScottK> protonchris: It'll probably be tomorrow before I can look at it.  My youngest daughter's birthday is today and we're about to head out for the party.
[17:05] <protonchris> ScottK: No problem.  Have fun today!!!
[17:06] <protonchris> ScottK: I'm not in a rush.  I just wanted to make sure that the bug wasn't waiting on me :)
[17:09] <RainCT> Mirv: do you mind if I modify your changelog entry so that it lists the names of the patchs?
[17:11] <ScottK> RainCT: Would you mind looking after protonchris's wxglade debdiff for Bug #204895?
[17:11] <ubotu> Launchpad bug 204895 in wxglade "Packages failed archive rebuild test possibly due to python-central transition" [Undecided,In progress] https://launchpad.net/bugs/204895
[17:13] <Mirv> RainCT: that's fine
[17:34] <pochu> ScottK: did you manually uploaded phatch, or do you have some cool archive admin friend?
[17:35] <pochu> (or you have super powers?)
[17:51] <sebner> asac: ping :)
[17:52] <sebner> aloha afflux
[17:53] <afflux> huhu sebner
[17:53] <afflux> sebner: using 5-a-day? consider joining the ubuntu-de-locoteam! :)
[17:53] <RainCT> Mirv: sorry that it's taking so long, my connection is slow :P
[17:53] <sebner> afflux: No. We'll see ;)
[17:53] <RainCT> Mirv: I've added some more translations to the .desktop, btw
[17:53] <asac> sebner: can you please use -mozillateam for mozilla /xulrunner issues?
[17:53] <sebner> asac: ah sure.sry
[17:53] <asac> there are others that might know something
[17:54] <asac> :)
[17:54] <afflux> sebner: hehe, juliux asked me to run some sort of german bugsession for recruiting for 5-a-day
[17:55] <sebner> afflux: well in fact. I have not really time for it for now (final exams are around) :)
[17:55] <afflux> oh
[17:55] <afflux> good luck then!
[17:56] <sebner> afflux: thanks
[17:59] <Mirv> RainCT: no problem, really great that you're working on it. more .desktop translations are naturally encouraged, too :)
[18:07] <slytherin> Can anyone please reply to my mail about debconf preseed sent on mailing list?
[18:25] <jpatrick> greeneggsnospam: don't you like ham?
[19:02] <afflux> anyone who likes to sponsor bug 208974 or bug 186141? :)
[19:02] <ubotu> Launchpad bug 208974 in screenlets "candidate for version 0.0.12-0ubuntu3" [Medium,New] https://launchpad.net/bugs/208974
[19:02] <ubotu> Launchpad bug 186141 in nautilus-actions "missing nautilus-actions menu entries" [Medium,Confirmed] https://launchpad.net/bugs/186141
[19:23] <slytherin> afflux: I am not a  developer but still I would like to ask. This is related to nautilus-actions. Can you make use of pkg-config to retrieve the extension directory instead of hard coding the value?
[19:24] <afflux> slytherin: I think so, let me check the -dev package
[19:24] <slytherin> afflux: you can take a look at nautilus-open-terminal to see what I am talking about
[19:27] <afflux> slytherin: right, that's far better, thanks for the hint!
[19:27] <slytherin> afflux: Welcome. :-)
[19:34] <slangasek> protonchris: gdl got rebuilt on sparc which should fix the FTBFS, but it looks like glom didn't really get dep-waited; will follow up
[19:49] <protonchris> slangasek: thanks.
[19:51] <protonchris> slangasek: looks like it is building.  Thanks.
[21:28] <bobbo> Is anyone around to check over the debdiff for bug #184084 (in checky)
[21:28] <ubotu> Launchpad bug 184084 in checky "Extension description mentions Iceweasel/Icedove/Iceape" [Undecided,Confirmed] https://launchpad.net/bugs/184084
[22:08] <norsetto> evening gents
[22:08] <RAOF> Morning norsetto.
[22:09] <sebner> aloha norsetto
[22:10] <norsetto> sebner: don't even think to put flowers around my neck ....
[22:11] <sebner> norsetto: hrhr
[22:11] <afflux> anyone who likes to sponsor bug 208974 or bug 186141? :)
[22:12] <ubotu> Launchpad bug 208974 in screenlets "candidate for version 0.0.12-0ubuntu3" [Medium,New] https://launchpad.net/bugs/208974
[22:12] <ubotu> Launchpad bug 186141 in nautilus-actions "missing nautilus-actions menu entries" [Medium,Confirmed] https://launchpad.net/bugs/186141
[22:13] <sebner> norsetto: any news about conky?
[22:17] <norsetto> sebner: no
[22:19]  * nxvl HUGS norsetto 
[22:23] <sebner> norsetto: if you have time please take a look at bug #209012
[22:23] <ubotu> Launchpad bug 209012 in monodevelop "[FFe] Merge monodevelop_1.0+dfsg-1 from Debian(Unstable)" [Undecided,Confirmed] https://launchpad.net/bugs/209012
[22:25] <sebner> gn8 folks
[23:12] <LimCore> hello
[23:13] <LimCore> sshfs seems to be extreamly unstable ( me and like 5 other crash reports in https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/ )  so I was wondering, should I  try to buuild own .deb from sources of more up to date version? or is anyone else doing that and needs testing before giving this fixed version to all users?