[06:01] <retour> Hi all! I have a Compaq Proliant 2500 with dual PentiumPro + UltraWide SCSI RAID adapter and 4 SCSI drives (Raid0). Ubuntu 7.04 desktop fails to install with kernel panic. I expect problems with detection of memory amount (280MB). Do I have a better chance with Ubuntu server edition or they are generally same distros with differently preconfigured packages?
[06:02] <tgm4883_laptop> retour, perhaps this is better in #ubuntu?
[06:05] <retour> tgm: I did but no reply so far? This question is not proper here? What Masters of Univers community is all about? Not supergeeks?
[06:05] <tgm4883_laptop> retour, its for the universe repo
[06:05] <tgm4883_laptop> packaging and such
[06:06] <tgm4883_laptop> retour, https://wiki.ubuntu.com/MOTU
[06:08] <retour> thank you! sorry for bothering wrong channel
[06:13] <gouki> Supergeeks?!
[07:38] <dholbach> good morning
[07:39] <Hobbsee> it's dholbach!  everybody behave!
[07:39] <LaserJock> dholbach!
[07:39] <dholbach> hey LaserJock
[07:40] <man-di> grrrr
[07:40] <StevenK> man-di: Tribe 4?
[07:41] <jmg> ^
[07:41] <man-di> StevenK: needs to long to download
[07:41] <man-di> I want to boot my main machine
[07:42] <man-di> problem is that my kernel is on / inside LVM which needs lilo
[07:42] <man-di> and lilo broke somehow
[07:42] <jmg> kernel should be on boot outside lvm
[07:42] <StevenK> Agreed
[07:43] <jmg> it can be on a raid1 but not an lvm
[07:43] <man-di> jmg: yes, I was to lame to think of that on install, I wanted to fix this today
[07:43] <jmg> man-di: ha ha </nelson>
[07:43] <man-di> it bootet from lvm with lilo okay yesterday
[07:43] <man-di> just grub1 doesnt support kernel on lvm
[07:44] <jmg> quick, someone set up man-di an internet listening tftp server, so he can netboot
[07:44] <man-di> jmg: already tried as a i have netboot here
[07:44] <jmg> man-di: how did it fail?
[07:44] <man-di> but this damn machine rejects to boot with this either
[07:45] <jmg> doh
[07:45] <man-di> I think its mainly due to the network driver not being in the official kernel yet
[07:46] <jmg> man-di: ouch
[07:46] <jmg> man-di: sounds like you've got a real lemony snicket
[07:47] <man-di> yeh
[07:47] <man-di> was fun to install Linux on this machine
[07:47] <jmg> man-di: rebuild kernel?
[07:47] <jmg> man-di: what machine is it?
[07:47] <man-di> I had to put another network card into it for installation
[07:48] <man-di> its Core2Quad with marvell chipset
[07:48] <man-di> was really fun that neither chipset nor ethernet driver are in official kernel yet, only in git of sub-projects
[07:49] <jmg> man-di: so check out the git tree and build it
[07:50] <man-di> gaaa
[07:50] <man-di> I just want it to work
[07:50] <jmg> heh
[07:50] <man-di> jmg: so I need to use a slow machine to build a new kernel to be able to boot that fast machine
[07:51] <man-di> if I want it really slow I could try to build the kernel on the NSLU2...
[07:51] <jmg> man-di: now you're getting somewhere
[08:35] <lucas> Hobbsee: (re: kde on http://people.debian.org/~lucas/ubuntu-versions/)
[08:35] <lucas> how do I determine which packages to list on that page?
[08:35] <Hobbsee> lucas: section: kde, i thought
[08:39] <lucas> would that pick them all?
[08:40] <Hobbsee> i didnt think so - it wouldnt do the section: gnome, section: utils, etc...
[08:40] <lucas> no I mean: wouldn't it miss interesting packages?
[08:41] <Hobbsee> well, ideallyyou'd do one for every section, i guess
[08:41] <lucas> I mean: interesting packages for you
[08:42] <Hobbsee> oh right.
[08:42] <Hobbsee> lucas: if i'm interested in a particualr package, i normally subscribe thru LP, check the upstream rss feed, etc.
[08:42] <Hobbsee> lucas: i'm thinking for thsoe of us interested in sections
[08:42] <lucas> for example k3b is KDE and Section: otherfs
[08:42] <lucas> otherosfs
[08:43] <Hobbsee> oh, interesting.
[08:43] <Hobbsee> hmmm, then i dont know
[08:45] <\sh_away> lucas: fix it
[08:47] <lucas> it was just an example, there are probably other packages in the same case
[08:48] <lucas> I could use apt-rdepends to find all the interesting packages, but not as long as it's on gluck.d.o
[08:59] <superm1> Hobbsee, what would be the best way to address a question to the motu-uvf team, since there doesn't appear to be a mailing list?  Should i just post to the normal motu mailing list?
[08:59] <Hobbsee> superm1: yeah
[09:00] <superm1> ok
[09:00] <Hobbsee> superm1: of course, you could CC all the members of the team,b ut that doesnt do well for privacy
[09:00] <Hobbsee> er, for public-nature of mail
[09:00] <superm1> that's what i assumed
[09:01] <superm1> hence i wanted to double check what you thought would be better
[09:06] <Hobbsee> superm1: depends on the tone of the mail, i expect.
[09:06] <Hobbsee> superm1: and what wider things are in MOTU
[09:07] <superm1> Hobbsee, I'll fire it off later on and you'll see i guess :)  Bed time for me now. nn
[09:07] <StevenK> man-di: So, what's happening with sear? :-)
[09:07] <Hobbsee> night!
[09:07] <man-di> StevenK: current I package sear CVS
[09:07] <man-di> but it needs libwfut (which is not in Debian yet)
[09:08] <man-di> sear cvs is the only version supporting guichan 0.6.1
[09:08] <man-di> I'm talking on sponsoring with the libwfut maintainer
[09:09] <StevenK> man-di: Will libwfut also build in Ubuntu?
[09:11] <man-di> yes
[09:11] <man-di> its a pretty simple lib
[09:11] <man-di> no strange dependecies
[09:12] <man-di> I just need to teach its maintainer not to use automake when he dont needs to
[09:12] <elmargol> how do I sign my package source?
[09:12] <man-di> elmargol: with debsign
[09:13] <elmargol> man-di: fakeroot dpkg-buildpackage -sa? and then debsign?
[09:16] <Hobbsee> you can specify with -k<keyid> and it will let you sign it too
[09:17] <elmargol> Hobbsee: How can I disable the build process? I just need the signed source
[09:18] <TheMuso> dpkg-buildpackage -rfakeroot -S
[09:19] <Hobbsee> use -S
[09:19] <elmargol> thx
[09:26] <Hobbsee> siretart: what's the new address for http://tiber.tauware.de/~sistpoty/MoM ?
[09:28] <Hobbsee> (or isnt there one yet?)
[09:30] <Hobbsee> Since we cannot assume, that tiber was in fact not compromised, all the
[09:30] <Hobbsee> previously uploaded packages were not imported into the new instance. Also
[09:30] <Hobbsee> the database started completely empty.
[09:30] <Hobbsee> \o/
[09:30] <Hobbsee> excellent!
[09:31] <Hobbsee> well, that makes reviewing easier for a start
[09:33] <ajmitch> yep! :)
[09:35] <Hobbsee> hehe, yeah
[09:35] <dholbach> ajmitch: ~30000 mails when I got back
[09:36] <Hobbsee> dholbach: that's impressive.  a lot of that would be -bugs?
[09:36] <dholbach> yeah
[09:36] <ajmitch> select all, delete
[09:36] <Hobbsee> exactly
[09:50] <TheMuso> o/c
[09:50] <TheMuso> ugh
[09:51] <TheMuso> Well, at least my workflow will be changing for good soon...
[09:51] <TheMuso> No more eratic kvm+crappy screen reader output.
[10:07] <elmargol> I have a question about a init.d file. On debian they use {} around variables. Why doesn't this work on ubuntu feisty fawn?
[10:08] <Hobbsee> elmargol: bash vs dash
[10:11] <elmargol> Hobbsee: Do we use dash or bash on feisty?
[10:11] <Hobbsee> elmargol:
[10:11] <Hobbsee> sarah@LongPointyStick:~$ ls -lh /bin/sh
[10:11] <Hobbsee> lrwxrwxrwx 1 root root 4 2007-06-22 04:11 /bin/sh -> dash
[10:14] <elmargol> Hobbsee: how do I fix this? use /bin/bash instead of /bin/sh?
[10:14] <Hobbsee> no, you remove the bashism, so it works on all POSIX-compliant shells.
[10:15] <elmargol> is there a way to see non working lines?
[10:15] <Hobbsee> dash -n script
[10:15] <elmargol> big thx
[10:15] <Hobbsee> foo{bar1, bar2}'s are bashisms, definetly
[10:15] <Hobbsee> use foobar1, foobar2 instead
[10:15] <Hobbsee> etc
[10:16] <revilodraw> does anyone know how i can make my laptop audio buttons work in kde, because they work in gnome but not kde
[10:17] <Hobbsee> revilodraw: which model laptop, and which ones?
[10:18] <revilodraw> Hobbsee: its a dell inspiron 6400 and i would like to be able to get the volume up/down and mute buttons to work
[10:19] <Hobbsee> revilodraw: ahhh.  and they dont work in amarok?
[10:19] <Hobbsee> revilodraw: set the global shortcuts in amarok.  they do work, except there's something in amarok stopping them.  they're set correctly in kmilo
[10:20] <revilodraw> Hobbsee: they used to work in amarok, but i dont use amarok because it performs terribly in both environments (it used to work beautifully though, and i have tried reinstalling)
[10:20] <revilodraw> hobbsee: its not just amarok, they dont work  at all in the kde environemnt
[10:20] <Hobbsee> no, but htey usually work once you set them in amarok.
[10:20] <Hobbsee> regardless of whether you use amarok again
[10:21] <Hobbsee> at least, that's what i've found.
[10:21] <revilodraw> hobbsee: ok thats weird, it shouldnt be like that; kde shouldnt rely on amarok at all...but thanks a lot for the info
[10:21] <Hobbsee> revilodraw: i don thitnk it does - i think amarok ends up screwing it up
[10:21] <Hobbsee> revilodraw: like i say, those are correctly coded into kmilo
[10:22] <revilodraw> hobbsee: wow u are right changing them in amarok helped thank you!! but what is kmilo?
[10:23] <Hobbsee> it's the kde daemon thing for keyboard shortcuts
[10:23] <revilodraw> hobbsee: ooh ok how can i access it by itself?
[10:24] <Hobbsee> revilodraw: i suspect /usr/share/hotkey-setup/dell.hk
[10:25] <revilodraw> Hobbsee: ok thanks! actually the buttons arent turning my speaker volume up/down they r turning the volume bar up and down in amarok
[10:25] <Hobbsee> and if you close amarok?
[10:25] <Hobbsee> that's weird though.  it "just works" here
[10:25] <revilodraw> ill try
[10:26] <revilodraw> hmm yeh when amarok is closed the buttons dont respond to being pushed... ill try configuring the keyboard shortcuts in kde
[11:56] <DarkSun88> Hi all
[11:57] <norsetto> hiya all
[11:58] <dholbach> hey norsetto
[11:59] <norsetto> daniel \o/
[11:59] <dholbacj> norsetto: you've been quite busy, when I was not around
[12:00] <norsetto> whats up mate? safe and well I hope !? wading through those 2546748 emails I guess ....
[12:00] <dholbach> exactly :)
[12:00] <norsetto> dholbach: hey, I'm only responsible for 10% of that .....
[12:01] <dholbach> hehehe :)
[12:05] <dholbach> norsetto: at some stage, highvoltage, you and I should discuss how we can speed up the mentoring
[12:06] <dholbach> norsetto: we should make it absolutely clear that our mentoring is just supposed to help with the initial steps and not guiding contributors up until they become MOTUs
[12:06] <dholbach> helping with getting the first upload done via the normal review process should be the number one task for mentors
[12:07] <dholbach> after that people should be able to cope with the regular processes which work quite well now
[12:07] <dholbach> but maybe we should take some more time to discuss this properly
[12:08] <dholbach> also having some kind of ongoing QA of our documentation would be something we should make easier
[12:08] <dholbach> the faster the process, the more contributors we can take on
[12:09] <norsetto> dholbach: yes, I think we should discuss this properly
[12:10] <dholbach> do you think my ideas roughly make sense?
[12:12] <norsetto> dholbach: not sure actually; I mean, do we need mentors to tell where to finds bugs and how do we upload to REVU?
[12:13] <dholbach> I just think that the sponsoring teams should take care of reviews and helping out with that
[12:14] <norsetto> dholbach: definetively
[12:14] <TheMuso> I sometimes feel that there are only a few MOTUs who help process the Ubuntu universe Sponsors queue in Launchpad.
[12:14] <dholbach> mentors should probably be more on the "hand holding" side regarding processes, documentation links, who to talk to, where to look for answers and so on
[12:14] <dholbach> TheMuso: I'll put more efforts into that again once I'm through my mail backlog
[12:15] <norsetto> dholbach: seems a bit diminutive to me (but then, I look at it from the other side of the fence)
[12:15] <dholbach> and make sure that some canonical people take care of them as well
[12:15] <TheMuso> dholbach: Not asking you specifically to have a look, but it seems that not many active MOTUs help with sponsoring... Or thats how it seems to me anyway.
[12:15] <norsetto> TheMuso: Hi Luke, any feedback on that email of mine?
[12:16] <Hobbsee> TheMuso: i suspect that's accurate
[12:16] <TheMuso> norsetto: not yet.
[12:16] <dholbach> norsetto: what I see at the moment is that we have lots of people sitting on the mentoring slots and they don't make use of the 'official processes' we have
[12:16] <dholbach> norsetto: like 1) using sponsoring bugs, 2) asking the motu mentors list for help, 3) asking for more, better, fixed documentation and so on
[12:17] <norsetto> dholbach: yes thats correct
[12:17] <dholbach> norsetto: I think that motu mentors is a valuable addition, but they shouldn't try to do everything
[12:18] <norsetto> dholbach: please tell her to stop biting :-)
[12:19] <dholbach> norsetto: I tried that for ages now
[12:19] <Hobbsee> norsetto: me?  bite?
[12:20] <Hobbsee> dholbach: you know better than that.  i dont bite, i poke people in the ribs.
[12:20] <norsetto> dholbach: I have mixed feeling about this now; I have the impression that the program is actually making us loose contributors instead of gaining them
[12:20] <highvoltage> dholbach: indeed. it wasn't clear to me in the beginning either, I can see how people can think that mentoring is for more than the initial steps
[12:21] <highvoltage> (sorry for lag, at work atm)
[12:21] <norsetto> highvoltage: hi mate!
[12:21] <Hobbsee> i get the feeling that hopefulls feel that they hvae to have a mentor to get anywhere
[12:21] <Hobbsee> and hwile that helps...
[12:21] <dholbach> highvoltage, norsetto - maybe we should discuss this on ubuntu-motu-mentors@
[12:22] <dholbach> highvoltage, norsetto: I'll try to write that up properly
[12:22] <highvoltage> dholbach: that would be convenient
[12:22] <Hobbsee> oh meh, that would require me subscribing to the thing, to read it
[12:23] <norsetto> dholbach: I have the impression that hobbsee is volunteering as a mentor (mentrice?), should I add a slot for her?
[12:23] <Hobbsee> dream on
[12:24] <Hobbsee> i dont have the patience for it, havent you seen me in here enough to know?
[12:24] <norsetto> hobbsee: I have a contributor ready for you ;-)
[12:24] <Hobbsee> norsetto: oh, who?
[12:24] <Hobbsee> norsetto: if you say kmos, i'm going to kill you...
[12:24] <Hobbsee> very, very painfully
[12:24] <norsetto> :-X
[12:25] <zul> yeah Hobbsee is evil
[12:25] <Hobbsee> zul: do you sponsor people?
[12:25] <zul> *snicker* i sponsored you ;)
[12:26] <Hobbsee> zul: er, make that mentoring.
[12:26] <zul> you are still evil though
[12:26] <zul> again *snicker*
[12:26] <zul> i dont hvae the patience
[12:26] <Hobbsee> zul: you just wait until i meet you at UDS
[12:27] <zul> if i go ;)
[12:27] <Hobbsee> well, whichever one you go to
[12:27] <Hobbsee> zul: you cant use that reason, because i've already used it.
[12:27] <zul> probably at gutsy+2 when I can get time off of work
[12:28] <Hobbsee> that'd be cool
[12:28] <zul> Hobbsee: er...I dont have the stamina?
[12:28] <Hobbsee> zul: tryand get that one past dholbach
[12:28] <zul> heh
[12:29] <mok0> By mistake I dput a _i386.changes file to REVU. Can someone here nuke it please?
[12:29] <mok0> Its called btk-core-0.8.1
[12:32] <TheMuso> It does.
[12:32] <TheMuso> at the moment.
[12:32] <Kmos> [11:24]  <Hobbsee> norsetto: if you say kmos, i'm going to kill you...
[12:32] <Kmos> LOL
[12:33] <Hobbsee> TheMuso: ah, i have a shell there, but am not in hte revu group
[12:33] <Hobbsee> Kmos: :)
[12:34] <mok0> Thanks for looking. I'll ask again later.
[12:34] <TheMuso> Hobbsee: Some of us regulars around here should be added to the group, so we can help admin.
[12:34] <TheMuso> I was actually going to ask for revu admin rights until it went down.
[12:34] <Hobbsee> TheMuso: true, but siretart's rethinking security, etc
[12:34] <TheMuso> riht
[12:34] <TheMuso> right
[12:34] <mok0> Uploaders should be able to nuke their own uploads.
[12:35] <Hobbsee> then again, any MOTU should be able to have permission, theoretically speaking
[12:35] <Hobbsee> mok0: requires a shell to do the removing.
[12:35] <Kmos> mok0: maybe in the next version of revu website.
[12:35] <Hobbsee> if anyone ever codes it
[12:35] <Kmos> yeah
[12:36] <mok0> Hobbsee: I am thinking of revising revu so it could be done without shell acess
[12:36] <Kmos> that will be a easy one =)
[12:36] <Hobbsee> that'd be nice
[12:36] <mok0> the authentication is in place
[12:37] <mok0> alternatively, they should give support for dget
[12:37] <Hobbsee> it had support for dget
[12:37] <mok0> Hobbsee: and... ?
[12:38] <Hobbsee> so i'm not sure why you'd be trying to add it :)
[12:38] <mok0> Hobbsee: Why was it removed?
[12:38] <Hobbsee> i dont think it was.  i'm fairly sure that it still exists
[12:39] <Hobbsee> although i've not tried on the interim server
[12:39] <mok0> I'll try it
[12:40] <norsetto> anyone know what is the status for REVU passwords? Can we use the old one? Do we have to require a new one?
[12:40] <Hobbsee> norsetto: recover it
[12:40] <Hobbsee> norsetto: i think that was said in the revu mail from siretart
[12:40] <norsetto> Hobbsee: tried but doesn't work :-(
[12:40] <Hobbsee> norsetto: it got comprimised, so all the packages on there got ditched, and all the passwords got changed
[12:41] <geser> Hobbsee: recover works only for MOTUs, contributors need a new upload
[12:41] <Hobbsee> norsetto: it may not all be working yet.
[12:41] <Hobbsee> geser: ahhhh....
[12:41] <Hobbsee> thanks
[12:41] <geser> siretart imported only the ubuntu-dev group
[12:41] <norsetto> Hobbsee: yeah, I get None as a result (which I even tried, its not a good password :-))
[12:42] <Hobbsee> hehe
[12:42] <Hobbsee> geser: ahhh, right, yes
[12:42] <Hobbsee> this is what happens when i only skim ~40 emails in one hit
[12:43] <siretart> oh, yummy hilights
[12:43] <Hobbsee> siretart: indeed!
[12:43] <siretart> I read help offers in the backlog?
[12:44] <norsetto> geser: thx
[12:44] <siretart> we (sistpoty and me) could really need help with revu's new home
[12:46] <siretart> btw, since sparky is part of the ubuntuwire network, all ubuntu-dev people can login on tiber and look how it works
[12:46] <Hobbsee> siretart: we dont have permission, not being in the revu team to delete, though
[12:46] <siretart> delete?
[12:47] <Hobbsee> siretart: or move, etc.
[12:47] <Hobbsee> siretart: things from incomming or whatever
[12:47] <siretart> ah, the incomine queue, true
[12:47] <siretart> the queue seems to be 777 now, no need for the group AFAISI
[12:50] <siretart> Hobbsee: ok, I'll add you to the revu group
[12:50] <siretart> sistpoty  is standing next to me
[12:50] <Hobbsee> cool
[12:50] <siretart> Adding user `hobbsee' to group `revu' ...
[12:50] <siretart> Done.
[12:51] <siretart> he waves back
[12:51] <Hobbsee> there we go, removed.
[12:51] <Hobbsee> thanks
[12:52] <Hobbsee> haha
[12:52] <Hobbsee> that reminds me of vuntz
[12:52] <Hobbsee> (read his blog posts about guadec)
[12:54] <mok0> I could now upload, thanks y'all!
[12:56] <mok0> (btw, in the discussion above, I said "dget", I meant "dcut". Silly me)
[01:29] <geser> Hobbsee: have you seen bug #133590? doesn't it need an UVFe?
[01:29] <ubotu> Launchpad bug 133590 in swfdec-mozilla "Please sync swfdec-mozilla (universe) from Debian unstable (main)" [Undecided,Confirmed]  https://launchpad.net/bugs/133590
[01:29] <siretart> Hobbsee: ok good news. We have a new home for revu (and revu2 development) now. the host will be named 'spooky.informatik.uni-erlangen.de'. sistpoty and me will be local admins, hosting is at university of erlangen
[01:29] <siretart> the machine needs to be setup. sistpoty and me will try to do that on friday afternoon
[01:32] <Hobbsee> siretart: neat!  :)
[01:32] <Hobbsee> slomo: ping
[01:32] <Hobbsee> geser: i hadnt, no
[01:59] <toutouff> waw, nice one :)
[02:13] <ScottK> Good morning all.
[02:13] <TheMuso> Hey ScottK.
[02:13] <Hobbsee> hi ScottK
[02:14] <zul> hey ScottK
[02:14] <geser> Hi ScottK
[02:15] <ScottK> Hello TheMuso, Hobbsee, zul, and geser
[02:15] <TheMuso> Hey persia. Long time no see.
[02:16] <persia> TheMuso: Hey.
[02:16] <geser> Hi persia
[02:17] <persia> hi geser.  Thanks for watching for gaphas.
[02:17] <geser> persia: what problems did you have with the gaphas package?
[02:18] <geser> I changed debian/pyversions to 2.5 to get it build with python2.5
[02:18] <persia> geser: pyversions << 2.,4.  ezinstall builds nose egg info on clean:, etc.
[02:19] <persia> geser: You could build a package after removing pyversions?  For me, debian/clean wasn't.
[02:19] <geser> importing the gaphas module build for python2.5 worked
[02:20] <xxxxx1> mornin' people
[02:20] <xxxxx1> :)
[02:20] <geser> persia: Depends: python (>= 2.5), python (<< 2.6), python-support (>= 0.2), python-decorator, python-gtk2
[02:20] <geser> after changing debian/pyversions to 2.5
[02:21] <persia> geser: Hmm...  I wonder why I get nose-0.10.0b1-py2.5.egg/
[02:21] <geser> had you have python-setuptools installed?
[02:22] <persia> geser: Yes.
[02:22] <geser> without it fetched some eggs from the internet
[02:22] <persia> geser: I get eggs from the internet even with python-setuptools installed.  I suspect it's because I didn't have python-nose installed on the host (only in the build chroot).
[02:24] <persia> geser: More generally, if I build everything in gaphas & gaphor (using cheeseshop eggs), I run into problems with zope.  I think I can get it working with gaphor 0.10.4, but I'm not sure if I want gaphas 0.1.4, 0.2.0, or 0.3.x yet.
[02:24] <geser> looking on it again I guess I build the source package with dpkg-source -b as I don't have a changes file (didn't generate it yet)
[02:24] <ScottK> geser: The other thing is that if you have to make a change (e.g. python 2.4 -> 2.5) then you don't need to request a sync.  Just modify the package and upload it like you would for a merge.
[02:24] <persia> geser: Hmm.  Do you have python-nose installed locally?
[02:25] <persia> ScottK: sync request is already gone :)
[02:25] <geser> ScottK: I know, persia mentioned the needed change in my sync request
[02:25] <ScottK> OK.
[02:26] <ScottK> I was under the impression you knew about it before you requested.  Nevermind.
[02:26] <geser> persia: not in my dev chroot
[02:26] <persia> ScottK: What's your opinion of ezinstall use in debian/rules?
[02:26] <ScottK> Bad.
[02:27] <persia> geser: Interesting.  I get "unrepresentable changes to source" when trying `debuild -S -sa`.  Perhaps it makes binaries, but not source.
[02:27] <ScottK> That's the one that grabs modules and downloads the from the net, right?
[02:27] <persia> ScottK: That's the feeling I had.  Thanks for the confirmation.
[02:27] <persia> ScottK: Yep.
[02:28] <geser> persia: I had those at first too, therefore I redid my change and build the source package with dpkg-source -b
[02:28] <ScottK> It is a pretty sigificant breach of the pakcaging system.
[02:28] <persia> ScottK: You'll find the upstream solution for http://gaphor.devjavu.com/projects/gaphor/ticket/36 amusing then :)
[02:29] <persia> geser: Ah.  That makes sense.  I'm not happy about dpkg-source -b, as it makes life hard for people making patches.  I'm hoping to find a solution that doesn't involve randomly installing things from the internet (although I only have 10 days left :))
[02:29] <ScottK> As an upstream, that's a reasonable response.  Debian packaging problems aren't their problem.
[02:29] <ScottK> persia: There are new package freeze exceptions too.
[02:29] <persia> ScottK: I guess.  I still prefer exception handling for missing libraries, etc.
[02:30] <ScottK> Agreed.
[02:30] <ScottK> For gaphas, I'd be supportive of an exception if needed.
[02:30] <persia> ScottK: I don't think I can make a convincing argument for a freeze exception for gaphor: it's been broken since Breezy/
[02:30] <ScottK> Actually, I think that makes it easier.
[02:30] <ScottK> No regression risk which is the big thing to avoid.
[02:31] <ScottK> Lots of people complain about it too.
[02:31] <persia> ScottK: Hmmm..  Interesting viewpoint.  I'd think rather that it wasn't a feature that was sufficiently important for such a late change.
[02:31] <ScottK> What $SOMONE should do is write a debianized replacement for ezinstall that works within the packaging system.
[02:32] <geser> persia: I installed now also python-nose and run dpkg-buildpackage -S and the debdiff shows no extra eggs
[02:32] <ScottK> $SOMONE/SOMEONE
[02:32] <ScottK> persia: I view the freeze process as a risk management excercise.  In the case of gaphor, there is no downside risk.
[02:33] <persia> geser: Hmm..   I don't think there is Pre-Build-Depends.  I still don't think that the package is right, but I wouldn't object to an upload with the base changes, as long as it results in a working gaphor (which really needs zope investigation).
[02:34] <geser> persia: are we talking now about gaphor or gaphas?
[02:34] <persia> ScottK: That makes quite a bit of sense.  I'm certainly reevaluating.
[02:34] <persia> geser: They are related.  I don't see any point to adding gaphas unless it makes gaphor work.  If there's another client, either 0.2.0 or 0.3.x would be a reasonable candidate.
[02:35] <geser> persia: ok, but currently gaphor has an unmet dep on python-gaphas
[02:36] <persia> geser: Right.  gaphor hasn't worked since breezy, for a variety of reasons.  In my tests with gaphas 0.1.4 and gaphas 0.2.0, I was not able to get gaphor working.  Unless there is another program that depends on python-gaphas, it doesn't really matter if it's an unmetdep or a segfault, as I see it.
[02:37] <xxxxx1> hey persia, ScottK, TheMuso
[02:37] <persia> On the other hand, if I still don't have something working in another week, I'll probably upload 0.2.0, just to get the package in, with additional efforts to get it clean afterwards.
[02:37] <miles> hello all
[02:37] <persia> xxxxx1: Hey.
[02:37] <ScottK> Hello xxxxx1.
[02:39] <geser> persia: does gaphor in Debian the same problems?
[02:40] <persia> geser: Yep.  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423515 is the root.  I've been exchanging email with Cdric, but with UVF, and UNF approaching, I uploaded gaphor so as not to need a UVF exception.
[02:40] <ubotu> Debian bug 423515 in gaphor "gaphor segfaults after upgrading python-diacanvas2" [Normal,Open] 
[02:41] <persia> That's the same as bug 30344
[02:41] <ubotu> Launchpad bug 30344 in gaphor "Gaphor doesn't start" [High,Incomplete]  https://launchpad.net/bugs/30344
[02:41] <geser> persia: I'd prefer to have python-gaphas in the archive. That way one could fix gaphor (if a fix gets found) after the release through -updates (or -backports)
[02:43] <persia> geser: OK.  Feel free to upload if you think it's important.  My main reason for wanting another week is UVF: I don't know if I want to grab gaphas 0.3.x, but most of the necessary changes can probably be done in a patch.
[02:44] <Hobbsee> persia: you should be able to still get a UVF for most thigns, at this point
[02:44] <zul> grrr...must kill
[02:44] <persia> Hobbsee: Yes, but given my current time committments, it's easier to do things in a way that doesn't require approval :)
[02:45] <geser> persia: I can wait with uploading gaphas till short before NPFU if that helps you
[02:45] <Hobbsee> persia: :)
[02:45] <persia> geser: Thanks.  I'm hoping to have a bit of time this week to chase it, but will definitely upload some version of gaphas this coming weekend, whether I find a final solution or not.
[02:46] <geser> ok
[02:46] <persia> geser: Do you have any pending changes other than the python 2.5 dependencies?
[02:47] <persia> geser: Also, why python (<< 2.6)?
[02:52] <slomo> Hobbsee: pong? re: swfdec-mozilla, i didn't notice that uvf was in effect already... i thought it is tomorrow
[02:52] <Hobbsee> slomo: that's main freeze for tribe 5
[02:53] <ScottK> slomo: Are you subscribed to the MOTU mailing list?
[02:54] <slomo> Hobbsee: i'll care for proper uvf exception stuff later, thanks for noticing ;)
[02:54] <slomo> bbl
[02:54] <slomo> ScottK: sure
[02:54] <Hobbsee> slomo: no problem, and thank geser
[02:54] <ScottK> OK.  I was just wondering because Hobbsee forwarded the UVF announcement there.  That's all.
[02:56] <persia> ScottK: About zekr: do you know why the MOZILLA_FIVE_HOME check was trimmed so agressively?
[02:56] <ScottK2> persia: No.  I know he got some comments from the upstream about the package, but not if that's related.
[02:57] <ScottK2> Let me see if I can find his e-mail and forward it to you.
[02:57] <persia> ScottK2: Thanks.  It doesn't seem to break anything, but I generally don't like to sponsor things I don't understand :)
[02:58] <ScottK2> I can understand that.
[02:59] <ScottK2> persia: I thought he'd sent me mail that talked about the changes, but I can't find it.
[03:00] <persia> ScottK2: OK.  I'm otherwise happy, but am not likely to find time to chase him down.  Would you mind chasing him?  I'm happy to build & upload with some confirmation for only the MOZILLA_FIVE_HOME change (unless you get your disks fixed first :))
[03:00] <ScottK2> If you do decide to upload it, please wait a bit as the original zekr upload "Failed to Upload" to the archive after building successfully.  That's being looked into now, so it might be prudent to wait and see if something was wrong with the package or if Soyuz just burped.
[03:01] <persia> ScottK2: In that case I'll definitely hold off a bit.  If the weather stays as is, I should have another chance to look at it in ~23 hours.
[03:02] <ScottK2> I just got confirmation that it's a Soyuz bug.  Hooray?
[03:02] <Hobbsee> persia: obviously, with the UVF, if it looks sane, then it'll be accepted
[03:02] <persia> Hobbsee: context?  You've lost me :)
[03:03] <Hobbsee> persia: [22:44]  <persia> Hobbsee: Yes, but given my current time committments, it's easier to do things in a way that doesn't require approval :)
[03:03] <persia> Hobbsee: Ah.  Yes.  Thanks.
[03:04] <persia> ScottK2: Which bug?  Do you have a number?
[03:04] <ScottK2> persia: No.  I gather it tickled a new one.
[03:04] <ScottK2> Inifinity said to feel free to go ahead and do the new upload.
[03:04] <ScottK2> It'll either work or not, but he's going to try and figure out what's up with Soyuz.
[03:05] <persia> ScottK2: OK.  What do you think about MOZILLA_FIVE_HOME?  Just go with it, or wait foe the packager?
[03:05] <ScottK2> persia: I have not had a chance to look at the source for more than about 30 seconds.
[03:06] <persia> ScottK2: OK.  I'll just test a bit, and see if I can figure it out then.
[03:22] <ImNOTcesarefranc> slomo: ping
[03:24] <geser> persia: the only change I did was changing debian/pyversions from 2.4 to 2.5 and that python (<< 2.6) comes from ${python:Depends}
[03:25] <persia> geser: OK.  Thanks.  I suspect I'm confusing source dependencies with binary dependencies :)
[03:28] <geser> pygi: as you seem to work on swfdec has slomo talked to you about syncing swfdec0.5 (bug #133589)?
[03:28] <ubotu> Launchpad bug 133589 in Ubuntu "Please sync swfdec0.5 (universe) from Debian unstable (main)" [Undecided,Confirmed]  https://launchpad.net/bugs/133589
[03:29] <POX_> geser: change debian/pyversions to "2.4-"
[03:29] <pygi> geser, he didn't, no
[03:29] <persia> POX_: What does that achieve?
[03:29] <pygi> geser, we're working on our own packages (me and asac)
[03:30] <POX_> it will tell pysupport that this module works fine with 2.4 and 2.5
[03:30] <POX_> (and probably with 2.6)
[03:30] <pygi> geser, https://bugs.launchpad.net/ubuntu/+source/swfdec0.4/+bug/133052 --> just waiting for me to do swfdec-mozilla
[03:30] <POX_> => it will not add python (<< 2.6) dependency
[03:30] <ubotu> Launchpad bug 133052 in swfdec0.4 "[needs review]  swfdec0.5.1 [needs upload] " [Undecided,New] 
[03:30] <pygi> slomo, poke?
[03:31] <asac> pygi: ... if its in debian already, why not use theirs?
[03:31] <persia> POX_: Just to make sure I understand, will that also generate binary packages for each available python version?
[03:31] <geser> POX_: doesn't it need "support" in debian/rules to build the package for the various python versions?
[03:31] <POX_> no, I will just tell pysupport to compile it for these versions
[03:31] <pygi> asac, ergh ... because we need some changes in?
[03:31] <asac> do we?
[03:32] <pygi> asac, well, I don't think debian did any of those browsers stuff, update-alternatives, etc, etc
[03:33] <asac> ah yes ... but then we should do a merge for those changes
[03:33] <pygi> asac, lemme just see some things
[03:33] <asac> and hope that debian will adapt those
[03:33] <pygi> I also want to see if they included the patch I put in my package
[03:33] <asac> i will open discussion about using flash alternatives in debian anyway
[03:34] <geser> persia: it will adjust the dependencies to python (>= 2.4), python (<<2.6) and it might work as gaphas doesn't have any python modules
[03:35] <pygi> asac, they also don't include the patch that I was said by Company is required
[03:35] <pygi> quite a lot of changes between us and them
[03:35] <persia> geser: Right.  I'll have to change gaphor to match: it's currently 2.5 only, I think.
[03:35] <pygi> asac, but you decide, I'm none here after all :)
[03:35] <asac> pygi: who maintains debian package?
[03:35] <pygi> asac, ds
[03:36] <geser> persia: with python-central/python-support you have now only one binary package for all supported python versions.
[03:36] <persia> geser: Cool!  In that case, life is good.
[03:37] <persia> POX_: Thanks for the pointer about 2.4-
[03:38] <pygi> asac, he's in swfdec
[03:38] <asac> pygi: but i am not atm :)
[03:38] <pygi> asac, /join #swfdec does the trick
[03:38] <asac> yeah ;)
[03:38] <asac> done
[03:40] <ImNOTcesarefranc> persia: was wondering, any reason not to add desktop-file as a tag in https://wiki.ubuntu.com/MOTU/Bugs?
[03:41] <ScottK2> It's not terribly MOTU specific.
[03:41] <persia> ImNOTcesarefranc: Despite my interest, I'm not sure it's high enough priority to be a significant focus.  One of the big arguments against ubuntu-specific .desktop files is translations.
[03:42] <persia> There's a translate-desktop-file spec out, but it's not very active.  If it's completed, then desktop-files should surely be a goal for the next release.
[03:42] <POX_> geser: gaphas calls dh_pysupoprt so it will work
[03:42] <persia> ScottK2: Actually, main has much better .desktop file coverage than universe right now.  A large reason for this is the app-install-data effort.
[03:42] <ScottK2> I see.
[03:44] <ImNOTcesarefranc> persia: ok, thats clear, but what I was asking is: since that page is also "To make bugs easier to find for new contributors", would it make sense to add that tag, or we consider it covered by the bitesize one?
[03:46] <ScottK> OK.  Now that the router is rebooted, maybe DHCP won't go nuts.
[03:47] <persia> ImNOTcesarefranc: While most desktop-file bugs are also bitesize (except rare cases like the nVidia logo issue), I don't consider bitesize to cover desktop-file.  My main reason for not wanting to put it there is that there are strong opinions both ways regarding whether we should be pushing that change, and I'd rather see new people working on other things, unless they have a .desktop file itch to scratch, in which case it really doesn't matter 
[03:48] <ImNOTcesarefranc> persia: ok; my reason for asking is that I was also thinking about bugs in the .desktop file itself, not just that the .desktop file is missing
[03:50] <persia> ImNOTcesarefranc: That's an interesting case, and becoming more prevalent as the missing-desktop-file issue is addressed.  On the other hand, previous efforts to move towards standards-compliance have met with some resistance, although the spec is more mature now.
[03:51] <miles> come on im tryin to do work
[03:51] <persia> ImNOTcesarefranc: If you think sufficient bugs exist that are standards-compliance issues, rather than missing-file issues, I don't see any reason to not include it on the page.  I haven't reviewed the desktop-file bugs in a few months.
[03:56] <persia> ScottK: zekr_0.5.1.dfsg-0ubuntu2 up.
[04:00] <ImNOTcesarefranc> persia: well, not only the compliance to the freedesktop 1.0 spec, there are bugs (more correctly, wishes) like bug 133600 or bug 127739,  which I think could be good candidates for new contributors; in any case I see your point, its not worth adding this to the wiki page
[04:00] <ubotu> Launchpad bug 133600 in flightgear "There is on icon in xubuntu menu" [Undecided,Confirmed]  https://launchpad.net/bugs/133600
[04:00] <ubotu> Launchpad bug 127739 in nvtv "menu entry for nvtv has no icon" [Wishlist,Confirmed]  https://launchpad.net/bugs/127739
[04:00] <ScottK> persia: Cool.  Thanks.
[04:00] <ScottK> It'll be interesting to see if this one actually gets into the archive.
[04:03] <persia> ImNOTcesarefranc: I'd suggest both of those deserve both desktop-file and bitesize.  In the (rare) case where desktop-file isn't bitesize, I don't think it's a good target for a new person (e.g. nvidia-glx).
[04:03] <ImNOTcesarefranc> persia: right
[04:03] <persia> ScottK: Source NEW is done, right?  We're just waiting on binary NEW?
[04:04] <ScottK> Yes.
[04:04] <ScottK> Soyuz just has to deliver the binary so it can go into the NEW queue.
[04:05] <persia> ScottK: I don't anticipate any issues then.  It's a bit buggy, the transliterised fonts are painful to look at, etc., but it should be there.
[04:06] <ScottK> OK.  Just cross your fingers on Soyuz.
[04:17] <DaBonBon> can someone please look at this bug - https://bugs.launchpad.net/bugs/132603
[04:17] <ubotu> Launchpad bug 132603 in uswsusp "Please update the uswsusp package" [Wishlist,Triaged] 
[04:17] <DaBonBon> it's almost time
[04:17] <DaBonBon> i'm sure this small change would pass through the freeze :(
[04:18] <ScottK> Is there an updated package available and tested?
[04:19] <DaBonBon> no
[04:19] <DaBonBon> atleast not by me
[04:20] <ScottK> Well that would be the first step.  I see that StevenK and bluekuja has uploaded updates to that package in Gutsy.
[04:20] <StevenK> Don't look at me. Merging uswsusp is a pain.
[04:20] <ScottK> I understand that bluekuja is on vacation.
[04:21] <DaBonBon> StevenK: oh i'm sorry didn't know it was so difficult :(
[04:21] <ScottK> DaBonBon: Then you either need to find someone who will or do it yourself.
[04:21] <StevenK> It would also require making the Debian patch even more painful, since Debian haven't updated their package.
[04:38] <mjg59> Is Andrea Veri around?
[04:39] <Hobbsee> mjg59: on holidays
[04:39] <Hobbsee> mjg59: (bluekuja)
[04:39] <mjg59> Thanks
[04:39] <Hobbsee> Adri2000: have you noticed that we're in UVF?
[04:39] <mjg59> His last upload of uswsusp was utterly broken
[04:39] <DaBonBon> ah that explains why bluekuja didn't reply to my mail :)
[04:42] <Hobbsee> Ademan: er, never mind
[04:57] <Adri2000> Hobbsee: yes, why?
[04:57] <Hobbsee> Adri2000: never mind, thought it was a new upstream version
[04:58] <Adri2000> :)
[05:07] <ImNOTcesarefranc> any motu willing to check bug 70367 and/or bug 133051 (both in u-u-s queue)?
[05:07] <ubotu> Launchpad bug 70367 in imlib "imlib1 does not correctly handle 32-bit visuals" [Undecided,Confirmed]  https://launchpad.net/bugs/70367
[05:07] <ubotu> Launchpad bug 133051 in tpb "Please merge tpb 0.6.4-2.3 from Debian unstable (main)" [Undecided,Confirmed]  https://launchpad.net/bugs/133051
[05:16] <ImNOTcesarefranc> dholbach: would you mind if I merge gobby?
[05:17] <dholbach> ImNOTcesarefranc: not at all
[05:17] <dholbach> ImNOTcesarefranc: please go ahead
[05:17] <ImNOTcesarefranc> dholbach: ok, thx
[05:40] <ScottK> Yeahhh!  I just got my first REVU comment mail from the new REVU!
[05:43] <elkbuntu> the stuff excitement is made of?
[06:26] <soothsay> Anybody know of a good quick introduction to autotools?
[06:27] <nixternal> soothsay: /usr/share/doc/autotools-dev
[06:27] <nixternal> as long as you have autotools installed, you will have those docs...README.debian.gz and the examples directory has a little intro
[06:28] <ImNOTcesarefranc> soothsay: dunno if this is quick for you, but its what i used: http://www.linuxtopia.org/online_books/linux_development_tools/libtool_autoconf_automake_book/autobook_toc.html
[06:29] <soothsay> nixternal, ImNOTcesarefranc: Thanks
[06:30] <nixternal> no problem
[06:46] <tristanbob> was avahi running by default in Fiesty?
[06:48] <mok0> tristanbob: yes but it's not configured
[06:52] <tristanbob> mok0: just wondering from a security perspective, it is listening on a port?  If not, is that going to change in 7.10?
[06:53] <keescook> tristanbob: yes, avahi was running in Feisty.
[06:53] <mok0> Yes it's listening to a port
[06:54] <tristanbob> https://wiki.ubuntu.com/DefaultNetworkServices
[06:54] <tristanbob> Thanks keescook! that is what I was interested in
[06:55] <keescook> the exceptions to the "no listening ports by default" are dhclient and avahi.
[07:00] <geser> keescook: hi, can you look at bug #133477 and ack it?
[07:00] <ubotu> Launchpad bug 133477 in id3lib3.8.3 "[Sync request]  Sync id3lib3.8.3 (3.8.3-7) from Debian unstable (main)" [Undecided,New]  https://launchpad.net/bugs/133477
[07:02] <slomo> ImNOTcesarefranc: pong?
[07:02] <ImNOTcesarefranc> slomo: hey!
[07:02] <keescook> geser: sure, looks fine.  is this a problem in earlier releases too?
[07:03] <slomo> pygi: pong?
[07:03] <ImNOTcesarefranc> slomo: was wondering if you received my email about mentoring?
[07:03] <geser> keescook: I haven't check yet
[07:03] <keescook> geser: hm, I think it is, the earlier versions are relatively unchanged.  :P
[07:04] <slomo> ImNOTcesarefranc: doh, yes... thought i already answered that, one moment please
[07:05] <geser> keescook: I think it too, as already warty had the same upstream version (only a different revision)
[07:10] <ImNOTcesarefranc> slomo: got it now, thx!
[07:13] <pygi> slomo, wrt swfdec sync ...
[07:13] <keescook> geser: this is less bad than I initially thought; it builds the bad filename in the local directory.
[07:13] <pygi> slomo, that needs to be discussed with me and asac first :)
[07:13] <slomo> pygi: ok, thought it wouldn't be a problem as it's a new package anyway... do with it whatever you want then ;)
[07:14] <pygi> slomo, oki, thank you :)
[07:14] <asac> pygi: how about synching now ... and then if we need more diverge from there?
[07:15] <asac> ups
[07:15] <asac> he is gone
[07:15] <asac> hmm
[07:17] <geser> asac: pygi is back
[07:18] <asac> 19:14 < asac> pygi: how about synching now ... and then if we need more diverge from there?
[07:18] <asac> pygi: off to sport now
[07:18] <pygi> asac, ok, ok, I'll poke when you are back
[07:18] <pygi> asac, also I'll think more about it
[07:19] <pygi> everybody is all of the sudden lately interested in open-source implementation of flash =)
[07:22] <peanutb> because it half works
[07:22] <peanutb> if it half-works people are going to care
[07:27] <soothsay> Does autotools automatically invoke libfoo-config for libraries?
[07:30] <soothsay> I've got a program that invokes xmlrpc-c-config in ./configure, but xmlrpc-c-config doesn't seem to be included in libxmlrpc-c3
[07:32] <soothsay> Is the problem with the way the configure script is generated (i.e. it shouldn't use xmlrpc-c-config) or should xmlrpc-c-config be included in libxmlrpc?
[07:59] <Amaranth> hrm, never seen this error before
[07:59] <Amaranth> dpkg-genchanges: failure: cannot read files list file: No such file or directory
[08:13] <Supremus> hey
[08:15] <Supremus> is there any sponsor for main who can look at bug 33586
[08:15] <ubotu> Launchpad bug 33586 in nmap ".desktop file cleanup for nmapfe" [Wishlist,Confirmed]  https://launchpad.net/bugs/33586
[08:16] <Amaranth> oh, i forgot -S
[08:16] <Amaranth> *headdesk*
[08:20] <Lamego> StevenK, alive ?
[08:21] <geser> Lamego: it's after 4 am in Australia, he'll probably be sleeping now
[08:21] <Lamego> ah ok :P
[08:21] <Lamego> tks :)
[08:35] <zul> is it me or did it get real quiet
[08:54] <instabin|work> will ubuntu 7.10 have cnr? I asked in #ubuntu+1 but nobody knew
[08:57] <geser> cnr?
[08:57] <superm1> geser, click-n-run.  it's something that came from linspire
[08:57] <instabin|work> Yes
[08:57] <superm1> i heard it may be in 7.10, but i don't know for sure
[08:57] <instabin|work> There was talk about adding it before...
[09:00] <superm1> instabin|work, at Ubuntu Live, i spoke to the gentleman representing the Linspire booth, and he seemed confident that it would make it into 7.10 at that time, but I haven't reaffirmed that with anyone in Ubuntu.
[09:02] <instabin|work> I was just checking out freespire 2.0 in a virtual machine to see how cnr worked, Since i couldnt find it in 7.10 yet
[09:06] <pwnguin> is it too late to get a new version of a package in gutsy that was "released" 4 days ago?
[09:07] <pwnguin> it's already got an updated package in debian unstable
[09:07] <geser> pwnguin: you need to get an UVF exception from the motu-uvf team (if it's a universe package)
[09:08] <pwnguin> out of curiousity, uvf stands for?
[09:08] <geser> upstream version freeze
[09:08] <pwnguin> i see
[09:08] <pwnguin> what unfortunate timing
[09:09] <pwnguin> well, i doubt it's actually fixed any existing bugs
[09:09] <geser> if you're still interested: https://wiki.ubuntu.com/FreezeExceptionProcess#head-9c768217b322f8567d24d91647eaf0a256a73046
[09:20] <mok0> I'd like someone to review http://revu.tauware.de/details.py?upid=19
[09:24] <Lamego> pwnguin, what is the package ?
[09:49] <norsetto> RAOF: peek
[10:23] <pygi> asac, ok, let's do this: 1)sync 2)apply patch from my package 3)do needed modifications 4)do changes on swfdec-mozilla for browser id's 5)upload 6)voila!
[10:27] <asac> yeah
[10:28] <pygi> asac, fine, then you/slomo should do the UVF exception process for that thing he requested, and also make sure swfdec-mozilla gets synced (last time it wasnt)
[10:37] <asac> pygi: i will figure out tomorrow
[10:37] <pygi> asac, kk
[10:37] <pygi> thanks
[10:37] <asac> pygi: can we take swfdec-mozilla unmodified?
[10:38] <pygi> asac, well, no. We need update-alternatives in there and we need browser id's inside?
[10:38] <asac> ok
[10:38] <pygi> asac, basically, we will sync them unmodified, but we'll change them afterwards
[10:39] <pygi> we currently don't ship ubuntu changes inside /me thinks
[10:39] <pygi> no patches or stuff
[10:39] <pygi> and it's NEW package anyway
[10:45] <pwnguin> Lamego: oregano, a tool for making electrical schematics
[10:45] <pwnguin> Lamego: it's fairly good, but my roommates can't use it for school like pspice because the interface is slightly junky.
[10:46] <pwnguin> Lamego: and they refuse to learn regular spice
[10:46] <Lamego> does it builds on feisty ?
[10:46] <pwnguin> there is a feisty package
[10:46] <Lamego> updated to the latest version ?
[10:47] <pwnguin> and a gutsy package, i dont know if the new version builds
[10:47] <Lamego> ok
[10:47] <pwnguin> it builds in debian i hear ;)
[10:47] <pygi> mr_pouit, ping
[11:03] <sooth> Does autotools automatically invoke libfoo-config to determine -I and -L compile parameters, or is that user defined?
[11:32] <mohammad> ScottK: hello it seems that zekr is uploaded to launchpad https://launchpad.net/ubuntu/gutsy/+source/zekr again. but there is no binary available. is it fine?
[11:32] <ScottK> Yes.  I checked and it is in the NEW queue as it is a new binary package.
[11:33] <ScottK> New source packages go through NEW and then the new binary goes through NEW too.
[11:33] <ScottK> Source NEW is generally where problems come up.
[11:33] <ScottK> It turns out the first upload hanging was a bug with the build system (Soyuz), nothing to do with Zekr.
[11:34] <ScottK> Did you also see that persia uploaded your revision?
[11:34] <mohammad> ScottK: you mean zekr 0.5.1.dfsg-0ubuntu2? yes thanks
[11:35] <ScottK> Yes.  I put it on REVU and then persia (emmett) looked at it and uploaded it.
[11:36] <mohammad> ScottK: I think you uploaded ttf-sil-scheherazade before zekr, but it seems the source is not available :https://launchpad.net/ubuntu/gutsy/+source/ttf-sil-scheherazade, is there any problem?
[11:36] <ScottK> Since the package name changed it has to go through NEW again.  No problem.
[11:37] <ScottK> Since you made zekr depend on ttf-sil-scheherazade | ttf-scheherazade it'll work out just fine.
[11:38] <ScottK> Once ttf-sil-scheherazade is out of NEW, well ask for ttf-scheherazade to be removed.
[11:38] <ScottK> well/we'll
[11:40] <mohammad> ScottK: I knew that Nicolas Spalinger after I uploaded ttf-scheherazade  began to work on packaging of  ttf-sil-scheherazade for Debian, but it seems his package will not be ready for gutsy, he asked me to apply the changes I made. what wil happen when his package is ready?
[11:41] <mohammad> ScottK: will the current ttf-sil-scheherazade in ubuntu be replaced by the one he makes for Debian?
[11:41] <ScottK> When his package is in Debian and the Ubuntu archive is open for Gutsy +1, ask for a sync or a merge from Debian.
[11:41] <ScottK> Not automatically.
[11:41] <ScottK> Generally if a package is in Debian we prefer to use it so as not to duplicate effort.
[11:42] <ScottK> You might ask him just to upload your package to Debian with appropriate Debian distro/version.
[11:42] <ScottK> That would save him trouble.
[11:45] <mohammad> Is it possible to upload any translation (like zekr-quran-translations-ru) which is in the Recommends section of zekr after Aug 30 ?
[11:46] <mohammad> ScottK^
[11:47] <ScottK> mohammad: I'm really not sure how translations are done in Ubuntu.
[11:47] <ScottK> They have a different process and a different set of deadlines.
[11:47] <ScottK> I've got to go pick up one of my daughters from school, so I'll see you later.
[11:48] <mohammad> ScottK: thank you you help me a lot :) see you later
[11:55] <zul> hello\
[11:55] <norsetto> There is nothing about merges here: https://wiki.ubuntu.com/FreezeExceptionProcess. Are merges not concerned by the UVF!?
[12:01] <DktrKranz> every package is concerned. if you propose a merge which provides a new upstream release, you will need to ask for an UVFe
[12:08] <norsetto> DktrKranz: thx, and if it is a merge with same upstream tarball? There is no need for an ffe then?
[12:08] <DktrKranz> if the version is the same, you can proceed the usual way
[12:09] <norsetto> DktrKranz: dankeschoen ....
[12:09] <DktrKranz> erm...?? :)
[12:09] <norsetto> DktrKranz: and give my regards to the camel :-)
[12:23] <mok0> Some time ago, I found the NEW queue on LP, but now I can't find it anymore. Has it moved?
[12:24] <Pici> mok0: https://launchpad.net/ubuntu/gutsy/+queue perhaps?
[12:25] <mok0> Yeah! Thx!