[08:05] <huats> morning
[10:36] <Riddell> kenvandine: how are you getting on with the new libindicate?
[10:37] <asac> lool: where do i put reviews for the eucalyptus MIR?
[10:37] <asac> lool: the wiki table has no column for comments of reviewer ... or should i use the reviewneeded column like:
[10:37] <asac> problems: 1. asdasd 2. qweq
[10:38] <asac> sorry, but wasnt at the meeting ;)
[10:39] <asac> lool: also there are packages not listed in any MIR set
[10:39] <asac> e.g. antlr
[10:39] <asac> does that mean they are just needed without any reason?
[10:39] <asac> i mean: do we assume that there is a real reason for a package even though we dont have a rational?
[10:40] <lool> asac: Either put in Status or add a column
[10:41] <lool> asac: The packages with 0 on the left column are the ones which the next version of eucalyptus will depend on
[10:42] <asac> lool: so our java spec feels a bit outdated ... debian spec says: "java libraries MUST not depend on any runtime (effectivly we drop the runtime dependency) "
[10:42] <asac> our spec still wants -headless et al
[10:42] <asac> https://wiki.ubuntu.com/JavaTeam/LibraryPackaging
[10:43] <asac> anyway. i guess its ok to still depend on it
[10:44] <lool> asac: Hmm you might want to ping doko about it
[10:44] <lool> He has good understanding on how the Debian versus Ubuntu policies relate
[10:44] <asac> yeah will do
[10:45] <asac> lool: i also have asm3 on my system, so i will probably review that. if you wanted to have it explicitly let me know ;)
[10:45] <lool> Oh no feel free!
[10:45] <asac> i will add your nick to the next topmost one in turn ;)
[10:46] <lool> eh
[10:46] <Riddell> ooh asac is onto MIRs, don't forget mine :)
[10:57] <asac> hehe
[11:43] <MadsRH> Does anyone know anything about PackageKid? I was hoping to see Richard Hughes's UI work land in Karmic: http://blogs.gnome.org/hughsie/2009/04/14/gnome-packagekit-updates/
[11:46] <asac> lool: did you read my question about rational?
[11:47] <asac> i have not libconcurrent-java .... doesnt even have a rdepends ;)
[11:47] <asac> hmm
[11:47] <asac> maybe thats how java is ;)
[11:47] <asac> let me check Sources
[11:49] <asac> lool: ok found it ... its build-dep for libaspectwerkz2-java
[11:49] <asac> will document it there
[11:54] <lool> asac: Just replied
[11:54] <lool> asac: There's rationale between [] on some packages
[11:54] <lool> Otherwise it's just deps of euca
[11:54] <asac> lool: i saw the [] ... (though i missed it for this one because i was in edit mode )
[11:55] <asac> lool: question is mostly about the top level packages (with depend count 0)
[11:55] <asac> but i will check your reply
[11:56] <lool> asac: These are deps of the eucalpytus upstream version we intend to ship in karmic
[11:56] <lool> According to the eucalyptus upstream folks
[11:56] <asac> lool: ok lets do a component-mismatches step after fiinishing 0 and 1
[11:57] <asac> err 3,2,1 ;)
[11:57] <asac> might be that we review something for nothing though ... if a 0 depends on a 1 and 0 isnt required ;)
[11:58] <lool> asac: Yes, its the risk with the whole list
[11:59] <lool> asac: The packages were "unconfirmed" until recently; I didnt assign any unconfirmed packages though
[11:59] <asac> what does "unconfirmed" mean ;)?
[12:01] <lool> asac: It meant we werent sure whether it would be required
[12:01]  * lool lunch &
[12:39] <asac> lool: also doing easymock and trove now
[12:40] <asac> lool: btw, i baiscally approve under assumption that bugs are fixed that i file and document. i guess thats ok so we dont need re-submission et al
[12:46] <lool> asac: its fine with the bugs noted in the wiki page imo
[12:51] <asac> lool: also grabbing jrexx and
[12:51] <asac> libjoda-time-java
[12:53]  * lool is impressed
[13:32] <asac> lool: all 3 and 2 are done \o/
[13:32] <asac> i will send a mail later about a quick review list for java packages
[13:32] <asac> based on the questions doko answered
[13:58] <lool> asac: Thanks a lot!  ttx will be more relaxed now  ;)
[14:01] <rodrigo_> wow, nice -> http://nlokos.blogspot.com/2009/08/crossing-finish-line.html
[14:01] <rodrigo_> when are we getting that packaged? :D
[14:02] <kenvandine> i saw that live at guadec
[14:02] <kenvandine> it was cool
[15:20] <statik>  bratsche, i believe the bzr-search plugin can search through history
[15:32] <kenvandine> Riddell, are you blocked on libindicate?
[15:32] <kenvandine> i have some other more pressing things... but libindicate is on my todo list
[15:33] <Riddell> kenvandine: one of my todo items is, I also have other more pressing things :)
[15:33] <kenvandine> Riddell, ok... :)
[15:33] <kenvandine> Riddell, how is the indicator stuff in kde looking?
[15:36] <Riddell> dunno, it's waiting on new libindicate :)
[15:36] <Riddell> well, kmail is
[15:36] <Riddell> konversation is working well
[15:40] <kenvandine> Riddell, awesome
[15:44] <chrisccoulson> does anyone else have to keep signing on with launchpad everytime they want to use it?
[15:53] <Laney> chrisccoulson: yeah it's happened to me a few times
[15:55] <chrisccoulson> Laney - glad it's not just me then ;)
[15:56] <chrisccoulson> it really is a PITA
[15:56] <Laney> slangasek mentioned it too
[15:56]  * Laney pinged #lp
[15:56] <chrisccoulson> Laney - thanks
[15:56] <chrisccoulson> right, back to work for me
[15:56] <Laney> that's no fun :(
[15:57] <chrisccoulson> it's definately no fun ;)
[15:57] <chrisccoulson> thats why i spend most of my time on here
[16:51] <rodrigo_> how can I add some gconf keys values on package installation?
[17:05] <chrisccoulson> rodrigo_ - you want to set some gconf keys by default on install right?
[17:05] <chrisccoulson> to do that, you can ship a gconf-defaults file in debian/ (or <package_name>-gconf-defaults)
[17:05] <chrisccoulson> with key/value pairs in
[17:06] <chrisccoulson> and make a call to dh_gconf in debian/rules
[17:06] <rodrigo_> ah, cool
[17:06] <rodrigo_> chrisccoulson: thanks
[17:06] <chrisccoulson> if you're using cdbs and already include the gnome class, then that already takes care of the dh_gconf call i think
[17:15] <rodrigo_> ok
[17:16] <hyperair> you mean package.gconf-defaults, not package-gconf-defaults.
[17:18] <chrisccoulson> hyperair - yes, that was a typo ;)
[17:18] <hyperair> =)
[18:00]  * kenvandine runs to lunch
[18:04] <rickspencer3> tkamppeter: hey - what's up with bug 394447 ?
[18:04] <rickspencer3> bug #394447
[18:37] <rickspencer3> pedro_: are you around?
[19:00] <pedro_> rickspencer3, yeap
[19:12] <rickspencer3> pedro_: bug #402169
[19:12] <rickspencer3> and bug #402175
[19:12] <rickspencer3> these seem like upstream bugs to me, right?
[19:13] <pedro_> looking
[19:13] <pedro_> rickspencer3, that's correct, will send those upstream now if they aren't there yet
[19:14] <rickspencer3> pedro_: thanks!
[19:14] <pedro_> my pleasure ;-)
[20:57] <tkamppeter> rickspencer3: I have seen bug 394447, seems that the HP guys have messed up the driver. I have reported it as HPLIP upstream bug.
[20:57] <rickspencer3> tkamppeter: thanks Till
[21:00] <tkamppeter> rickspencer3: Unfortunately, I do not have a sample of this printer category (my printers are all much newer).
[21:00] <rickspencer3> hmm
[21:00] <rickspencer3> tkamppeter: in your experience, do you suspect that HP will fix it, or should I be concerned?
[21:01] <tkamppeter> I have a little doubt, I reported a lot of bugs and not all got fixed. There are some patches dangling around in our package which should be applied upstream.
[21:02] <tkamppeter> The printer is rather old and I wonder why they did not succeed to keep the printer working.
[21:05] <tkamppeter> rickspencer3: Bug 392040 suggests that it is a PPD issue.
[21:23] <tkamppeter> rickspencer3: I want to ask you something about CUPS 1.4 introduction.
[21:24] <rickspencer3> tkamppeter: go ahead
[21:24] <tkamppeter> Mike Sweet published the RC1 on June 8. Now I was waiting for the final and wondering where it is.
[21:25] <tkamppeter> I posted on the CUPS upstream ML and Mike answered off-list, that the HEAD of the SVN is the final now.
[21:26] <tkamppeter> It is only not tagged and released because Apple wants to sync it with the OS X.
[21:26] <tkamppeter> This can come slightly after our FF.
[21:28] <tkamppeter> So I want to ask you, whether I can package up the current SVN as it it is technically final and upload this before our FF, and then after FF when 1.4.0 comes out officially do a no-change-release replacing the upstream tarball by the official tarball.
[21:29] <tkamppeter> rickspencer3: ^^
[21:35] <rickspencer3> tkamppeter: this makes sense to me
[21:35] <rickspencer3> I would think pitti would want to weight in, but if you can't wait until Monday, I would double check possible with asac also
[21:35] <rickspencer3> but overall, getting in before ff even if from svn seems logical to me
[21:35] <tkamppeter> asac, can you look at my messages in the last 10 or 15 lines from here?
[21:40] <tkamppeter> rickspencer3: Thanks.
[21:46] <asac> tkamppeter: yes. package your own tar.gz using 1.4.0~svnREVID as upstream version
[21:47] <asac> and when he tags it, upload the 1.4.0 ... which wouldnt need a feature freeze exception anymore
[21:48] <tkamppeter> asac, thanks, I will do this tomorrow or Monday.
[21:49] <asac> good. i will be gone on monday, so ask pitti then if you need more info
[22:07] <chrisccoulson> hey bryce - you might know the answer to this, so i'll ask you before searching through the xorg code - are there some convenience functions used already that i can make use of to write messages to the xorg log file?
[22:07] <bryce> chrisccoulson, yes
[22:08] <bryce> chrisccoulson, usually if you scroll around in whatever file you're editing you'll spot the print calls in the correct calling syntax that you should use in that file
[22:08] <chrisccoulson> bryce - thanks, i'll take a look :)