[00:00] <snikker> ah, ok... thanks.
[00:04] <james_w> anyone know what's going on with http://launchpadlibrarian.net/19916491/buildlog_ubuntu-jaunty-i386.glui_2.36-2ubuntu1_FAILEDTOBUILD.txt.gz ?
[00:04] <james_w> touch configure-stamp
[00:04] <james_w> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
[00:06] <RAOF> Looks like the actual error is above that.
[00:06] <azeem> james_w: hrm, *maybe* those warnings spit out by libtool led to a non-zero exit status, and bootstrap is reporting that
[00:06] <RAOF> WHile running bootstrap.sh
[00:06] <azeem> RAOF: which error?
[00:07] <azeem> oh
[00:07] <azeem> right
[00:07] <james_w> ah, oh yeah
[00:07] <james_w> is that a parallel make or something?
[00:08] <RAOF> Also, it looks like that's trying a parallel build, and build-stamp's running before configure has finished (or, in fact, started)
[00:09] <james_w> so build-stamp should depend on configure-stamp?
[00:10] <RAOF> Probably on configure?
[00:11] <james_w> hmm, maybe
[00:11] <RAOF> Well, actually, it likely doesn't make any difference.  But yeah; build-stamp should depend on configure(-stamp), because it doesn't work until configure's been run :)
[00:11] <james_w> configure is PHONY, so wouldn't have make build-stamp be run every time?
[00:12] <RAOF> Um...
[00:12] <azeem> sometimes, I wonder whether that configure: target in debian/rules was invented before or after the advent of autoconf
[00:13] <RAOF> I think dependenices of a PHONY target aren't refreshed if they're up to date, but that's something I'd want to check to be sure.
[00:13] <azeem> yeah, I'd assume build-stamp would just be a no-op then if the stampfile already exists
[00:16] <Coringao> ola alguem pode dizer em portugues aqui.. por favor
[00:16] <Coringao> É sobre o repositorio Ubuntu Games
[00:17] <Coringao> tipo tenho um repositorio
[00:17] <azeem> Coringao: this is an english channel
[00:17] <Coringao> deb http://archive.ubuntugames.org intrepid main
[00:18] <Coringao> azeem, sorry.. not english  :(
[00:18] <RAOF> There is a Portugese channel, though.  That'd be #ubuntu-pt (?)
[00:19]  * RAOF can never remember his locale codes.
[00:20] <Coringao> RAOF, I created a repository for the Ubuntu Games
[00:21] <Coringao> RAOF, Where it exists games not official in the Ubuntu
[00:22] <Coringao> RAOF, I am creative and administrator of link Ubuntu Games
[00:22] <Coringao> http://www.ubuntugames.org
[00:23] <RAOF> Do you have a question?
[00:23] <Coringao> RAOF, would like to officialize the repository that I created
[00:24] <RAOF> Right.  Why are the games not in the Ubuntu repositories already?
[00:24] <Coringao> sorry... I am using a translator.
[00:24] <azeem> Coringao: does somebody from your team speak good english?
[00:26] <Coringao> azeem, sorry.. I do not have team. I made this alone project.
[00:26] <Coringao> :(
[00:29] <leleobhz> well
[00:29] <Coringao> leleobhz, De um help aqui
[00:30] <leleobhz> trying to explain quickly
[00:30] <leleobhz> Coringao has created a repository only for games not packaged yet for ubuntu
[00:30] <leleobhz> and he want to know if have a way to add these packages to official branch of ubuntu
[00:31] <leleobhz> actually these packages are stored into ubuntugames.org server
[00:31] <leleobhz> this guy is the project mantainer
[00:31] <leleobhz> the idea is insert these games into multiverse or universe repositories
[00:31] <azeem> are you sure?
[00:32] <leleobhz> about what?
[00:32] <azeem> it sounded like he just wanted to have his repo "blessed"
[00:32] <azeem> not getting his packages in
[00:32] <wgrant> The idea seems to me to be to create another separate repo that is useless and destroys more upgrades..
[00:32] <leleobhz> no
[00:32] <RAOF> There's the standard way, same as getting any other package in Ubuntu.  https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages?action=show&redirect=MOTU%2FPackages%2FNew is an English version of the page; I'm not sure if there's a Portugese translation.
[00:32] <azeem> but if he really wants to get his packages into universe, he just become a MOTU
[00:33] <azeem> the language barrier might be a problem, though
[00:33] <leleobhz> the idea is only to add these packages to ubuntu repositories
[00:33] <wgrant> leleobhz: Why does that site exist, then?
[00:33] <leleobhz> wgrant: because a lot of these games dont exist packaged for ubuntu
[00:33] <wgrant> Then somebody should package them for Ubuntu.
[00:34] <leleobhz> and the intention is teach a easy way to novice users get their games working on linux
[00:34] <azeem> it seems to have been quite some work to build up this community etc.
[00:34] <leleobhz> [24/11-22:32:59] < azeem> but if he really wants to get his packages into universe, he just become a MOTU
[00:34]  * leleobhz think this is the case...
[00:34] <wgrant> I don't see why people are so quick to start their own repositories and communities when they can with substantially greater ease leverage the existing repository and community.
[00:35] <azeem> well, becoming a motu doesn't exactly happen overnight these days, AIUI
[00:35] <leleobhz> the idea is dont need a isolated repository, but have these games available throught ubuntu
[00:35] <wgrant> One doesn't seen to be a MOTU to get packages into universe.
[00:35] <wgrant> s/seen/need/
[00:35] <azeem> leleobhz: there's a vibrant Debian/Ubuntu games team
[00:35] <wgrant> leleobhz: Why does the isolated repository exist, then?
[00:35] <azeem> leleobhz: possibly, somebody of them speaks portuguese
[00:36] <azeem> leleobhz: I think there are at least a couple of spanish speakers in there
[00:36] <azeem> he should contact them
[00:36] <azeem> IMO
[00:36] <leleobhz> wgrant: because the packages isnt on ubuntu (yet i hope :p_
[00:36] <leleobhz> azeem: its a great idea too
[00:36] <azeem> wgrant: let's assume it was by ignorance of the available procedures
[00:37] <wgrant> azeem: There is an awful lot of that around these days, it seems.
[00:37] <azeem> yeah, sure
[00:37] <leleobhz> azeem: yes... these guys arent very experienced about packaging
[00:37] <leleobhz> well, ill discuss with Coringao these ideas
[00:37] <azeem> I guess there's a lot of over-motivated people who hear about FLOSS communities, get excited and want to start their own community
[00:37] <james_w> I have some sympathy though, I wouldn't want to try and push 20 packages in to Ubuntu
[00:38] <azeem> yeah
[00:38] <wgrant> Then I would posit that they have no business running their own repository to work around QA procedures.
[00:38] <leleobhz> and i need to get away because im busy
[00:38] <azeem> leleobhz: thanks for doing this!
[00:38] <azeem> now, where is bddebian when you need him
[00:39] <azeem> wgrant: it's Free Software
[00:39] <azeem> what they do isn't smart for the community, but they can do whatever they please
[00:39] <wgrant> I didn't say it wasn't permitted.
[00:40] <azeem> just remember that Debian people though exactly the same of Ubuntu when it started up
[00:40] <azeem> but anyway, let's hope this is getting resolved in the games team or something
[00:40] <azeem> thought*, anyway
[00:40] <wgrant> True.
[00:49] <directhex> there are cases where you don't have many options
[00:49] <directhex> e.g. my mono updates repo, since mono is barred from foo-backports
[00:49] <azeem> heh
[00:51] <directhex> and i'll continue to cite my 12000+ user statistic, even though the number has dropped significantly post-intrepid-release :/
[01:47] <kirkland> mathiaz: i managed to create an ubuntu branch of ecryptfs-utils: http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=shortlog;h=ubuntu
[01:49] <mathiaz> kirkland: great
[01:49] <kirkland> mathiaz: okay, i'm trying iscsitarget.failed-upgrade
[01:50] <mathiaz> kirkland: I've build your package - it seems that it's working if you renamed iscsitarget.prerm to prerm
[01:51] <kirkland> mathiaz: oh, hmm...  interesting.  i named it iscsitarget.prerm per man dh_installdeb
[01:51] <mathiaz> kirkland: right - however you have docs and dir files in debian/
[01:51] <mathiaz> kirkland: so it seems that debhelper assumes that your only building one package.
[01:52] <mathiaz> kirkland: and you can just use prerm, postinst
[01:52] <kirkland> mathiaz: okay, let me give that a shot
[01:52] <mathiaz> kirkland: ok - how did you notice that it wouldn't work?
[01:57] <kirkland> mathiaz: that what wouldn't work?
[01:58] <kirkland> mathiaz: i tried building the package, and expected the file debian/iscsitarget.prerm.debhelper to be generated, with my code plus the auto-generated code
[01:58] <kirkland> mathiaz:  when you do that (rename it to prerm), do you get: E: iscsitarget: maintainer-shell-script-fails-syntax-check prerm
[02:00] <kirkland> mathiaz: nevermind
[02:00] <kirkland> mathiaz: boneheaded syntax error on my part
[02:04] <kirkland> mathiaz: hmm, so when you said it "worked" ...  did your built package end up with a fully populated debian/iscsitarget.prerm.debhelper ???
[02:06] <kirkland> mathiaz: hmm, but it does look right in debian/iscsitarget/DEBIAN
[02:07] <mathiaz> kirkland: ok - so that means the package is probably correct then.
[02:14] <nhandler> To get a package backported to intrepid, do I just file a bug against intrepid-backports and subscribe ubuntu-backporters?
[02:16] <ScottK-laptop> nhandler: Yes.  If you can say you've tested that it builds, installs, and runs, then say so and set it to confirmed.
[02:17] <ScottK-laptop> nhandler: Feel free to ping me after you've done that.
[02:17] <nhandler> ScottK-laptop: Is it a requirement to upload it to a PPA?
[02:18] <ScottK-laptop> nhandler: Not at all.
[02:18] <ScottK-laptop> nhandler: You  tell me you  tested it and that's good enough.  If it FTBFS, then I send NCommander to hunt you down.
[02:18] <nhandler> ScottK-laptop: Great. I'll submit the bug report. It built cleanly in pbuilder
[02:19] <NCommander> wait, what?
[02:19] <ScottK-laptop> NCommander: Easy.  Not yet.
[02:29] <nhandler> ScottK-laptop: Bug #301914
[02:31] <kirkland> mathiaz: okay, i've got it going now ;-)
[02:31] <kirkland> mathiaz: tested, working
[02:35] <ScottK-laptop> nhandler: Looking
[02:36] <nhandler> Thanks ScottK-laptop
[02:36] <mathiaz> kirkland: did you add the code to failed-upgrade?
[02:36] <kirkland> mathiaz: no, prerm
[02:36] <kirkland> mathiaz: that seemed to work better
[02:37] <ScottK-laptop> nhandler: You also need to say it installs and runs.
[02:37] <mathiaz> kirkland: hm - I meant i the prerm script - under which action did you put the code?
[02:37] <mathiaz> kirkland: upgrade or failed-upgrade?
[02:37] <nhandler> ScottK-laptop: Ok, I'll add that in (it does install/run)
[02:37] <ScottK-laptop> Great.
[02:38] <kirkland> mathiaz: oooooohhhhhh
[02:38] <kirkland> mathiaz: great idea
[02:39] <kirkland> mathiaz:  i couldn't it to work under that part of the case statement, so i removed it entirely
[02:39] <kirkland> mathiaz: duh, it belongs under failed-upgrade
[02:39] <mathiaz> kirkland: http://women.debian.org/wiki/English/MaintainerScripts
[02:39] <mathiaz> kirkland: ^^ there is a chart about the sequence of maintainer script calls.
[02:39] <ScottK-laptop> nhandler: Ack'ed.  Now it's just question of when an archive admin processes it.
[02:40] <nhandler> ScottK-laptop: Thanks a lot
[02:42] <kirkland> mathiaz: bingo, that works perfectly
[02:43] <kirkland> mathiaz: http://pastebin.ubuntu.com/76655/
[02:48] <kirkland> mathiaz: cool, i'm happy with it, uploading ....
[02:52] <mathiaz> kirkland: hm - have you already uploadedÉ
[02:52] <mathiaz> kirkland: ?
[02:52] <kirkland> mathiaz: nope
[02:53] <kirkland> mathiaz: was giving you a chance to respond, since you had looked at it
[02:53] <mathiaz> kirkland: what about protecting the code with a version comparisonÉ
[02:53] <mathiaz> kirkland: ?
[02:53] <mathiaz> kirkland: OTOH you're checking the md5sum
[02:53] <kirkland> mathiaz: i thought about that, but i figure the md5sum was even stronger
[02:55] <mathiaz> kirkland: ok - I think it makes sense.
[02:56] <mathiaz> kirkland: what kind of testing did you do?
[02:56] <kirkland> mathiaz: 1) installed the new package on a system with no iscsitarget package installed
[02:57] <kirkland> mathiaz: 2) installed the new package on a system with the Intrepid iscsitarget package installed
[02:57] <kirkland> (ie upgraded)
[02:57] <kirkland> mathiaz: 3) upgraded from the current jaunty package
[02:57] <kirkland> mathiaz: 4) upgraded against itself
[02:57] <kirkland> mathiaz: all of those seemed to succeed
[02:58] <mathiaz> kirkland:hm ok.
[02:59] <mathiaz> kirkland: I don't see the point of 4) though
[03:04] <kirkland> mathiaz: good enough?  any other concerns?
[03:05] <mathiaz> kirkland: no other concerns.
[03:05] <mathiaz> kirkland: I was just wondering what was the use case of 4)
[03:06] <kirkland> mathiaz: none really, now that i think of it
[03:37] <freeflying> james_w: fcitx has a nmu upload in debian, would u like sync it?
[03:37] <ScottK-laptop> freeflying: Is there currently an Ubuntu difference?
[03:38] <ScottK-laptop> We're in auto-sync now, so if there isn't it'll happen automatically.
[03:39] <freeflying> ScottK-laptop: no, I prepare upload a svn snapshot of fcitx, its good for me to sync it before I uplaod :)
[04:15] <Elbrus> has anybody experience in building in with sbuild? when I add universe to the sources.list I get a "W: GPG error: http://us.archive.ubuntu.com hardy Release: Could not execute '/usr/bin/gpgv' to verify signature (is gnupg installed?)" warning and the build failes.
[04:15] <Elbrus> I could install gnupg in the schroot, but than the root is not "clean" anymore...
[04:16] <Elbrus> Any idea how to handle this correctly?
[04:27] <jmarsden> Elbrus: Read https://help.ubuntu.com/community/SbuildLVMHowto and check the --source-template option?
[04:30] <Elbrus> jmarsden: I have no experience with LVM, it is something worth learning at this moment?
[04:35] <jmarsden> I'm not sure.  Try just reading the sbuild man pages or do more googling for sbuild ubuntu sources?  LVM isn't hard, but if you've never played with it, I'm not sure it's necessary at this point for you either.
[04:36] <Elbrus> what is the minimum that the root should have: build-essential and ubuntu-minimal?
[04:40] <jmarsden> Does man 7 sbuild-setup not answer that?  In a rather Debian-focused way, but still... it mentions several things to apt-get.
[04:41] <jmarsden> Is there a reason you can't use pbuilder, which seems to be simpler to set up and use?
[04:42] <Elbrus> jmarsden: I used the sbuild-createchroot script which is *supposed* to take care of it
[04:42] <Elbrus> jmarsden: yes, lazarus does not want to build in it... to much happening before the source is passed to the jail
[04:42] <Elbrus> might be a bug worth reporting to lazarus, but of that I am not sure
[04:43] <Elbrus> jmarsden: oh, I use pdebuild, but IIUC that is nearly the same, right/
[04:44] <Elbrus> s/\//?
[04:44] <jmarsden> Yes.  You can use   sudo pbuilder --login to play around inside a pbuilder if you need to set something up just so for lazarus?
[04:46] <jmarsden> Worst case, once lazarus builds for you outside of a chrooted world, you could just upload it to your PPA, and see whether it builds OK there? ;)
[04:46] <Elbrus> hmm, it really pukes on it before it even gets to pbuild (the clean rule calles patch and unpatch, I think it goes wrong there)
[04:47] <Elbrus> I prefer only building inside chroots, because I am not so experienced in programming that I trust the handling outside the jail... or am I exagurating here?
[04:48] <jmarsden> It's up to you... I'm not an expert at all.  I tend to build things in my real live machine, then check for dependency issues etc in a pbuilder, then upload to PPA, then if all of those work, my build is probably OK.
[04:52] <Elbrus> and how do you build against different ubuntu versions outside a chroot?
[04:53] <Elbrus> or just test the building on the live machine and then the rest in the PPA?
[04:54] <Elbrus> jmarsden: thanks for the help
[04:55]  * Elbrus is going to bed now.
[04:55] <jmarsden> Elbrus: No problem
[06:10] <dholbach> good morning
[06:12] <NCommander> morning dholbach
[06:13] <dholbach> hi NCommander
[06:14] <NCommander> how goes it dholbach?
[06:14] <dholbach> good good - how 'bout you?
[06:14] <NCommander> Packaging KDE 4.1.80
[06:14] <nellery> hi dholbach
[06:14] <dholbach> great
[06:14] <dholbach> hi nellery
[06:53] <nellery> where does the --logfile option of pbuilder place the created log?
[06:54] <Hobbsee> wherever you specify it directly afterwards, normally
[06:54] <nellery> so --logfile ~/build.log would be fine?
[06:55] <Hobbsee> yes,b ut that may well end up in /root/build.log if you're not careful.
[06:55] <nellery> Hobbsee: I see, thanks for your help
[06:57] <Hobbsee> nellery: you're welcome. If you want to make absolutely sure where it goes, specify an absolute path (eg /home/nellery/build.log)
[06:57] <nellery> Hobbsee: yup, I got that
[06:57] <Hobbsee> cool :)
[06:57] <nellery> thanks
[06:57] <Hobbsee> you're welcome
[13:02] <stefanlsd> Laney: around?
[13:34] <Laney> hi stefanlsd
[13:35] <stefanlsd> Laney: heys. let me try remember what i wanted to ask you :)
[13:36] <Laney> :O
[13:37] <stefanlsd> Laney: I think it was re: bug #246720
[13:38] <Laney> What about it?
[13:39] <stefanlsd> thats the part i cant remember. was doing the merge of the new libavg and wanted to ask u something bout that.   (was on the weekend, so yeah)
[13:45] <Laney> heh
[13:45] <Laney> well if you remember then you can ask me
[13:45] <jussio1> Laney: what happened to the btnx package?'
[13:45] <Laney> jussio1: I gave up
[13:45] <jussio1> :(
[13:45] <jussio1> why?
[13:46] <Laney> The code wasn't in good shape iirc
[13:46] <Laney> have a go at packaging it if you want
[13:47] <jussio1> Laney: if you failed... Im guessing myskills ar much less than yours...
[13:49] <Laney> not necessarily!
[13:55] <jussio1> Laney: Ive not really toched packaging for a while, although I should do....
[14:13] <DktrKranz> nhandler: re loadlin merge, I've got a working copy in my PPA. Anyway, I just passed -fno-stack-protector to the right location, but I'm still not comfortable with it.
[14:13] <DktrKranz> I'd like to see it more in detail
[14:16] <azeem> (IME, the person who did the last loadlin Debian upload is extremely competent at what he does)
[14:19] <DktrKranz> azeem: well, I'm not confident -fno-stack-protector is the best way to "fix" FTBFS in Ubuntu buildds, absolutely no blame to Debian maint.
[14:30] <RainCT> hey
[14:34] <DktrKranz> hey RainCT
[15:06] <bddebian> Heya gang
[15:26] <jcfp> motu's, if you have some time please review http://revu.ubuntuwire.com/details.py?package=sabnzbdplus
[15:27] <Laney> YEAH! DO!
[16:58] <geser> Hi bddebian
[16:59] <bddebian> Heya geser
[17:22] <|eMerzh|> Hi all, i need some help for my package,....i don't understand how to split my package into main and -doc...(http://revu.ubuntuwire.com/details.py?package=sqliteman) ...could someone help me?
[17:28] <RainCT> |eMerzh|: install everything into debian/tmp and from there put it into the appropiate binary package listing the directories you want to include into it in debian/sqliteman.install and debian/sqliteman-doc.install
[17:32] <kirkland> kees: https://code.edge.launchpad.net/~kirkland/bogosec/trunk revisions 294 and 295
[17:33] <kirkland> kees: mikeowens is repacking for updated upload to revu
[17:33] <|eMerzh|> RainCT: ok i'll try this
[17:44] <kees> kirkland: cool!
[18:17] <RainCT> jono: Hey. Did gnome-shell build correctly for you on Intrepid?
[18:18] <jono> RainCT, yep
[18:19] <RainCT> jono: with which automake version?
[18:19] <jono> RainCT, no idea
[18:19] <RainCT> jono: dpkg -l | grep automake  :)
[18:19] <jono> ii  automake                                  1:1.10.1-3                              A tool for generating GNU Standards-compliant Makefiles
[18:20] <jono> ii  automake1.9                               1.9.6+nogfdl-3ubuntu1                   A tool for generating GNU Standards-compliant Makefiles
[18:21] <RainCT> jono: Alright, I'll try with this one. Thanks :).   (It's FTBFS here and a guy who is helping me on #gnome-shell said it may be because of automake)
[18:21] <jono> wicked
[18:21] <jono> good luck :)
[18:22] <RainCT> thanks :)
[18:24]  * RainCT hugs jono -- it build now! :)
[18:26] <jono> woo!
[18:26]  * jono hugs RainCT
[18:26] <jono> :)
[18:30]  * directhex pokes RainCT
[18:30]  * RainCT looks at directhex
[18:31] <directhex> RainCT, mono 2 landed in debian. got a gbrainy transition ready?
[18:31] <RainCT> directhex: I have some changes in SVN but I'm not sure if there was something missing
[18:32] <directhex> RainCT, in pkg-cli-apps?
[18:33] <RainCT> directhex: Yep. svn.debian.org/svn/pkg-cli-apps/packages/gbrainy/trunk
[18:33]  * |eMerzh| has just udpate his package....any review/comments is welcome (http://revu.ubuntuwire.com/details.py?package=sqliteman ) thanks to all
[18:35] <iulian> directhex: I'm the maintainer of giver (it's on http://wiki.debian.org/Teams/DebianMonoGroup/Mono20TransitionTODO) and I wonder what I should do.
[18:35] <iulian> I've no idea about this transition.
[18:36] <directhex> iulian, i wrote instructions on http://wiki.debian.org/Teams/DebianMonoGroup/Mono20Transition#head-67c13a005dab7f510b0fd1ee8db7a30689e89669
[18:36] <directhex> iulian, if anything's unclear, please ask
[18:36]  * iulian is looking
[18:37] <directhex> oh, sodding cdbs. RainCT, looking at your control/rules, you still need to transition it, but i don't understand cdbs enough for the rules change
[18:38] <directhex> - mono-gmcs (>= 1.1.8)
[18:38] <directhex> + mono-devel (>= 2.0)
[18:38] <directhex> that's the control change
[18:40] <RainCT> directhex: yep, the control change is done, but I've just noticed that I didn't commit it :)
[18:41] <sebner> RainCT: gbrainy?
[18:41] <RainCT> directhex: I'll look into the rules one once I've more time (unless you discover what change is required before :))..
[18:41] <RainCT> sebner: yep
[18:41] <sebner> RainCT: nice
[18:42] <RainCT> themuse: where have your caps gone? :P
[18:43] <directhex> ding ding, who feels like telling me how to add a custom flag to ./configure in cdbs-land?
[18:43] <directhex> you're all cdbs-using weenies here, right? :p
[18:43] <sebner> directhex: wäääähhhhhh, noooooooo
[18:45] <directhex> RainCT, looking at gbrainy source, you need to pass MCS=/usr/bin/csc to ./configure
[18:45] <directhex> RainCT, but cdbs is scary!
[18:45] <Laney> directhex: DEB_CONFIGURE_USER_FLAGS += blah
[18:45] <directhex> aha, there you go. thanks Laney
[18:46]  * directhex adds to debian wiki
[18:50] <directhex> how does DEB_CONFIGURE_EXTRA_FLAGS differ from DEB_CONFIGURE_USER_FLAGS?
[18:52] <ScottK> IIRC extra adds to the existing list and the other one replaces it.
[18:54]  * directhex thinks extra is better then
[18:55] <iulian> directhex: Aren't the packages located at svn.d.o/svn/pkg-cli-apps/packages/pkg?
[18:56] <Laney> $(DEB_CONFIGURE_INVOKE) $(DEB_CONFIGURE_EXTRA_FLAGS) $(DEB_USER_CONFIGURE_FLAGS)
[18:56] <Laney> I don't really understand the difference
[18:56] <iulian> directhex: Bleah, they aren't. Just checked on alioth machine.
[18:56] <directhex> iulian, the ones which are in our svn, yes. not all of them are though
[18:57] <directhex> iulian, we don't steal packages which people don't want to have available for collaborative maintenance
[18:57] <directhex> except ironpython, we want to steal that one ;)
[18:57] <iulian> And why can't I co?
[18:58] <iulian> Heh
[18:58] <directhex> giver IS in svn?
[18:58] <iulian> Yes, it is.
[18:58] <iulian> directhex: http://svn.debian.org/wsvn/pkg-cli-apps/packages/giver/
[18:59] <directhex> well, yeah then. don't you have commit access to that folder? o_o
[18:59] <iulian> 110026(pkg-cli-apps),150026(scm_pkg-cli-apps)
[19:00] <iulian> I should.
[19:00] <directhex> well... carry on then!
[19:00]  * directhex got confused :|
[19:01] <slytherin> iulian: what is the url you are using?
[19:01] <directhex> Path: /home/directhex/Projects/pkg-cli-apps/packages/giver/trunk/debian/rules
[19:01] <directhex> Last Changed Author: iulian-guest
[19:02] <iulian> Hmm, then how can I pull that from svn?
[19:02] <slytherin> iulian: what is the url you are using?
[19:02] <directhex> URL: svn+ssh://svn.debian.org/svn/pkg-cli-apps/packages/giver/
[19:03] <directhex> use your iulian-guest alioth login
[19:03] <iulian> slytherin: ^
[19:03] <iulian> directhex: I believe I did that.
[19:03] <directhex> probably need to set it in ~/.ssh/config
[19:03] <iulian> Hmm, I will try again.
[19:03] <directhex> Host svn.debian.org
[19:03] <directhex> User directhex-guest
[19:03] <iulian> I usually use<EMAIL_ADDRESS>[19:04] <slytherin> iulian: I believe the url should be svn+ssh://svn.debian.org/pkg-cli-apps/packages/giver/
[19:06] <amikrop> Hi. When I boot with the vga=791 option, the tty resolution is set correctly, but my splash screen is messed up. Any help, please?
[19:08] <iulian><EMAIL_ADDRESS>No such file or directory
[19:08] <iulian> Am I missing something?
[19:08]  * RainCT grumbles about aptitude not accepting alternative installs (ie, "aptitude install a | b", which wouldn't do anything if either of them is installed) :P
[19:08] <directhex> iulian, odd. try just checking out<EMAIL_ADDRESS>?
[19:13] <slytherin> directhex: I believe that /svn/pkg-cli-apps should be only /pkg-cli-apps
[19:13] <directhex> oh, should it? balls
[19:14] <iulian> directhex: Ah crap. Forgot the co part. This is the reason why it didn't work. svn is just not my preferred vcs TBH.
[19:14] <directhex> iulian, well, until alioth has a Visual SourceSafe service... :(
[19:15] <iulian> slytherin: There is no pkg-cli-apps dir in /. So it should be /svn/pkg-cli-apps.
[19:15] <iulian> Yay, he already left.
[19:16] <directhex> iulian, got there in the end? \o/
[19:16] <iulian> directhex: Why you guys don't switch to git? IIRC I talked to meebey a few months ago and he wasn't too happy about how svn works.
[19:16] <amikrop> When I boot with the vga=791 option, the tty resolution is set correctly, but my splash screen is messed up. Any help, please?
[19:17] <directhex> iulian, does alioth do git? is that recent?
[19:17] <directhex> amikrop, change the settings in /etc/usplash.conf
[19:18] <amikrop> directhex: and make them what?
[19:18] <directhex> amikrop, erm, make them match 791?
[19:18] <directhex> i think 791 is 1024x768 isn't it?
[19:19] <amikrop> directhex: currently, they are my screen's full res
[19:19] <amikrop> directhex: yes
[19:19] <amikrop> directhex: currently, they are 1920x1200
[19:19] <directhex> ah, was about to ask if it was widescreen trouble
[19:19] <amikrop> directhex: I *have* a widescreen, right?
[19:20] <iulian> directhex: No, I believe not. lrwxrwxrwx 1 root root 23 2006-10-25 12:02 /git -> /srv/git.debian.org/git
[19:20] <amikrop> directhex: ?
[19:20] <directhex> i'd love to fix usplash to cope with widescreen properly, but it's funky c, and i'm scared of just offering backseat programming advice to someone like mjg59
[19:20] <directhex> amikrop, 1920x1200 is 19:10 widescreen, yes. 24/27" tft.
[19:21] <directhex> amikrop, but 791 is a non-widescreen mode
[19:21] <amikrop> directhex: so, what mode would be good for my ttys?
[19:21] <directhex> amikrop, well, "best" would be a 1920x1200 framebuffer
[19:21] <amikrop> directhex: there is not a mode for 1920x1200
[19:22] <directhex> amikrop, not if you're reading charts from sites like linuxquestions there isn't
[19:22] <amikrop> directhex: but...?
[19:22] <directhex> amikrop, install "hwinfo", run "sudo hwinfo --framebuffer"
[19:22] <directhex> amikrop, your GPU may offer a non-standard >1024 mode
[19:22] <directhex> e.g. my laptop has 1280x800
[19:23] <amikrop> directhex: ok, it diplsayed many modes
[19:24] <amikrop> which should I choose?
[19:24] <directhex> amikrop, it displays modes in hex, e.g   Mode 0x0307: 1280x1024 (+1280), 8 bits
[19:24] <directhex> amikrop, pick the "best" mode you can find, and convert the hex mode to decimal
[19:24] <amikrop> directhex: I know, I just ran it
[19:24] <amikrop> directhex: what is the "best"?
[19:25] <directhex> amikrop, well, 1920x1200x24, if you have it
[19:25] <amikrop> The onw with the higher bits? the one with the +number in parantheses? the higher res?
[19:25] <amikrop> * one
[19:26] <jmarsden|work> amikrop: 1920x1200 with 24 bits is the one you want
[19:26] <amikrop> directhex: it is not available
[19:26] <amikrop> jmarsden: it is not available
[19:27]  * directhex smells user support rather than packaging work
[19:27] <amikrop> directhex: two "good" ones seem to be 1600x1200x16 and 1024x768x24
[19:27] <amikrop> sorry
[19:27] <directhex> amikrop, well, use one of those then.
[19:28] <amikrop> 1280x1024x24 and 1600x1200x16
[19:28] <amikrop> directhex: what is the best of these two?
[19:28] <directhex> convert the Mode to decimal and use that line in your menu.lst - e.g.   "Mode 0x0317: 1024x768 (+2048), 16 bits" might look familiar
[19:28] <directhex> amikrop, which do you care more about, the resolution or the color depth? in your consoles, this is.
[19:29] <amikrop> directhex: well, which do *you* care about most, in your consoles?
[19:30] <amikrop> directhex: so? :-)
[19:31] <directhex> amikrop, which do you want in your text console. 65,536 colours or 16,777,216 colours?
[19:31] <amikrop> directhex: It doesn't matter so much, I guess...
[19:32] <amikrop> directhex: Because it is just a console.
[19:32] <amikrop> directhex: right?
[19:32] <directhex> right. but i wasn't answering for you
[19:32] <amikrop> directhex: excuse me? you weren't answering for me? I didn't understand that...
[19:35] <directhex> amikrop, you spent 10 minutes asking which number was bigger, in a development channel
[19:35] <amikrop> directhex: Well, I am sorry.
[19:36] <directhex> amikrop, so like i said. pick the mode you want to use, convert the Mode 0x bit to decimal, use that number instead of 791, and ensure /etc/usplash.conf matches it
[19:37] <amikrop> directhex: after, $ sudo update-initramfs -u ?
[19:37] <directhex> yeah.
[19:37] <directhex> and update-grub after changing menu.lst
[19:37] <amikrop> ok, thanks, and excuse me, again
[19:47] <directhex> was i out of order? O-o
[19:50] <iulian> directhex: Is it required to add CSC=/usr/bin/csc when configuring?
[19:51] <amikrop> directhex: I put vga=884 for 1600x1200x16 but it told me that the the mode 386 or somthing was invalid (during boot) and it prompted me to choose on now. And it gave me a list with modes different than that https://wiki.ubuntu.com/FrameBuffer#grub.
[19:52] <directhex> iulian, strictly speaking, we'll let you live as long as you were already using gmcs - but we want to see the compiler overridden to be 'csc', which is our 'default c# compiler for this release' executable
[19:52] <amikrop> directhex: It gave me a list with 3xy, 3xz etc, and not 7xy, 8xz like the one above
[19:52] <amikrop> I guess its the decimal conversion part, which you told me about
[19:52] <iulian> directhex: Ah-ha
[19:52] <directhex> amikrop, then your GPU behaves funny and doesn't offer high res modes until late in the boot process (e.g. after the driver is loaded). my old geforce did that
[19:53] <directhex> iulian, but different apps use a different thing in autoconf - i need to check the giver source to see if it uses CSC or MCS or CAKE or what
[19:54] <directhex> hm, no autofoo in giver. sigh
[19:54] <amikrop> directhex: any suggestions?
[19:54] <iulian> directhex: That would be great. In the meantime I will test the package to see if it works.
[19:54] <iulian> directhex: Ah, OK.
[19:54] <directhex> iulian, looks like it takes GMCS
[19:55] <directhex> so GMCS=/usr/bin/csc
[19:55] <directhex> amikrop, well, when in doubt, back down to 791 shou;d always work
[19:55] <amikrop> directhex: but 791 is not wide screen
[19:56] <directhex> amikrop, neither is any of the modes you mentioned. and usplash doesn't work peoperly with widescreen consoles
[19:56] <amikrop> directhex: ok, then. thanks.
[19:57] <iulian> directhex: Shouldn't it be /gmcs instead of /csc?
[19:58] <directhex> iulian, currently csc is a link to gmcs.
[19:59] <directhex> iulian, upstream have talked about merging gmcs and mcs again - so we might do something make sure we can phase changes to suit us
[19:59] <directhex> iulian, the way 'python' isn't neccessarily 'python3.0'
[20:00] <iulian> OK, I will just use csc then.
[20:01] <Rinchen> Hi MOTUs!  Question... I've just been alerted to a security exposure in a MOTU packaged Universe package.  Whom do I report this too?
[20:02] <Rinchen> Bug on the source package?
[20:02] <directhex> iulian, looks like you might get the honour of being the first *app* to be transitioned :p
[20:02] <RainCT> Rinchen: Yep
[20:02] <iulian> directhex: Oh, really? Cool ;)
[20:02] <RainCT> Rinchen: there's an option to make the bug private
[20:02] <Rinchen> right... ok.
[20:03] <Rinchen> looks like it was filed
[20:03] <handschuh> Is there anybody who wants to be the second advocate on http://revu.ubuntuwire.com/details.py?package=uiflite ?
[20:03] <Rinchen> but not marked as a security vuln
[20:03] <directhex> iulian, unless you & RainCT get into some kind of exciting battle
[20:03] <Rinchen> actually, it is...
[20:03]  * Rinchen curses his LP Admin privs sometimes :-)
[20:03] <Rinchen> thanks
[20:04] <RainCT> np
[20:04] <RainCT> directhex: heh, no, I leave him the honor :)
[20:08] <directhex> the weekend's mono 2 transition work made both ars technica and boycott novell \o/
[20:08] <iulian> directhex: I see that mono-devel is still in experimental. Should I target it to experimental as well?
[20:08] <directhex> iulian, yes.
[20:09] <directhex> iulian, this is pre-work for squeeze! and jaunty, of course
[20:09] <iulian> directhex: Yeah, wondered why pbuilder failed.
[20:10] <directhex> ah. i recommend you test against jaunty in pbuilder for now
[20:10] <directhex> as mono 2.0-1 in experimental is a little broken - 2.0.1 should land later tonight
[20:10] <iulian> OK
[20:10] <directhex> (it's already in jaunty)
[20:14] <ajmitch> directhex: how many nastygrams have you got for supporting the evil mono?
[20:15] <directhex> ajmitch, to my inbox? only one. the anti-mono crowd are mostly cowards, so they just insulte me on irc & blogs
[20:16] <ajmitch> directhex, singlehandedly destroying free software ;)
[20:16] <directhex> ajmitch, not at all. meebey is the jedi master of mono on debian. it'd go nowhere without him
[20:17] <ajmitch> I know
[20:21] <amikrop> I sticked with 791. How can I set my TTYs to be colorful, now? Is it an option in ~/.bash_profile or something?
[20:21] <amikrop> directhex
[20:21] <directhex> yes.
[20:21] <amikrop> directhex: How can I find out which option it it?
[20:22] <directhex> force_color_prompt=yes
[20:22] <directhex> in bashrc
[20:22] <DRebellion> Hi, could anybody point me to a list of the possible values for the Section: field in debian/control?
[20:23] <amikrop> directhex: thanks :)
[20:29] <iulian> directhex: It's done. It built without problems. Please take a peek at http://users.alioth.debian.org/~iulian-guest/giver_diff
[20:30] <directhex> iulian, looks perfect to me, let me run it by meebey
[20:31] <iulian> directhex: OK, I will commit to svn as well.
[20:32] <slytherin> can someone please give back libxpp3-java?
[20:33] <ScottK> slytherin: Done.
[20:33] <directhex> bring it back, sing it back, bring it back, sing it back to meeeeeeeee
[20:34] <slytherin> ScottK: thanks
[20:34] <directhex> iulian, apparently your restructured rules are a bit odd (the mono 2 transition bit is fine), can you join oftc #debian-mono to speak with meebey?
[20:35] <iulian> Sure
[20:36] <|eMerzh|> if someone want to review my updated package (http://revu.ubuntuwire.com/details.py?package=sqliteman) ... please feel free to leave comments or advocacy
[20:37] <amikrop> directhex: PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ' this line displays green. how can I make it display red?
[20:37] <slytherin> |eMerzh|: There is no need to advertise the package so frequently except on revu days.
[20:38] <directhex> amikrop, i'm no expert on ANSI color codes
[20:38] <ajmitch> play with the numbers
[20:39] <fabrice_sp> Hi. I'm writing the debian/copyright file for a software that is 'GPL' (that's what there is in source files). Is it the same as GPL-2+ ?
[20:39] <amikrop> ajmitch: which numbers?
[20:39] <ajmitch> 32m & 34m
[20:39] <amikrop> directhex: at least, do you know what part is about the color?
[20:39]  * ajmitch can't remember, it's been so long
[20:40] <directhex> fabrice_sp, what does the COPYING file it comes with say?
[20:40] <ajmitch> fabrice_sp: they don't have the usual GPL header in the source?
[20:40] <fabrice_sp> COPYING says "GNU GENERAL PUBLIC LICENSE"
[20:40] <directhex> no version? seriously sounds like v1 o_o
[20:40] <fabrice_sp> yes
[20:41] <fabrice_sp> but v1 has been superseded by v2, right?
[20:41] <ajmitch> any date mentioned in COPYING?
[20:41] <fabrice_sp> Copyright (C) 1989, 1991 Free Software Foundation, Inc.
[20:41] <ajmitch> sounds like GPL 2
[20:42] <fabrice_sp> yes: i've just found that: Version 2, June 1991
[20:43] <fabrice_sp> so it's a GPL-2 only? No +?
[20:43] <fabrice_sp> my reviewer in REVU tells me about GPL-3 :-/
[20:44] <|eMerzh|> slytherin: oups...don't want to upset ....just impatient to see if it 'll we accepted....its my first package....
[20:44] <ajmitch> does the source file not have the appropriate GPL headers in comments?
[20:44] <slytherin> fabrice_sp: check if all files are under same license.
[20:44] <fabrice_sp> slytherin: That's what I'm doing
[20:45] <fabrice_sp> but the sources files only have 'Licence:     GPL'
[20:45] <slytherin> |eMerzh|: Don't worry, someone will review it eventually
[20:45] <slytherin> geser: ping
[20:45] <fabrice_sp> so COPYING licence (GPL-2) apply in that case?
[20:48] <fabrice_sp> arghh: one source file  is under wxWindows licence :-/
[20:48] <ajmitch> oh fun
[20:48] <ajmitch> copyright stuff is a hassle at best
[20:51] <fabrice_sp> ajmitch: yes :-/
[20:52] <fabrice_sp> the new format for copyright file is clearer, I think
[20:52] <fabrice_sp> so it's a bit easier
[21:00] <slytherin> ScottK: one more please - libjboss-classloader-java
[21:15] <slytherin> ScottK: ping


