[12:48] <njs> Is this the right place to ask general questions about packaging?
[12:48] <njs> I have a software project.  As a convenience for users, we distribute binaries of new versions, until distros have a chance to pick it up.  So our unofficial sid deb has version "<release number>-0.1", to avoid bumping into the official package.  What version do I use for a package built for, say, dapper?
[12:49] <bluefoxicy> 0.1ubuntu0 I think
[12:53] <crimsun> that's fine. What's the holdup on getting it into Sid?
[12:55] <lifeless> njs: the usual convention is to put the packages for different distribution releases (sid/dapper/etch etc) into different directories
[12:56] <lifeless> njs: theres no need for a different version number between the different builds unless there is an actual change.
[12:58] <Laser_away> bddebian: ah, stink!
[12:59] <bddebian> I stink?
[01:01] <njs> lifeless: hrm.  seems confusing.
[01:04] <Laser_away> bddebian: no, about Scilab
[01:04] <bddebian> I know, I was kidding :-)
[01:05] <LaserJock> bddebian: debian-science is thinking of setting up a unoffical repo for this sort of thing
[01:06] <tritium> LaserJock: what sort of thing
[01:06] <tritium> ?
[01:06] <LaserJock> licensing problems and experimental packages
[01:06] <tritium> oh
[01:07] <LaserJock> I'm just not sure what to do
[01:07] <LaserJock> scientists need to get with it when it comes to licensing their software
[01:07] <njs> lifeless: wouldn't that break upgrading from dapper to edgy, say?
[01:10] <phanatic> njs: if you need to rebould the package (newer dependencies), then you bump the version anyway (from 0.1 to 0.2 for example)
[01:11] <njs> phanatic: okay, right.  so what if you have to rebuild it for older dependencies? :-)
[01:14] <phanatic> you do the same thing... there is no special versioning for dapper or edgy... just version bumps. (and X-ubuntuX when it gets modified)
[01:34] <hub> w00t
[01:34] <hub> hugin released, the license is fixed
[01:34] <hub> I should be able to upload it this time
[01:44] <LaserJock> anybody know what the policy is for getting stuff into Debian's non-free is?
[01:46] <LaserJock> is it the same as Multiverse?
[01:50] <slomo> LaserJock: http://www.debian.org/doc/debian-policy/ch-archive.html#s-non-free
[01:51] <LaserJock> ah, I guess I should've figured it would be in the Debian Policy
[03:08] <LaserJock> crimsun: how do you ignore joins and parts?
[03:08] <bddebian> ?
[03:08] <LaserJock> I was thinking of taking a dive into #ubuntu for a few minutes
[03:09] <crimsun> /ignore #channel JOINS PARTS
[03:09] <LaserJock> but I have to turn of the joins and parts or I get a more of a headache then usual
[03:09] <lprofil> good evening
[03:09] <crimsun> lprofil: hi. What's the issue with libfaac-dev?
[03:10] <LaserJock> lprofil: it's not so much annoying as off topic
[03:10] <lprofil> is anybody of you able to install libfaac-dev ?
[03:10] <crimsun> yes, libfaac-dev installs fine for me on Dapper and Edgy.
[03:10] <lprofil> damn
[03:10] <lprofil> it says:
[03:10] <lprofil> The following packages have unmet dependencies:
[03:10] <lprofil>   libfaac-dev: Depends: libmp4-dev but it is not installable
[03:10] <lprofil> E: Broken packages
[03:11] <lprofil> apt-get install -f does not fix it
[03:11] <crimsun> you're not using Ubuntu's libfaac-dev, then.
[03:11] <lprofil> any suggestions ?
[03:11] <crimsun> our libfaac-dev has this:
[03:11] <crimsun>   Depends: libmp4v2-dev
[03:11] <lprofil> how do you mean?
[03:11] <crimsun> so you must be using another repo like marillat's.
[03:11] <lprofil> ok
[03:11] <crimsun> ``apt-cache policy libfaac-dev''
[03:12] <lprofil> oha, i didn't know the "policy" option
[03:12] <lprofil> :)
[03:14] <LaserJock> lprofil: was that the problem?
[03:16] <lprofil> yes
[03:16] <lprofil> i do not know yet if it _was_
[03:18] <ajmitch> almost sounds like bug 53834 can be rejected then
[03:18] <Ubugtu> Malone bug 53834 in faac "Broken dependecies when trying to install libfaac" [Untriaged,Needs info]  http://launchpad.net/bugs/53834
[03:19] <crimsun> that's a definite Rejected IME
[03:20] <bddebian> Hey, I'm trying to build this package called axiom, can anyone help me? ;-P
[03:20] <ajmitch> bddebian: no
[03:20] <bddebian> ajmitch: Well I know YOU won't help me :-)
[03:23] <lprofil> what's your prob?
[03:23] <lprofil> ./configure
[03:23] <lprofil> make
[03:23] <lprofil> make install
[03:23] <lprofil> ?
[03:23] <lprofil> or isn't it that trivial?
[03:23] <ajmitch> hehe
[03:23] <lprofil> ;-)
[03:23] <ajmitch> certainly not that trivial
[03:24] <lprofil> tell us
[03:24] <bddebian> lprofil: I'm being a little sarcastic.    It's an algebra package
[03:25] <LaserJock> lprofil: apt-get source axiom
[03:25] <LaserJock> bddebian: hehe
[03:25] <ajmitch> LaserJock: it's been broken for awhile, I believe
[03:25] <bddebian> LaserJock: Sort of but it build-deps xfree86-common and then FTBFSs
[03:26] <ajmitch> only certain people are brave enough to deal with it ;)
[03:26] <LaserJock> so it's broken in Debian as well?
[03:26] <bddebian> I can fix the C generated errors but now it doesn't build a object file.. :-(
[03:26] <bddebian> LaserJock: I think it has to be since it still build deps xfree86-common but I'm not sure
[03:26] <ajmitch> LaserJock: debian bug 376017
[03:26] <Ubugtu> Debian bug 376017 in axiom "Subject: axiom: FTBFS: Obsolete Build-Depends on xfree86-common" [Serious,Open]  http://bugs.debian.org/376017
[03:27] <ajmitch> don't know if the rest of the errors he's seeing show up there
[03:27] <ajmitch> since it won't have been rebuilt for an age
[03:27] <bddebian> Nope
[03:27] <bddebian> I was going to post my findings but I can't figure out the object file thing
[03:28] <bddebian> Of course upstream has been dead since 09 of 2005 :-(
[03:29] <lprofil> sorry to interrupt you but are you trying to compile it from sources ?
[03:29] <LaserJock> some day science packages just make me want to cry
[03:29] <bddebian> lprofil: No, the debian source package
[03:29] <lprofil> under ubuntu?
[03:29] <bddebian> Aye
[03:30] <LaserJock> lprofil: we are the Ubuntu Universe developers here
[03:30] <LaserJock> we are trying to make sure packages in Universe build right
[03:30] <LaserJock> and are as updated and bug free as possible
[03:31] <ajmitch> bddebian: except that you've got your key in the keyring...
[03:34] <bddebian> Having a gpg key does not make me a developer
[03:35] <ajmitch> being trusted enough to have upload rights does
[03:35] <ajmitch> so stop arguing
[03:35] <LaserJock> bddebian: shut up and accept it!
[03:35] <LaserJock> ;-)
[03:35] <bddebian> :-)\
[03:36] <lprofil> i got some trouble adding marillats gpg key
[03:36] <lprofil> gpg: WARNING: unsafe ownership on configuration file `/home/mantikor/.gnupg/gpg.conf'
[03:36] <lprofil> gpg: WARNING: nothing exported
[03:36] <lprofil> gpg: no valid OpenPGP data found.
[03:36] <lprofil> when i type
[03:36] <lprofil>  gpg --export 010908312D230C5F | apt-key add -
[03:37] <ajmitch> why do you want to get packages from marillat's repositories?
[03:37] <LaserJock> lprofil: to be honest, just don't do marillat
[03:37] <lprofil> hmm
[03:37] <ajmitch> they'll break things, as you've seen
[03:37] <lprofil> well, i will try to be a bit more specific with my prob
[03:37] <ajmitch> & then we end up with the bugreports
[03:37] <lprofil> i am trying to compile cinelerra
[03:38] <lprofil> i get this error when i ./configure the cvs sources:
[03:38] <lprofil> libfaac libraries       missing
[03:38] <lprofil> libfaac headers         missing
[03:38] <lprofil> even if i have libfaac installed
[03:38] <ajmitch> and libfaac-dev?
[03:39] <LaserJock> do you have a -dev package?
[03:39] <lprofil> but not libfaac-dev
[03:39] <LaserJock> doh, ajmitch beat me
[03:39] <lprofil> i cannot install libfaac-dev
[03:39] <ajmitch> you couldn't install because you were using marillat repositories, right?
[03:39] <lprofil> no
[03:40] <lprofil> i didn't add them yet due to the gpg problem
[03:40] <ajmitch> what I said, get rid of that marillat repository line, please
[03:40] <lprofil> maybe that saved me from further trouble
[03:40] <lprofil> i didn't add it and won't do so
[03:41] <LaserJock> are you sure?
[03:41] <lprofil> back to the "libfaac-dev: Depends: libmp4-dev but it is not installable" prob
[03:41] <lprofil> yes, sure
[03:41] <LaserJock> did you remove the lines and apt-get update?
[03:41] <ajmitch> because the package in dapper does not depend on libmp4-dev
[03:41] <ajmitch> do you have multiverse enabled for dapper in your sources.list ?
[03:41] <lprofil> i'll do but they didn't affect due to the missing gpg keys
[03:42] <LaserJock> yes it did
[03:42] <lprofil> i will do remove them...
[03:42] <lprofil> i had the prob before
[03:42] <LaserJock> just because it gave you gpg warnings doesn't mean it isn't in your apt cache
[03:42] <lprofil> removed
[03:43] <ajmitch> can you please put the output of 'apt-cache policy libfaac-dev' on pastebin
[03:43] <lprofil> what is pastebin?
[03:44] <lprofil> libfaac-dev:
[03:44] <lprofil>   Installed: (none)
[03:44] <lprofil>   Candidate: 1.24+cvs20060416-0.1
[03:44] <lprofil>   Version table:
[03:44] <lprofil>      1.24+cvs20060416-0.1 0
[03:44] <lprofil>         500 http://www.kiberpipa.org ./ Packages
[03:44] <lprofil>      1.24clean-0ubuntu4 0
[03:44] <lprofil>         500 http://de.archive.ubuntu.com dapper/multiverse Packages
[03:44] <hub> hugin 0.6 is a pain to build on dapper
[03:44] <ajmitch> I see
[03:44] <ajmitch> lprofil: it avoids you flooding the channel like that
[03:44] <lprofil> how do i use it?
[03:44] <ajmitch> please remove/disable the line in sources.list with http://www.kiberpipa.org
[03:45] <LaserJock> lprofil: use http://paste.ubuntu-nl.org
[03:45] <ajmitch> mixing in non-ubuntu repositories is often going to give you problems
[03:45] <lprofil> thanks
[03:46] <lprofil> i erased the lines; did a apt-get update but still have the broken dependecies probs
[03:46] <LaserJock> lprofil: pastebin the problem
[03:47] <Hobbsee> hi all
[03:47] <LaserJock> hi Hobbsee
[03:47] <bddebian> Heya Hobbsee
[03:47] <Hobbsee> LaserJock: bddebian :)
[03:48] <lprofil> put in my name and the message
[03:48] <Hobbsee> oh for goodness sake!
[03:48] <lprofil> how to submit?
[03:49] <lprofil> send button
[03:49] <Hobbsee> bug 49066 is crazy.
[03:49] <Ubugtu> Malone bug 49066 in kdelibs "Dependency errors for kdelibs4c2" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/49066
[03:49] <LaserJock> lprofil: yeah, then give us the URL
[03:49] <crimsun> Hobbsee: for breezy?
[03:49] <lprofil> http://paste.ubuntu-nl.org/18743
[03:49] <Hobbsee> crimsun: i think so
[03:49] <ajmitch> lprofil: right, so that problem is caused by the non-ubuntu libfaac still being on your system
[03:49] <lprofil> aha
[03:50] <crimsun> Hobbsee: oh that's a straight Rejected.
[03:50] <lprofil> how do i link the installed libfaac libaries to my cinelerra config file?
[03:50] <Hobbsee> crimsun: exactly.
[03:50] <Hobbsee> crimsun: what exactly should i say as a rejected message, do you think?
[03:51] <lprofil> is there a possiblity to tell cinelerra that this libaries are already installed?
[03:51] <ajmitch> lprofil: just install libfaac0 & libfaac-dev from dapper
[03:52] <lprofil> i cannot install libfaac-dev
[03:52] <crimsun> Hobbsee: something along the lines of 'kdelibs4c2a is very different to kdelibs4c2, and mixing binaries compiled for different Ubuntu releases often results in these such problems. Please ask ktechlab.org to recompile their source package against Dapper libs.'
[03:52] <Hobbsee> crimsun: thanks :)
[03:53] <LaserJock> lprofil: get rid of the non-ubuntu libfaac and install the Ubuntu one
[03:53] <lprofil> by removing the universe respositories?
[03:55] <LaserJock> no
[03:55] <LaserJock> how about apt-get remove libfaac and then apt-get libfaac
[03:55] <ajmitch> libfaac0, actually
[03:56] <LaserJock> well, whatever
[03:59] <lprofil> works
[04:01] <lprofil> now i will try again
[04:02] <lprofil> i will try again to compile cinelerra
[04:02] <lprofil> thanks for the hint - wether it worked or not
[04:04] <LaserJock> lprofil: that's why it's a good idea to not use non-ubuntu repos
[04:04] <lprofil> configured without any errors
[04:04] <LaserJock> lprofil: and if you need more help please ask #ubuntu
[04:04] <lprofil> i have to compile now
[04:04] <lprofil> i will do so
[04:06] <lprofil> what does moto means by the way?
[04:06] <ajmitch> see topic
[04:06] <lprofil> :)
[04:07] <lprofil> so you guys are merging the debian files to ubuntu?
[04:30] <bddebian> lprofil: Yes pretty much
[05:31] <LaserJock> jeeze, gotta love a package with 106 open bugs in Debian including 5 RC
[05:33] <bddebian> Heh
[05:33] <bddebian> Which package?
[05:33] <LaserJock> tetex-base
[05:35] <bddebian> Ah yes, I was just going to look at that
[05:35] <bddebian> Is upstream active?
[05:36] <LaserJock> sorta depends on what you mean as upstream and active
[05:36] <bddebian> Upstream, upstream
[05:36] <bddebian> ie not Debian :-)
[05:36] <LaserJock> we, again
[05:36] <LaserJock> *well
[05:37] <bddebian> Or has Debian become de-facto upstream?
[05:37] <LaserJock> no
[05:37] <LaserJock> CTAN is upstream
[05:38] <bddebian> Oh
[05:38] <LaserJock> http://www.ctan.org/tex-archive/systems/unix/teTeX/
[05:39] <LaserJock> last release (3.0) was 2005-02-08
[05:41] <bddebian> aye, I was just looking at the pages
[05:42] <LaserJock> we also have texlive now too: http://www.ctan.org/tex-archive/systems/texlive/
[05:46] <bddebian> LaserJock: I was looking at that, but it seems to point back to CTAN?
[05:46] <LaserJock> at what?
[05:47] <LaserJock> texlive?
[05:47] <bddebian> The texlive page says to check out CTAN.  I'm trying to figure it out
[05:49] <bddebian> I'm confused
[05:50] <LaserJock> hehe, welcome to TeX
[06:00] <bddebian> Well I gotta head to bed.  Gnight man
[06:38] <ajmitch> sigh, I want to have libnss-ldap synced to fix one bug which makes my box unbootable, but it seems the lib has 4 other RC bugs against it that break things just as badly
[06:39] <Lathiat> heh
[06:45] <Hobbsee> ajmitch: fix all the bugs?  :P
[06:50] <ajmitch> you know I'm just going to ignore you when you keep saying things like that
[06:51] <Hobbsee> bleh.  how boring.
[07:36] <Hobbsee> Laser_away: you around?
[07:48] <RichJ> he passed out Hobbsee
[07:48] <RichJ> went to bed
[07:49] <Hobbsee> RichJ: ah okay
[07:49] <Hobbsee> oh good, Laser_away unping
[07:49] <Hobbsee> upstream fixed it anyway
[07:49] <RichJ> hehe
[07:49] <RichJ> anyone already do edgy updates tonight?
[07:56] <Hobbsee> hehe, yes, i did.
[08:58] !lilo:*! services will be shutting down for just a moment....please bear with us
[08:59] <dholbach> good morning
[09:01] <imbrandon> moins dholbach
[09:01] <jsgotangco> hi
[09:01] <dholbach> hey imbrandon
[09:01] <dholbach> hey jsgotangco
[09:01] <dholbach> how do you guys do?
[09:01] <imbrandon> good good , waiting for my updates to finish ;)
[09:01] <jsgotangco> raining all day on my side
[09:02] <Hobbsee> dholbach: w.r.t. what?
[09:02] <Hobbsee> guess i'm not supposed to answer anyway
[09:02] <dholbach> Hobbsee: whatever :)
[09:02] <dholbach> jsgotangco: i wish it'd rain once over here :)
[09:02] <dholbach> jsgotangco: (my dog too)
[09:02] <jsgotangco> hows the summer?
[09:02] <Hobbsee> dholbach: i requested a few more syncs, uploaded a couple of bits, nothing major :P
[09:02] <Hobbsee> pft.  what summer (grumble)
[09:02] <dholbach> imbrandon: you're finished now with the house?
[09:02] <dholbach> Hobbsee: i noticed - ROCK ON! :-)
[09:02] <Hobbsee> dholbach: :)
[09:03] <imbrandon> dholbach: yup yup finished this afternoon ;)
[09:03] <Hobbsee> dholbach: you wouldnt be saying that if i broke the stuff :P
[09:03] <crimsun> breaking stuff is part of the process :-)
[09:03] <dholbach> Hobbsee: at least you tried ;)
[09:03] <dholbach> hey crimsun :)
[09:03] <imbrandon> heya crimsun ;)
[09:03] <Hobbsee> heh
[09:03] <crimsun> heya dholbach
[09:03] <dholbach> Hobbsee: it's early enough in the cycle to break stuff
[09:03] !lilo:*! one more restart for services, please bear with us
[09:04] <imbrandon> heh not when she has it loaded as her main os dholbach ;)
[09:04] <dholbach> Hobbsee: come on, that's below you - if you break stuff, then break something major :)
[09:05] <Hobbsee> dholbach: haha.  i'm thinking about it, but tonio_ would be very angry with me
[09:05] <imbrandon> Hobbsee like *cough* xorg 7.1 *cough*
[09:05] <imbrandon> heh
[09:05] <Hobbsee> haha
[09:05] <dholbach> or glib or qt or something :)
[09:05] <Hobbsee> imbrandon: not quite the main one - i do have dapper, which i booted to a couple of days ago for a bit.
[09:06] <dholbach> hmmm coffee
[09:06] <imbrandon> Hobbsee: heheh yea just upload kde versioned "kde4svn-0ubuntu1" and see how fast we make slashdot LOL
[09:06] <Hobbsee> imbrandon: LOL!  nwo that would be fun
[09:07] <Hobbsee> now look what you've done, dholbach!
[09:07] <dholbach> you have a crystal wall at home?
[09:07] <imbrandon> hahaha
[09:07] <dholbach> now THAT's an enterieur I never imagined possible :)
[09:07] <imbrandon> heh
[09:08] <imbrandon> common guys help me get a job in EU so i can move ;)
[09:08] <imbrandon> lol
[09:08] <Hobbsee> dholbach: or a mirror wall, take your pick
[09:08] <Hobbsee> dholbach: something breakable, anyway
[09:08] <Hobbsee> imbrandon: i'm not interested in mountain dew, you're safe.
[09:08] <imbrandon> seven years bad luch
[09:08] <imbrandon> luck
[09:09] <Hobbsee> bleh.  that i doubt.
[09:13] !lilo:*! one more tiiiiiime..... 8)
[09:19] !lilo:*! hmmmm, reports of our immediate success were premature
[09:19] !lilo:*! one more trie
[09:19] !lilo:*! erm try
[09:20] !lilo:*! services restart
[09:20] !lilo:*! (working on a cloaking glitch)
[09:25] <Gloubiboulga> hello universe!
[09:25] <crimsun> hi Gauvain
[09:25] <Gloubiboulga> hi Daniel
[09:25] <Hobbsee> hi Gloubiboulga
[09:26] <Gloubiboulga> hi Hobbsee
[09:26] <Hobbsee> dholbach: now, you knwo, you shouldnt go picking up random people and throwing them at me, without their consent.   i'm sure imbrandon didnt appreciaet it!
[09:26] <Hobbsee> ack, honey on keyboard
[09:26] <dholbach> hey Gauvain
[09:27] <Gloubiboulga> hi Daniel n2
[09:27] <dholbach> :-)
[09:27] <dholbach> crimsun was active in Ubuntu land before me, iirc :)
[09:28] <crimsun> we're getting old, eh? ;-)
[09:28] <Gloubiboulga> hehe
[09:29] <dholbach> i remember one evening, where i tried to update the g*mm libraries (because i needed them for my thesis) - seb128 nearly killed me, when he had to explain shlibs (and how to bump them) for the (n+1)-th time
[09:29] <Gloubiboulga> yay! a mail from Jani!
[09:29] <dholbach> oh nice
[09:29] <dholbach> what is he doing? :)
[09:30] <Hobbsee> dholbach: heh, so should i ask you how you do bump them?
[09:30] <Gloubiboulga> he's working on xubuntu :)
[09:30] <Gloubiboulga> and he suggests me to apply for core-dev, which I seriously think about
[09:30] <dholbach> rock on, Gloubiboulga!
[09:30] <Gloubiboulga> :)
[09:31] <Gloubiboulga> The problem is that if Jani is not around, I can't do much :/
[09:31] <Gloubiboulga> everything is in main now
[09:31] <dholbach> Gloubiboulga: if you need stuff uploaded, tell me
[09:31] <crimsun> or me
[09:31] <Gloubiboulga> thanks Daniels :)
[09:31] <dholbach> i won't have time to triple-check stuff, but i trust you know how to fix stuff you broke ;)
[09:31] <crimsun> you'd be a shoo-in for core-dev given your work in Dapper
[09:32] <dholbach> Hobbsee: it was in a package which had debian/libsomething.shlibs files - the changelog indicated that there were new interfaces added, so i'd have to bump the versions in the .shlibs file
[09:32] <dholbach> Hobbsee: i think i didn't quite understand at the time :)
[09:32] <Gloubiboulga> well, let's see next Tuesday :)
[09:32] <Hobbsee> dholbach: ah right
[09:32] <crimsun> Gloubiboulga: rock on, and g'luck of course :-)
[09:32] <Hobbsee> Gloubiboulga: yay :)
[09:32] <dholbach> :-)
[09:35] <imbrandon> heh
[09:35] <imbrandon> Hobbsee: next kcc at 2100utc ? just kiddin
[09:35] <Toadstool> good morning
[09:35] <Hobbsee> imbrandon: 2100UTC isnt so bad - and that'll likely be the next time.  that's 7a,
[09:36] <imbrandon> moins Toadstool
[09:36] <Hobbsee> *7am
[09:36] <Gloubiboulga> Salut Toadstool
[09:36] <ajmitch> hi Toadstool
[09:36] <Hobbsee> imbrandon: i either have to have a crap meeting time, or step down from the committee.
[09:36] <imbrandon> ahh i was thinking it was your 6am ( my bad math )
[09:36] <Hobbsee> imbrandon: and you can all decide which of those you'd prefer
[09:36] <Hobbsee> 2000 UTC is my 6am
[09:36] <jsgotangco> are you in perth?
[09:37] <dholbach> hey ajmitch
[09:37] <ajmitch> how are you?
[09:37] <imbrandon> heya aj
[09:37] <imbrandon> err ajmitch
[09:37] <ajmitch> hi imbrandon
[09:37] <imbrandon> damm tab
[09:37] <ajmitch> heh
[09:38] <Hobbsee> jsgotangco: no, sydney - they're mostly in europe
[09:38] <imbrandon> cept me and i just am a night owl and dont care about time(s)
[09:38] <Hobbsee> hehe
[09:38] <Hobbsee> yeah, you can do that :P
[09:38] <imbrandon> i sleep and wake when i want ;) /me pays the sun no attn
[09:39] <Hobbsee> lucky
[09:39] <imbrandon> tis about 3am here for me, though i would love to be in EU atm ;)
[09:39] <Hobbsee> actually, i'll probably tell Riddell that a meeting at 2100UTC on a wednesday is fine.
[09:40] <imbrandon> HIG ? human interface guide ?
[09:40] <ajmitch> yes
[09:40] <imbrandon> cool
[09:40] <Hobbsee> eek.  col.d
[09:40] <ajmitch> so that I don't put together a monstrosity, there are some good tips there
[09:40] <imbrandon> yea useability.kde.org has some good info too ( although i know your a gnome guy heh )
[09:40] <Hobbsee> heh
[09:40] <Hobbsee> ajmitch cant stand kde.
[09:41] <imbrandon> s/kde.org/kde.com
[09:41] <Hobbsee> imbrandon: .org, surely.
[09:41] <crimsun> I'm not a big KDE fan, either, but I'm forcing myself to use it so I can try and get this audio stuff fixed up
[09:41] <imbrandon> err yea one of those darnit
[09:41] <imbrandon> crimsun: yay !
[09:41] <imbrandon> lol
[09:44] <imbrandon> hrm ok since some of the "big dawgs" are arround whats some sugestion / stuff i can work on to get my MOTU skills better  /me would like to be confident to go for MOTU semi soon , just keep plugin merges ?
[09:44] <crimsun> merges are an excellent entry point
[09:45] <imbrandon> kk i'll keep with those for the moment then ;)
[09:45] <Hobbsee> imbrandon: merges, merges, merges :P
[09:45] <crimsun> back in the day we'd fight over wiki locks. You younguns have it easy. ;-)
[09:45] <imbrandon> heheh
[09:45] <Toadstool> :)
[09:46] <ajmitch> why, I remember back in those days... ;)
[09:46] <Hobbsee> crimsun: hah
[09:46] <Hobbsee> ajmitch: yeah, but you're old and decrepit :P
[09:47] <Hobbsee> heh
[09:47] <imbrandon> ROFLAMAO , you are too now Hobbsee , into the adult world at 18+ ;)
[09:47] <phanatic> morning
[09:47] <Hobbsee> imbrandon: yeah, i keep telling people that im' old - they dont seem to belive me.
[09:47] <imbrandon> heh
[09:47] <imbrandon> moins phanatic
[09:48] <phanatic> hey imbrandon and everyone :)
[09:48] <bjp> good morning phanatic!
[09:48] <phanatic> hello bjp
[09:59] <slomo> hi
[10:00] <imbrandon_> heya slomo
[10:00] <phanatic> hey slomo
[10:19] <slomo> lucas: ping?
[10:20] <viviersf> ajmitch, ping
[10:20] <imbrandon_> crimsun: hrm ok dumb question but whats the diffrence between outstaning / new / updated merges ?
[10:20] <ajmitch> viviersf: pong
[10:20] <viviersf> ajmitch, quick Q, how do make a package remove another package before installing
[10:21] <imbrandon_> replaces ( in debain/control ) is one way
[10:21] <viviersf> i did that
[10:21] <ajmitch> viviersf: conflicts
[10:21] <viviersf> ah thx ajmitch
[10:21] <crimsun> imbrandon_: updated -> a newer debian package revision is available for an edgy merge that has already been done
[10:22] <ajmitch> though you may want conflicts: package
[10:22] <ajmitch> replaces: package
[10:22] <ajmitch> if it is really a replacement
[10:22] <crimsun> imbrandon_: new -> a newer debian package revision is available for a warty/hoary/breezy/dapper merge (i.e., no edgy merge has been done)
[10:23] <viviersf> ajmitch, it is possible to use provides and and replaces together ?
[10:23] <ajmitch> viviersf: in what way?
[10:24] <viviersf> hmmm
[10:24] <ajmitch> explain what you're wanting to do
[10:24] <viviersf> k
[10:24] <imbrandon_> ahh thanks crimsun
[10:24] <viviersf> i have my own blah-default-settings
[10:24] <slomo> lucas: as you already made the debian<->ubuntu package comparision pages... could you also make one for debian-multimedia.org<->ubuntu? :)
[10:24] <viviersf> the package must remove kubuntu-default-settings
[10:24] <viviersf> but i dont want the kubuntu-desktop package get removed
[10:25] <ajmitch> viviersf: it's possible, I think
[10:25] <viviersf> wait
[10:25] <viviersf> lemme try without the provides and see if it works then
[10:25] <ajmitch> viviersf: see kdelibs4c2a in edgy for example - it conflicts,replaces & provides kdelibs-bin
[10:26] <imbrandon_> ( without removeing all of kde ;P )
[10:27] <viviersf> lol kk
[10:28] <dholbach> I'd like to announce the motu school sessions and the motu mentor concept - which lists would you send it to, apart from u-motu@?
[10:28] <dholbach> fridge of course, but what else?
[10:28] <dholbach> u-devel-anounce?
[10:29] <imbrandon_> dholbach: bcc me and i'll post it on buntudot.org too
[10:29] <viviersf> sigh
[10:29] <viviersf> 18mb download
[10:29] <dholbach> imbrandon_: your mail adress is?
[10:29] <dholbach> oh it' s in LP, nevermind
[10:29] <imbrandon_><EMAIL_ADDRESS>[10:30] <imbrandon_> ;)
[10:30] <imbrandon_> or i guess<EMAIL_ADDRESS>works too but never tried it really other than an initial test message
[10:31] <ajmitch> should I sign up as a mentor?
[10:31] <imbrandon_> ajmitch: i think you should , your always helping motu hopefulls
[10:31] <imbrandon_> liek me ;)
[10:31] <imbrandon_> like*
[10:32] <ajmitch> there's a difference between randomly healping & having time to be a mentor though
[10:32] <ajmitch> s/healp/help/
[10:32] <imbrandon_> true
[10:33] <ajmitch> since I'm not the most active MOTU anyway :)
[10:34] <lucas> slomo: ping me later please
[10:38] <imbrandon_> lol
[10:50] <Fujitsu> A good email... But what's with `very contributors'?
[10:50] <dholbach> urg
[10:50] <dholbach> not enough coffee
[10:50] <Fujitsu> Very new, you mean?
[10:50] <dholbach> something like that, yes :)
[10:50] <Toadstool> heh
[10:51] <Toadstool> I didn't even notice, maybe I need more coffee too :)
[10:52] <Gloubiboulga> instead of a "building a nice source package" session I thought about a "Make the reviewers happy with your first REVU upload" session
[10:53] <Gloubiboulga> e.g. non native packages, standard versions...
[10:53] <dholbach> Gloubiboulga: i'm glad you volunteered!
[10:53] <dholbach> :-)
[10:53] <Gloubiboulga> hehe
[10:53] <Arbiter> Gloubiboulga, colorscheme package was not rejected yet :/
[10:53] <Gloubiboulga> we often have to say, bump debhelper compat, standard versions...
[10:53] <Arbiter> (ps: Hi Gloubiboulga :) )
[10:54] <Gloubiboulga> Arbiter, I'll ping Kamion and keybuk about this
[10:54] <slomo> Arbiter: just wait some time :) NEW is likely to be processed today
[10:54] <Arbiter> Gloubiboulga, yup
[10:54] <Gloubiboulga> slomo, we want it REJECTED since upstream has changed the name
[10:54] <Arbiter> i'm going to upload package changes (the fixed changelog entry for agave)
[10:54] <slomo> Gloubiboulga: oh ok
[11:00] <imbrandon_> crimsun got 10 minutes ?
[11:01] <crimsun> imbrandon_: let me finish this phone call (~3 mins)
[11:01] <imbrandon_> okie np
[11:06] <crimsun> imbrandon: hi
[11:07] <imbrandon> heya , ok
[11:07] <imbrandon> you rember the quick and dirty you gave someone about packing 101 with kponies hehe
[11:07] <crimsun> vaguely
[11:07] <imbrandon> can you do a merging 101 ~10 minute quick and dirty using something simple like http://merges.ubuntu.com/y/yate/REPORT
[11:08] <crimsun> sure, gimme a sec to load everything
[11:08] <imbrandon> i have all the grab merge and pbuilder setups done etc so no need for THAT basic of a setup but you know ....
[11:08] <crimsun> lots of thrashing, memory pressure, etc.
[11:08] <imbrandon> ;)
[11:09] <imbrandon> hehe okie
[11:09] <crimsun> (I'm doing this on Friday night iirc)
[11:09] <imbrandon> ahh cool
[11:09] <imbrandon> i will definately be there for that
[11:11] <crimsun> imbrandon: ok
[11:11] <imbrandon> listening*
[11:12] <crimsun> do you need me to address anything in particular?
[11:12] <imbrandon> nah just an overview , well basicly what to do after you ahve grabed the merge with grabmerge and changed the nessesarry bits
[11:12] <imbrandon> in the dir that it unzips
[11:12] <imbrandon> is where i'm at
[11:13] <crimsun> ok, so you've just done ../grab-merge.sh yates
[11:13] <imbrandon> but a general overview would be good becouse most of this so far is self taught / figured out
[11:13] <crimsun> err, yate.
[11:13] <imbrandon> yup
[11:13] <imbrandon> brandon@intrepid:~/devel/merges/yate/yate-1.0.0-1.dfsg-1ubuntu1$
[11:13] <imbrandon> is where i'm at/ have
[11:13] <crimsun> all right. There's of course more than one way to do a merge, so I'll just talk about how I'd approach it.
[11:14] <imbrandon> ok
[11:14] <crimsun> the first thing is of course to read REPORT
[11:14] <imbrandon> right , got that open in the www browser
[11:14] <crimsun> note any conflicts marked with C or C*
[11:14] <imbrandon> k
[11:14] <crimsun> I also look for reasons why a Ubuntu delta was necessary
[11:15] <crimsun> for this reason I have Ubuntu's debian/changelog open, too
[11:15] <imbrandon> ok from .....
[11:15] <crimsun> (yet another reason why documenting changes is good)
[11:15] <imbrandon> the changelog from 0.8.7+cvs20050604-4ubuntu1 that it downloaded ?
[11:16] <crimsun> you can either look in ../yate_0.8.7+cvs20050604-4ubuntu1.diff.gz or look at the changelog linked from packages.uc
[11:16] <imbrandon> ok
[11:16] <crimsun> you'll see that Daniel documented the Ubuntu delta as a stricter versioned build-dependency
[11:17] <imbrandon> right - Bumped Build-Depends on newest libopenh323.
[11:17] <dholbach> not sure if you need to keep that - you can just try
[11:17] <crimsun> now I'd open debian/control  (in the extracted merge dir)
[11:17] <dholbach> for edgy we only have one openh323 version
[11:17] <crimsun> [honestly it's a sync, but we can look at it both ways]
[11:18] <dholbach> :)
[11:18] <imbrandon> heh /me had to pick a sync on the first go arround lol
[11:18] <imbrandon> ok deb/control open
[11:19] <crimsun> ok, so at the diff markers, you'll see the stricter b-d
[11:19] <imbrandon> yup 1.15.x to 1.17.x
[11:19] <imbrandon> looks like debian put stricter libpri-dev too
[11:20] <crimsun> now supposing that the Ubuntu delta is actually critical, you'd merge all the Ubuntu changes into the Debian version
[11:20] <imbrandon> right but this case 1.15.x is ok ( correct ? )
[11:20] <crimsun> that is, we always prefer the Debian version unless there's a reason to roll in the Ubuntu ones
[11:20] <imbrandon> kk yea
[11:21] <crimsun> for the time being assume that we actually need the stricter 1.17.3
[11:21] <imbrandon> ok
[11:21] <crimsun> so what I'd do is update Debian's libopenh323-dev to the stricter versioned b-d, then delete the Ubuntu delta
[11:21] <imbrandon> right, just did that
[11:22] <imbrandon> and used the debian uploaders ( there was one added )
[11:22] <crimsun> right
[11:22] <crimsun> since I only touched the libopenh323-dev for Debian's b-d, the rest is 'automatic' when I delete the Ubuntu delta
[11:23] <imbrandon> right ok
[11:23] <crimsun> now since there aren't other conflicts listed in REPORT, I'd just once-over debian/
[11:24] <imbrandon> and change /changelog from mom to me ( if we was gonna actualy upload this , pretending we are )
[11:24] <imbrandon> correct ?
[11:24] <crimsun> right
[11:25] <crimsun> then issue the obligatory ``fakeroot ../merge-buildpackage -kyour_id'', pbuild, etc.
[11:26] <crimsun> (then ping a MOTU to do the upload)
[11:26] <imbrandon> ok so i do the buildpackage script , if all go's well , i do pbuild and if it builds then upload to revu and poke a MOTU ? ( not this time beouse of a sync but normaly )
[11:26] <imbrandon> no merge-genchnges ?
[11:26] <crimsun> right, or you can just use your own Web space to host the source package temporarily
[11:26] <imbrandon> yea ( i do that most of the time becouse revu is slow for me )
[11:27] <imbrandon> heh
[11:27] <imbrandon> what about the gen-changes ?
[11:27] <imbrandon> err merge-genchanges
[11:28] <crimsun> notice that merge-buildpackage does that.
[11:28] <crimsun> (rather, dpkg-buildpackage)
[11:28] <imbrandon> ahh okie
[11:28] <crimsun> ok, so here's the fun part.
[11:28] <imbrandon> k
[11:29] <crimsun> suppose you ../grab-merge.sh foo, you look at REPORT, everything looks like a merge.
[11:29] <crimsun> How do you tell when stuff can actually be synced insteadL
[11:29] <crimsun> ?
[11:29] <imbrandon> hrm
[11:29] <imbrandon> no clue tbh
[11:30] <imbrandon> when the ubuntu deltas are in upstream already ?
[11:30] <imbrandon> heh
[11:30] <crimsun> in this case it's a matter of saying, "hmm, we don't need the strong b-d [the Ubuntu delta]  anymore, because there's only one libopenh323-dev in Edgy"
[11:30] <imbrandon> right ok
[11:30] <imbrandon> whereas in dapper there was more than one
[11:31] <imbrandon> and they might nnot have upgraded
[11:31] <imbrandon> or ( deb sid ) etc
[11:31] <crimsun> meaning "if I were to upload this source package now to be built, there's no way I could get an older libopenh323"
[11:32] <imbrandon> right right , so when its something like stroger dep or build-dep i can check the version currently in edgy
[11:32] <crimsun> right
[11:32] <imbrandon> if thats the only change then its not needed
[11:32] <imbrandon> and can be synced
[11:32] <crimsun> generally, correct.
[11:32] <imbrandon> cool
[11:32] <crimsun> now one of the cases I would consider is, "What if this package were requested to be backported?"
[11:33] <imbrandon> ahhh
[11:33] <crimsun> so we're in Edgy now, and both Dapper and Edgy have sufficiently new versions of libopenh323-dev that the Ubuntu delta can be dropped
[11:34] <imbrandon> and it wouldent get backported all the way do breezy
[11:34] <imbrandon> right ?
[11:34] <imbrandon> so no worries there
[11:34] <crimsun> to be honest that would be a legit backport request, but for our purposes I would ignore them.
[11:34] <imbrandon> ok
[11:35] <imbrandon> speaking of ? any word on soyuz ?
[11:35] <crimsun> the reason being that because Debian's b-d is fulfilled by Breezy's
[11:35] <crimsun> s/because//
[11:36] <imbrandon> huh ?
[11:36] <imbrandon> lost me on that one
[11:36] <crimsun> in the extremely improbable case that someone wanted yate backported from Edgy to breezy-backports, the sync from Debian Sid would be fine
[11:37] <imbrandon> ahh okie
[11:37] <crimsun> so generally the rule of thumb is "concentrate on Edgy, but if you want to be kind, think of dapper-backports"
[11:37] <imbrandon> right
[11:38] <crimsun> there are a lot more examples that I'll cover on Friday where merges can turn into syncs
[11:38] <crimsun> and some where merges have to remain merges
[11:38] <imbrandon> cool . i'll definately be there
[11:38] <crimsun> for example, suppose we have a Ubuntu delta that's just the GL{,u} transition
[11:38] <imbrandon> k
[11:39] <crimsun> if the Debian source package b-ds xlibmesa-gl-dev but the Ubuntu delta has libgl1-mesa-dev | libgl1-dev, then we can drop the Ubuntu delta
[11:39] <crimsun> it was necessary in Dapper, but in Edgy we have xlibmesa-gl-dev again
[11:40] <imbrandon> ahh cool
[11:40] <crimsun> on the /other/ hand, it does /not/ hold true for libglu1-mesa-dev | libglu1-dev
[11:40] <crimsun> we have to keep that delta currently
[11:40] <crimsun> that is, if Debian b-ds xlibmesa-glu-dev, we cannot use that
[11:41] <imbrandon> ahh
[11:41] <crimsun> merges are generally pretty fast once you get the hang of them
[11:42] <imbrandon> yea seems so
[11:42] <Fujitsu> Yeah, I found that after the first few.
[11:42] <crimsun> the real nasty ones are major version jumps where classes and templates are involved
[11:42] <crimsun> and a major gotcha is bashisms in the maintainer scripts
[11:42] <imbrandon> so for the moment i'll go ahead and file a sync req for yate ok ?
[11:42] <crimsun> yep, make sure you get a MOTU to sign off on it
[11:42] <imbrandon> yup yup
[11:44] <shenki> hello
[11:45] <Fujitsu> Hi shenki.
[11:45] <shenki> Fujitsu, you're everywhere :P
[11:45] <Fujitsu> shenki, just the 20 channels :)
[11:45] <imbrandon> crimsun: malone 53873 if you wanna do the honors
[11:45] <shenki> i'm keen to get a few things added to edgy, and I'm not sure about the best way to go about it
[11:45] <Ubugtu> Malone bug 53873 in yate "please sync 1.0.0-1.dfsg-1 from debian unstable" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/53873
[11:46] <shenki> i've written up this wiki page https://wiki.ubuntu.com/CompleteNetworkManager which contains some of the details
[11:46] <shenki> in summary, i want to get networkmanager's vpn plugins packaged, and possibly pam_keyring included also
[11:47] <Fujitsu> shenki, I was looking at doing pam_keyring.
[11:47] <shenki> yeah?
[11:47] <Fujitsu> network-manager-vpnc is already there...
[11:47] <shenki> in edgy?
[11:47] <shenki> because it wasn't in dapper
[11:47] <crimsun> imbrandon: done.
[11:48] <Fujitsu> Oh.
[11:48] <Fujitsu> Oops.
[11:48] <crimsun> off for work, 'later guys :-)
[11:48] <Fujitsu> That's a package I grabbed from elsewhere >_<
[11:48] <shenki> :)
[11:48] <imbrandon> later crimsun, thanks
[11:49] <Fujitsu> Bye crimsun.
[11:49] <shenki> yeah. as i wrote on the wiki page, dapper has the gui for configuring the vpn plugins in networkmanager, but no plugins shipped. which was quite confusing for the user "why include the dialouge if there's no way to use it?"
[11:49] <Fujitsu> Well, the dialog is built into NM itself, while the plugins are not.
[11:50] <shenki> very true. but i would argue that the dailouge should be disabled if it's unable to be used
[11:50] <shenki> anyway, that's all beside the point :)
[11:52] <shenki> the plugins side of things is a given - the vpn software itself is already in, so all that is needed is the vpn plugins to be packaged
[11:52] <shenki> it's pam_keyring that might be a bit sticky. a few places mention it's a potential security issue
[11:52] <Fujitsu> Yeah, I'll look into doing that. I need some packages to make :P
[11:53] <Fujitsu> It could potentially be a security risk... But it's incredibly useful.
[11:53] <shenki> true
[11:53] <shenki> i guess the reason i came here was to find out who needs to be made aware of the wiki page for it to progress any further
[12:13] <dholbach> hey lfittl
[12:14] <lfittl> hi dholbach :)
[12:16] <shawarma> Hi! I need a bit of clarification about what to put in the changelog when doing merges... If I don't change anything at all (ie. the automatic merge went without a hitch), I just generate a .changes and upload and leave the MoM-entry in the changelog, right? And if I change anything at all, I put my own changelog entry in?
[12:20] <Gloubiboulga> shawarma, I'd change the changelog entry even if MoM has done the merge without manual editing
[12:21] <Fujitsu> That's what I was told to do, Gloubiboulga.
[12:21] <Gloubiboulga> it's nice to know who took care of a merge :)
[12:21] <shawarma> LOL!
[12:21] <shawarma> crimsun told me the *exact* opposite a week ago.
[12:21] <Gloubiboulga> hmm
[12:21] <shawarma> he added a disclaimer though.
[12:22] <shawarma> Ah.. I thought my logs went back that long... I can't find it right now.
[12:23] <shawarma> but i totally agree that it's nice to know who did the upload.
[12:23] <Gloubiboulga> well, I don't know what I can tell
[12:23] <Gloubiboulga> I do trust crimsun
[12:24] <shawarma> I'll do that. Should the changelog entry just say "resynced with debian" or should I list the actual changes again (they are of course already mentioned in the changelog since it's been done once before for ubuntu).
[12:24] <Gloubiboulga> you can mention them again I think (but maybe I shouldn't answer :p )
[12:25] <Fujitsu> If I have an upstream package that insists on installing its INSTALL and LICENSE.gz, do I let it, or do I patch the installation to make it not?
[12:25] <Fujitsu> Gloubiboulga, I was told you should generally list the remaining changes as sub-items of the sync entry.
[12:25] <shawarma> Fujitsu: Cool, I'll do that.
[12:26] <shawarma> Do I also just upload merges to REVU or is there some special way of handling them?
[12:26] <tseng> is Kevin Kubasik here
[12:26] <Fujitsu> shawarma, get a MOTU to upload them directly.
[12:26] <Fujitsu> (ie. Gloubiboulga)
[12:26] <Gloubiboulga> :)
[12:26] <slomo> shawarma: better find someone to upload it in the channel... and better supply a debdiff instead of a complete package
[12:27] <shawarma> slomo: debdiff between ?
[12:27] <shawarma> slomo: The old ubuntu package or the new debian package?
[12:27] <slomo> shawarma: i prefer debdiff between base debian revision and your merged version... but other's oppinions may differ ;)
[12:28] <Fujitsu> Anybody got any answers for me?
[12:28] <shawarma> Fujitsu: Why would you not let it install them?
[12:28] <Gloubiboulga> Fujitsu, LICENSE.gz should be in copied debian/copyright
[12:28] <slomo> Fujitsu: remove the INSTALL file and LICENSE.gz should be in debian/copyright and not installed separately
[12:28] <Fujitsu> shawarma, lintian complains.
[12:28] <Fujitsu> slomo, that's what I thought.
[12:29] <Fujitsu> slomo, remove them entirely? Or just don't install them>?
[12:29] <slomo> just don't ship them in the binary packages
[12:30] <Fujitsu> How do I avoid that without removing them in the diff.gz?
[12:31] <Gloubiboulga> remove the files from debian/<package>/ after the 'make install' or wathever you use to install the files
[12:31] <slomo> do you use debian/$package.install files? or just let make install install everything into debian/$package? in any case, just remove the files from debian/$package or don't list it in the debian/$package.install files
[12:32] <Fujitsu> It in fact isn't a make[, install]  type thing, it's just a python script that installs everything.
[12:32] <Fujitsu> But I'll remove it from inside debian/, yes.
[12:33] <freeflying> anyone can give some clues on set up a buildd,thanks
[12:33] <shawarma> slomo: When you sadi "base debian revision" before.. Is that the version the old ubuntu package is based on or is it the new one?
[12:34] <slomo> shawarma: the new one, i.e. the debdiff will only contain the ubuntu changes
[12:34] <shawarma> freeflying: I just hacked one together yesterday. If you ask really nicely I might send you the python script when I've cleaned it up a bit. :-)
[12:35] <shawarma> slomo: Right, that's what I thought, but the REPORT file calls the old debian revision "base". Got a bit confused. :-)
[12:35] <freeflying> shawarma: nice, if you can please mail me  zhengpeng-hou  AT ubuntu.com, thanks
[12:35] <slomo> shawarma: how does the report call the new debian revision?
[12:36] <shawarma> slomo: just "debian".
[12:36] <shawarma> slomo: e.g. http://merges.ubuntu.com/a/arkrpg/REPORT
[12:36] <slomo> shawarma: ok
[12:39] <Fujitsu> Hmm... If ConvertAll hasn't had a new release since Feb 2005, does that fail the `actively maintained' criterion?
[12:40] <shawarma> slomo: Like so? http://www.linux2go.dk/edgy-merges/asterisk-merge.debdiff
[12:40] <Kamping_Kaiser> debian would loose a fair bit of wight (and ubuntu too i expect) if stuff needs to be actively maintained o_-
[12:41] <slomo> shawarma: yes
[12:41] <slomo> Kamping_Kaiser: in debian it's somewhat required already
[12:41] <Fujitsu> Kamping_Kaiser, but the new package policy mentions that it needs to be actively maintained.
[12:41] <Fujitsu> And ConvertAll looks like it could be fairly useful, and it's on MOTU/Packages/Candidates
[12:42] <shawarma> slomo: "yes" == "yes, that's the correct way to do it", or "yes" == "yes, that looks great. I'll upload it for you right away" ? :-)
[12:42] <Kamping_Kaiser> the 4 programs i looked at in the last 2 days (cant remember the names) were all 3/4 yeras with no updates :| its anoying as heck. one was 5 years
[12:43] <slomo> shawarma: the former :) i don't have much time atm
[12:43] <shawarma> slomo: Ok. Thanks for your help.
[12:43] <slomo> Kamping_Kaiser: 3/4 year is not much... maybe there simply wasn't a reason for a new version yet or something :) and even 5 years could be ok in some cases...
[12:44] <shawarma> Gloubiboulga: Would you care to accept this patch and upload it for me, please? http://www.linux2go.dk/edgy-merges/asterisk-merge.debdiff
[12:44] <Gloubiboulga> shawarma, yep
[12:44] <shawarma> Gloubiboulga: Coooooool.
[12:44] <Kamping_Kaiser> slomo, yes :) i was debating pinging the mainteriners and asking
[12:49] <imbrandon> dholbach: ping
[12:49] <imbrandon> err any MOTU ?
[12:50] <imbrandon> heh StevenK wanna do a quick merge upload ? http://revu.tauware.de/details.py?upid=2775
[12:51] <imbrandon> heh want me to upload it to my own webserver ?
[12:51] <imbrandon> i can if its easier
[12:52] <Fujitsu> Er... I'd like a REVU account. How do I go about obtaining one?
[12:52] <imbrandon> Fujitsu: /topic , very end
[12:52] <StevenK> imbrandon: I'll do a test build, I just need to wait for my current build to finish.
[12:52] <Fujitsu> Ah. It auths through Launchpad? I assumed it was a more manual process :)
[12:53] <imbrandon> kk no worries
[12:53] <imbrandon> Fujitsu: it uesd to be
[12:54] <imbrandon> one more step to REVU2 ;)
[12:54] <Fujitsu> Ah,
[12:57] <imbrandon> hrm brb
[12:58] <Fujitsu> Shouldn't REVU give me something to decrypt when I ask for a password recovery?
[12:59] <Fujitsu> imbrandon, do I have to do a password recovery the first time?
[12:59] <ajmitch> Fujitsu: only if you've uploaded a package
[12:59] <Fujitsu> ajmitch, OK...
[01:00] <ajmitch> the password is just for logging into the web ui for replying to comments
[01:01] <Fujitsu> How do I upload a package, then!?
[01:01] <ajmitch> with dput, as the wiki page says
[01:01] <Fujitsu> Ah. Oops.
[01:07] <shawarma> That info should really be on revu itself.
[01:12] <Fujitsu> Yeah, it should.
[01:14] <DanielC> Hello, I'm working on another package that I want to submit to Revu. Where can I find a list of the sections available (for the Section: field in the control file).
[01:14] <ajmitch> Fujitsu: https://launchpad.net/products/revu/+filebug
[01:15] <Fujitsu> I was thinking of that, ajmitch :)
[01:15] <ajmitch> DanielC: debian policy, #2.4
[01:15] <DanielC> ajmitch: Where can I find debain policy?
[01:15] <Gloubiboulga> shawarma, have you checked the build with pbuilder? it FTBFS
[01:15] <ajmitch> DanielC: google will show you, or in the debian-policy package
[01:15] <DanielC> k
[01:18] <DanielC> Hmm... in what section would you put a text-based (console) reader for OpenDocument files?
[01:18] <DanielC> I'm thinking "utils"
[01:19] <imbrandon> ajmitch: how do i "archive" my files that have been uploaded all ready ?
[01:19] <imbrandon> ( on revu )
[01:19] <ajmitch> imbrandon: you give a revu admin a list of packages to archive
[01:19] <imbrandon> ajmitch:  ohh ok
[01:19] <shawarma> Gloubiboulga: Hm.. I thought I did.
[01:21] <shawarma> Gloubiboulga: Ah... filename completion can be a dangerous thing. I check another package instead of asterisk. that package build just fine, though. On both amd64 and i386. :-)
[01:22] <imbrandon> ajmitch: can you archinve these for me ( already uploaded ) ... ipodslave , kdissert , icewm , and apt-mirror please
[01:22] <imbrandon> archive*
[01:22] <Gloubiboulga> shawarma, it's an easy fix I think, just a missing build dep
[01:23] <shawarma> Gloubiboulga: Ok. I'll fix it in a few minutes.
[01:23] <Gloubiboulga> shawarma, ping me when you have a new debdiff ;)
[01:24] <shawarma> Gloubiboulga: Will do. Thanks!
[01:25] <shenki> Fujitsu: are you packaging pam_keyring?
[01:26] <Fujitsu> shenki, I probably will.
[01:26] <shenki> ok. timeframe?
[01:26] <Fujitsu> I'm really not sure. Less than a week... But then it needs to get through REVU etc.
[01:28] <shenki> yep
[01:37] <StevenK> imbrandon: Can you put the .changes file somewhere I can nab it?
[01:39] <imbrandon> StevenK: yea gimme one sec
[01:43] <imbrandon> StevenK: http://www.buntudot.org/people/~imbrandon/misc/gtkpod_0.99.4-1ubuntu1_source.changes
[01:45] <StevenK> imbrandon: Hrm. The checksum for the diff.gz in the changes file doesn't match the file itself.
[01:46] <imbrandon> hrm thats strange
[01:46] <imbrandon> ohhh
[01:46] <imbrandon> i copied and dident ftp it
[01:46] <imbrandon> gah
[01:46] <imbrandon> ok one sec lemme ssh to that box and ftp it lol
[01:47] <StevenK> Is the diff.gz or the .changes file correct?
[01:47] <imbrandon> the diff
[01:48] <imbrandon> the .changes i copy and pasted a new file on the server becosue i had an ssh session already on buntu dot
[01:48] <imbrandon> i can ftp the orig changes to buntudot if you need it
[01:48] <zul> hi
[01:48] <imbrandon> moins
[01:49] <StevenK> imbrandon: The orig .changes would be good.
[01:49] <imbrandon> yup one sec
[01:52] <imbrandon> StevenK: http://imbrandon.sytes.net/gtkpod_0.99.4-1ubuntu1_source.changes
[01:52] <imbrandon> ^^ orig
[01:53] <StevenK> imbrandon: I think REVU has done something to the diff.gz, then.
[01:54] <StevenK> 4886fab70d48545fc7fdeb70ddf03f60  gtkpod_0.99.4-1ubuntu1.diff.gz
[01:54] <imbrandon> hrm ok lemme stick all my orig files on the wwwdir one sec
[01:55] <StevenK> Only the diff.gz is different.
[01:56] <imbrandon> http://imbrandon.sytes.net/gtkpod
[01:56] <StevenK> 403
[01:56] <imbrandon> i just ln -s that dir to the www dir so you can look at the origs
[01:56] <StevenK> Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
[01:56] <imbrandon> gah
[01:56] <imbrandon> moment
[01:58] <imbrandon> ok try now
[01:59] <imbrandon> StevenK:
[02:00] <StevenK> That works.
[02:00] <imbrandon> kk
[02:01] <StevenK> imbrandon: Successfully uploaded packages.
[02:01] <imbrandon> cool thanks
[02:02] <imbrandon> sorry for the trubble dunno what was up with revu
[02:02] <imbrandon> becouse thats the dir i dput'd from lol
[02:03] <StevenK> I've seen it once before.
[02:05] <imbrandon> StevenK: got time to look over one more merge ? i would like someone to look it over becouse its only my 4th merge and i THINK i did it right and it builds good just wanna be sure
[02:06] <imbrandon> if busy no biggie though
[02:08] <StevenK> Hrm. If I knew that, I would have given gtkpod a harder look.
[02:09] <imbrandon> heh well gtk pod i had a little help with i knew it was good ( plus it was a simple one )
[02:10] <imbrandon> http://imbrandon.sytes.net/xawtv  << StevenK  wanna look
[02:11] <imbrandon> actualy i should say 4th merge that wasent mine , i've done about 8-10 merges, and quite a few other sponsored uploads ;)
[02:13] <shawarma> Gloubiboulga: That asterisk thing. It's linux/compiler.h it moans about, right? That's in linux-kernel-headers.. Is that a part of build-essential in Debian, perhaps?
[02:14] <Gloubiboulga> hum, I don't think so
[02:15] <shawarma> Gloubiboulga: Ah, yes, it is. libc6 depends on it.
[02:15] <shawarma> libc6-dev, of course.
[02:15] <shawarma> ...but so does ours.. wtf?
[02:15] <Gloubiboulga> right
[02:18] <shawarma> Gloubiboulga: It was the same error you got, right?
[02:18] <Gloubiboulga> shawarma, yes
[02:19] <shawarma> Gloubiboulga: Ah... it turns out compiler.h is not in our linux-kernel-headers in edgy.
[02:19] <shawarma> Gloubiboulga: I'll figure something out.
[02:20] <Gloubiboulga> linux-kernel-headers: usr/include/linux/compiler.h
[02:20] <Gloubiboulga> with apt-file
[02:20] <zul> Gloubiboulga: compiler.h is an empty file in dapper
[02:21] <Gloubiboulga> well, it's on edgy
[02:21] <shawarma> Gloubiboulga: Yes, but it's not there in edgy.
[02:21] <Gloubiboulga> -
[02:21] <shawarma> Gloubiboulga: i know apt-file says it is, but it's not. :-)
[02:21] <Gloubiboulga> ok...
[02:21] <Gloubiboulga> stupid apt-file
[02:21] <shawarma> http://packages.ubuntu.com/cgi-bin/search_contents.pl?searchmode=filelist&word=linux-kernel-headers&version=edgy&arch=i386
[02:22] <shawarma> Well, if it's empty, I'll just comment it out in the file that's trying to include it.
[02:23] <shawarma> zul: Do you happen to know when it was removed?
[02:23] <zul> probably when the kernel-team took over lkh
[02:24] <shawarma> zul: What would be more correct. To bug kernel-team to put it back or to comment it out in the file trying to include it?
[02:25] <zul> shawarma: well im on the kernel-team but BenC away this week ill bug him when he gets back
[02:25] <shawarma> zul: So the former?
[02:25] <zul> i dont see removing it right now as a big probalem
[02:26] <zul> i say remove it for now and open a bug
[02:26] <shawarma> zul: Ok. Thanks.
[02:30] <Kamping_Kaiser> i'm looking at amap, and it fails to install  (cant find thc.org), now theres already a patch to fix this, but i dont understand it - should i try and work with existing patch/s or just try and fix it and diff the 'fixed' source?
[02:37] <Kamping_Kaiser> sorry - someone told me last night of a wrapper to dpkg-buildpackage - what is it?
[02:37] <Kamping_Kaiser> hey Hobbsee :)
[02:38] <zul> debuild?
[02:39] <Kamping_Kaiser> yes, thats it :) thanks zul
[02:39] <Hobbsee> hi Kamping_Kaiser, hi everyone else
[02:39] <Kamping_Kaiser> :)
[02:39] <phanatic> hey Hobbsee
[02:40] <Hobbsee> hi phanatic
[02:40] <Hobbsee> Kamping_Kaiser: hehe, yeah
[02:40] <Hobbsee> it's great for that
[02:41] <Kamping_Kaiser> :)
[02:42] <Kamping_Kaiser> never tried editing someone elses C before :| hope i get ot mostly ok.
[02:43] <Kamping_Kaiser> found the right string to change - need to know what to change it to... wonder if i can turn it off....
[02:46] <Kamping_Kaiser> wb Hobbsee_ , your connection crap atm?
[02:47] <shawarma> Gloubiboulga: http://www.linux2go.dk/edgy-merges/asterisk-merge.debdiff
[02:47] <Gloubiboulga> shawarma, I try to get this $*#@# package working and I'll have a look
[02:48] <Hobbsee> Gloubiboulga: which were you working on?
[02:50] <Gloubiboulga> I try to enable python bindings for libexo
[02:50] <Gloubiboulga> this new python policy...
[02:50] <Hobbsee> Gloubiboulga: eek
[02:52] <Gloubiboulga> see, it's even killed Hobbsee
[02:53] <Toadstool> :)
[02:55] <Mithrandir> hiya Hobbsee
[02:55] <Hobbsee> hi Mithrandir!
[02:56] <Mithrandir> Hobbsee: not very tickly.  And a bit lonely after simira went to her parents with both our cats.
[02:56] <Kamping_Kaiser> anyone feeling inspired?
[02:57] <Hobbsee> Mithrandir: :(
[02:57] <ogra> Mithrandir, why did you let her take the cats then ?
[02:58] <Hobbsee> Mithrandir: guess i'll just have to poke you then, or maybe give you a hug...hmmm...
[02:58] <Mithrandir> ogra: better to take them in a car than on a train.
[02:59] <ogra> right ... you didnt say you'd follow her :)
[03:00] <Mithrandir> well, our wedding is going to be in Molde where her parents live, so I better. :-P
[03:01] <Kamping_Kaiser> hehe
[03:01] <Kamping_Kaiser> anyone here know how the debian bts works? *goes to try and work it out*
[03:01] <ogra> lol, yes indeed
[03:01] <Mithrandir> Hobbsee: August 5th.
[03:02] <Hobbsee> Mithrandir: ahh :)
[03:02] <StevenK> Mithrandir: How long have you two been engaged?
[03:02] <Mithrandir> StevenK: since March 20th 2005
[03:03] <StevenK> I proposed in August 2004 and my wife and I got married on the 1st of March, 2005.
[03:04] <slomo> Kamping_Kaiser: it's explained on bugs.debian.org... via mail is the easiest imho
[03:04] <StevenK> People kept telling us we were mad for such a short engagement period.
[03:04] <Mithrandir> StevenK: well, one often has been together for a time before getting enganged too.
[03:05] <StevenK> Well, of course.
[03:05] <Mithrandir> Hobbsee: for us it was more a question of logistics -- when was it convenient to have it.
[03:05] <Hobbsee> Mithrandir: ah yes, good point
[03:05] <Mithrandir> (and Karianne wanted it to be late-summer)
[03:05] <Kamping_Kaiser> slomo, thanks :), i managed to find the bug report i needed - seems a bug i filed against ubuntu is a clone of this. :|
[03:05] <StevenK> Hobbsee: Usually, because the bride has been planning her wedding since her 12th birthday and everything has to be just so.
[03:05] <Hobbsee> StevenK: heh.  i'm clearly a failure as a woman then.
[03:06] <StevenK> Hobbsee: Not the 'usually'. My wife hadn't been.
[03:06] <StevenK> Er.
[03:06] <StevenK> s/Not/Note/
[03:07] <Hobbsee> StevenK: ah
[03:07] <Mithrandir> some friends of us married after being together for about two or three months.  They're still living happily together, so I guess that approach works for some people.
[03:08] <Kamping_Kaiser> Hobbsee, we'll let you in here still ;)
[03:08] <StevenK> My wife and I had been dating for about 18 months before I proposed.
[03:08] <Hobbsee> Kamping_Kaiser: hehe
[03:08] <zul> StevenK: i was dating my wife for about 5 years before i asked
[03:09] <Hobbsee> (yay, i never have to ask someone :P )
[03:09] <StevenK> Hell, my wife was hinting that'd she like me to ask to a question pretty close to our 12 month anniversary.
[03:09] <Hobbsee> hehe
[03:10] <Mithrandir> Hobbsee: since you're a girl, you're (traditionally) not even allowed to ask, except on February 29th.
[03:10] <Hobbsee> Mithrandir: hehe.  true.
[03:11] <StevenK> Heh
[03:13] <Kamping_Kaiser> YAY. i only have to change 2 lines of a postinst script to fix this... i hope
[03:25] <Kamping_Kaiser> can someone look at bug 53041 for me? (and optionally fix it properly). i'm just trying to link it to an upstream bug, but it does have a patch there
[03:25] <Ubugtu> Malone bug 53041 in amap "fails install trying to connect to unknown host" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/53041
[03:27] <Kamping_Kaiser> yay. i learn how to link to debian bugs today :o
[03:29] <Kamping_Kaiser> hey bddebian :D
[03:30] <bddebian> Heya gang
[03:30] <bddebian> Hi Kamping_Kaiser
[03:30] <Kamping_Kaiser> :)
[03:32] <phanatic> hey Yagisan and bddebian
[03:32] <Kamping_Kaiser> just tested... the patch works
[03:33] <bddebian> Heya phanatic
[04:05] <zul> grrr...why is dput just sitting there?
[04:33] <bddebian> Laser_away: ping me when you come around please
[04:34] <bddebian> Who is: 	Daniele Favara ?
[04:35] <Hobbsee> bddebian: check google?
[04:35] <Hobbsee> no idea.
[04:35] <Arbiter> bddebian, https://launchpad.net/people/nomed?
[04:35] <bddebian> Well he/she uploaded or was sponsored for ivman
[04:36] <Hobbsee> bddebian: i'm regarding almost all merges now as fair game.
[04:38] <bddebian> Hobbsee: Well it scares me when it's someone like doko or ogra, etc.. :-)
[04:39] <Hobbsee> bddebian: hehe, true.  i didnt think ogra was that scary
[04:39] <Hobbsee> doko though...yeah, i see your point
[04:40] <zul> how can you check to see if something is in the new queue for edgy?
[04:40] <ogra> https://launchpad.net/distros/ubuntu/edgy/+queue
[04:40] <Hobbsee> ogra: what, you mean you are scary?
[04:40] <zul> merci
[04:40] <bddebian> zul: https://launchpad.net/distros/ubuntu/edgy/+queue
[04:41] <bddebian> Oh, woops
[04:41] <Mithrandir> Hobbsee: ogra is scary when he wears his short shorts. :-P
[04:41] <bddebian> hehe
[04:41] <Hobbsee> Mithrandir: TMI!
[04:41] <ogra> Hobbsee, nah, but the assumption that doko could be scary to anyone is funny :)
[04:41] <Hobbsee> heh
[04:41] <zul> i probably dont want to visualize that...thanks :)
[04:41] <ogra> Mithrandir, i thought only for elmo :P
[04:41] <Hobbsee> ogra: he's scary to me, as i've never spoken to him.  well, maybe once.  and he's very high up.
[04:42] <Hobbsee> Mithrandir: i'm of the opinion that most, if not all, guys are scary when they wear short shorts :P
[04:43] <doko> hmm ... do I have to understand
[04:43] <Hobbsee> uh oh, i thought doko wasnt in here...
[04:44] <ogra> heh
[04:45] <Mithrandir> Hobbsee: heh.  There's short shorts and there's _short_ shorts.  If you get what I mean. ;-)
[04:45] <ogra> Mithrandir, btw these are not my shortest ones ...
[04:45] <Mithrandir> ogra: T.M.I.
[04:45] <Hobbsee> Mithrandir: yeah, unfortunately i do get what you mean.
[04:45] <Hobbsee> definetly TMI.
[04:46] <Arbiter> hey slomo :)
[05:03] <CarlFK> I am making a generic version of https://help.ubuntu.com/community/BuildingWineFromSource
[05:04] <CarlFK> "Install additional libraries" - what is the proper way to figure out that list?
[05:08] <shawarma> Whenever i try to build something in my Edgy pbuilder that uses python2.3, I get some errors related to this python-central thing... Is there a simple fix?
[05:08] <bddebian> shawarma: python2.3 is broken
[05:09] <shawarma> bddebian: Oh, joy.
[05:09] <bddebian> And if it uses python-central, it shouldn't be requiring 2.3
[05:09] <bddebian> It should only pull the versions that we have that work
[05:10] <shawarma> bddebian: How can I tell if it's using it? A build-dep?
[05:11] <bddebian> shawarma: Could be a build-dep or maybe in rules, etc
[05:14] <shawarma> bddebian: Hmm.... Where can I find some info about it? The infamous python policy?
[05:15] <bddebian> shawarma: http://wiki.debian.org/DebianPython/NewPolicy
[05:18] <bddebian> dholbach: ping?
[05:19] <dholbach> bddebian: pong
[05:21] <bddebian> dholbach: Any idea what's up with contacts?
[05:22] <dholbach> bddebian: can you elaborate?
[05:22] <bddebian> dholbach: I'm trying to finish off the manual merges in Universe
[05:22] <dholbach> bddebian: and? :)
[05:23] <bddebian> dholbach: Have you been "maintaining" it outside of Debian?
[05:23] <dholbach> bddebian: i never did an upload to debian
[05:24] <dholbach> i don't know what you mean?
[05:24] <tseng> he means you have one version, debian has another, and they arent even close
[05:24] <bddebian> dholbach: Well it's in Debian now, I guess that is my question :-)
[05:24] <dholbach> if you ask me, if you can sync it from Debian - yeah that's fine with me, if it builds, installs and installs the same files :)
[05:24] <azeem> that's a fact, not a question
[05:24] <dholbach> i don't insist on maintainership of it, not at all
[05:26] <shawarma> bddebian: Hm... I changed the dependency from python2.3-dev to python2.4-dev. That did the trick.
[05:27] <bddebian> shawarma: If it is using python-central, the dep should just be python-dev
[05:27] <bddebian> I think
[05:27] <shawarma> bddebian: It's not using python-central.
[05:28] <bddebian> Oh
[05:28] <shawarma> bddebian: I just thought it did, beacuse it moaned about some pycentral stuff in my build logs.
[05:29] <bddebian> Then you should be fine.  Make sure that there weren't any /usr/lib/python2.3/... stuff in any .dirs, .install, rules, etc also :)
[05:30] <shawarma> bddebian: Right. Thanks.
[05:32] <Arbiter> package kdocker is coming for you dear MOTUs :D
[05:33] <Arbiter> Gloubiboulga, was colorscheme nuked?
[05:33] <Gloubiboulga> Arbiter, I don't know, I haven't re-checked
[05:33] <Arbiter> ow
[05:34] <Arbiter> Gloubiboulga, i've fixed the debian/changelog entry
[05:34] <Arbiter> (for agave)
[05:36] <Gloubiboulga> Arbiter, ok, I'll have a look
[05:36] <Gloubiboulga> later ;)
[05:37] <Arbiter> :)
[05:43] <bddebian> Hmm, contacts is missing a build-dep on zlib1g it seems
[05:45] <bddebian> Oh dumb-ass, wrong package
[05:45] <bddebian> I really think I need to quit :-(
[05:45] <Gloubiboulga> bah, don't worry, I've spent 3 hours on libexo bindings
[05:45] <Toadstool> :D
[05:45] <Gloubiboulga> and Toadstool found the solution for me :)
[05:45] <Gloubiboulga> in 3 minutes
[05:46] <Gloubiboulga> :D
[05:47] <Gloubiboulga> bddebian, ivman will need a merge anyway (/var/run stuff again)
[05:47] <bddebian> Gloubiboulga: OK, I'll leave it alone, thanks
[05:52] <Arbiter> i need reviews for: http://revu.tauware.de/details.py?upid=2745 && http://revu.tauware.de/details.py?upid=2776
[05:52] <Arbiter> thanks
[05:58] <Gloubiboulga> Arbiter, https://launchpad.net/distros/ubuntu/edgy/+queue?queue_state=0&queue_text=color, not yet rejected
[05:59] <Arbiter> aw
[05:59] <Arbiter> Gloubiboulga, can you review the two packages above? :)
[05:59] <Arbiter> (when you have some free time)
[06:00] <Gloubiboulga> Arbiter, I'd like to work on my packages first, but I will
[06:00] <Arbiter> gh
[06:00] <Arbiter> thanks :)
[06:00] <Gloubiboulga> (tomorrow maybe)
[06:00] <Arbiter> thanks a lot
[06:01] <Hobbsee> Arbiter: you got kdocker to work?  good job!
[06:01] <Arbiter> Hobbsee, yup :)
[06:02] <Arbiter> i've tried also a pbuilder build and seems to compile successfully
[06:02] <Hobbsee> Arbiter: It was downloaded from http://switch.dl.sourceforge.net/sourceforge/kdocker/kdocker-1.3.tar.gz <-- should be the site, not the direct link
[06:02] <Hobbsee> Arbiter: how did you avoid it not having a ./configure?
[06:02] <Arbiter> Hobbsee, it's qmake
[06:02] <Hobbsee> Arbiter: yeah, i saw that - i could never get it to work.
[06:02] <Arbiter> i've made a patch for kdocker.pro
[06:02] <Arbiter> (debian/patches)
[06:03] <Arbiter> Hobbsee, should i change it with something like kdocker.sourceforge.net?
[06:03] <Hobbsee> Arbiter: yes
[06:03] <Arbiter> wait a sec
[06:04] <bddebian> dholbach: We need an MOTU class on shlib deps :-)
[06:04] <Arbiter> Hobbsee, fixed & uploaded
[06:04] <Hobbsee> bddebian: we do, want to teach it?
[06:04] <Arbiter> just wait for revu sync
[06:05] <Hobbsee> Arbiter: why's the patch there?
[06:05] <bddebian> Hobbsee: If I had a clue, I'd love to :-)
[06:05] <Arbiter> Hobbsee, mh?
[06:05] <Hobbsee> bddebian: hah.  get a clue, and do it.
[06:05] <Hobbsee> Arbiter: the one for kdocker.pro - why not just specify the install path in debian/rules?
[06:05] <Arbiter> because it doesn't work :P
[06:06] <Arbiter> make DESTDIR="blahblah" install doesn't work :P
[06:06] <Hobbsee> hum.  okay
[06:06] <bddebian> dholbach: OK, contacts in debian depends {shlib:Depends}, {misc:Depends}, evolution-data-server, and your version just does shlib and misc depends.  You think it's still OK to sync?
[06:06] <raphink> anyone has got an idea why http://paste.ubuntu-nl.org/18788 doesn't run the clean rule after the install ?
[06:06] <raphink> :s
[06:06] <raphink> I'm sure it's a stupid mistake but I don't get it
[06:07] <raphink> Hobbsee, bddebian : any idea ?
[06:07] <raphink> or Gloubiboulga maybe
[06:07] <bddebian> ack, cdbs.. My eyes....
[06:07] <Hobbsee> raphink: presumably you dont need the kde.mk in there?
[06:08] <tseng> why would it run clean after install?
[06:08] <raphink> Hobbsee: there's no kde.mk
[06:08] <tseng> it normally runs clean on a fresh build attempt
[06:08] <raphink> tseng: well isn't the package supposed to be cleaned after build, too?
[06:08] <tseng> no?
[06:08] <raphink> :s
[06:08] <Hobbsee> raphink: well...yeah...
[06:09] <raphink> in all my packages, clean:: is called after the build
[06:09] <raphink> aswell as before
[06:09] <tseng> news to me.
[06:09] <Gloubiboulga> raphink, revu-report calls clean after the build :)
[06:09] <Gloubiboulga> not dpkg-buildpackage AFAIK
[06:09] <raphink> ah?
[06:09] <Gloubiboulga> yes, I think so
[06:09] <raphink>  you might be right :)
[06:09] <Gloubiboulga> hehe, you need some rest ;)
[06:10] <raphink> I guess
[06:11] <dholbach> bddebian: ok to sync yes, i'm not offended :)
[06:11] <bddebian> dholbach: OK, thx
[06:11] <bddebian> hub: You here?
[06:11] <hub> bddebian: I an
[06:12] <bddebian> hub: Are you an MOTU yet?
[06:12] <hub> bddebian: I am
[06:12] <bddebian> hub: Great.  Are you going to merge/sync gphotofs?
[06:12] <hub> why?
[06:13] <hub> there is a merge for it?
[06:13] <hub> I'll do it
[06:13] <bddebian> http://merges.ubuntu.com/universe-manual.html
[06:13] <hub> I haven't checked the merge list for sometime
[06:13] <hub> will do it
[06:13] <bddebian> Thanks
[06:13] <LaserJock> bddebian: yes?
[06:13] <bddebian> Heya LaserJock
[06:13] <LaserJock> Hobbsee: yes?
[06:13] <bddebian> Now I forgot :-(
[06:13] <hub> the patch lead to a 404
[06:13] <hub> ...
[06:14] <Hobbsee> LaserJock: dont worry, i found my answer.  hence the unping :P
[06:14] <LaserJock> ok
[06:14] <bddebian> LaserJock: Damn my short term memory, I can't remember :-(
[06:14] <hub> bddebian: https://patches.ubuntu.com/g/gphotofs/  does not exist
[06:14] <bddebian> Oh, yeah.  Is your science packages list updated automagically or do you have to manually refresh it?
[06:14] <hub> bddebian: so what can I do?
[06:14] <LaserJock> bddebian: manually
[06:15] <bddebian> Ah :-(
[06:15] <LaserJock> I try to do it most every day
[06:15] <bddebian> hub: Can you sync it?
[06:15] <bddebian> LaserJock: Well I've lost track of what I've done :-)
[06:15] <hub> bddebian: no. I don't know how to do that
[06:15] <hub> bddebian: unless I just grab Debian pkg and merge with Ubuntu and upload
[06:15] <bddebian> Yep
[06:16] <bddebian> If a merge is necessary.  If not, just request a sync on LP
[06:16] <hub> bddebian: ok
[06:16] <hub> bddebian: I'll do that this evening
[06:17] <hub> bddebian: I'v got to put some real work right now
[06:18] <bddebian> hub: No problem, thanks
[06:18] <raphink> shame on me
[06:18] <bddebian> Damn Hobbsee, I can't keep up with you.. :-)
[06:18] <Hobbsee> bddebian: hmmm?
[06:19] <bddebian> Hobbsee: Your uploads :-)
[06:19] <Hobbsee> bddebian: ahh :)
[06:19] <Hobbsee> bddebian: which ones were these?
[06:20] <bddebian> Hobbsee: Just in general
[06:21] <LaserJock> bddebian: ok, I just updated the list to the latest in the archives
[06:22] <hub> bddebian: I don't find in the wiki the procedure to request a sync
[06:23] <hub> bddebian: which component shall I file the LP request?
[06:23] <bddebian> LaserJock: Rockin', thanks d00d
[06:23] <tseng> file under the name of the package
[06:24] <tseng> no assignee
[06:24] <hub> ok
[06:24] <tseng> subscribe to ubuntu-archive
[06:24] <bddebian> Aye
[06:24] <tseng> 'please sync blah'
[06:24] <LaserJock> wiki.ubuntu.com/DeveloperDocumentation has a Sync section I believe
[06:25] <hub> search didn't find it
[06:25] <tseng> search is fairly useless
[06:41] <|alba|> Hi. I want to help, how do I start?
[06:42] <LaserJock> have you seen wiki.ubuntu.com/MOTU ?
[06:43] <LaserJock> perhaps you might be interested in wiki.ubuntu.com/MOTU/Mentors
[06:43] <|alba|> nope, i'll try the wiki. Is it important to have a mentor?
[06:45] <LaserJock> it's not neccessary
[06:45] <LaserJock> but the Mentors help you get you started
[06:45] <|alba|> Ok
[06:45] <LaserJock> you can also ask questions here too
[06:45] <dEn`> guys ..how do i use nmap with ubuntu, it sayd i need to be root. even though i did a sudo nmap
[06:45] <LaserJock> dEn`: please try #ubuntu
[06:46] <dEn`> okay thanks
[06:47] <shawarma> Gloubiboulga: Did you save the url for that asterisk patch or should I toss it at someone else?
[06:57] <Gloubiboulga> shawarma, it's uploaded ;)
[06:57] <shawarma> Wow!
[06:57] <shawarma> Gloubiboulga: thanks!
[06:57] <Gloubiboulga> thanks you :)
[06:57] <Gloubiboulga> thank*
[06:57] <shawarma> Gloubiboulga: I got one more.
[06:58] <Gloubiboulga> shawarma, could you ping me tomorrow for it?
[06:58] <Gloubiboulga> I'm afraid I won't have time tonight
[06:58] <shawarma> Gloubiboulga: http://www.linux2go.dk/edgy-merges/bacula-merge.diff
[06:59] <shawarma> Gloubiboulga: Oh, right. No problem.
[06:59] <Gloubiboulga> or find an other uploader ;)
[07:00] <shawarma> I could do that. :-)
[07:00] <LaserJock> shawarma: I dont' see "added ${shlibs:Depends} dependency to bacula-director-pgsql " in the debdiff
[07:02] <shawarma> LaserJock: wtf... You're right.
[07:03] <LaserJock> maybe that was taken care of upstream?
[07:03] <shawarma> I clearly remember adding it..
[07:04] <shawarma> Weirdness. gimme a minute.
[07:09] <shawarma> LaserJock: Ah... I know why..
[07:12] <shawarma> LaserJock: Don't ask. :-)
[07:12] <Hobbsee> shawarma: i'm asking - what happened?
[07:14] <shawarma> Hobbsee: Gah... I did a dpkg-buildpackage at one point without editing the changelog, so the actual debian diff.gz was overwritten. Then I corrected the changelog, did some other changes, ran dpkg-buildpackage again and made my debdiff..
[07:15] <Hobbsee> shawarma: ahh...right
[07:15] <shawarma> Hobbsee_: so the debdiff was between two revisions I've made, neither of which are the original debian version. Now I just need to find out how much I had done before that.
[07:15] <Hobbsee> yep
[07:15] <Hobbsee> heh
[07:17] <CarlFK> how come apt-get source jigdo; dpkg-buildpackage made 2 .debs?
[07:17] <CarlFK> jigdo and jigdo-file
[07:17] <LaserJock> because there are 2 packages produced from the source :-)
[07:18] <LaserJock> look at debian/control
[07:18] <LaserJock> ah, stink.  You're referring to someone else methinks.
[07:49] <CarlFK> bluefoxicy: thanks - I like vanilla
[07:53] <bluefoxicy> some windows guy asked me why all linux programs have a perverse sense of humor
[07:54] <CarlFK> win apps do too, it just isn't funny :)
[07:54] <bluefoxicy> heh
[07:55] <bluefoxicy> well, I told him that the config app wasn't joking when it said he really, really, really needed to fix his config so his password database didn't have to be world-readable
[08:05] <CarlFK> what drives the name of the deb that dpkg-buildpackage makes?  debian/files ?
[08:06] <crimsun> it's actually debian/changelog
[08:06] <crimsun> well, actually we need a more precise question
[08:07] <crimsun> the version comes from debian/changelog; the names of the binary debs come from debian/control
[08:08] <CarlFK> that  makes sense
[08:24] <bddebian> Heya crimsun
[08:25] <crimsun> hi bddebian
[08:26] <lucas> slomo: ping ,
[08:26] <lucas> ?
[08:30] <bddebian> crimsun: Feel like axiom? :-)
[08:30] <crimsun> I feel like a sauna
[08:32] <CarlFK> dpkg -i foo.deb wants a bunch of deps - is there some easy way to apt-get them all?
[08:32] <LaserJock> bddebian: last I saw hell hadn't froze over ;-)
[08:32] <LaserJock> apt-get -f install
[08:32] <LaserJock> or use gdebi to install the .deb
[08:34] <bddebian> LaserJock: Bah, bunch of sissies :-)
[08:34] <LaserJock> bddebian: we just want our ponies
[08:34] <zul> screw ponies i want alcohol ;)
[08:36] <bddebian> You want to get drunk and screw ponies?
[08:37] <LaserJock> wow
[08:37] <zul> bddebian: that was uncalled for
[08:37] <CarlFK> how would I use apt-get -f install?
[08:38] <CarlFK> (with a local .deb file )
[08:40] <tseng> dpkg -i foo.db
[08:40] <tseng> apt-get -f install
[08:40] <tseng> if you are asking what I think
[08:40] <CarlFK> maybe :)
[08:40] <bddebian> yes
[08:40] <tseng> bddebian: that was a bit off the wall, I think.
[08:41] <bddebian> ?
[08:41] <tseng> sigh.
[08:42] <CarlFK> apt-get -f install; The following packages will be REMOVED:
[08:43] <tseng> sounds like you did something you shouldn't have
[08:43] <tseng> what did you install?
[08:44] <CarlFK> jigdo_0.7.3_i386.deb
[08:44] <tseng> erm.
[08:44] <CarlFK> that I just made out of 7.2's debian/ and 7.3s tarball
[08:44] <tseng> what does it want to remove?
[08:45] <CarlFK> jigdo
[08:45] <tseng> ok.
[08:47] <bddebian> LaserJock: So /kick me :-)
[08:47] <LaserJock> bddebian: you know I couldn't do that, I'd have to let tseng or zul :-)
[08:47] <tseng> I would love to kick him
[08:48] <tseng> but I don't see a reason to
[08:49] <bddebian> You want me to leave?  I can leave.
[08:50] <zul> i dont have ops
[08:50] <LaserJock> bddebian: don't leave, just try to play nice ;-)
[08:51] <tseng> everyone has ops
[08:51] <tseng> you can come in off the street and op if you were so bold
[08:51] <zul> hmm....ill remmeber that next time
[08:52] <zul> tseng: it was an unforutnate comment though
[08:53] <LaserJock> oh for goodness sakes
[08:58] <LaserJock> hmm, I wonder what my chances of getting thrashed by ubuntu-archive is
[08:58] <LaserJock> I filed 6 bugs about packages that have changed section in Debian
[08:59] <tseng> i have never been "thrashed" by any member of ubuntu-archive
[08:59] <tseng> only politely told I was wrong
[08:59] <LaserJock> true, me neither
[09:00] <LaserJock> Kamion seemed to indicate it was OK, I just feel sorta bad when they are so busy and it is a fairly minor thing
[09:00] <LaserJock> I guess they are free to ignore the bugs until they have time to deal with them
[09:01] <zul> most likely
[09:02] <LaserJock> it makes my life a fair amount easier if they are in the right section
[09:10] <CarlFK> my jigdo dep mess: http://paste.ubuntu-nl.org/18798
[09:11] <CarlFK> that is using a .deb made from apt-get source, not the tarball
[09:13] <LaserJock> CarlFK: did you grab the edgy source and try to install on Dapper?
[09:13] <CarlFK> hmm - close.  dapper source, insatll on breezy
[09:14] <LaserJock> oh my
[09:14] <LaserJock> did you build it on breezy?
[09:14] <CarlFK> no, build on dapper
[09:14] <LaserJock> ok, well if you build on Dapper and then try to install on Breezy you are going to have problems like that
[09:15] <CarlFK> starting to think it is time to up update the breezy box
[09:15] <LaserJock> you can try grabing the Dapper source and build on breezy and then install on breezy
[09:15] <LaserJock> but you need to build and install with the same release to get the deps right
[09:17] <CarlFK> thanks for the help
[09:18] <CarlFK> heh - make that build on dapper, install on hoary
[09:20] <LaserJock> oh jeeze
[09:20] <CarlFK> yup
[09:27] <shawarma> LaserJock: That should do it: http://www.linux2go.dk/edgy-merges/bacula-merge.diff
[09:27] <shawarma> bbiab
[09:41] <slomo> lucas: still there?
[09:42] <lucas> yes
[09:42] <lucas> my connection was reset earlier, so if you told me something, I might have missed it
[09:42] <slomo> ok... do you have some time in the next days to make a ubuntu<->debian-multimedia.org comparison page like you did for ubuntu<->debian?
[09:43] <lucas> yes, just replying an email and I'm on it
[09:51] <lucas> any french speaking MOTU who know REVU well around ?
[10:10] <lucas> it's really impressive how bzr can take ages to commit a single small file ...
[10:10] <tseng> lucas: its knitting :)
[10:13] <slomo> tseng: ?
[10:13] <lucas> arg, I made a typo. let's commit again
[10:14] <lucas> bzr: the tool that makes you HATE typos.
[10:14] <LaserJock> tseng: yeah, but my wife is faster at knitting then bzr is
[10:14] <micahcowan> as a non-bzr-user, what about bzr use makes you hate typos?
[10:15] <lucas> micahcowan: committing takes a huge amount of time and is not function of the size of the change you are committing
[10:19] <micahcowan> lucas: function of number of distributed repositories (unsure how it works)?
[10:19] <lucas> no
[10:19] <lucas> maybe it's function of the repository size
[10:20] <lucas> but my repository is small
[11:05] <bddebian> How the hell can just adding dh_install and dh_desktop cause a package to FTBFS?
[11:06] <LaserJock> perhaps the deps have changed?
[11:06] <LaserJock> from the last time it was built?
[11:07] <sharms> bddebian: sounds like fun :)
[11:12] <crimsun> check debian/*.install
[11:18] <bddebian> LaserJock: The debian package builds clean.  As soon as I add dh_install debian/foo.deskop usr/share/applications and dh_desktop it blows
[11:19] <mhz> hi there
[11:19] <mhz> anyone here in charge of schooltool?
[11:21] <bddebian> crimsun: What would I look for?
[11:22] <crimsun> bddebian: post the build log, please
[11:23] <bddebian> crimsun: You want the whole thing or just the last few lines?
[11:24] <crimsun> the whole thing.
[11:24] <bddebian> Hmm
[11:27] <bddebian> Oh, I see why it's failing but I don't get why the debian package fails
[11:27] <bddebian> Err works
[11:28] <bddebian> rules:  mv debian/grace6/usr/bin/xmgrace-5.99.1 debian/grace6/usr/bin/xmgrace6
[11:28] <bddebian> grace6.install usr/share/grace6/bin/xmgrace-5.99.1             usr/bin
[11:34] <Riddell> rraphink: ping
[11:38] <crimsun> bddebian: .install looks odd.
[11:38] <bddebian> crimsun: Yeah
[11:39] <crimsun> bddebian: meaning "if it already does it in rules, why call dh_install?"
[11:39] <crimsun> not to mention that should probably be debian/usr/share/grace6/bin/xmgrace-5.99.1 in .install
[11:40] <bddebian> crimsun: I added the dh_install to install the desktop file but I changed it to install -d and install -m instead
[11:41] <crimsun> bddebian: my guess is that if both the rules command is active and dh_install is called, then it's bailing on dh_install because the origin isn't valid in .install at that point (it has already been moved)
[11:41] <bddebian> Aye
[11:42] <crimsun> although upon closer inspection, the .install moves from debian/grace6/usr/share/ ?
[11:42] <bddebian> Yep, install -d and -m worked
[11:42] <bddebian> Yeah, it's got some issues
[11:42] <crimsun> right, that means the .install is fubar
[11:43] <bddebian> Yep
[11:43] <crimsun> invalid origin most probably
[11:43] <crimsun> usr/share vs. usr/bin
[11:43] <bddebian> Aye
[11:43] <bddebian> I'd better head home.  Thanks for your help!
[11:46] <crimsun> np, thank you
[12:03] <zul> hey
[12:05] <LaserJock> hi
[12:05] <zul> how is it going laserjock?
[12:05] <LaserJock> oh, it's going ok
[12:05] <LaserJock> trying to clean up my email


[00:12] <psidrum> is there a RSS Lens for Unity?
[00:19] <popey> psidrum, there's a news one, I've not seen an rss one
[00:24] <bobweaver> psidrum,  you could write one is there a site that you are looking to get rss or like a lens that is all you bookmarked rss ?
[01:22] <bobweaver> I have a question and need help
[01:23] <bobweaver> Now that everything is getting ported to NUX how is the phone and or the tv going to work
[01:23] <Daekdroom> What do you mean by getting ported to Nux?
[01:23] <bobweaver> you know one phone = one ubuntu = desktop = tv = UbuntuOne ?
[01:24] <bobweaver> Like  I hear that all QT is beeing droped
[01:24] <bobweaver> sorry about my spelling
[01:24] <Daekdroom> You mean unity-2d being dropped and there only being Unity (which uses Nux)
[01:25] <Daekdroom> Well, Unity (and Nux and Compiz) are being ported to Open GL ES, which is more common in TVs and phones than Open GL
[01:25] <bobweaver> Yes but there are so many things that are offered for QT and other things that are offered with NUX as NUX is just a lib it can have a declaritive view correct ?
[01:25] <Daekdroom> (as a matter of fact, Open GL ES was created having embedded systems.
[01:26] <Daekdroom> It's not that everything is getting ported to Nux.
[01:26] <Daekdroom> It's only Unity.
[01:26] <bobweaver> That is awesome but how to make QTmoblity and other declaritive views happen ?
[01:26] <bobweaver> as nux is c++ it can be exported
[01:27] <Daekdroom> I think I've misunderstood your question :/
[01:27] <bobweaver> sorry about my spelling 75 % of inter-action is body lang
[01:28] <bobweaver> this is what I mean IF Ubuntu tv and Ubutnu Phone use which they do 2d
[01:28] <bobweaver> which is qml
[01:28] <bobweaver> which calls declaritive views for c++ why not keep that on the burner so to say
[01:28] <Daekdroom> That's for the Unity interface.
[01:29] <Daekdroom> That does not mean developers won't be able to use QML for apps.
[01:29] <bobweaver> but say I can make massive things happen
[01:29] <bobweaver> like this
[01:30] <bobweaver> http://www.youtube.com/watch?v=KMgQpS8F6_o&feature=g-upl
[01:30] <bobweaver> How can I plug that into Unity with no 2d ?
[01:32] <Daekdroom> I'm sure that if they want developers to be able to do that, they'll provide an API or something.
[01:32] <Daekdroom> So far Ubuntu TV is a prototype.
[01:32] <bobweaver> you see what I am saying about the phone and the tv and the desktop thou
[01:33] <bobweaver> as symbian is well symbian will Nux run on symbian
[01:34] <bobweaver> sorry it took me a week to get hello world app
[01:34] <bobweaver> kinda new to NUX lib seems like gamers lib cool stuff
[01:36] <bobweaver> Daekdroom,  if the phone code was there for me to see I would be doing the same thing. err . how to explain . Like if I had the code I woud plug everything in real real fast to be like I talked about abov
[01:37] <bobweaver> because it is qt
[01:37] <Daekdroom> So you concern is about not being able to do those things when there's no QT?
[01:38] <bobweaver> because it is simple there are many advantages to qt as I am sure that there are for NUX also . but what I dont get is that the Ubutnu 2d uses NUX and that is just a c++ lib that is called in build
[01:38] <bobweaver> correct aboout the QT part
[01:38] <bobweaver> is there something going on that I do not know about
[01:38] <bobweaver> with money or something and nokia ?
[01:39] <bobweaver> just a guess plz take it that way no harm
[01:39] <Daekdroom> As far as I know, they decided to drop Unity-2D because it was taking too much effort to develop Unity, which uses Nux, and Unity2D, which uses QT, while they shared little code.
[01:39] <bobweaver> Like ever sense the Whole building thing things have been alot different
[01:40] <bobweaver> what If I could take up slax ?
[01:40] <bobweaver> who to talk to ?
[01:40] <Daekdroom> I have no idea, honestly.
[01:40] <bobweaver> I would love LOVE LOVE to port Unity 6.0 Nux3.0 QT5.0
[01:41] <bobweaver> as I think that compiz is being under utilzed
[01:42] <bobweaver> like if there was a #import Compiz 1.0   Somethis{}add states and transtions and call compiz in the states and transtions
[01:42] <bobweaver> onclicked: if this and that
[01:44] <bobweaver> It Just seems foolish to drop such a great lib unless... there is a excusse me here a "pissing contest " going on one again 70 some % of communication is body lang
[01:44] <bobweaver> plz dont take this the wrong way just questions
[01:46] <Daekdroom> Well, Unity-2D seemed to me like something that was always attempting to catch up to Unity(3D), so I wasn't surprised by seeing 2D getting drooped.
[01:46] <Daekdroom> It was a fallback version for those who did not have video acceleration to use Unity.
[01:47] <Daekdroom> Otherwise, using QT to make Unity wouldn't have been the choice, in my opinion.
[01:49] <Daekdroom> If they created Nux so they could develop Unity, I think there must have been something the libs that already existed did not offer.
[03:04] <bobweaver> IMHO it is the other way around that makes a great circle there are many things taht you can do in QT that you can not do in NUX one of them being declaritive views and the other formfactors
[03:04] <bobweaver> and also rendering might have been behind but it is kinda loopy in a way
[03:05] <bobweaver> Looks like clues lead to ........
[07:33] <MCR1> Is jenkins unity building somehow broken ?
[07:33] <MCR1> cd /home/ubuntu/jenkins/workspace/unity-ci/distribution/quantal/flavor/amd64/pbuilder_setup/work/trunk/obj-x86_64-linux-gnu/plugins/unityshell && cat /home/ubuntu/jenkins/workspace/unity-ci/distribution/quantal/flavor/amd64/pbuilder_setup/work/trunk/plugins/unityshell/unityshell.xml.in | sed -e "'s" "<_" < "g'" -e "'s" "</_" "</" "g'" > /home/ubuntu/jenkins/workspace/unity-ci/distribution/quantal/flavor/amd64/pbuilder_setup/work/trunk/obj-x
[07:33] <MCR1> /bin/sh: 1: cannot open g': No such file
[07:36] <mmrazik> MCR1: yes, it is. I'm looking into it
[07:41] <MCR1> mmrazik: I just tried to build Unity/nux with a script that usually worked, but now it failed with this error, maybe it is related:
[07:41] <MCR1> -- checking for module 'unity-protocol-private'
[07:41] <MCR1> --   package 'unity-protocol-private' not found
[07:41] <mmrazik> MCR1: that is something else. You need an up-to-date version of libunity
[07:42] <mmrazik> should be available in the staging ppa
[07:42] <MCR1> mmrazik: oh, ok - thx.
[07:42] <mmrazik> (but right now when you do dist-upgrade with staging PPA it will remove unity so be aware)
[07:44] <MCR1> mmrazik: I am currently logging into a custom Compiz-Standalone session, combined with Unity-2d - but thanks for the warning :)
[08:27] <MCR1> duflu: Hi! GREAT work on Compiz :) - it is getting smoother every day. I know you are working hard on the GLES branch, but it would be nice if you could take a short look at: https://code.launchpad.net/~mc-return/compiz/compiz.merge-plugin-simple-animations/+merge/115048 and https://code.launchpad.net/~mc-return/compiz/compiz.merge-plugin-wizard/+merge/111565
[08:29] <duflu> MCR1: Thanks. Though if you build the gles2 branch you might notice a few plugins and animations don't build or work in there. I want to get gles2 finished and merged to lp:compiz before considering any more of your plugin proposals. AFAIK, the most recent ones that were accepted don't work with gles2 :(
[08:29] <duflu> Making just the plugins used by Unity default profile work is the first priority.
[08:31] <MCR1> duflu: My fear is that I came one year to late with my merge proposals, because I did not check the Compiz move to launchpad :( - I understand that my timing is not the best :(
[08:32] <duflu> MCR1: That's not your fault. Both repos were being actively used simultaneously for a while. It was very confusing.
[08:34] <MCR1> duflu: Yes, I was still subscribed to the RSS git feed and was quite worried, because the rate of commits there was so low - and no action at all @ compiz-dev.
[08:34] <MCR1> duflu: But I am happy that Compiz is alive - more than in the last years :)
[08:35] <MCR1> *@ #compiz-dev
[08:36] <MCR1> duflu: So your work and engagement is highly appreciated (by me at least) - thanks for making Compiz what it should be :)
[08:37] <duflu> MCR1: No problem. Have you tried the gles2 branch?
[08:39] <brendand> i'm all of a sudden unable to run 3d: http://paste.ubuntu.com/1111556/
[08:39] <brendand> think it's related to a failed installation of fglrx
[08:39] <brendand> either that or a kernel upgrade
[08:39] <brendand> most likely the former
[08:40] <MCR1> duflu: Although when I see the bug reports of the GLES branch I can smell a lot of new troubles... No, I have not tried it yet, although I promised smspillaz to test it, but I am quite happy my special config (which is complicated enough as you know) works now... and I fear to touch a running system ;)
[08:41] <duflu> brendand: I think that can happen when the fglrx installer/uninstaller gets different libGL's mixed up. Try uninstalling fglrx and forcefully reinstalling it.
[08:41] <brendand> duflu, that's the thing. it's not installed. it failed
[08:41] <duflu> Ah OK. Simple then
[08:41] <brendand> although the package is
[08:42] <brendand> but jockey says the driver is not
[08:42] <MCR1> duflu: But if there is an easy way of switching between those branches (without f*cking up what I have installed) - I would like to help you with testing and minor fixes ofc.
[08:42] <duflu> brandand: Older versions of fglrx had broken uninstallation leaving the wrong libGL installed. You need to force reinstall of the mesa packages to get the right one back
[08:43] <duflu> MCR1: Fast and safe switching between branches only works if you can easily compile from source. And even then, it's only simple if you're also willing to recompile unity, or live without unity while testing :(
[08:43] <MCR1> duflu: But currently I am building lp:compiz and then copying the built stuff per hand, because I have not checked that (yet): https://answers.launchpad.net/compiz/+question/203490
[08:48] <duflu> MCR1: Answer added
[08:50] <duflu> brendand: Older versions of fglrx had broken uninstallation leaving the wrong libGL installed. You need to force reinstall of the mesa packages to get the right one back
[08:50] <MCR1> duflu: The problem here is that Compiz behaves completely different without Unity-3d (I am currently running Unity-2d with Compiz), but I just fixed my script to automatically update and compile and install Unity-3d (in my home dir) again, so if I gain the knowledge how to run a parallel installation of a compiled lp:compiz - Oh thanks - exactly what I needed :)
[08:51] <duflu> MCR1: When building a new unity for your custom compiz you need:   env PKG_CONFIG_PATH=~/staging/lib/pkgconfig cmake ........
[08:55] <MCR1> duflu: This is the script I am currently using to build Unity - I will try to extend that to also build lp:compiz...
[08:56] <MCR1> duflu: http://pastebin.com/d4DnWM1Z
[08:56] <MCR1> duflu: Now I'll stop stealing your time ;) Thanks again.
[08:57] <MCR1> duflu: I should have all the info I need now :)
[12:53] <sil2100> mhr3: regarding unity lenses and the new vala - since I'm not a vala coder, I don't know this for sure, but...
[12:54] <sil2100> mhr3: or maybe wait, hm, forget about my question-to-be-asked
[14:28] <sil2100> jaytaoko: ping
[14:30] <jaytaoko> sil2100: hello, in a meeting, will ping you after
[14:32] <sil2100> jaytaoko: ok, thanks!
[14:54] <jaytaoko> sil2100: hello
[14:56] <sil2100> jaytaoko: hi! :)
[14:57] <sil2100> jaytaoko: I would like to release the nux SRU right now, it's something that is a requirement for the regionalDamage changes to be ported to precise for unity
[14:57] <jaytaoko> sil2100: I have tested it and approved it
[14:58] <sil2100> jaytaoko: we already tested the changes and it's all green, but I would actually like to know your opinion whether you think we should release it as patches, or release a new tarball (and bump the nux version)
[14:58] <sil2100> Since right now I did it as a distro release
[14:58] <sil2100> (no new tarball)
[14:59] <jaytaoko> sil2100: let me ask didrocks or seb128
[15:00] <sil2100> jaytaoko: ok ;)
[15:00] <jaytaoko> sil2100: but tell me, what is your opinion on this?
[15:00] <sil2100> jaytaoko: they're on some conference now from what I know, but just give me a sign
[15:01] <gord> GUADEC right? won't see them till next week i think
[15:01] <jaytaoko> sil2100: is this an emergency? or can we wait for their feedbacks?
[15:01] <mhr3> sil2100, sooo... i'm not sure if you were actually asking something... were you? :)
[15:01] <sil2100> jaytaoko: personally, well, we _could_ do a new tarball, but the diff is not that big
[15:02] <jaytaoko> gord: thanks for the info
[15:02] <sil2100> mhr3: I wanted, but then I understood that my question was stupid, so I didn't ;p
[15:02] <mhr3> lol, ok
[15:02] <sil2100> jaytaoko: I would like to release it this week, since next week we need to land the unity regionalDamage changes and SRU it
[15:03] <jaytaoko> sil2100: so if you do a patch you won't be upgrading the release number, is that correct?
[15:03] <sil2100> jaytaoko: I was asking you, since I just wanted to know if you had any particular plans for what needs to land for nux 2.14
[15:03] <sil2100> jaytaoko: correct - just the ubuntu number
[15:04] <sil2100> So it will be nux 2.12.0-0ubuntu2
[15:05] <jaytaoko> sil2100: let me have a look at what went into the SRU again...
[15:05] <sil2100> jaytaoko: http://bazaar.launchpad.net/~unity-team/nux/2.0/revision/616 <- here is the revision
[15:06] <sil2100> It seems 618, 619, 621, 622, 623, 624, 631 commits were imported, which is quite big - but the overall diff is not super big
[15:08] <jaytaoko> sil2100: ok, I think a patch should do. What about unity? are you changing the version for it?
[15:09] <mhr3> sil2100, was the packaging updated yet to use 0.16?
[15:09] <mhr3> it's taking a while considering it's a oneliner ;)
[15:10] <mhr3> but maybe it's not, what do i know
[15:10] <sil2100> mhr3: its taking a while since didrocks is not around - and I had this power shortage
[15:11] <sil2100> mhr3: Didier wanted me to change something, so I did - I just need to send him an e-mail
[15:12] <sil2100> mhr3: so you'll have it by tomorrow morning, I promise! ;)
[15:12] <sil2100> jaytaoko: hm, we're not sure yet - I think we'll only be distro-patching for unity
[15:12] <sil2100> jaytaoko: since we'll probably be only releasing an SRU that includes the regionalDamage fixes
[15:13] <sil2100> jaytaoko: so the rest that is supposed to land will land later, with a new tarball
[15:13] <jaytaoko> sil2100: ok. So fine then for a patch for the nux SRU
[15:14] <mhr3> sil2100, cool, i once took a month to investigate a bug that was in end fixed by changing a ">" to ">=", so it's not that bad yet i guess :D
[15:14] <sil2100> jaytaoko: ACK! Thanks - I'll try contacting Didier later as well
[15:14] <sil2100> mhr3: hehe ;)
[15:15] <mhr3> and when i did they told me the license for what it was using expired a month ago :P
[15:36] <seb128> sil2100, jaytaoko: hey
[15:37] <seb128> sil2100, jaytaoko: I read the backlog, Didier says a tarball would be better
[15:37] <seb128> sil2100, jaytaoko: if you need to reach us use email rather this week since we are not a lot online during GUADEC
[15:39] <jaytaoko> seb128: ok
[15:40] <jaytaoko> sil2100: so, tarball it is!
[15:40] <jaytaoko> seb128: enjoy Guadec!
[15:40] <sil2100> jaytaoko, seb128: ACK! :)
[15:40] <seb128> jaytaoko, thanks
[16:18] <sil2100> mhr3: valac distro changes pushed - I approved the merge requests ;)
[16:19] <mhr3> sil2100, but, but, it was supposed to happen tomorrow :P
[16:19] <mhr3> sil2100, thanks :)
[16:23] <sil2100> hehe
[16:23] <sil2100> Didier was quick to act with pushing my changes ;)
[17:18] <carl1> where could I get info about how to publish unity menus without use GApplication?