[00:07] <zul> evening
[00:43] <StevenK> blueyed: The kbuild Build-Depends was because it doesn't build with anything less
[01:22] <blueyed> Thanks, StevenK. I'll forward it to Debian.
[01:39] <bddebian> Heya gang
[01:39] <somerville32> Heya
[01:40] <bddebian> :-)
[01:40] <superm1> hey bddebian
[01:40] <bddebian> Hi superm1
[01:41] <superm1> feeling revuee?
[01:42] <bddebian> Sure why not
[01:42] <superm1> cool.
[01:42] <superm1> ical2sqlite is what i sent up
[01:46] <bddebian> superm1: OK, gotta update my hardy pbuilder quick
[01:46] <superm1> okay, i'm gonna run an errand for a little bit anyhow.  i'll be back in ~20
[01:59] <TheMuso> Yay for circuit breakers.
[02:00] <StevenK> TheMuso: Er, yes. I've a friend who would have gotten a mains jump start if it weren't for the safety switch
[02:00] <TheMuso> Well this has happened for the third time with the same power outlet.
[02:00]  * TheMuso suspects bad wiring
[02:02] <StevenK> Mmmm, that outlet could be dodgy
[02:02] <TheMuso> Yeah. And it hasn't been touched in our work on the house either.
[02:03]  * Hobbsee wishes people would'nt send her private email that is not in english.
[02:03] <TheMuso> lol
[02:03] <TheMuso> spam
[02:03] <cheguevara_> lol
[02:04]  * ajmitch send Hobbsee an email in New Zealandish
[02:04] <Hobbsee> I please do not understand ingles to translate it in Castilian
[02:04] <Hobbsee> ...right then...
[02:04] <Hobbsee> so, uh, you're replying to an email that i've sent....why not translate it yourself?
[02:05] <StevenK> Because apparently they don't understand "ingles" (English)
[02:05] <Hobbsee> there are online translators
[02:05] <Hobbsee> which is how i got that translation
[02:36] <slangasek> Hobbsee: you need to find a better online translator, if only for the humor value of getting "ingles" properly translated as "groins"
[02:36] <Hobbsee> slangasek: hah :)
[02:36] <Hobbsee> slangasek: that was babelfish
[02:43] <slangasek> Hobbsee<EMAIL_ADDRESS>[02:44] <Hobbsee> slangasek: hah!  nice.
[04:08] <ScottK> keescook: I've been watching for the clamav security update for Gutsy to appear and I haven't see it yet ...
[04:10] <Fujitsu> ScottK: It has to all build, then be (manually, I think) pushed to LP, which will pick it up at the next */55. LP has been turned off for a while, so it might appear soon.
[04:11] <ScottK> Fujitsu: Thanks.
[04:11]  * ScottK can't ask for the feisty-backport until it's at least published ...
[04:13] <harrisony> If someone uploads a package to REVU, it has errors is there a procedure if a new person wants to upload an updated version (its been a month since the person uploaded the package and feedback was given)
[04:16] <Hobbsee> harrisony: go ahead, probably, if it's been a month
[04:17] <harrisony> Hobbsee: so just upload it?
[04:17] <Hobbsee> yeah
[04:17] <harrisony> you people dont need to do any ninja hacks
[04:18] <Hobbsee> maybe emailing the person that they haven't done a new version in a while, and did get feedback on it
[04:18] <Hobbsee> nope
[04:32] <harrisony> Hobbsee: should i add like previously created by .. in the changelog or delete their entry or
[04:34] <Hobbsee> based on the packaing of <user> would be a good idea
[04:34] <harrisony> :)
[04:45] <superm1> harrisony, well assuming of course that you *are* basing it on their packaging :)
[04:46] <j1mc> hi superm1 - if a package name doesn't have "ubuntu" in the package name, does that mean it is no different than the debian package?
[04:47] <superm1> hi j1mc, if its not in the version number then correct, there are no ubuntu changes to it
[04:47] <harrisony> superm1: im pretty much downloading it, fixing the errors and reuploading
[04:47] <superm1> the package source name should be the same as in debian however (and typically doesnt have ubuntu in it)
[04:49] <j1mc> there is a piece of software that i was looking to update, tilda.  both debian unstable and ubuntu hardy archives show it as being at 0.09.4+cvs20071012-1, but the new version is 0.09.5.  i'm just getting started with this - would i still read up on merging?
[04:50] <superm1> j1mc, so if the same version is in debian unstable,  but you want to get the newer version in hardy, then the first thing i'd do is check if debian is already working on it
[04:50] <superm1> via a svn tree or anything like that
[04:50] <superm1> that way you dont double up the work
[04:51] <superm1> if you dont see any such thing, then you would then work on doing the new upstream version yourself
[04:51] <superm1> and the new version number would be like this:
[04:51] <superm1> 0.09.5-0ubuntu1
[04:51] <j1mc> so check debian's svn tree for the package?
[04:51] <superm1> yeah that's usually a good idea to start out
[04:52] <j1mc> ok, if i don't see any activity there, would i read up on merges to start the 0ubuntu1 package?
[04:53] <superm1> well usually not too much work is needed to handle a new upstream version like that
[04:53] <superm1> i'd try to drop the debian directory in the new extracted upstream tarball
[04:53] <superm1> and see if it can build
[04:53] <superm1> if so, then its a very easy package and you just need to increment the changelog and submit it
[04:54] <j1mc> ok... thanks.  i'll keep that in mind.
[04:54] <j1mc> the guy who wrote tilda is in the chicago-lug, so . . . i figured it would be something good to start with.
[04:55] <superm1> oh neat :)
[04:57] <j1mc> this is where i'm looking to see if there's any activity on this package update in debian: http://packages.debian.org/sid/tilda
[04:57] <j1mc> should i be looking somewhere else?
[04:57] <j1mc> i've checked the bug reports, and developer information that is linked off of that page.
[04:58] <nxvl> finaly i can dget LP packages!
[04:59] <j1mc> naw, wait... i got it...  http://buildd.debian.org/pkg.cgi?pkg=tilda
[05:39] <keescook> ScottK: ppc still hadn't built yet -- I've pushed the rest, I can push ppc when it finishes later on
[05:44]  * somerville32 now has 30 uploads.
[05:44] <StevenK> keescook: So, how do we fix mk-sbuild-lv? :-)
[05:45] <keescook> StevenK: hmmm... what's wrong?  I haven't used it recently...
[05:45] <StevenK> keescook: This is going back to our discussion at AllHands, about using one LV for everything.
[05:46] <keescook> StevenK: ah! right. context-shift complete.
[05:46] <keescook> uhm
[05:46] <keescook> well.... basically, schroot needs to be taught to use a subdirectory of a snapshot instead of the root directory
[05:47] <keescook> then mk-sbuild-lv needs to be adjusted to grow a master lv instead of making a new one and drop in the right schroot conf
[05:47] <keescook> so, mostly, trick schroot.
[05:48] <StevenK> Ah
[06:38] <slytherin> Hi all. I am trying to fix lucene2 FTBFS. The core classes compile with GCJ but there appears to be failure in unit tests. This cause the package not to build. Is unit tests failure a good enough reason not to build a package. If it is not then what is the way by which I can ignore failures?
[06:39] <dholbach> good morning
[06:39] <TheMuso> Hey dholbach.
[06:40] <dholbach> hey TheMuso
[06:40] <slytherin> dholbach: hi. :-)
[06:40] <dholbach> heya slytherin :)
[06:40] <TheMuso> c
[06:40] <TheMuso> wrong tab
[06:42] <slytherin> dholbach: One question specifically for you. What is the next step for bug 177477? The Debian package maintainer has fixed it in debian as per my hints. Do we now sync that package and drop Ubuntu changes?
[06:42] <ubotu> Launchpad bug 177477 in libglazedlists-java "Fix FTBFS by adding java-gcj-compat-dev as build dependency" [Undecided,Fix committed] https://launchpad.net/bugs/177477
[06:42] <dholbach> slytherin: you need to find out if there are any ubuntu changes worth keeping, if not, we can sync it
[06:44] <slytherin> dholbach: No. There was no specific changes in Ubuntu. So I guess once the fixed package is uploaded in Debian unstable I will have to log a bug for sync again, right?
[06:44] <dholbach> slytherin: you can turn the bug into a sync bug then :)
[06:45] <slytherin> dholbach: by adding tag? or just adding a comment?
[06:46] <dholbach> changing the bug title and summary
[06:48] <nixternal> hola
[06:48] <slytherin> dholbach: Actually I was thinking to keep that bug to track other packages which can be fixed in similar way.
[06:49] <dholbach> slytherin: usually we file a sync bug per package
[06:49] <dholbach> https://wiki.ubuntu.com/SyncRequestProcess
[06:50] <slytherin> dholbach: No you didn't understand me. I meant keeping the bug summary to track packages which can be fixed by putting java-gcj-compat-dev in builde depends. I will just go on adding the debdiff for packages which can be fixed this way.
[06:51] <persia> slytherin: If the package is failing unit tests, it usually means something went wrong in the build process, and should be properly fixed (rather than ignoring the tests).
[06:51] <dholbach> slytherin: ahhhh ok
[06:51] <slytherin> persia: I will have to check what is the reason of unit tests failure. Will get back in 2-3 hours. :-)
[06:52] <persia> slytherin: You'll want a new bug for the sync then, to avoid spamming the archive-admins with all the debdiffs.
[07:38] <warp10> Hi all!
[07:43] <Fujitsu> Wooo, I think we have a very hungry Soyuz tonight.
[07:53] <persia> Is it really true there are no current or pending builds?
[07:53] <slangasek> it's true that we don't have them :)
[07:53] <slangasek> it's just not /right/ that we don't have them. ;)
[07:54] <Fujitsu> Right, Soyuz is rather hungry.
[07:54] <Fujitsu> The build records aren't just some strange status - they're actually gone.
[07:54] <persia> Ah.  That's actually better then.  If Soyuz managed to get ahead of the developers, it would be bad.  One part of Soyuz not feeding another is a different issue.
[07:55]  * Fujitsu commented on this a while ago in #launchpad.
[07:59] <Fujitsu> Hm, seems most of them are actually marked as being for superseded sources.
[08:10] <dholbach> hey luisbg
[08:19] <luisbg> hey dholbach
[09:07] <geser> good morning
[09:09] <mok0> good morning
[09:23] <Romes> I'm not getting any help at the ubuntu channel... anybody in here bored that wants to deal with an utter noob?
[09:24] <Romes> I think something about the philosophy of linux is confusing me
[09:24] <Romes> I seem to have to install the most basic things to get something to work :S
[09:25] <Romes> I'm getting an error... and I googled it, and I got a forum telling me to "install kernel sources"
[09:25] <Romes> ... I don't even know what that means
[09:27] <mok0> Romes: this is not a forum for that type of questions, but just for once.... what is the error you got?
[09:28] <Romes> oh man... sorry... bah
[09:28] <Romes> er... let me copy/paste
[09:28] <Fujitsu> !paste
[09:28] <ubotu> pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic)
[09:28] <Romes> oh, it's just a one-liner ;)
[09:28] <Fujitsu> Ah.
[09:32] <Romes> http://paste.ubuntu-nl.org/49002/
[09:32] <Romes> sorry about that, turns out it was multiline afterall
[09:33] <Romes> sorry again, I had to change it... left something out
[09:33] <Romes> http://paste.ubuntu-nl.org/49003/
[09:34] <Romes> if it seems like I'm taking forever, it's because I have to type out the errors manually (no internet on my ubuntu comp)
[09:35] <mok0> Romes: why are you running make?
[09:35] <Romes> I'm getting a lot of "x is undeclared"
[09:35] <Romes> the "INSTALL" file tells me to :P
[09:35] <mok0> Romes: install what?
[09:35] <Romes> ndiswrapper, sorry
[09:35] <Romes> oh yeah, I forgot that I didn't give any background
[09:36] <Romes> Um... my wireless card didn't work out of the box, so I tried to install ASUS linux drivers, but that install failed, so my friend (who's gone) told me to install ndiswrapper... which also isn't working... so I caved and came onto IRC :P
[09:36] <mok0> Romes: you should install ndiswrapper via apt-get
[09:37] <Romes> no internet :(
[09:37] <mok0> Romes: put it on an USB stick
[09:37] <Romes> I put the tar.gz file on a usb stick
[09:37] <Romes> I'm feeling stupider by the second
[09:38] <mok0> Romes: if you use the .deb you don't need to compile it; that can be tricky
[09:38] <Romes> .deb? Ah, I'll look for that!
[09:38] <mok0> Romes: what version is your system running?
[09:39] <Romes> let me check... what's the command again? uname -a? or something?
[09:39] <mok0> yeah
[09:39] <Romes> 2.6.22-14
[09:39] <pochu> lsb_release, too
[09:40] <pochu> That should be Gutsy
[09:40] <Romes> yup
[09:40] <Romes> sorry, didn't know what you meant by version
[09:40] <Romes> I'm migrating from Vista, so you can imagine that this is an entirely new world to me :P
[09:41] <mok0> Romes: welcome to a great world
[09:41] <Romes> lol... thanks mok0 :D
[09:41] <Romes> I'll feel more "liberated" once I understand how this stuff works... hah
[09:41] <Romes> anyways, back to looking for the .deb
[09:42] <Romes> I'll update you :P
[09:42] <mok0> Romes: http://packages.ubuntu.com/gutsy/misc/ndiswrapper-common
[09:43] <Romes> thanks! I don't see a .deb download on that page, though. That's where I got the .tar.gz file
[09:44] <mok0> Romes: http://packages.ubuntu.com/gutsy/net/ndisgtk
[09:45] <Romes> alright, new question... I'm on a regular old intel... am I i386?
[09:45] <mok0> Romes: yes
[09:46] <Romes> awesome
[09:47] <mok0> Romes: i386 for binary packages and "all" for the arch. independent packages
[09:48] <Romes> ah, okay... is there an advantage to binary packages? are the independent ones the packages that you have to compile on your machine?
[09:48] <Romes> makes sense if that's the case
[09:48] <mok0> Romes: No, the all packages are common for all the archs
[09:48] <Romes> Ah
[09:49] <mok0> Romes: The source comes in "source" packages, which consist of 3 files: a .dsc, a .diff.gz and a .orig.tar.gz
[09:49] <Romes> Ahhhhh
[09:50] <mok0> Romes: but you shouldn't need to worry about source packages
[09:50] <Romes> Stupid me, I didn't catch on to that.
[09:51] <Romes> hmm, there's no readme in this file
[09:51] <mok0> Romes: binary packages have been built from the source code
[09:51] <mok0> Romes: Can't you get an internet connection somehow?
[09:51] <Romes> So I just added an unnecessary step, essentially.
[09:51] <Romes> My router is nowhere near me
[09:51] <mok0> Romes: yes
[09:52] <mok0> Romes: It makes things a million times easier... you can install ndiswrapper with one command
[09:52] <Romes> hehe, I know, that's what my friend was telling me... it all depends on an internet connection, though :P
[09:52] <mok0> Romes: ... and it will automatically pull in other packages that it depends on
[09:52] <Romes> very nice
[09:53] <Romes> so should I run the makefile?
[09:53] <pochu> Romes: double click the .deb file.
[09:53] <Romes> there... I might be blind... but I don't see it
[09:53] <mok0> Romes: In the window manager
[09:53] <Romes> there's a .desktop, .8, .glade, and a couple image files
[09:54] <pochu> Romes: don't unpack it! :)
[09:54] <Romes> bahaha
[09:55] <mok0> Romes: I don't know ndiswrapper, but ndiswrapper-common is only one of the debs you need (pretty sure of that)
[09:55] <Fujitsu> !ndiswrapper
[09:55] <ubotu> Wireless documentation can be found at https://help.ubuntu.com/community/WifiDocs
[09:55] <Romes> lol, man... okay
[09:57] <mok0> Gotta go, se you later
[09:58] <Romes> okay it's installing
[09:58] <Romes> thank you so much mok0 :d
[09:58] <Romes> :d
[09:58] <Romes> thanks to others as well
[09:58] <Romes> pochu ;)
[09:58] <Romes> cheers
[10:03] <slytherin> dholbach: One more FTBFS fixed in similar way. Added debdiff to same bug. :-)
[10:04] <geser> slytherin: which bug is it?
[10:04] <slytherin> geser: bug 177477.
[10:05] <ubotu> Launchpad bug 177477 in libglazedlists-java "Fix FTBFS by adding java-gcj-compat-dev as build dependency" [Undecided,Fix committed] https://launchpad.net/bugs/177477
[10:05] <slytherin> geser: Affects more than one packages. I am using it as tracker bug.
[10:09] <TheMuso> Alright. Time to hit up the sponsors queue.
[10:11] <TheMuso> dholbach: That was bloody quick.
[10:12] <dholbach> TheMuso: you deserve it :)
[10:12] <TheMuso> Perhaps, but i sent that email not 5 minutes ago. :)
[10:12] <dholbach> maybe that's my new year's pledge: reply on MC mails a bit quicker :)
[10:12] <TheMuso> lol
[10:32] <totopalma> norsetto, hi :)
[10:33] <norsetto> hi there totopalma
[10:38] <mok0> norsetto: I think we never arrived at a conclusion wrt xtide. Are you prepared to sponsor it?
[10:39] <norsetto> mok0: Its u-u-s subscribed? If so its just a matter of waiting until its your turn in the queue
[10:40] <mok0> norsetto: yes, u-u-s is subscribed. I wasn't sure about the procedure. What does "subscribed" imply? I assumed it just meant that an email is sent somewhere...
[10:41] <norsetto> mok0: when you suscribe it shows up in the u-u-s list of bugs
[10:41] <mok0> norsetto: Ah, cool.
[10:41] <mok0> norsetto: Is that something us mortals can look at??
[10:42] <norsetto> mok0: you are about half way so it shouldn't take too long
[10:42]  * TheMuso notes that he picks at random.
[10:43] <norsetto> mok0: https://bugs.launchpad.net/~ubuntu-universe-sponsors/?field.searchtext=&orderby=-date_last_updated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
[10:43] <TheMuso> a lot of the time
[10:43] <TheMuso> Or, https://bugs.launchpad.net/~ubuntu-universe-sponsors
[10:43] <mok0> norsetto: So part of the job of a MOTU is to help processing this list?
[10:44] <TheMuso> mok0: Yes.
[10:44] <mok0> TheMuso: :-)
[10:44] <norsetto> mok0: if you are nice with TheMuso he will look at it right away ....
[10:45] <mok0> norsetto: I'm nice with everyone ;-)
[10:45] <TheMuso> I've actually glanced over it, I'll make it my next one.
[10:45] <mok0> TheMuso: Great. I'll remain online in case you have any questions
[11:21] <TheMuso> mok0: Reviewing xtide.
[11:21] <mok0> TheMuso: cool
[11:35] <TheMuso> mok0: Also taking care of the xtide-data bug.
[11:35] <mok0> TheMuso: yes, xtide-data needs to be fixed
[11:36] <TheMuso> Yep, thats what I'm saying. I'll attend to that after I've done xtide.
[11:36] <mok0> TheMuso: DD developer is responsive, so these mods will appear from upstream sooner or later
[11:37] <TheMuso> Nice.
[11:38] <LucidFox> Wow, packages.qa.debian.org has been redesigned
[11:41] <TheMuso> mok0: Um, there is a newer version of xtide-data in debian.
[11:41] <TheMuso> and ubuntu
[11:41] <TheMuso> mok0: Mind rebasing against that?
[11:42] <MenZa> ooh pretty, LucidFox
[11:43] <mok0> TheMuso: NP
[11:43] <mok0> mok0: My guess it that the debdiff still works ;-)
[11:43] <TheMuso> no it doesn't.
[11:44] <mok0> Ah ok
[11:44] <TheMuso> Doesn't apply at least
[11:48] <mok0> TheMuso: I was interrupted
[11:48] <TheMuso> mok0: np
[11:52] <zul> morning
[11:52] <TheMuso> Hey zul.
[11:52] <zul> hey TheMuso how goes it?
[11:52] <TheMuso> zul: Well thanks. Yourself?
[11:52] <zul> good just woke up
[12:06] <mok0> TheMuso: What is the point of having Build-Depends-Indep: and Build-Depends: both mention debhelper??
[12:07] <TheMuso> mok0: Sorry, I am unable to help. I'm not 100% thinking straight, and am about to turn in for the night.
[12:07] <TheMuso> There are the debian policy docs.
[12:07] <mok0> TheMuso: I'll just leave it there, then
[12:08] <TheMuso> Sorry I can't be of further help at the moment.
[12:08] <mok0> TheMuso: Do you want me to upload the new debdiff to LP, or do you want it via DCC?
[12:09] <TheMuso> mok0: Upload to LP, I can't look at it now.
[12:09] <TheMuso> and subscribe universe sponsors
[12:09]  * persia thinks debhelper is Build-Depends, and not Build-Depends-Indep, and that arch:all policies are broken in subtle and unfixable ways.
[12:09] <mok0> TheMuso: Thanks
[12:09] <mok0> persia: But this package has both
[12:09] <persia> mok0: And it shouldn't, but it doesn't break anything if it does.
[12:10] <mok0> I
[12:10] <mok0> I'll just leave it there, then
[12:31] <slytherin> is revu down?
[12:31] <persia> slytherin: works from here
[12:32] <slytherin> persia: working with http://revu.tauware.de/ but not http://revu.ubuntuwire.com/
[12:33] <persia> slytherin: The latter works from here
[12:41] <Kmos> http://packages.qa.debian.org got a new face today =)
[12:49]  * persia requests someone to please look at bug #133888 & upload the patch.  I just can't make a clean build for local reasons, and am becoming tempted to upload without the final build test.
[12:49] <ubotu> Launchpad bug 133888 in wxwidgets2.8 "upgrade wxwidgets2.8 to the <IP_ADDRESS> release" [Wishlist,Confirmed] https://launchpad.net/bugs/133888
[12:52] <mruiz> hi all
[12:52] <dfiloni> persia: yesterday I talk with DktrKranz. For he my package appears good but he want to test it whit some programs
[12:53] <persia> dfiloni: OK.  As long as someone is working on it.  I don't like to see something sitting in the sponsors queue for 10 days, and shouldn't upload that without a local build test.\
[12:54] <dfiloni> persia: I know... now I'm working at <IP_ADDRESS> version, it's very hard this version
[12:55] <persia> dfiloni: What makes <IP_ADDRESS> harder than <IP_ADDRESS>?
[12:56] <dfiloni> persia: Editra editor
[12:56] <dfiloni> persia: this is my latest lintian output: http://pastebin.ubuntu.com/2882/
[12:58] <persia> Urk!  I wouldn't have expected that much given how clean you'd gotten <IP_ADDRESS>.  Seems a little frustrating.  Thanks for wrestling with it.
[12:58] <Kmos> persia: how much it takes to build on pbuilder ?
[12:59] <persia> Kmos: how much what?  If you mean space: it's around 6-8GB.  If you mean time, at least a couple hours.
[13:00] <mruiz> Kmos, it depends on the package
[13:00] <Kmos> persia: space isn't a problem here..
[13:00] <persia> Kmos: There's already a build log in the bug, so it doesn't need another: just some testing by someone who didn't artificially constrain their build environments.
[13:05] <dfiloni> persia: why you changed the bug?
[13:05] <persia> dfiloni: Bugs awaiting sponsorship shouldn't be assigned to non-sponsors.
[13:06] <dfiloni> ok
[13:09] <dfiloni> persia: the same think also in the atanks bug?
[13:11] <slytherin> What does >> sign means when specifying version for a build dependency?
[13:11] <persia> dfiloni: I haven't looked at the atanks bug recently, but if it's queued for the sponsors, and assigned to a non-sponsor, it won't get sponsored for a while.
[13:11] <persia> slytherin: Really more than.
[13:13] <slytherin> can a build fail if a universe package depends on multiverse package for build?
[13:13] <persia> slytherin: Yes, but it likely won't, but it's a bug, so don't do that.
[13:15] <slytherin> persia: I am not doing it. I was just checking docbook-xsl-saxon build logs. I see and entry 'libsaxon-java has no candidate'. libsaxon-java is in multiverse.
[13:15] <persia> slytherin: In that case, the "universe cannot build-dep on multiverse" rule was working that day.  This is good.  One of the two likely needs to move.
[13:16] <slytherin> persia: Just checked in debian. libsaxon-java is in main, build with GCJ so it can be moved to universe. :-)
[13:17] <persia> slytherin: Excellent.  You've practice filing the "please move to universe" bugs, right?
[13:18]  * persia cheers the new "Java in universe" effort
[13:18] <slytherin> persia: I am trying to squash as many java related FTBFS as possible. And most of the times solutions have been simple except in case of batik. :-)
[13:18] <persia> batik was the one that had all sorts of new build-deps, right?
[13:20] <slytherin> persia: Not exactly. current version in Ubuntu uses loads of sun specific apis. the latest beta solves that problem to great extent but depends on another library. :-)
[13:20] <persia> slytherin: Right.  I only remembered the bit about the extra library.
[13:21] <slytherin> I have uploaded that library to revu and waiting for someone to hammer it. :-)
[13:22] <persia> slytherin: Is it both source & binary lintian & linda clean?
[13:23] <slytherin> persia: As far as I understand it, it is clean.
[13:23] <persia> slytherin: OK.  You ran both checkers with all the options against the source and binary .changes files?  Neither had any output?
[13:24] <slytherin> persia: Let me check once again.
[13:24] <persia> slytherin: In case you don't remember all the switches for maximum verbosity, they are listed on https://wiki.ubuntu.com/MOTU/Contributing
[13:28] <slytherin> persia: Both clean
[13:28] <persia> slytherin: In that case, you need to upgrade your lintian and linda.  The current versions don't agree on one point, so it would be impossible for them to be clean :)
[13:29]  * persia agrees with lintian about the disagreement, but hasn't figured out the secret trick required prior to the linda update yet
[13:29] <slytherin> persia: I am on gutsy. So that might be problem.
[13:30] <LucidFox> persia> What "Java in universe" effort?
[13:30]  * Hobbsee waves
[13:30] <persia> slytherin: There are backports for both available in -backports.  You can download them directly from the pool (http://archive.ubuntu.com/ubuntu/pool/main/l/) if you like.
[13:31] <persia> LucidFox: slytherin's new "Java in universe" effort, to follow Debian's "Java in main".
[13:31] <slytherin> Ok. I will. perhaps tomorrow. :-)
[13:32] <persia> LucidFox: Essentially, a lot of the Java packages actually work with the latest free compilers & VMs, so don't need to be in multiverse anymore.  It requires manual investigation for each package, but when complete, they can be promoted.
[13:32] <persia> Hi Hobbsee
[13:32] <LucidFox> But icedtea isn't in Debian yet, is it?
[13:32] <LucidFox> Or do they mean other tools?
[13:32] <persia> LucidFox: A lot of them work even with gcj
[13:32] <LucidFox> Ah.
[13:34] <persia> blueyed: There's no need to close bugs twice in a changelog :)
[13:36] <geser> Hi Hobbsee
[13:37] <Hobbsee> heya
[13:39] <blueyed> persia: IIRC this was just for reference (the second one)
[13:40] <persia> blueyed: Hrm.  I'm not sure if it breaks anything to do that: maybe worth an experiment.  The upload was stalled for other reasons though :(
[13:43] <blueyed> persia: which one is this?
[13:43] <persia> blueyed: I forget already: I'll check my mail (but it should be in yours as well)
[13:44] <blueyed> persia: cuetag? It's set to in progress by you.
[13:45] <persia> blueyed: Ah.  Yes.  That was it.  Assigned to you for the last little change.
[13:45] <blueyed> I see. Thanks.
[13:46] <persia> somerville32: Please close the sponsoring request bugs with your candidates :)
[13:46] <slytherin> LucidFox: The main problem is that it looks like package maintainers are underestimating GCJ and simply don't try building package with it. So you will find Sun's jdk as the first or only build dependency in many packages.
[13:47] <Hobbsee> effie_jayx: hahaha :D
[13:47] <LucidFox> True.
[13:47] <effie_jayx> Hobbsee,  ;)
[13:48] <effie_jayx> I got scared when you said ... You're late...
[13:48] <LucidFox> libhiglayout-java built with free-java-sdk, and when I pointed that out to the maintainer, he said he was unaware that free Java build tools even existed.
[13:48] <slytherin> LOL
[13:48] <Hobbsee> effie_jayx: either that, or you were a lot early for hte next one :)
[13:48]  * persia notes that the main merge push is over, and we should be looking at bugfixing & integration & features (which may also mean some merging)
[13:50] <blueyed> persia: Fixed the diff. Should I assign u-u-s sponsors again, or will you do it?
[13:50] <blueyed> s/assign/subscribe/
[13:51] <slytherin> blueyed: Add subscription yourself.
[13:51] <persia> blueyed: Better if you subscribe again.  I'm just hitting what would be my last queue request for the evening.  If I end up doing more later, I'm more likely to find it in the queue than in my bug subscriptions.
[13:52] <blueyed> Makes sense. Done.
[14:28] <gpocentek> persia: onless you already work on it I can take care of the xffm patch
[14:28] <persia> gpocentek: That'd be great.  I wasn't going to chase it: more just trying to push rainct's maintainer mangling completion effort.
[14:29] <gpocentek> I wonder if we should keep xffm in the archive to be honnest
[14:29] <gpocentek> looks like debian got ride of it
[14:31] <persia> gpocentek: Now I'm confused.  I can't see that Debian ever had xffm-icons
[14:32] <gpocentek> persia: it was in sarge
[14:32] <gpocentek> xffm4-icons
[14:33] <gpocentek> persia: do you think we should really update the maintainer?
[14:33] <gpocentek> I don't find this useful
[14:34] <persia> gpocentek: Yes.  I firmly believe that we should not have any packages with ubuntu versions that don't have ubuntu Maintainers.
[14:34] <gpocentek> ok
[14:34] <persia> Further, in cases like this, it helps identify things that should be dropped from the archive.  If we just ignore the corner cases of things that haven't been updated in a while, we end up with lots of cruft.
[14:35] <gpocentek> agreed
[14:35]  * gpocentek wonders why devscripts should be a build-dep
[14:35] <persia> gpocentek: Is xffm actually useful for Xubuntu these days?  If not, I think we ought drop both xffm-* and xffm4-* (and libxffm3 which seems to still be present as well)
[14:36] <gpocentek> persia: they are not used in xubuntu
[14:37] <persia> gpocentek: OK.  Do you want to keep them?
[14:37] <gpocentek> no
[14:38] <gpocentek> persia: I'll go through the list of packages and report bugs to remove them
[14:39] <persia> gpocentek: Well, since you seem to be Maintainer for a few, I say it's your call :)
[14:39] <gpocentek> I wonder if it the packages have been used since we get thunar in the archive
[14:39] <persia> I'd think one bug would be better as they are all related.  Saves the archive-admins chasing all the bugs for various interdependencies.  Maybe multiple tasks.
[14:40] <gpocentek> right
[14:49] <dfiloni> persia: do you think I should fix image-file-in-usr-lib lintian warnings? I can override warnings or try to fix they. What I should do
[14:51] <persia> dfiloni: I think images belong in /usr/share/ .  If you're talking about wxwidgets, please put them in the right place.  If you're asking about a different package, it's best to ignore the warning (not override) if the package comes from Debian, and fix it if the package is only in Ubuntu.
[14:53] <dfiloni> persia: I'm talking about wxwidgets. Images are a parts of a theme, if I put them in the right place the package cannot working
[14:53] <dfiloni> persia: I think I should link the icons
[14:53] <persia> dfiloni: Can something else be adjusted to make it work, perhaps with a patch?  There's no reason for themes to be architecture-specific (as far as I know).
[14:54] <dfiloni> persia: I don't know
[14:55] <persia> dfiloni: Depending on your interest, I'd suggest either patching the source to make themes in /usr/share/ work, or leaving the lintian warning so someone else can see the bug.  In this case, an override would be bad, as it would hide the problem.  Also, since the package is already in the archive, it doesn't have to be lintian clean to upload (although that is nice).
[14:56] <dfiloni> persia: I will try to patch the source, I want a clean package
[14:57] <persia> dfiloni: Thanks.  If you get stuck on that, feel free to request upload of the rest, and keep working on that.  Since it won't change the library version, it is very unlikely to break rdepends, so it is safe to do later.  The upgrade should be done sooner to make sure it gets tested properly.
[14:58] <dfiloni> persia: ok
[15:20] <bddebian> Heya gang
[15:23] <geser> Hi bddebian
[15:24]  * persia wonders if MOTU SWAT wishes nominations for closed CVEs possibly exposed in previous releases to be approved to highlight the subscribed queue
[15:28] <bddebian> Hi geser, persia
[15:28] <persia> hey bddebian
[15:31] <MenZa> persia, that sentence needed more acronyms
[15:34] <bddebian> heh
[15:34] <persia> MenZa: Why?  I actually prefer that to my far-too-common "DIFe is available from UUS, especially for FTBFS, UEHS, or NBS stuff", which is less comprehensible to the newcomer.
[15:34] <MenZa> I was being serious. :(
[15:35] <slytherin> persia: One question. You were handling gnusim8085 packaging in which you asked me to add watch file. I have added watch file. Is it ok if I assign the bug back to you now?
[15:36] <dholbach> persia: http://wiki.ubuntu.com/UbuntuDevelopment/Abbreviations :)
[15:36] <persia> slytherin: I'd recommend assigning nobody and subscribing the sponsors queue.  Take a look at my assigned bugs list if you don't believe me.  Among other things, I have now owned the most-duplicated bug in LP for 5 releases.
[15:37] <persia> dholbach: Thanks.  I'm not up much longer, but I'll add to that :)
[15:37] <dholbach> persia: you ROCK
[15:37] <slytherin> Ok. Actually previously it was assigned to nobody. But looks like since it was set 'In Progress' it was not considered by other sponsors. I will set it to confirmed.
[15:37] <persia> slytherin: Thanks :)
[15:37]  * slytherin agrees with dholbach :-D
[15:39]  * persia has filed some needs-packaging bugs for audio-plugins if anyone is interested.  Early & frequent review available.
[15:46] <pochu> persia, dfiloni: have you seen the yet again recent discussion about wx2.8 in debian-devel?
[15:47] <dfiloni> pochu: yes
[15:47] <persia> dholbach: http://wiki.ubuntu.com/UbuntuDevelopment/Abbreviations updated, with a special inclusion, just for you :)
[15:47] <dholbach> persia: HAHAHA :-)
[15:47]  * dholbach hugs persia
[15:47] <persia> pochu: pointer?  Also, isn't it still blocking on the only-two-versions-of-a-library policy?
[15:49] <RainCT> persia: some url for those needs-packaging?
[15:50] <pochu> persia: http://lists.debian.org/debian-devel/2007/12/msg00520.html, specially
[15:50] <persia> RainCT: bugs #177672 #177673 #177678 #177679
[15:51] <ubotu> Launchpad bug 177672 in ubuntu "Please package wildmidi" [Undecided,New] https://launchpad.net/bugs/177672
[15:51] <pochu> persia: specially Daniel Baumann's plan:  * review and upload the package from Vadim in the next days.
[15:51] <pochu>   * try to really get rid of wxwidget2.4.
[15:51] <pochu>   * try to get rid of wxwidget2.6 if possible.
[15:51] <pochu> Sounds like an ambitious plan ;-)
[15:52] <persia> pochu: I trust Vadim regarding the package, but suggest coordination between Vadim & dfiloni, as there's lots of distro-specific tweaking dfiloni has don that vadim might not be familiar with, but which would be good for Debian as well as Ubuntu.
[15:53] <persia> For really getting rid of wxwidget2.4, we're really, really close (except that jugglemaster annoyed me).
[15:53] <pochu> dfiloni: wanna comaintain wx in Debian? ;-)
[15:53]  * pochu hides :)
[15:53] <persia> For getting rid of wxwidgets2.6, we're likely a year away: there's still a large number of FTBFS due to API shift, and it needs upstream pressure (a Debian migration to support 2.8 will help).
[15:55] <dfiloni> persia: I think I can help debian because I don't know more about packaging, I'm learning
[15:55] <persia> dfiloni: You can certainly help, but I'd agree you're just learning, so probably shouldn't be a maintainer by yourself.  pochu has a bit more experience, and together I think you'd do a good job.
[15:55] <pochu> persia: lol, me?
[15:56] <pochu> persia: well yes, I'm experienced with 'pbuilder-hardy build wx*dsc' ;-)
[15:56] <persia> pochu: Why not?  You dare touch the package, you seem to have the right attitude as a package maintainer, and most of your work is pretty good.
[15:56] <pochu> persia: wx scares me :-(
[15:57] <pochu> And I prefer pure Gtk ;)
[15:57] <persia> pochu: Scares everyone, but Vadim would be happy to help with that part :)
[15:57] <pochu> Heh, right.
[15:57] <pochu> Well actually there are a couple of wx developers, and a DD willing to take care of it. Of course, the more the better
[15:57] <dfiloni> persia: sorry, I wanted to write I can'T
[15:58] <dfiloni> persia: I think I can't help debian because I don't know more about packaging, I'm learning
[15:58] <persia> dfiloni: I read it that way.  My answer still stands.
[15:58] <dfiloni> persia: ok
[16:04]  * RainCT decides he doesn't like audio packages :P
[16:05] <persia> RainCT: :)  No worries.  Thanks for looking.
[16:09] <Kmos> dholbach: i got the mail, thanks.. i need to reply to it accepting it or not ?
[16:12] <dholbach> Kmos: the MC is going to vote, but if you have anything to say about it, please do
[16:12] <Kmos> ok
[16:13] <Kmos> dholbach: thanks
[16:42] <dfiloni> persia: I found in wxPython/wx/tools/setup.py lines that contain pixmaps dir
[16:42] <persia> dfiloni: Excellent :)
[16:42] <dfiloni> *Editra/setup.py
[16:58] <dfiloni> persia: can't debian use <IP_ADDRESS> that I've done?
[16:59] <dfiloni> if will be approved
[18:54] <jonnymind> hello
[18:54] <pochu> hey jonnymind
[18:55] <jonnymind> :-)
[18:55] <jonnymind> pochu: have you checked my last upload?
[18:56] <pochu> I don't think so, link?
[18:57] <jonnymind> justsec
[19:01] <jonnymind> bug 174470
[19:01] <nxvl_work> which is the URL for bitsize bugs on LP?
[19:01] <ubotu> Launchpad bug 174470 in ubuntu "Package for the Falcon Programming Language" [Wishlist,In progress] https://launchpad.net/bugs/174470
[19:01] <nxvl_work> !bitsize
[19:01] <ubotu> Sorry, I don't know anything about bitsize - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[19:02] <imbrandon> !bitesize
[19:02] <ubotu> A list of bugs that are considered easy to fix and good for beginners to attempt can be found at: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=bitesize
[19:04] <pochu> jonnymind: checking
[19:04] <nxvl_work> oh i miss the "e"
[19:04] <nxvl_work> :P
[19:04] <jonnymind> pochu: thnx
[19:04] <nxvl_work> imbrandon: thnx :D
[19:06] <tonyyarusso> imbrandon: oh btw - did you have an idea of when flashplugin-nonfree's fix would be available for released versions?
[19:07] <pochu> jonnymind: no documentation for falcon other than the manpages?
[19:07] <jonnymind> on the site
[19:07] <jonnymind> about 180 pages function ref + manual
[19:07] <jonnymind> a4
[19:07] <jonnymind> Plus embedding guide, various tools help and so on
[19:08] <jonnymind> However, I am refining it all. On 0.8.6, there will be even more.
[19:08] <pochu> How much space do they take? Might be a good idea to make a -doc package
[19:08] <jonnymind> excellent idea.
[19:08] <jonnymind> they are relatively small pdf, smaller if rendered on html.
[19:09] <pochu> jonnymind: you could ship the source in the tarballs, and build them as html at build time.
[19:09] <jonnymind> ... source is odt.
[19:09] <jonnymind> (gpl doc 1.2
[19:09] <pochu> Ouch.
[19:10] <imbrandon> tonyyarusso: yes i'm working on a sru, i'll probably have it uploaded today
[19:10] <pochu> GFDL, right?
[19:10] <jonnymind> yes
[19:10] <tonyyarusso> imbrandon: cool
[19:11] <pochu> jonnymind: hehe, this is funny: W: falcon-dev: unusual-interpreter ./usr/bin/falconeer.fal #!/usr/bin/falcon
[19:11] <jonnymind> :-) hai!
[19:12] <pochu>       (C) 2007-2012 Giancarlo Niccolai
[19:12] <pochu> jonnymind: 2012?
[19:12] <jonnymind> oh well, I really DIDN'T know WHAT to put there.
[19:13] <jonnymind> I don't even get the meaning of copyright on a free software...
[19:13] <pochu> well put $beginning_of_your_work - $current_year
[19:13] <jonnymind> Oh, that's a great idea.
[19:13] <pochu> jonnymind: If you are not putting it in the Public Domain, then it needs to have a copyright holder, afaik.
[19:13] <jonnymind> consider it done.
[19:14] <pochu> IANAL though, so don't listen to me ;)
[19:14] <jonnymind> I see. IMHO, authorship right should be more important, and last 75 years. But americans are so fond in copyright...
[19:14] <pochu> jonnymind: the copyright file needs a bit of work. Would you mind using the dh_make template?
[19:15] <jonnymind> pochu: yes
[19:15] <jonnymind> I mean, yes, I do mind.
[19:15] <pochu> And it needs to say exactly what files are under GFDL (e.g. docs/*)
[19:15] <pochu> jonnymind: may I ask why? :)
[19:15] <jonnymind> The package build process is automatized and is upstreamed in our build system,
[19:16] <jonnymind> which is a multiplatform build system made of several scripts.
[19:16] <pochu> jonnymind: heh, I mean debian/copyright :-)
[19:16] <jonnymind> I tried to use auto things from debian, but it just didn't stand.
[19:16] <imbrandon> your package modifies debian/copyright on every build? nasty
[19:16] <jonnymind> pochu: there's no gfdl in that package (atm)
[19:16] <jonnymind> yes
[19:17] <jonnymind> Of course it does: the VERSION changes at every build.
[19:17] <imbrandon> VERSION in debian/copyright ?
[19:17] <jonnymind> possibly yes.
[19:18] <jonnymind> Falcon 0.8.5, Falcon 0.8.6 ... Falcon 1.0...
[19:18] <imbrandon> very nasty way to do things imho, glad i'm not sponsoring it
[19:18] <pochu> jonnymind: you *can't* change anything in debian/ automatically
[19:18] <pochu> at least AFAIK
[19:18] <jonnymind> imbradon: honestly, I don't see why.
[19:18] <imbrandon> pochu: right its against policy iirc
[19:18] <jonnymind> pochu: again, I don't see why.
[19:19] <jonnymind> ... Ok, point out the policy line.
[19:19] <pochu> jonnymind: and I don't see 0.8.5 there
[19:19] <imbrandon> jonnymind: because policy states anything automaticly generated needs to be checked by hand before completion
[19:19] <imbrandon> jonnymind: sure one sec
[19:19] <jonnymind> pochu: it MIGHT be there.
[19:19] <pochu> emilio@pochu:~/tmp/tmp/falcon-0.8.5/debian$ grep '0.8.5' copyright
[19:19] <pochu> emilio@pochu:~/tmp/tmp/falcon-0.8.5/debian$
[19:19] <jonnymind> imbradon: Oh, I do.
[19:19] <jonnymind> and everyone in charge will.
[19:20] <imbrandon> if your build system does it you cant
[19:20] <jonnymind> Of course we can:
[19:20] <imbrandon> not if it does it automagicly on every build
[19:20] <jonnymind> Ah,... no.
[19:20] <pochu> Still. Changing anything in your upstream tarball is alright. Changing it in debian/ isn't, IMHO.
[19:20] <jonnymind> Sorry, I meant every RELEASE.
[19:20] <jonnymind> I have script to set up things when the release is ready.
[19:20] <jonnymind> And they setup a skeleton that is then checked by hand.
[19:21] <jonnymind> they prepare the ground for the releases.
[19:21] <imbrandon> you repackage on every release?
[19:21] <imbrandon> nasty
[19:21] <jonnymind> Well. I see no other way to change the things in a package than repackaging.
[19:21] <imbrandon> modify the existing package on new releases is the way
[19:22] <pochu> jonnymind: we are talking about debian/copyright here, not copyright
[19:22] <pochu> (just in case :)
[19:22] <jonnymind> pochu: oic.
[19:22] <jonnymind> pochu: in this case, I don't mind what it goes there as long as it is compliant.
[19:22] <pochu> jonnymind: you are completely free to do whatever you want with copyright!
[19:22] <pochu> :-)
[19:22] <imbrandon> right
[19:23] <imbrandon> this all pertains to debian/*
[19:23] <jonnymind> AHHH, now I get it.
[19:23] <pochu> Sorry for the confusion :-)
[19:23] <jonnymind> Well, there is nothing automated in that case.
[19:23] <jonnymind> I had a script to put the version on binary packages, but I removed it because source packages determines it automagically
[19:24] <jonnymind> the things in the /debian dir are full static.
[19:24] <imbrandon> hrm i thought falcon was on 2.0beta3 anyhow, was last time i looked
[19:24] <jonnymind> 1.0beta3.
[19:24] <jonnymind> I changed numbering to be compliant with different distros.
[19:25] <jonnymind> I.e. redhat is a mess with "beta" in names.
[19:25] <jonnymind> And I won't descend into magic of win version numbering.
[19:25] <pochu> jonnymind: in debian/copyright, you need to list the license of all the files. So just saying that everything is released under the Falcon license but the files under docs/ are under the DFDL is fine.
[19:25] <imbrandon> jonnymind: nope 2.0.0~beta3 http://falcon.kaarsemaker.net/
[19:25] <imbrandon> just checked
[19:26] <jonnymind> pochu: ok
[19:26] <jonnymind> imbradon: not mine.
[19:26] <jonnymind> http://www.falconpl.org
[19:27] <imbrandon> ahh looks like a namspace conflict, have you got with the other falcon maintainers to resolve this ?
[19:27] <pochu> jonnymind: so you need to explictly say what files are licensed under GFDL, and put something like this:
[19:27] <pochu> On Debian systems, the complete text of the GNU General
[19:27] <pochu> Public License can be found in `/usr/share/common-licenses/GPL'.
[19:27] <pochu> s/GPL/GFDL-1.2/
[19:28] <pochu> and s/General Public/Free Documentation/
[19:28] <imbrandon> pochu: s/GPL/GPL-2 now because it defaults to 3 now
[19:28] <pochu> imbrandon: well it's not GPLed, but GFDLed (the documentation) ;)
[19:28] <imbrandon> :)
[19:30] <jonnymind> imbradon: I proposed (many times) falconpl.
[19:31] <jonnymind> but Everyone here said: it's fine this way...
[19:32] <jonnymind> I am *willing* to change the name into falconpl, if just needed
[19:33] <imbrandon> i dont care either way, the correct thing to do would be get with the other falcon software makers and come up with a solution
[19:34] <nxvl_work> where can i get information about how the menu entries are placed?
[19:35] <jonnymind> pochu: I will fix license/copyright things asap.
[19:35] <jonnymind> imbradon: I didn't even know about that software. we'll discuss the topic.
[19:36] <imbrandon> kk, sure thats all i was pointing out :)
[19:36] <jonnymind> (although, there should be nothing to discuss if I just change the name of the package in falconpl.
[19:36] <jonnymind> Which is ok to me, for various reasons.
[19:36] <imbrandon> well you would both still produce a "falcon" binary though
[19:36] <imbrandon> i'm sure
[19:37] <jonnymind> that would be a problem.
[19:37] <imbrandon> right
[19:37] <jonnymind> what is that other falcon thing?
[19:37] <JanC> a .deb repository "builder"
[19:37] <imbrandon> its a apt repository maintainer
[19:38] <jonnymind> imbradon: no we can't.
[19:38] <pochu> jonnymind: the shlibs looks wrong to me. You currently have $library_name SONAME, but it should be $library_name SONAME binary_package_name
[19:38] <jonnymind> from their site: Falcon plugins, like falcon itself, are written in python.
[19:38] <pochu> jonnymind: i.e. you need to add libfalcon-engine1
[19:39] <imbrandon> jonnymind: what does that matter ?
[19:39] <jonnymind> they won't produce a binary.
[19:39] <imbrandon> jonnymind: ok a "falcon" command
[19:39] <jonnymind> however, I'll check with them,
[19:40] <imbrandon> same diffrence in this case
[19:40] <imbrandon> ok i got to run
[19:40] <jonnymind> pochu: I don't get it.
[19:40] <jonnymind> May you please specify the line to the comments in the bug?
[19:40] <jonnymind> Got to go: dinner. Bll.
[19:41] <jonnymind> Thanks everyone.
[19:55] <mruiz> hi all
[19:57] <TheMuso> Hey folks.
[20:01] <mruiz> Time ago I had an account on REVU, but it disappeared. How can I get a new one?
[20:04] <pochu> mruiz: are you subscribed to ubuntu-universe-contributors in LP?
[20:04] <pochu> And do you have a gpg key in your lp account?
[20:09] <mruiz> pochu, yes
[20:10] <mruiz> All accounts from the old REVU instance have been removed, all MOTU accounts should have been recreate ... from REVU page
[20:13] <Supremus> norsetto, hi !! :D
[20:13] <norsetto> Hi supremus
[20:15] <Supremus> norsetto, How are you?
[20:15] <norsetto> Supremus: quite well, you too I hope
[20:15] <totopalma> norsetto, hi :)
[20:16] <Supremus> yes :D
[20:17] <dfiloni> Hi norsetto :)
[20:18] <mruiz> pochu, thanks for your help... I recreated my account :-)
[20:19] <norsetto> Hola dfiloni
[20:20] <norsetto> superm1: I was wondering about the kernel modules in your ppa .... do you have a ralink wireless yourself?
[20:21] <superm1> norsetto, no i dont
[20:21] <superm1> i didnt realize i had ralink support on any of my packages though?
[20:21] <superm1> i have an updated linux-ubuntu-modules, but the fix should be in -proposed right now too afaik
[20:21] <norsetto> superm1: sure, you have the legacy drivers in the modules one
[20:22] <superm1> ah.  well nothing has been changed in that
[20:23] <norsetto> superm1: ah ok! I was hoping they were finally getting rid of the rt2x00 crap and install the legacy ones
[20:23] <superm1> norsetto, not all too sure on that :)
[20:24] <Adri2000> TheMuso: regarding bug #176837, I thought the process was to assign to the contributor when there are things to fix?
[20:25] <ubotu> Launchpad bug 176837 in audacious-plugins "Please merge audacious-plugins 1.4.2-1 (universe) from Debian unstable" [Undecided,Fix released] https://launchpad.net/bugs/176837
[20:25] <TheMuso> Adri2000: not as far as I know. I haven't read the policy for a while, but I don't try and rigidly stick to it.
[20:25] <jonnymind> back
[20:27] <Adri2000> " If the patch needs work
[20:27] <Adri2000>     *
[20:27] <Adri2000>       Set the Status to "Incomplete"
[20:27] <Adri2000>     *
[20:27] <Adri2000>       Assign the patch submitter
[20:27] <Adri2000> "
[20:28] <TheMuso> Ah well.
[20:28] <Adri2000> but then I guess it's the contributor who should unassign himself when he provides a new debdiff
[20:28] <TheMuso> As I said, I don't like ridigly sticking to policy
[20:28] <TheMuso> As long as I'm aware of the guidelines, thats fine for me.
[21:04] <gilir> hi
[21:06] <mruiz> hi all, I uploaded a package to revu and I need a review: http://revu.ubuntuwire.com/details.py?package=adtool, thanks!
[21:07] <gilir> is there someone nice and available to review awn-extras-applet on REVU ? :)
[21:14] <rzr> hi there
[21:14] <rzr> any cannonical guys arround ? I've been contacted for a job
[21:15] <imbrandon> rzr: probably best to contact them back the same way they contacted you
[21:16] <rzr> that's what i've just done
[21:16] <imbrandon> :)
[21:16] <rzr> i wanted to have take the temperature from inside :)
[21:17] <imbrandon> there are a few Canonical employes arround and more in #ubuntu-devel and #launchpad and a few other places :)
[21:18] <pochu> rzr: may I ask you which position? :)
[21:18] <rzr> like #debian-*
[21:18] <rzr> sure
[21:18] <rzr> something like ...blanblah... LinuxOS
[21:21] <slangasek> rzr: the temperature in this part of Canonical is about 58°F according to the thermostat
[21:22] <imbrandon> slangasek: :)
[21:22] <rzr> too cold anyway ...
[21:22] <rzr> let's work from crimosoft instead ;)
[21:23] <slangasek> they're farther north, it's 54° there
[21:24] <rzr> metric system please :)
[21:41] <Ubulette> http://intlstore.mozilla.org/images/MZ9011E.jpg   lol
[21:55] <pochu> Ubulette: :-)
[21:55] <Flare183> What are all the section?
[21:55] <Flare183> I need a list
[21:55] <Flare183> please
[21:56] <geser> Flare183: http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[21:57] <Flare183> thanks
[22:00] <kane77> hi, what needs to be done to get package into next ubuntu release? (t
[22:02] <kane77> (I'd like to have groovy package included in hardy)
[22:03] <pochu> It's already there, but DEPWAITing
[22:03] <pochu>     groovy | 0.1.0beta10-3 | http://archive.ubuntu.com hardy/multiverse Sources
[22:03] <pochu> https://edge.launchpad.net/ubuntu/+source/groovy/
[22:04] <somerville32> What is groovy do?
[22:06] <Ubulette> why isn't packages.u.c working with hardy ? it's been broken for several week now
[22:17] <cyberix> How do you fix "Binary contains unneeded section comment." or "Binary is not stripped."?
[22:24] <zorglu_> q. is there something like .pdi (pcbsd installer) but on linux ?
[22:35] <kane77> somerville32, it's a scripting language with javaish syntax
[22:35] <geser> Ubulette: how is p.u.c broken?
[22:38] <Ubulette> geser, in "Search the contents of packages", hardy is no longer listed
[22:39] <Ubulette> geser, and in pkg descriptions, "files" now says "no current information available"
[22:39] <Ubulette> like in http://packages.ubuntu.com/hardy/libs/gstreamer0.10-plugins-base
[22:39] <geser> ah, that one. The Contents.gz files aren't generated for hardy yet
[22:39] <Ubulette> they were, up to a few weeks ago
[22:40] <geser> Generating them is time-consuming and they're outdated really fast now
[22:40] <Ubulette> but it's difficult to track moving files without that
[22:40] <geser> my guess it that they will generated in the future again, when hardy has less changes
[22:41] <geser> yes, unfortunately
[22:50] <Ubulette> geser, should be pretty easy to make on the fly using one of the dh_ script so it updates only what needs to be updated
[22:51] <geser> Ubulette: I don't know how exactly those Content files are generated
[22:51] <geser> Ubulette: adding should be easy: add the dpkg-deb -c output to that file but what about removals of old data?
[22:52] <Ubulette> just add the package name as a key, then remove everything for that key 1st
[22:57] <geser> Ubulette: ask in #ubuntu-devel or #launchpad about the Contents files. I don't know where the right place is.
[23:03] <Ubulette> geser, well, i don't have much to add. I miss the feature and i think it could be light just by doing the task on the fly, that's about it.
[23:04] <geser> Ubulette: I guess if it was that easy, it would probably be done
[23:04] <Ubulette> maybe not with the current design, no idea of what it looks like now
[23:05] <geser> me neither
[23:06] <norsetto> ubulette: whats wrong with apt-file?
[23:06] <geser> norsetto: it needs also the same Content files which aren't there yet
[23:06] <cyberix> My last package, being a sourceless binary application, raised lots of discussion. So this time I packaged public domain software!
[23:06] <cyberix> http://revu.tauware.de/details.py?package=malbolge
[23:07] <cyberix> Be the first one to review it.
[23:07] <cyberix> Here on R-E-V-U
[23:07] <norsetto> geser: does it? mine seems to work pretty happily (but then perhaps its not looking at hardy)
[23:08] <geser> norsetto: gutsy has Content files therefore it works on packages.u.c but hardy has no Content files
[23:15] <Ubulette> yep, apt-files uses sources.list to see where to fetch the indices so in my case, it tries and fails on http://archive.ubuntu.com/ubuntu/dists/hardy/Contents-i386.gz
[23:38] <norsetto> oh well ... time for bed
[23:38] <norsetto> g'night all
[23:47] <cyberix> When is the next revu day going to be?
[23:48] <pochu> cyberix: It's every Monday afaik
[23:48] <pochu> So next Monday ;)
[23:48] <cyberix> oh
[23:48] <pochu> Although it'll be December 24th, so there might be few activity here ;)
[23:49] <cyberix> :-(
[23:49] <cyberix> What a pity there is no reverse D
[23:50] <pfein> is there a quick guide/howto on building a .deb?  I need to version bump an existing ubuntu package...
[23:51] <TheMuso> !packagingguide | pfein
[23:51] <ubotu> pfein: packagingguide is The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports
[23:51] <TheMuso> pfein: That should have the info you need.


[08:59] <dholbach> good morning
[14:33] <daker> dholbach: https://fbcdn-sphotos-f-a.akamaihd.net/hphotos-ak-prn2/1480680_188079981393991_123273417_n.jpg
[15:25] <dholbach> daker, :-)
[15:25] <daker> dholbach: http://www.buzzfeed.com/marietelling/48-photos-qui-vous-donneront-envie-daller-au-maroc
[15:26] <daker> see "Rabat" photos, you had a photo with the extact shot
[15:27] <dholbach> daker, haha, yes that's right :)
[15:27] <dholbach> wow, many places I didn't get to see
[15:28] <daker> yes you need at least a month! not two weeks :)
[15:35] <dholbach> I know, I know, I know :)
[17:01] <dholbach> all right my friends - have a great rest of the year - see you in 2014! hugs!


[02:40] <czajkowski> nobody is awake in this timezone :(
[03:03]  * nigelb waves to czajkowski
[03:04] <nigelb> czajkowski: pleia2 is also probably awake.
[03:08] <czajkowski> nigelb: ello
[03:09] <nigelb> czajkowski: Where are you today? Far East or Far West?
[03:11] <czajkowski> west coast out in silicon valley
[03:42] <jose> o/
[03:42] <jose> half-awake, finishing up some university papers
[06:13] <dholbach> good morning
[07:24] <davidcalle> Morning o/
[07:25] <dholbach> salut davidcalle
[07:26] <davidcalle> Hey dholbach ! No, not deployed yet ;-)
[07:26] <dholbach> ok... fine
[07:26]  * dholbach storms out
[07:27] <davidcalle> :D
[10:06] <czajkowski> aloha
[10:17] <popey> yo
[10:26] <czajkowski> can I just point out timezones are a larege pita!
[10:59] <nigelb> heh
[16:01] <jono> dpm, hey
[16:01] <jono> all set?
[16:02] <dpm> yep


[00:57] <wallyworld> axw: no, we use the normal provider
[02:22] <thumper> axw: I don't suppose you know how to configure log forwarding?
[02:23] <axw> thumper: you need to set logforward-enabled=true, syslog-host=<host>, syslog-ca-cert=<pem-encoded-ca-cert>, syslog-client-cert=<pem-encoded-client-cert>, syslog-client-key=<pem-encoded-client-key>
[02:24] <axw> so easy ;)
[02:24] <thumper> in the model config?
[02:24] <axw> thumper: yep
[02:24] <axw> thumper: in the controller model config
[02:24] <axw> thumper: not to be confused with controller config...
[02:24] <thumper> hazaah
[02:24] <thumper> axw: I was thinking... we could make this change for log forwarding completely transparent...
[02:25] <thumper> by just making the worker model dependent and not one for the controller
[02:25] <thumper> and still have the tailer just deal with a single model
[02:26] <axw> thumper: yes we could. we'd just need to use model config defaults to ensure all models get the same syslog-foo config
[02:26] <thumper> or... transparently have that worker just get the config from the controller
[02:26] <thumper> and don't worry at this stage about getting it from the model config for *that* model
[02:27] <thumper> it is a bit ick, but not terrible
[02:29] <axw> thumper: what I want eventually is for different models to log to the relevant cloud log sink. so a GCE model should go into the stackdriver logging for that model's project. should be able to do something similar for Azure (though I can't quite figure out the API)
[02:29]  * thumper nods
[02:29] <axw> thumper: that would allow JAAS users to get their model logs
[02:29] <axw> without going through debug-l;og
[02:29] <thumper> sounds very useful
[02:30] <axw> thumper: it would be useful to have controller-wide config too though. so maybe a hierarchy.
[02:30]  * thumper nods
[02:30] <thumper> sounds like we should start a spec outlining the work
[02:31] <axw> should also run it by IS and JAAS, I'm sure they'll have some things they'd want
[02:31] <thumper> yeah
[02:31] <thumper> for the future work for sure
[02:31] <thumper> for the "let's not screw jaas"
[02:31] <thumper> I'm all for minimal exposure to the way it works now
[02:31] <axw> yup
[02:33]  * thumper may have found the next piece of work for babbageclunk
[02:33] <thumper> babbageclunk: call when you are around?
[03:10] <axw> wallyworld: have you snapped juju recently? it wants to use golang-go, which is go-1.6...
[03:12] <axw> hmm maybe it doesn't matter
[03:32] <babbageclunk> thumper: back, sorry, went for a run
[03:32] <thumper> gee, wouldn't want to run here today
[03:32] <thumper> it is wet and cold
[03:32] <thumper> getting very cold
[03:32] <thumper> like 5° cold
[03:32] <thumper> babbageclunk: hangout?
[03:33] <babbageclunk> beautiful day for a run here, cold and sunny and windy
[03:33] <thumper> babbageclunk: more stuff https://hangouts.google.com/hangouts/_/canonical.com/stuff
[05:38] <babbageclunk> wallyworld: can a relation change from being container-scoped to global-scoped? Maybe if there's charm upgrade? Trying to decide whether it's safe to cache decisions.
[06:23] <wallyworld> babbageclunk: i don't think so, no
[06:52] <rogpeppe> axw: saw my name mentioned earlier - did my recent changes break anything?
[06:52] <axw> rogpeppe: not sure, wallyworld said something about some cert related failures
[06:52] <wallyworld> rogpeppe: i sent an email
[06:53] <rogpeppe> wallyworld: ah, thanks
[06:53] <wallyworld> it appears it may have
[06:53] <wallyworld> not 100% sure
[06:54] <rogpeppe> wallyworld: are those errors happening every time?
[06:55] <wallyworld> not sure, there had only been one or two test runs post the landing that i had checked this morning
[06:58] <rogpeppe> wallyworld: hmm, it definitely isn't happening every time. weird.
[06:58] <rogpeppe> wallyworld: it's definitely the kind of area that *could* have been affected by my change
[06:58] <rogpeppe> wallyworld: but i'd expect it to be deterministic
[06:58] <wallyworld> yeah. it's plausible the pR and failures are related but not certain
[06:59] <wallyworld> i looked at the test runs just prior to the landing and couldn't see the failures there
[06:59] <wallyworld> but hard to draw a conclusion when it is intermittent
[06:59] <rogpeppe> wallyworld: yeah
[07:00] <wallyworld> i was thinking something may jump out at you
[07:00] <wallyworld> it's not an area i have expert knowledge in
[07:06] <rogpeppe> wallyworld: nothing's jumping out so far
[07:06] <wallyworld> joy
[07:16] <rogpeppe> wallyworld: we'll have to see if more of those kind of errors happen
[07:17] <wallyworld> yeah, need a few runs to gauge the depth of the issue
[07:17] <rogpeppe> wallyworld: in http://juju-ci.vapour.ws/job/github-check-merge-juju/1087/artifact/artifacts/grant.log there's at least one suspicious-looking error after the cert error
[07:17] <rogpeppe> 22:53:50 ERROR juju.tools.lxdclient client_instance.go:267 while removing instance "juju-85ed71-0": Failed to destroy ZFS filesystem: cannot open 'lxd-pool/containers/juju-85ed71-0': dataset does not exist
[07:17] <rogpeppe> wallyworld: so perhaps the cert error is usual
[07:19] <wallyworld> maybe, could be a timing issue
[08:42] <wallyworld> axw: a small PR, quick review? https://github.com/juju/juju/pull/7365
[08:43] <axw> wallyworld: sure, just a minute
[08:50] <axw> wallyworld: swap you https://github.com/juju/juju/pull/7366 ?
[08:50] <wallyworld> ok
[08:51] <wallyworld> axw: those pyc files were supposed to be removed already!
[08:52] <axw> wallyworld: I think they were removed in one directory but not the other
[08:52] <axw> anyway, added to gitignore so they won't sneak back in
[08:52] <wallyworld> 2 files is better than 108 :-)
[08:54] <wallyworld> axw: lgtm, will be good to see those tests passing again
[08:59] <axw> wallyworld: to save a roundtrip, my reply to your Q: "Why? ssh.Client.Command documents the argument as taking the syntax [user@]host. It shouldn't be needed."
[09:01] <wallyworld> axw: ok, no worries, i just thought it made it more obvious to the reader in the restore code. but i'm totally +-0 , ie no care factor either way
[09:02] <axw> wallyworld: if someone gets surprised they can add it back in :)
[09:07] <wallyworld> axw: i called it "cloudProviders" becuase it returns both addable and non-addable ones in 2 separate slices
[09:08] <axw> wallyworld: but the result is "providers", and "unsupported"
[09:08] <axw> wallyworld: cloudProviders+providers+unsupported doesn't tell me what it does
[09:08] <wallyworld> yeah, i just reused the previous var names, i can change to supported and unsupported
[09:09] <axw> no biggie, just not a super useful name when you're out of context
[09:09] <wallyworld> yeah, i'll come up with something
[09:10] <wallyworld> there's also a test isolation issue too from what was there already :-/
[09:10] <wallyworld> in the credential related suites somewhere. need to fix that too
[09:32] <wpk> Q: is it OK to remove API that's used only internally, by worker?
[09:37] <babbageclunk> wpk: I think the problem is that the controller might be running a more recent version of jujud than the agents, so they might still try to talk to the removed API/
[09:38] <babbageclunk> wpk: Oh, hang on - is it used by a worker in the unit or machine agents, or only in the model agent?
[09:41] <babbageclunk> wpk: I think in the latter case it's fine.
[09:48] <wpk> only in model agent
[09:48] <wpk> (discoverspaces worker)
[12:13] <rogpeppe> anyone know if the old juju reviews are still online? e.g. http://reviews.vapour.ws/r/1609
[12:34] <babbageclunk> rogpeppe: no, I think they turned them off a few weeks ago
[12:34] <rogpeppe> babbageclunk: oh
[12:34] <rogpeppe> babbageclunk: i think that's a really bad idea
[12:35] <rogpeppe> babbageclunk: they're actually a crucial part of the history of the project
[12:35] <babbageclunk> rogpeppe: I know - just after it happened I wanted to find something that I remember discussing in a review.
[12:35] <rogpeppe> babbageclunk: commit messages are often cursory at best
[12:35] <rogpeppe> babbageclunk: can we try getting them turned back on again?
[12:36] <babbageclunk> rogpeppe: yeah, I'll mention it to Tim
[12:36] <rogpeppe> babbageclunk: thanks
[12:36] <babbageclunk> (I mean, I assume they've kept the data!)
[12:36] <babbageclunk> :o
[12:38] <rogpeppe> babbageclunk: if they haven't, i'll be very unhappy
[12:38] <babbageclunk> I'll pass that on too
[12:40] <rogpeppe> babbageclunk: :)
[19:00] <balloons> hml, can I get a review of https://github.com/juju/juju/pull/7362?
[19:00] <hml> balloons: looking
[19:02] <hml> balloons: ha - i hate assuming anything… but… that’s a lot of files.  :-)
[19:03] <balloons> hml, :p It's akin to the PR I mention.. It's more or less dumping in the code from the old repos into juju
[19:03] <balloons> hml, there's one more for packaging, once I complete it :-)
[19:04] <hml> balloons: figured… i’ll go with assume this time if that’s okay with  you?  or do you want a sanity check?
[19:04] <balloons> hml, i don't just want to blind push things, hence the PR. So yes, a quick sanity check is most appreciated
[19:04] <hml> balloons: sanity checking now
[19:05] <balloons> I had to tweak the history on this import, so make sure it's clean for you
[19:08] <hml> balloons: where is the origin repro - haven’t mastered finding them in launchpad yet
[19:10] <balloons> hml, ahh, right. https://code.launchpad.net/~juju-qa/juju-ci-tools/repository
[19:10] <hml> balloons: ty


[14:59] <pleia2> I did some organization last night, going to send this off to the summary writers now (quite a bit early) so they can get a jump start and since I'm about to hop on another plane, bound for family duties on the other end this evening
[14:59] <pleia2> feel free to continue to add articles as they come up :)
[15:00] <PaulW2U> Good idea !
[15:01] <pleia2> PaulW2U: thanks so much for link collection again this week \o/
[15:04] <PaulW2U> np, do we include every planet article that mentions 14.10? I can see another 5 already
[15:05]  * pleia2 takes a look
[15:06] <pleia2> so I tossed the Flavors ones into a section under the release announcement
[15:06] <pleia2> I think it's ok to add the posts from individuals to the planet section
[15:07] <PaulW2U> ok
[15:11] <silverlion> hey pleia2
[15:15] <pleia2> good day silverlion