[02:08] <persia> kwwii: Is there a procedure to request certain letters get finished sooner for the font?  The UbuntuStudio login screen still uses the old font.
[02:35] <troy_s> persia: I'd suspect that Maag will release a full set.
[02:35] <troy_s> persia: It would depend on the brief, but I doubt that they are waiting with baited breath from Canonical. ;)
[02:40] <persia> troy_s: From the announcement I've seen, a set good Europe and surrounding environs is planned.  I just wanted to try to get a couple letters in the next few days :)
[02:42] <troy_s> persia: Use prokyon
[02:42] <persia> Go tell ScottL :)
[02:43]  * persia isn't actually doing the stuff, but just trying to get procedure to provide appropriate direction
[08:52] <thorwil> kwwii: morning! Iain is a fan of green and sepia?
[09:42] <kwwii> thorwil: hehe, oh yeah!
[14:01] <vish> #C6B9A6 , looks really nice color on ambience :)
[14:44] <kwwii> dashua: working on merging your changes
[16:00] <kwwii> dashua: let me know when you'll be around to discuss your changes ;)
[16:00] <knome> kwwii, hey kwwii
[16:00] <knome> hmm.
[16:00] <kwwii> hi
[16:01] <knome> kwwii, iain told me to contact you when i need a new favicon for xubuntu. ;]
[16:01] <kwwii> lol, nice
[16:02] <knome> i still actually haven't got the uds jaunty highres group photo.
[16:02] <knome> :P
[16:02]  * knome hides
[16:02] <kwwii> lol
[16:03] <kwwii> and I'm oging crazy trying to get things in for the deadline tonight
[16:03] <knome> heh, no hurry with my thing.
[16:03] <kwwii> knome: I honestly don't know what state the xubuntu identity is currently
[16:03] <knome> i'll have plenty of time to bug on later this week ^____^
[16:03] <kwwii> knome: we'd have to discuss it a but further
[16:04] <knome> kwwii, i'm working with the new website layout, we're in the midst of logo change
[16:04] <kwwii> knome: ok, if we can pin that down we can take care of it
[16:04] <knome> kwwii, we're trying to integrate something in the style of the new branding into xubuntu as well, but trying to have both the mouse and the COF is hard, especially in small sizes
[16:05] <knome> kwwii, just ping me anytime on Wed-Fri when you have time to discuss. i'm probably available.
[16:06] <kwwii> knome: cool, will do
[16:06] <Daviey> knome: I wonder if you could put the rat inside the logo, as if it was a hamster wheel?
[16:06] <knome> Daviey, hrr, it's a MOUSE :)
[16:06] <Daviey> nah, RAT :-)
[16:07] <knome> Daviey, well, we have that kind of already. but it's too complex.
[16:07] <kwwii> I always thought it was a rat
[16:07] <kwwii> a friendly looking rat
[16:07] <kwwii> :p
[16:07] <knome> Daviey, kwwii: we have a few ideas/drafts, but we are not that sure they'd work.
[16:08] <knome> and they haven't got that good response from our dev community either
[16:09] <islington> what about just the mouse face in the xubuntu colors?
[16:10] <knome> somebody would have to come up with a mouse face that 1) gets the dev community approval 2) works in small sizes
[16:11] <kwwii> knome: well, developerss are usually better at developing than design; and designers are better at design than development
[16:11] <kwwii> funny how that works
[16:11] <knome> heh
[16:11] <knome> funny
[16:11] <knome> but i'm pretty bad in imitating anything real
[16:11] <knome> i'm pretty good with abstract things, i thnk
[16:31] <islington> knome: k did the svg just cleaning in gimp now
[16:33] <knome> islington, okay.
[16:39] <islington> my attempt: http://i.imgur.com/5TIhH.png
[16:43] <islington> that eye might be too blurry though
[16:45] <knome> hmm
[16:45] <knome> the mouth(?) is weird
[16:48] <islington> those are whiskers, I think: http://imgur.com/XXgl1.png
[16:48] <knome> whiskey?
[16:48] <knome> ;)
[16:50] <islington> lol
[16:50] <islington> hold on splitting them up
[16:52]  * vish remembers knome isnt that good at remembering stuff either ;)  [Xubuntu Karmic wallpaper source still not available.. ]
[16:52] <knome> vish, it isn't? wow.
[16:52] <knome> vish, what's your email?
[16:52] <vish> oh , not in the bus again ? ;p
[16:53] <knome> not this time.
[16:53] <knome> drinking latte.
[16:53] <knome> (home)
[16:53] <vish> knome: email >pm
[16:53] <knome> okay
[17:00] <islington> http://i.imgur.com/kjheX.png
[17:05] <knome> can you paste the svg somewhere? i'll add that to our alternatives list
[17:05] <vish> 5
[17:05] <vish> 4
[17:06] <vish> 3
[17:06] <vish> 2
[17:06] <knome> vish, yup
[17:06] <vish> 1
[17:06] <knome> working on it
[17:06] <knome> ;)
[17:06] <vish> yay ;]
[17:06] <vish> damn didnt get to complete my countdown timer :(
[17:06] <islington> knome:  the svg is really bad, at 16, but as you wish where can I up it?
[17:07] <knome> islington, you can send it to<EMAIL_ADDRESS>[17:07] <islington> k
[17:07] <knome> islington, you can also include the png :)
[17:08] <knome> vish, sent
[17:08] <vish> knome: ty :)
[17:08] <knome> for the rest of you: https://wiki.ubuntu.com/Xubuntu/Artwork/Karmic (click the wallpaper image)
[17:10] <islington> knome: embedded png in svg
[17:10] <islington> sent
[17:10] <knome> islington, thanks!
[17:12] <islington> snap test time bbl
[17:23] <thorwil> knome: you should really forget about having both mouse and the CoF
[17:24] <knome> thorwil, i'm not *exhaustively* try to incorporate them both
[17:32] <dashua> kwwii, ping
[18:38] <kwwii> dashua: I'm in the middle of cooking dinner, will you be online later?
[18:39] <kwwii> dashua: otherwise I'll send an email ;)
[19:48] <kwwii> dashua: check out lp:~kwwii/+junk/light-themes-refresh
[19:49] <kwwii> dashua: that is your update, updated by me ;)
[19:57] <dashua> Ok cool.
[19:57] <dashua> Did you add those last focus_color changes?
[19:57] <dashua> I think you will like them.
[19:59] <zniavre> dashua,  can i ask what is this option for ?   :o)
[19:59] <zniavre> im sure i will like it too
[20:00] <dashua> GTK apps hide the line under F E V etc. until you hit ALT
[20:00] <dashua> kwwii, Nice man
[20:02] <zniavre> hmmm what is FEV ?please
[20:02] <dashua> File Edit View
[20:02] <zniavre> ok
[20:02] <dashua> There is a line underneath by default
[20:02] <dashua> This patch hides it until you hit ALT
[20:04] <dashua> kwwii, Nice. You kept the scrollbars :)
[20:05] <kwwii> dashua: yes, but I changed things a little bit
[20:05] <dashua> I like it
[20:05] <vish> iainfarrell: hi.. what does "gloam" stand for?
[20:05] <vish> the tag for the bug..
[20:05] <kwwii> iainfarrell: hey, you wanted something?
[20:06] <iainfarrell> hey vish and kwwii
[20:06] <dashua> kwwii, I would grab those focus_color changes.  I think that is what you were looking for.
[20:06] <iainfarrell> gloam is a word :)
[20:06] <kwwii> dashua: I worked on the buttons a bit too, but I'm not sure if I like them
[20:06] <dashua> Looks great :)
[20:06] <iainfarrell> and kwwii was looking for you earlier but not urgent
[20:06] <iainfarrell> how you doing?
[20:06] <vish> iainfarrell: like twilight? ok.. wondering that it meant for a bug ;)
[20:06] <kwwii> dashua: I'm hoping to use the theme (in that link) as-is ;)
[20:06] <kwwii> iainfarrell: doing well, about to push a theme update
[20:07] <iainfarrell> ohh another .deb?
[20:07] <kwwii> iainfarrell: nope, since I got no response I am just going to put it in lucid
[20:07] <kwwii> :)
[20:07] <dashua> kwwii, Do you want consistent theme focus on all buttons, tabs, scale, etc.?
[20:07] <iainfarrell> I see
[20:07] <dashua> The orange focus?
[20:07] <iainfarrell> one question I had was around Thunderbird
[20:07] <iainfarrell> and the scrolling lozenge
[20:07] <iainfarrell> also noticed something today when installing the .deb you sent over
[20:08] <iainfarrell> massive orange sausage on the bottom :)
[20:08] <iainfarrell> anything we can do about that?
[20:08] <iainfarrell> seems a bit out of place
[20:08]  * thorwil just froze inkscape on ungrouping 2304 objects
[20:08] <dashua> iainfarrell, Can you post a screenshot please?
[20:08] <kwwii> iainfarrell: ouch, haven't tested it with tb yet
[20:09] <iainfarrell> kwwii: it's the same bug as we talked about the other week
[20:09] <iainfarrell> and dashua not easily is the answer :)
[20:09] <iainfarrell> let me try
[20:09] <vish> the scroolbar pixmap could be a bit thinner.. seems too heavy on the windows ;)
[20:09] <vish> scroll*
[20:09] <kwwii> vish: the current code is not using the pixmaps anymore
[20:10] <vish> ah , ok
[20:11] <iainfarrell> kwwii: will send a screenshot
[20:11] <iainfarrell> I need to run
[20:11] <iainfarrell> need to get through mail
[20:11] <kwwii> iainfarrell: cool, have fun
[20:12] <dashua> Probably the progressbar.
[20:14] <dashua> iainfarrell, See ya :)
[20:16] <dashua> kwwii, Can you test those last revisons for focus_color and see if that is ok?
[20:17] <kwwii> dashua: you mean from your branch?
[20:17] <dashua> Yes
[20:17] <kwwii> dashua: so this is a change which is not in the stuff I put in my branch?
[20:17] <dashua> And if you want the gtk-auto-mnemonics = 1?
[20:17] <kwwii> yes, I added that to my stuff as well
[20:18] <dashua> You just changed the GtkRange::trough-under-steppers = 0?
[20:18] <kwwii> dashua: yes, as well
[20:18] <kwwii> I played with a lot of other small changes but wasn't happy with them
[20:18] <kwwii> dashua: so you mean the keyboard focus?
[20:18] <dashua> Yeah
[20:18] <dashua> Looks better with all orange
[20:19] <kwwii> I think the design calls for all focus to be orange ;)
[20:19] <islington> so I am working on porting the token icons into an icon theme. I am reminded of the definition for tedious
[20:19] <dashua> On the tabs, comoboxentry
[20:19] <dashua> Ok good
[20:19] <dashua> The changes are pushed in my branch then. :)
[20:19] <dashua> Rev. 46 was the last
[20:19] <kwwii> ok, I'll get a fresh copy
[20:20] <dashua> No other major changes from yours other than the GtkRange::trough-under-steppers = 0 and I add prelight_shade to murrine options.
[20:20] <kwwii> ok, cool
[20:21] <dashua> The added focus_color really looks great.
[20:23] <kwwii> building it now
[20:28] <kwwii> dashua: I like it, but I think it needs to be more solidly orange
[20:28] <kwwii> at least now it matches the others
[20:29] <dashua> Ok, It's the same color as scale, progressbar, radiochecks.
[20:30] <kwwii> yeah but the engine makes the inside much lighter, or?
[20:31] <kwwii> but I do like it all consistent at least ;)
[20:31] <dashua> Yeah, not sure if I can control that.
[20:32] <kwwii> right
[20:32] <kwwii> this is an improvement in any case
[20:32] <dashua> Yep, I think so. :)
[20:33] <kwwii> ok, I think I will get this version uploaded
[20:33] <dashua> Should be solid now. I spent all weekend bug fixing /tweaking.
[20:33] <kwwii> no doubt...you did some amazing work
[20:33] <dashua> Nice
[20:33] <dashua> Thx.
[20:33] <kwwii> seb asked me first thing this morning about it and who you are ;)
[20:34] <kwwii> we'll make you famous yet ;P
[20:34] <dashua> w00t
[20:35] <islington> screenshot?
[20:39] <kwwii> islington: lp:~kwwii/+junk/light-themes-refresh is the current almost uploaded changes (99.9% from dashua)
[20:40] <islington> not running gnome :( kw
[20:42] <kwwii> ;)
[20:58] <zniavre> ho understand what is focus_color thank you
[21:00] <zniavre> it works with scales it's nice to don't hav focus color around
[21:01] <zniavre> but not with radio/check buttons
[21:01] <zniavre> :o)
[22:40] <kwwii> zniavre: focus_color sets the keyboard focus color for many widgets
[22:41] <zniavre> yes i tried it and use it now for some widget
[22:44] <dashua> kwwii, I was just checking out your branch and it did not pull in all the focus changes.  Prelight_shades were not added also.
[22:45] <dashua> Have border_shades for comboboxentry will keep the focus there grey.
[22:45] <kwwii> dashua: argh, can you send a diff?
[22:45] <kwwii> ahh, right
[22:46] <kwwii> I'll look into it tomorrow
[22:46] <dashua> I guess you could my branch if those were the only changes.
[22:46] <kwwii> or maybe later
[22:46] <kwwii> yeah
[22:46] <dashua> I'll add the understeppers to mine if that is the only change
[22:46] <dashua> Keep it in sync
[22:46] <dashua> 0
[22:47] <kwwii> ;)
[22:47] <dashua> I added them.  Anything different just let me know?
[22:48] <kwwii> I'll probably have to make the buttons darker again
[22:48] <kwwii> and strengthen the lines around it
[22:48] <kwwii> s/it/them
[22:49] <dashua> Ok np
[23:10] <kwwii> dashua: btw, thanks for the excellent help


[00:29] <krytarik> Eickmeyer: https://web.libera.chat/#ubuntustudio - not that I think it matters particularly, since you seem to have already decided in favor of Matrix, but wrt the bug report stating stuff like this isn't possible anymore.. and there is a way to predefine a nick too.
[00:30] <krytarik> https://ubuntustudio.org/support/ - oh, and btw here it still says irc.freenode.net
[03:06] <Eickmeyer> krytarik: The Matrix bridge was easier. And, yes, I still need to update the website.
[03:06] <Eickmeyer> Matrix was decided, like, a year ago.
[03:07] <Eickmeyer> Saved our bacon with the changeover.


[12:17] <{slacky}> hello Riddell
[12:17] <Riddell> {slacky}: !
[12:18] <{slacky}> Riddell: the problem, at least with 5.10 live CD is that I can't set the gateway
[12:18] <Riddell> {slacky}: hmm, that's not good
[12:18] <{slacky}> when I give "route -n" from konsole I see Kubuntu doesn't set the gatway I specifyed
[12:19] <{slacky}> so I have to use "sudo route add default gw IP"
[12:19] <Riddell> {slacky}: the quick way to get round it is to set it in /etc/network/interfaces and ifup ifdown
[12:20] <Riddell> but obviously that won't help all our users
[12:20] <{slacky}> expecially if you release a new distro 2 days ago :(
[12:24] <{slacky}> Riddell: can you check this bug and report it?
[12:25] <Riddell> {slacky}: I've added it to my todo list (which means I won't get round to it until after 3.5beta2)
[12:26] <{slacky}> Riddell: well ok... you have 6 months to fix it if 2 release per year
[12:26] <{slacky}> Riddell: you didn't inserted KSniffer into Kubuntu because is too young and has very few features? :)
[12:27] <{slacky}> Riddell: you didn't insert KSniffer into Kubuntu because is too young and has very few features? :)
[12:27] <Riddell> {slacky}: ksniffer is in the repositories but we only have space for very few applications on the CD
[12:27] <Riddell> and if you need a sniffer then you have internet access anyway
[12:28] <{slacky}> Riddell: breezy is final realease 5.10?
[12:28] <Riddell> yep
[12:28] <{slacky}> Riddell: well into the DVD too?
[12:28] <Riddell> DVD is final too if that's what you mean
[12:29] <Riddell> we would have to get ksniffer into main to get it onto the DVD, which is quite possible
[12:29] <{slacky}> no I intend I used cd live and I've got to look for a repository where there was ksniffer
[12:29] <Tm_T> {slacky}: !
[12:30] <{slacky}> DVD has more space :), but they are just questions... I know ksniffer is very very young and not so usable
[12:30] <{slacky}> Tm_T: hello
[12:31] <{slacky}> Riddell: I tryed to look for ksniffer into the standard repository and it was not there, but I hope to fix more bug possible, add some feature to release 0.2 :)
[12:32] <Riddell> {slacky}: it's in the universe repository
[12:32] <{slacky}> Riddell: ah ok
[12:32] <Tm_T> {slacky}: what's up
[12:33] <{slacky}> Riddell: have you received my reply email to your email?
[12:35] <Riddell> {slacky}: yes
[12:35] <Riddell> I also have 1877 unanswered e-mails just now though, anything I should answer in it?
[12:36] <{slacky}> Riddell: :)
[12:39] <{slacky}> Riddell: you wrote: You should use XDG menus so it appears in Gnome's menu... just this I need to know... because I use direclty calling kdesu into .desktop file
[12:40] <Riddell> oh aye
[12:41] <Riddell> where is ksniffer in SVN?
[12:41] <Riddell> trunk/playground/network/ksniffer/
[12:41] <{slacky}> yes Riddell
[12:45] <Riddell> {slacky}: http://kubuntu.pastebin.com/394858
[12:45] <Riddell> that's the diff
[12:46] <Riddell> which I can commit if you wish
[12:47] <{slacky}> Riddell: but you removed kdesu
[12:48] <{slacky}> if you remove this
[12:48] <Riddell> and added X-KDE-SubstituteUID=true
[12:48] <{slacky}> ah
[12:48] <Riddell> not sure the details but that's how all KDE does it
[12:48] <{slacky}> mmm
[12:49] <{slacky}> Riddell: if this call "kdesu ksniffer" when I click in the Internet/ksniffer menu ok you can commit it
[12:49] <{slacky}> but I'll try it and commit
[12:49] <{slacky}> thanks
[12:50] <Riddell> it does, honest :)
[12:50] <{slacky}> ok
[12:50] <{slacky}> commit it
[12:52] <Riddell> woo, my first ksniffer commit
[12:52] <{slacky}> :)
[12:54] <{slacky}> Riddell: -kdelnkdir   = $(kde_appsdir)/Internet
[12:54] <{slacky}> Riddell: this will remove KSniffer from Internet menu?
[12:56] <Riddell> Categories=Qt;KDE;Network;  adds it back again in the XDG/freedesktop standard way
[12:56] <Riddell> so it'll appear in gnome and xfce etc
[12:57] <{slacky}> Riddell: and the KDE menu?
[12:58] <Riddell> of course :)
[12:59] <{slacky}> Riddell: I removed KSniffer from the KDE menu, updated my repository, installed changes and it doesn't appear in KDE menu anymore
[12:59] <{slacky}> Riddell: what's wrong?
[12:59] <Riddell> {slacky}: how did you remove it?
[01:00] <Riddell> where is ksniffer.desktop installed?
[01:00] <{slacky}> with the Settings/Menu Editor
[01:01] <Riddell> well if you removed it then it won't come back
[01:01] <Riddell> rm -r ~/.config ~/.local
[01:01] <{slacky}> but I made "make install"
[01:01] <{slacky}> ah I understand
[01:02] <{slacky}> you put it into the gnome menu that KDE look for it into the Gnome menu
[01:02] <{slacky}> sigh
[01:02] <{slacky}> I don't like this
[01:03] <Riddell> no, it's not in the gnome menu, it's in the freedesktop XDG menu rather than the legacy KDE menu
[01:03] <Riddell> all modern KDE apps do the same
[01:03] <Riddell> ls /usr/share/applications/kde to see them all
[01:04] <{slacky}> mmm ok
[01:04] <{slacky}> I've seen it
[01:12] <{slacky}> good night Riddell
[01:50] <Mez> hows things going
[01:50] <Riddell> compiling kde 3.5 beta 2
[01:50] <Tm_T> :o
[01:50] <Riddell> kdepim is doing evil things and not linking to qt
[01:51] <Mez> sounds fun
[01:51] <Tm_T> Riddell: forget it, I don't need it anyway (I compile it myself all the time ;p)
[01:51] <Mez> whats the updates from beta1
[01:51] <Riddell> Mez: how do you mean?
[01:51] <Riddell> Tm_T: hmm
[01:51] <Riddell> tempting
[01:51] <Tm_T> haha
[01:51] <Mez> what changes have there been from kdebeta1 -> kde 2.5 beta1
[01:52] <Mez> what changes have there been from kde3.5beta1 -> kde 3.5 beta2 *
[01:52] <Riddell> Mez: no idea
[01:57] <Tm_T> Riddell: I think I might "lend" some cpu time, can I help compiling packages?
[01:57] <Tm_T> I would like to try do some :)
[01:59] <Riddell> Tm_T: https://wiki.ubuntu.com/KDE35Packages
[01:59] <Tm_T> Riddell: doing it atm
[01:59] <Riddell> http://kubuntu.org/~jr/kde35beta2/
[02:00] <Riddell> give kdeadmin a shot
[02:00] <Tm_T> :)
[02:09] <Tm_T> hmh, this https://wiki.ubuntu.com/DebootstrapChroot is taking longer than I expected
[02:11] <Tm_T> hmm, maybe I will install kubuntu to my secondary workstation and start use it as packagefactory :p
[02:12] <Riddell> Tm_T: it's a long download
[02:12] <Tm_T> Riddell: looks like it
[02:12] <Tm_T> doesn't matter, can't sleep anyway
[02:12] <Riddell> Tm_T: yesterday it just sat there and hung doing nothing forever, killing it and restarting it got it going but there's always some pause at the start
[02:12] <Tm_T> :)
[02:12] <Riddell> Tm_T: is it downloading lots of stuff or just sitting there?
[02:12] <Tm_T> downloading
[02:13] <Tm_T> ah, done
[02:13] <Tm_T> next step ->
[02:13] <Tm_T> I: Base system installed successfully.
[02:13] <Tm_T> good to know :p
[02:14] <Riddell> cool
[02:14] <Riddell> I don't bother with the dchroot stuff
[02:14] <Tm_T> :)
[02:14] <Riddell> I just do plain chroot and work as root
[02:15] <Tm_T> hmm
[02:15] <Tm_T> og no
[02:15] <Tm_T> oh
[02:15] <Riddell> ?
[02:16] <Tm_T> hmm, nothing actually, got gpg errors.. ofcourse, I'm jsut installing gnugpg :p
[02:16] <Tm_T> -g
[02:17] <Tm_T> ok, I really need some food ->
[02:17] <Riddell> I ignore those
[02:17] <Riddell> but installing gpg is the other way
[02:18] <Tm_T> :)
[02:18] <Tm_T> food ->
[02:23] <Riddell> verwilst: I got kdenetwork done using your packages thanks
[02:33] <Tm_T> hmh
[02:33] <Tm_T> there's something strange in DebootstrapChroot guide
[02:34] <Riddell> Tm_T: what's that?
[02:34] <Tm_T> Next, we have to install sudo package to be able to use it being in chroot:
[02:34] <Riddell> Tm_T: that's only if you use dchroot
[02:34] <Riddell> which I don't
[02:34] <Tm_T> ok
[02:34] <Riddell> feel free to note that on the wiki
[02:35] <Riddell> I wrote that page and someone did a not very great job of changing it to dchroot
[02:35] <Tm_T> but, strange thing is: sudo apt-get install sudo
[02:35] <Riddell> yeah :)
[02:35] <Tm_T> err, what's that?!
[02:35] <Tm_T> Riddell: ok, so what's your way?
[02:36] <Riddell> yeah baby, kdepim is mine
[02:36] <Tm_T> :)
[02:36] <Tm_T> keep it, I don't wan't it anyway
[02:36] <Tm_T> ;)
[02:36] <Tm_T> Riddell: is there "your version" of that guide somewhere?
[02:36] <Riddell> Tm_T: don't use dchroot, just sudo chroot /var/foo
[02:36] <Tm_T> ok
[02:36] <Riddell> revert the changes whoever made to it :)
[02:38] <Tm_T> hm?
[02:39] <Tm_T> Riddell: ok, I think I'd do better if I try to get my head straight and do it again with better luck :p
[02:39] <Tm_T> I'm tired, in drugs an in pains
[02:39] <Tm_T> not that good combination imho
[02:39] <Riddell> the difference is just that dchroot dose cleverness to make you chroot as the same user, normal chroot doesn't
[02:40] <Riddell> I've never seen any need for dchroot
[02:41] <Tm_T> :)
[02:44] <Tm_T> Riddell: so what you're saying, "your way" is otherwise similar but you don't do those password etc hassles ?
[02:44] <Riddell> exactly
[02:45] <Tm_T> ok
[02:45] <Tm_T> make things easier =)
[02:45] <Tm_T> I'm root anyway
[02:46] <Tm_T> I think there's something really wrong in that guide
[02:47] <Riddell> please do fix it :)
[02:47] <Tm_T> well, I don't know what is the right way
[02:47] <Tm_T> I just have feeling that there's errors
[02:48] <Tm_T> like that fstab thing, should I modify my normal fstab or the one "in" chroot
[02:48] <Tm_T> I don't think that first option is correct
[02:48] <Tm_T> but that's what is that guide saying
[02:49] <Riddell> ?
[02:49] <Riddell> don't touch fstab
[02:49] <Tm_T> I won't
[02:49] <Riddell> oh I see
[02:50] <Riddell> well if you want to access your /home from within the chroot you can but again it's not worth the hassle
[02:50] <Tm_T> yup
[02:50] <Tm_T> so no fstab thing or mounting...
[02:50] <Riddell> no
[02:51] <Tm_T> next step then
[02:52] <Tm_T> ok, now I give up, my irssi have nice waves...
[02:52] <Tm_T> staring the ceiling ->
[06:33] <freeflying> Riddell : are you here
[06:36] <Tm_T> he's spirit remains with us
[06:38] <freeflying> :)
[09:20] <Tm_T> his?
[09:20] <Tm_T> anyway
[12:56] <pef> hello
[12:56] <pef> can I work on this bug ? https://launchpad.net/distros/ubuntu/+sources/qtparted/+bug/3212
[01:35] <Riddell> pef: yes please
[01:35] <Riddell> pef: dapper isn't open yet as far as I know but it should be soon enough
[01:35] <Riddell> all new launchpad dapper that is
[01:36] <pef> Riddell: ok :) since how many time kde apps uses unsermake ?
[01:39] <Tm_T> hmm, "switch user" doesn't seem to work
[01:39] <Riddell> pef: for how long?  over 2 years
[01:40] <Riddell> but it's not needed unless you do KDE 4
[01:41] <pef> Riddell: Do you think I should switch from debhelper to cdbs for qtparted ?
[01:41] <Riddell> pef: no, keep as close as possible to debian so it's easier for them to adopt back
[01:41] <Riddell> and e-mail the debain maintainer once it's in ubuntu
[01:42] <pef> Riddell: isn't this process automatic by utnubu project ?
[01:43] <Riddell> pef: possibly I'm not sure, but it's still polite to talk about it with the debian maintainer
[01:44] <pef> Riddell: ok, will do it
[01:45] <Riddell> oh and check it isn't already in debian of course
[01:47] <pef> Riddell: the 0.4.5 isn't present, only <IP_ADDRESS>
[01:49] <Riddell> ok, so grab the debian latest and start working from that since I don't think there's and ubuntu changes to the package
[01:49] <Riddell> s/and/any/
[01:50] <pef> Riddell: why not working directly to the most recent release ? (0.4.5) as requested by the bug report
[01:53] <Riddell> I ment for the debian packaging
[01:53] <Riddell> use debian's latest packaging and throw that onto the latest qtparted
[01:53] <Riddell> and voila
[01:53] <pef> oh ok :)
[01:54] <pef> Riddell: but I will lose debian/changelog entries made for Ubuntu
[01:54] <Riddell> hmm, yes just saw that
[01:55] <Riddell> however the changelog says it's in sync with debian for everything else so you just need to merge the changelogs
[01:56] <Riddell> 'changed "su-to-root" to "gksudo"'  hum
[01:56] <Riddell> Exec=/usr/bin/gksudo /usr/sbin/qtparted  eek!
[01:56] <Riddell> evilness
[01:56] <\sh> who is freeflying
[01:57] <\sh> (zhengpeng-hou)
[01:57] <\sh> ?
[01:57] <Riddell> \sh: nice chinese dude who's been in here a few times the last couple of days
[01:57] <\sh> Riddell: k..for approving
[01:58] <Riddell> \sh: dunno, he says he'll update scim and package skim so he sounds cool, and I guess we can unapprove him if he disappears off the internet
[01:58] <pef> Riddell: will take care of all that :)
[01:58] <\sh> Riddell: sure...approved him
[01:58] <Riddell> pef: use kdesu or X-KDE-SubstituteUID=true
[01:58] <\sh> kdesu should be the right answer to qtparted ;)
[01:58] <pef> Riddell: I know, same stuff as kvpnc ;)
[01:59] <\sh> Riddell: I'll start to package and test new python-qt/kde3 stuff tomorrow
[01:59] <Riddell> pef: make sure its using whatever our latest libparted is
[02:00] <Riddell> \sh: there's a new python-qt?
[02:00] <\sh> Riddell: yepp..
[02:00] <\sh> Riddell: and a new pre-release snapshot of pykde
[02:00] <Riddell> fun
[02:01] <\sh> Riddell: but...any possibility to re-enable python-kde3 building in kdebindings? and just dropping python-dcop stuff?
[02:01] <\sh> Riddell: I could wait for as well for the next release of pykde...for having kde>=3.4.2/kde3.5 support
[02:02] <\sh> Riddell: upstream wise ;)
[02:02] <pef> Riddell: autotools-dev stuff into debian diff.gz, erf :/
[02:03] <Riddell> \sh: that's possible but is the version in kdebindings always the latest pykde?
[02:03] <Riddell> pef: happens to the best of us
[02:04] <pef> :]
[02:04] <Riddell> \sh: why drop python-dcop?
[02:04] <\sh> Riddell: well it should be, but I don't know if kde upstream do take care about pykde stuff...I would like to see it to be taken over by kde upstream and maintaining by kde upstream as well
[02:05] <\sh> Riddell: cause python-dcop (as I read it in the configure.{ac/in} the last time in 3.4.2) has only python2.2/2.3 build-deps possible and not python2.4
[02:06] <\sh> Riddell: so if you enable python-kde3 at the same time as python-dcop it clashes with the python versions...python-kde3 can't use 2.2 anymore
[02:07] <\sh> Riddell: it's a mess, that's why python-kde3 is not enabled in kdebindings somehow
[02:07] <Riddell> python-dcop depends on python 2.4
[02:07] <Riddell> of course that doesn't mean it works
[02:07] <Riddell> jpatrick: who's that then?
[02:08] <jpatrick> Riddell: He was on Kubuntu Forums
[02:08] <jpatrick> Then he IMed me for a while
[02:08] <\sh> Riddell: ok..I'll test with 3.4.3 tomorrow.if I can enable python-kde3 and python-dcop together, fine...so we have to make sure, latest python-kde3 is in kdesvn
[02:09] <Riddell> \sh: kdebindings 3.5 beta 2 if it's any help http://kubuntu.org/~jr/kde35beta2/kdebindings-3.4.92.tar.bz2
[02:10] <\sh> Riddell: I'll do two test cases...one with stable breezy kde and with kde3.5beta2...I mean it won't make so much difference, cause python-kde3 will not support 3.4.2/3.4.3/>=3.5 until next official release+1
[02:11] <jpatrick> Riddell: Apparently he's supporting Linux in China...
[02:13] <Riddell> \sh: if python-kde is always behind kde it doesn't make sense to use kdebindings which is released with kde
[02:13] <Riddell> jpatrick: nice guy or nutty hanger on?
[02:14] <Riddell> \sh: chroot is your friend
[02:14] <Riddell> Lathiat: awooga
[02:14] <Riddell> jpatrick: he's on the channel just now so be nice in what you say :)
[02:14] <jpatrick> Riddell: :)
[02:14] <jpatrick> Riddell: nice guy overall
[02:15] <\sh> Riddell: well...yes chroot...but my install is a complete mess ;)
[02:15] <Riddell> excellent, lets approve him for kubuntu team then
[02:15] <\sh> Riddell: that's why I want to have it maintained by kde upstream...
[02:15] <jpatrick> Riddell: first time he spoke to a foreigner
[02:15] <Riddell> jpatrick: ooh, exciting
[02:15] <\sh> Riddell: and everything is somehow slow
[02:16] <\sh> regarding my new install of the other laptop..
[02:16] <jpatrick> Riddell: Have you seen this: http://kubuntuforums.net/index.php?topic=650.0 ?
[02:16] <Riddell> I like how people have whole blogs dedicated to kubuntu
[02:18] <Riddell> jpatrick: nope
[02:19] <pef> Riddell: can you try to build qtparted-0.4.5 from upstream tarball ?http://prdownloads.sourceforge.net/qtparted/qtparted-0.4.5.tar.bz2?download I have a fatal error running unsermake
[02:20] <Riddell> pef: don't use unsermake then
[02:20] <Riddell> uninstall unsermake
[02:21] <pef> Riddell: and add it to Conflicts ?
[02:21] <Riddell> pef: yeah
[02:22] <Riddell> then start again with a fresh buildtree, mixing unsermake and automake can mess things up
[02:31] <pef> Riddell: mm some files were generated by unsermake, so I can't switch so easily, I thing I have to write a patch to delete unsermake from shell scripts used to generate Makefile.*
[02:44] <Riddell> oh, qtparted does use unsermake
[02:45] <Riddell> interesting, must be the first program to do that by default
[02:45] <Riddell> INSTALL file doesn't mention it, I wonder if that was done by mistake then
[02:50] <Riddell> but it doesn't compile
[02:51] <pef> http://sourceforge.net/forum/forum.php?thread_id=1338759&forum_id=247293
[02:51] <pef> maybe corrected in the cvs
[02:54] <freeflying> hi you all
[02:55] <Riddell> pef: it compiles fine if not using unsermae
[02:55] <Riddell> unsermake
[02:55] <Riddell> pef: best thing would be to run  make -f admin/Makefile.common  on the origional source then recreate the .orig
[02:55] <Riddell> not that in the changelog and don't use unsermake
[02:55] <Riddell> and tell upstream of their mistake
[02:55] <Riddell> afternoon freeflying
[02:56] <pef> Riddell: ok, thank you :)
[02:56] <freeflying> inow i want to build scim-qtimm for breezy
[02:56] <freeflying> but it seemed the qt should be patch
[02:57] <freeflying> but the qt in breezy doesn't patched
[02:58] <Riddell> freeflying: we can patch it though for dapper
[02:59] <freeflying> then i shall patch it for myself use own
[03:02] <Riddell> freeflying: please do, let us know if it all works and we'll get the patch into kubuntu
[05:01] <pef> Riddell: can I use cdbs patch system on a debhelper rules ?
[05:02] <Riddell> pef: I doubt it, it's not hard to add it to debhelper
[05:02] <Riddell> just need to find a package that still uses it and copy
[05:03] <Riddell> koffice
[05:03] <Riddell> copy the # Apply Debian specific patches in debian/rules (and the unapply one too)
[05:04] <pef> mm
[05:05] <pef> I don't have some targets
[05:05] <pef> like config.status: foo
[05:09] <Riddell> ignore it then :)
[05:47] <pef> Riddell: what's important with dpatch ? patch before building and unpatch before cleaning ?
[05:53] <Riddell> pef: sounds about right
[05:54] <pef> Riddell: I don't fully understand why the dpatch man add multiples commands to call dpatch and multiples dpatch specific targets ?
[05:57] <Riddell> I've never used dpatch
[05:57] <Riddell> qt does
[06:12] <pef> Riddell: can you review my package later ?
[06:17] <Riddell> pef: of course
[07:03] <pef> Riddell: http://revu.tauware.de/details.py?upid=794
[08:04] <pef> have to go, bye !


[05:44] <wxl> looks like the builders are unhappy. only one amd64 machine???
[05:46] <wgrant> Fixing
[06:00] <wxl> oh that looks better. thanks wgrant :)
[14:43] <rbasak> Is there any way to retrieve the branch tip of an MP that has been force-pushed over, so I can compare what I reviewed before with what is there now?
[14:43] <rbasak> Usually I can use my local reflog against the remote branch, but today I see that on this particular MP I reviewed from cgit and never had it locally.
[17:27] <kyrofa> Is there an existing script that will sync all packages from one PPA to another? I know about copy-package, I guess I'm looking for a copy-package --all option, syncing from one PPA to another
[17:30] <cjwatson> rbasak: I think not if you didn't make a comment when you did your initial review, sorry.  It's something I'd like to improve at some point
[17:30] <cjwatson> kyrofa: Not that I know of
[17:30] <kyrofa> cjwatson, does the API give me a way to list packages in a given PPA?
[17:37] <cjwatson> kyrofa: https://launchpad.net/+apidoc/devel.html#archive-getPublishedSources
[17:38] <kyrofa> Thanks cjwatson, seeing that throughout these scripts, might be able to add the feature I want. I don't suppose there'd be any interest in my proposing that back upstream?
[17:47] <RikMills> kyrofa: kubuntu has this: https://git.launchpad.net/ka/tree/kopypackages2
[17:47] <kyrofa> RikMills, thanks for that, looks like what I'm wanting, I'll take it for a spin
[17:48] <RikMills> kyrofa: actually, correct branch: https://git.launchpad.net/ka/tree/kopypackages2?h=2.3
[17:49] <RikMills> that imports a fucntion from the rest of our tooling to pretty print error I think, but most is just LP api IIRC
[17:51] <kyrofa> RikMills, not 3.0 yet, eh?
[17:51] <rbasak> No problem, thanks
[17:52] <rbasak> I did make a comment in my initial review, FWIW, if that matters?
[17:52] <rbasak> Inline comments too
[17:52] <rbasak> I just hadn't fetched the branch locally
[17:53] <RikMills> kyrofa: nope. that 3.0 is very much work in progress stuff I am told by the guy who maintains our automation
[17:54] <kyrofa> Heh. Thanks RikMills, this is excellent
[17:54] <cjwatson> kyrofa: I don't know - I only do ubuntu-archive-tools stuff in passing these days
[18:35] <kyrofa> RikMills, doesn't look like that the -c option does anything in that script
[18:36] <RikMills> kyrofa: I think that is left over from previous implementation


[08:17] <Kon-> Does the Ubuntu kernel make any changes to latency? I've seen a fair number of people comment on how Debian gives them audio skipping while Ubuntu does not
[15:43] <JanC> Kon-: Ubuntu has an optional low-latency kernel, which is used in e.g. Ubuntu Studio
[15:52] <JanC> it should only be relevant for audio production or such, I think, not for just playing some music...


[02:14] <micahg> is it a soyuz bug if the build score is based on all the entries in teh changelog and not just the top entry?
[02:16] <wgrant> micahg: No. It's based on the Urgency field in the changes file.
[02:16] <wgrant> micahg: That should be the maximum urgency from all included changelog entries, I believe.
[02:17] <wgrant> But regardless it is not a Soyuz bug.
[02:17] <micahg> wgrant: ah, ok, so it's not a bug
[02:18]  * micahg will just skip the -v on the PPA next time then
[06:37] <spiv> Hmm.  I just did 'resubmit proposal' on a merge proposal without realising that it would have been better (in terms of the email produced at least) to update the description *first*.
[06:37] <spiv> I was expecting it to prompt me to update it, maybe show me a form along the lines of the original form used to file the MP.
[06:41] <StevenK> spiv: Yes, that would be nice.
[06:41] <StevenK> spiv: I've been tripped up with that myself
[07:45] <paddy_> With the ssh key it says paddy@paddy-desktop should it be <launchpad<EMAIL_ADDRESS>bzr is not working for me
[07:49] <spiv> paddy_: the name in the key doesn't matter at all
[07:49] <spiv> paddy_: what does 'ssh -v -l <launchpad username> bazaar.launchpad.net' output?  (pastebin it)
[07:51] <paddy_> http://pastebin.com/8K7xrsQn spiv
[07:55] <spiv> paddy_: "#
[07:55] <spiv> Agent admitted failure to sign using the key."
[07:56] <spiv> That's your problem.
[07:56] <spiv> You probably need to run 'ssh-add' or something like that.
[07:59] <paddy_> spiv that worked, thanks
[09:28] <neeraj> Hi, while uploading my package in ppa, I am getting this error msg again and again or two/six packages which I am packaging. Rejected Unable to find sugar-presence-service-0.90_0.90.1.orig.tar.bz2 in upload or distribution. Files specified in DSC are broken or missing, skipping package unpack verification.
[09:28] <neeraj> anyhelp?
[09:28] <bigjools> neeraj: it means you're not uploading the .orig file and it can't find the one you're referencing in the dsc file in the distro or your ppa
[09:30] <neeraj> but the orig file is present in the folder alongside dsc file named sugar-presence-service-0.90_0.90.1.orig.tar.bz2
[09:31] <neeraj>  debuild -S command asked me for it. So I am sure while building the package this orig file was used.
[09:33] <wgrant> neeraj: debuild uses it, but it won't upload it unless you give it the '-sa' option.
[09:37] <neeraj> I can't believe how on earth I didn't tried -sa and keep using -s flag. Wasted hours trying to solve this error. :(
[09:37] <neeraj> wgrant: bigjools thanks :)
[09:43] <neeraj> with -sa flag , I got this msg Source/binary (i.e. mixed) uploads are not allowed.
[09:43] <neeraj> Rejected ^
[09:46] <wgrant> neeraj: You need both -S and -sa
[09:53] <neeraj> Ohh.. wgrant thanks gain. So whenever I will use .orig file while building I have to use both -S and -sa and If I don't then only -S will work.?
[09:54] <glen> hi. can i somehow search for translations for my language across any projects?
[09:55] <glen> i mean i want to know how "somesentence" is translated in rosetta, as i know launchpad has hundreds or project translations
[09:55] <glen> yet i don't have myself a project so it would suggest me
[09:56] <henninge> glen: I am sorry, we don't have that option.
[09:57] <henninge> Also, even if you had a project, you would not see them atm because global suggestions have been deactivated to avoid page timeouts.
[10:18] <glen> yet it does sometimes suggest me translations from other projects, that is disabled now? or it just limits the result by some range?
[12:06] <neeraj> is there a anyway so that we can reduce build time on launchpad. I don't get much time for packaging and can't move ahead without verifying initial packages.
[12:07] <neeraj> *?
[12:07] <wgrant> neeraj: Have you tried using pbuilder locally?
[12:07] <wgrant> You should be testing on your own machine before you upload to Launchpad.
[12:08] <neeraj> I have tested on my own machine but build was failing on launchpad due to some error.
[12:08] <wgrant> Tested with pbuilder, or something else?
[12:09] <wgrant> pbuilder and sbuild ensure a clean build environment, so you can be sure you've got all the right build dependencies set.
[12:09] <neeraj> cbds version unmet denpendency. I build the package using debuild and installed the deb file.
[12:09] <neeraj> Ok reading about pbuilder
[14:47] <berco> Hi
[14:47] <cake_> i cant create a test project, i get an error which says i should reload the page after some time. now after the reload it tells me that url is taken BUT im 100% sure its not, ive picked serveral loong random ones
[14:47] <ogra_ac> hey, any LOSA around ?
[14:48] <berco> Can anyone help me enable "natty" on our PPA?
[14:48] <ogra_ac> berco (TI) has a prob with the TI ppa
[14:48]  * ogra_ac would expect natty to happen automatically there, but apparently it doesnt
[14:50] <berco> TI PPA @ https://launchpad.net/~tiomap-dev
[14:50] <bigjools> berco: just upload to natty
[14:50] <zyga> are natty chroots for package buildin expect to fail?
[14:50] <berco> bigjools: nothing needed? I remember my package got rejected last week
[14:51] <bigjools> berco: I was not around last week, what was the rejection?
[14:51] <bigjools> AFAIK it should work
[14:51] <berco> bigjools: I need to try again as I deleted the email...
[14:52] <bigjools> ok let me know
[14:54] <berco> bigjools: one other question I had last week was if I can list the distributions that I support in my changelog or if only one is allowed.
[14:54] <berco> for instance, is this allowed in the debian/changelog: titiler-memmgr (0.24.11-0ubuntu1) maverick natty; urgency=low
[14:55] <bigjools> berco: no, LP only supports a single target series
[14:55] <bigjools> but once it's built you can copy it between series if you don't need to rebuild
[14:55] <bigjools> otherwise you need to upload different versions to different series
[14:56] <berco> ok, thanks
[14:56] <bigjools> let me know if this FAQ explains it adequately: https://answers.launchpad.net/soyuz/+faq/1371
[14:59] <berco> bigjools: I think the FAQ is clear enough, maybe just need to add "distro series" in the title as when I was looking at the debian policy they call this field "distribution".
[15:00] <bigjools> berco: ok thanks for the feedback
[15:00] <berco> bigjools: np
[15:00] <bigjools> fixed :)
[15:43] <berco> bigjools: looks like I have an issue uploading to the PPA. Might be related to our internal network, I'm checking
[15:44] <bigjools> berco: what happens?
[15:46] <berco> bigjools: when I do the dput, I have "write failed: Broken pipe" message
[15:46] <bigjools> berco: ftp or sftp?
[15:47] <berco> bigjools: sftp
[15:47] <bigjools> berco: are you using maverick?
[15:47] <berco> bigjools: I'm still on Lucid on my PC machine
[15:47] <berco> can it explain?
[15:47] <bigjools> ok that should be ok - there's a known problem with the maverick dput over sftp
[15:48] <bigjools> have you used sftp before?
[15:48] <bigjools> and is your public key on your account and your account referenced in the "login" dput conf?
[15:48] <berco> bigjools: yes, all the time when uploading to our PPA on Launchpad
[15:49] <berco> bigjools: however, this is first time I try on this particular PPA (ti-omap-private)
[15:50] <bigjools> not sure what's up then
[15:50] <berco> bigjools: I just verified my dput.cf file and it has my login
[15:50] <berco> what about the public key, I forgot what I need to check here
[15:50] <berco> ?
[15:50] <bigjools> the service is up and I can ssh it (although it correctly says I can't get a shell)
[15:51] <bigjools> your ssh key needs to be associated with the account you're sftp-ing to
[15:53] <berco> bigjools: can you help me verify this latter item please?
[15:54] <berco> I'mnot confident I have it right
[15:54] <bigjools> berco: you can do it yourself, just visit the account page in Launchpad
[15:54] <berco> bigjools: on my account I can see the PPA subscription
[15:54] <berco> bigjools: so is that mean it's all good?
[15:55] <bigjools> there's a section mid-right of the page "SSH keys"
[15:55] <berco> yep, I see this section
[15:55] <bigjools> https://edge.launchpad.net/people/+me/+sshkeys
[15:55] <bigjools> should show the keys
[15:55] <bigjools> make sure the account is the same as the one in the "login =" section of the dput.cf you're using
[16:02] <berco> bigjools: the information shown at https://edge.launchpad.net/people/+me/+sshkeys is exactly what I have in my ~/.ssh/id_rsa.pub
[16:07] <bigjools> berco: ok, what happens if you ssh<EMAIL_ADDRESS>?
[16:24] <maxb> Incidentally I think I've figured out the dput hang over sftp on maverick - I'll have a go at fixing bzrlib tonight
[16:31] <berco> bigjools: ssh<EMAIL_ADDRESS>[16:31] <berco> No shells on this server.
[16:31] <berco> Connection to ppa.launchpad.net closed.
[16:32] <berco> bigjools: sorry for the delay but I just tried on my colleague's machine and it worked. So I will try to restart my PC.
[16:33]  * berco going for a reboot
[16:56] <berco> bigjools: I've been able to upload. Package has been accepted on launchpad but my dput command never returns on my PC. I wonder if there's an issue with corscrew as I'm behind a firewall and killing it will allow the dput command to return
[17:04] <bigjools> berco: there's a known regression with sftp from maverick where it hangs at the end
[17:04] <bigjools> other than that I don't know of any issues
[17:04] <bigjools> (sorry was OTP)
[17:05] <berco> bigjools: ok, thanks for the update. So looks like everything looks as good as it can be :)
[17:05] <berco> bigjools: thanks for your precious help
[17:06] <bigjools> berco: no worries, glad to help
[19:02] <lifeless> fta: hi
[19:02] <fta> lifeless, hi
[19:02] <lifeless> when the dashboard script crashes
[19:02] <lifeless> what does it look like
[19:03] <lifeless> I mean, how can I tell if I've made it fall down go boom
[19:03] <fta> i get a py stack with an html page containing an oops
[19:03] <fta> let me see if i still have some logs
[19:03] <lifeless> on the console or in a log file or in one of the html outputs ?
[19:04] <lifeless> fta: I'm running it here to qa this patch
[19:04] <lifeless> fta: I'm up to batch size 50 without error
[19:04] <fta> good
[19:05] <fta> (if it lasts)
[19:05] <lifeless> well, its a code change to be more sensible
[19:06] <fta> lifeless, here is one: http://paste.ubuntu.com/528850/
[19:07] <lifeless> fta: so thats shown on the console that your shell script is running in ?
[19:07] <fta> yes, the py script is called by a shell script (several times as mentioned in the bug) itself run by cron
[19:08] <lifeless> ok
[19:08] <lifeless> thats what I was asking - where to look for errors :)
[19:08] <fta> i get errors in my mailbox
[19:08] <lifeless> (I know what the errors look like :P)
[19:08] <fta> i said in the bug nothing is expected on stdout
[19:08] <fta> except py or lp errors
[19:08] <paddy_> how do i unassign my self to a bug?
[19:09] <lifeless> paddy_: click the yellow icon to the right of your name in the table at the time - in the 'assignee' column. Then click 'unassign me'.
[19:09] <lifeless> fta: 100 works.
[19:09] <fta> lifeless, \o/
[19:13] <fta> try the xorg-edgers ppa too, it's quite big: http://sarvatt.com/xorg-edgers/
[19:13] <lifeless> 200 works
[19:14] <lifeless> so how does that look ? '$BIN $OPTS xorg-edgers' ?
[19:14] <fta> view source shows: <!-- args line: -g -r xorg-edgers/ppa ubuntu-x-swat/x-updates -->
[19:15] <lifeless> trying
[19:16] <fta> i don't know if anyone else is use it
[19:17] <fta> also, you should disable the cache, otherwise, there's not much to poll and you'll never hit your limit
[19:18] <lifeless> ahh
[19:18] <lifeless> 200 on xorg broke
[19:18] <lifeless> oh
[19:18] <fta> maybe for mine too (if you drop the cache)
[19:18] <lifeless> deploy
[19:19] <lifeless> HTTP Error 503: Service Unavailable
[19:19] <lifeless> new code landing on qastaging
[19:19] <fta> o
[19:19] <fta> h
[19:21] <lifeless> where does the cache get stored ?
[19:22] <lifeless> found it
[19:22] <lifeless> running a full run, all the ppas including xorg-edgers, empty cache
[19:31] <lifeless> ok the xorg-edgers one died with the 200 size query
[19:31] <lifeless> fta: however I think it will be tolerable for you for a while, and we can come back later and make it faster still.
[19:36] <lifeless> fta: its in rev 11888
[19:37] <lifeless> fta: so when launchpad.net shows that in the bottom right of the page, you should get a performance boost
[19:37] <fta> lifeless, ok, excellent. thanks!
[19:37] <fta> lifeless, which chunk size do you recommend?
[19:38] <lifeless> fta: the largest that works reliably :)
[19:38] <lifeless> I don't know what that figure will be
[22:07] <lifeless> fta: we're deploying the fix now
[22:07] <lifeless> fta: if you're around in a bit it should be usable
[22:22] <paultag> LP is ooping on me a whole lot, is this already been reported?
[22:23] <paultag> If not, I've been able to have it OOPS on me lots. Here's the error codes ( so far ) -- http://pastebin.com/JvmF6fwP
[22:23] <cody-somerville> paultag, Reported. I'm told the're working to fix it now.
[22:24] <paultag> cody-somerville, awesome. Thanks so much :)
[22:25] <lifeless> fixed
[22:26] <lifeless> fta: please be trying the slow api again now
[22:28] <fta> lifeless, ok. excellent. moved to batches of 50. i'll let you know.
[22:56] <lifeless> fta: how did it go ?
[22:58] <fta> lifeless, seems ok.
[22:59] <lifeless> \o/
[23:02] <barry> lifeless: https://launchpad.net/~pythoneers/+archive/py27stack4/+packages
[23:04] <lifeless> barry: large ppa ?
[23:05] <barry> it does have a lot of packages.  i was actually trying to cull them, but kept getting the oops
[23:05] <lifeless> barry: when did you start getting the oops
[23:05] <barry> an hour or so ago
[23:05] <lifeless> and it was working before that ?
[23:06] <lifeless> when did you last see it work ?
[23:06] <barry> lifeless: yesterday
[23:06] <lifeless> ok
[23:06] <lifeless> so its probably a regression in 11888
[23:06] <lifeless> hmm
[23:06] <lifeless> grumble.
[23:06] <barry> dang
[23:07] <lifeless> though https://bugs.edge.launchpad.net/soyuz/+bug/672371
[23:08] <lifeless> when the oops comes through I'll have a peek
[23:08] <lifeless> till then, lunch
[23:08] <barry> lifeless: thanks.  i'' be breaking for dinner soon, and i'll subscribe to that bug