[12:04] <hub> desrt: the warnings for the code were not requirements
[12:05] <hub> desrt: that's why they where off-band
[12:05] <desrt> hub; nod.  i rereleased anyway to fix those other issues you also mentioned out of band
[12:07] <desrt> hub; i uploaded the 0.6.1 to revu with a new manpage, etc...
[12:08] <LaserJock> MrRio: you can just remove the .upload file or use dput -f to upload the same version if you want
[12:09] <Xoritor> anyone setup pbuilder on amd64?
[12:15] <hub> we are in feature freeze, aren't we?
[12:15] <LaserJock> yep
[12:15] <hub> desrt: you got my vote :-)
[12:15] <hub> desrt: but it won't be in dapper...
[12:16] <desrt> hub; !!
[12:16] <hub> desrt: you needs to more advocates :-)
[12:16] <Xoritor> anyone that can help me troubleshoot setting up pbuilder on amd64?
[12:16] <hub> s/to/two/
[12:16] <desrt> hub; tseng already agreed :)
[12:16] <Xoritor> ?
[12:16] <hub> desrt: tell him to advocate it :-)
[12:16] <Xoritor> advocates of what?
[12:16] <tseng> he only needs one more
[12:17] <hub> tseng: yeah.
[12:17] <hub> tseng: but since it will have to wait, maybe you can put your vote on REVU :-)
[12:17] <tseng> what has to wait
[12:17] <Xoritor> ?
[12:18] <hub> tseng: feature freeze, no?
[12:18] <tseng> hub: feature freeze has never applied to new universe packages in the past
[12:18] <LaserJock> hub: he could ask for an exception I suppose
[12:18] <LaserJock> tseng: it is
[12:18] <hub> tseng: I think it is
[12:18] <tseng> LaserJock: point me to a mail that says so please
[12:19] <hub> tseng: that was discussed at UBZ
[12:19] <hub> tseng: hold on
[12:19] <tseng> LaserJock: i have been doing this for 3 releases now
[12:19] <Xoritor> anyone help me with this?  http://pastebin.com/585958
[12:19] <LaserJock> tseng: I don't know if it was in an email but it was at a MOTU meeting, UVF and FF apply to us
[12:19] <hub> tseng: it has been discussed at UBZ afaik
[12:19] <Xoritor> or tell where to get more help?
[12:19] <tseng> LaserJock: what does UVF and FF have to do with NEW
[12:19] <LaserJock> FF is for NEW
[12:20] <tseng> sigh
[12:20] <hub> https://wiki.ubuntu.com/FeatureFreeze say no new package
[12:20] <hub> but does not say explicitly universe or not
[12:20] <Xoritor> whats the new packages?
[12:20] <LaserJock> Xoritor: packages that haven't been in Ubuntu before
[12:20] <tseng> that page is so vague as to be useless
[12:21] <Xoritor> ah
[12:21] <tseng> and its written by corey burger, who, no offense, intended, is not any kind of package maintainer afaik
[12:21] <LaserJock> yes, but I believe we covered this quite a while ago in a MOTU meeting that UVF and FF apply to Universe as they do to main
[12:21] <hub> tseng: well, I just gave my vote.
[12:22] <tseng> sigh
[12:22] <tseng> UVF and FF can apply all they want
[12:22] <tseng> "The point at which we cease creating and modifying internal features and packages."
[12:22] <tseng> traditionally, we have discouraged motus from working on new packages
[12:22] <tseng> we happily accepted new packages that came in anyway
[12:23] <tseng> like from desrt, who isnt interested in bugfixing $randomuniversepackage anyway
[12:23] <LaserJock> and no new packages after FF except by exception. You might talk to dholbach about it though
[12:23] <desrt> tseng; lies!  muine :)
[12:23] <tseng> nothing on this page says anything about new packages
[12:23] <tseng> in certain terms
[12:24] <tseng> to contradict our precedent
[12:24] <slomo_> tseng: it changed this time... no NEW packages after FF
[12:24] <tseng> slomo_: id love to see it in clear writing
[12:24] <tseng> after I do, I'd love to get an exception anyway
[12:24] <desrt> fwiw, muine-shell used to be in universe
[12:25] <desrt> it was removed because it failed to compile against the new dbus
[12:25] <desrt> i merely fixed that
[12:25] <slomo_> tseng: i know no clear writing anywhere... but it was decided at a meeting, maybe grep the logs ;)
[12:25] <ajmitch> tseng: https://wiki.ubuntu.com/DapperReleaseProcess
[12:25] <ajmitch> slomo_: I was at the table when this was discussed
[12:25] <tseng> ajmitch: thanks.
[12:26] <tseng> ajmitch: await my appeal
[12:26] <desrt> tseng; if you're planning on applying for exception you might want to make it on those grounds
[12:26] <ajmitch> tseng: I think exceptions are warranted
[12:26] <tseng> desrt: indeed.
[12:26] <hub> desrt: it was?
[12:26] <desrt> hub; it was.
[12:27] <hub> desrt: so why didn't you reuse the existing package?
[12:27] <desrt> i used to have it installed.  i assume it was coming from universe
[12:27] <desrt> hub;  i couldn't find it
[12:27] <hub> ah ok
[12:45] <minghua> siretart: ping
[12:51] <Xoritor> anyone seen this error?
[12:51] <Xoritor> W: Failure trying to run: chroot /var/cache/pbuilder/build/29171/. dpkg --force-depends --install var/cache/apt/archives/libc6_2.3.6-0ubuntu8_amd64.deb
[12:51] <Xoritor> pbuilder: debootstrap failed
[12:52] <Xoritor> could anyone tell me a diff mirror to use for pbuilder?
[12:52] <Xoritor> MIRRORSITE=http://archive.ubuntu.com/ubuntu
[12:52] <Xoritor> thats what im using now
[12:59] <LaserJock> Xoritor: are you making a dapper pbuilder?
[12:59] <Xoritor> LaserJock, yes
[01:00] <Xoritor> LaserJock, trying to... it works for i386
[01:00] <Xoritor> LaserJock, just dies with that on amd64
[01:04] <LaserJock> Xoritor: you might try building it for breezy first and then upgrading it.
[01:05] <Xoritor> pbuilder create --distribution breezy?
[01:05] <Xoritor> like that or edit the pbuilderrc
[01:06] <Xoritor> that worked to get it to breezy
[01:06] <Xoritor> lets see if it works over all
[01:06] <Xoritor> ;-)
[01:06] <Xoritor> thx
[01:29] <Xoritor> LaserJock, that worked!
[01:29] <Xoritor> well... have not tried the upgrade yet
[01:30] <LaserJock> k
[01:30] <Xoritor> oh hmm
[01:30] <Xoritor> it didnt
[01:30] <Xoritor> i thought it did
[01:30] <Xoritor> I: Base system installed successfully.
[01:31] <Xoritor> but then it does not work
[01:31] <Xoritor> E: failed to find /var/cache/pbuilder/base.tgz, have you done <pbuilder create> to create your base tarball yet?
[01:31] <Xoritor> suck
[01:32] <Xoritor> odd that it said sucessful
[01:32] <Xoritor> then was not
[01:32] <LaserJock> ok, what did you try to do?
[01:33] <Xoritor> E: Type 'http://www.ubuntu-nl.org/source-o-matic' is not known on line 22 in source list /etc/apt/sources.list
[01:33] <Xoritor> that was the error that killed it
[01:33] <Xoritor> -> installing dummy policy-rc.d
[01:33] <Xoritor> E: Type 'http://www.ubuntu-nl.org/source-o-matic' is not known on line 22 in source list /etc/apt/sources.list
[01:33] <Xoritor> i tried pbuilder create --distribution breezy
[01:33] <Xoritor> it said success
[01:33] <Xoritor> but i was not reading further... :-(
[01:33] <Xoritor> my fault
[01:34] <Xoritor> trying it again
[01:34] <LaserJock> ok are you using the Howto on the wiki?
[01:34] <Xoritor> yea
[01:34] <Xoritor> https://wiki.ubuntu.com/PbuilderHowto
[01:35] <LaserJock> did you adjust your /etc/pbuilder/apt.config ?
[01:35] <Xoritor> yea
[01:35] <LaserJock> it shouldn't be looking for source-o-matic
[01:36] <ajmitch> hey crimsun
[01:36] <crimsun> hey ajmitch
[01:36] <ajmitch> crimsun: I finally have sound on the laptop, after getting the CVS drivers to build
[01:36] <crimsun> ajmitch: rock!
[01:36] <Xoritor> doh... i mast have not saved my changes
[01:36] <Xoritor> :-(
[01:36] <Xoritor> sorry
[01:37] <Xoritor> thx for being a good sounding board ;-)
[01:38] <LaserJock> np
[01:45] <Xoritor> grr
[01:45] <Xoritor> E: Unmet dependencies. Try using -f.
[01:46] <Xoritor> trying again
[01:46] <Xoritor> :-/
[01:46] <ajmitch> crimsun: I guess it might be worth getting patches in, or hopefully alsa 1.0.11 will be out before kernel freeze
[01:50] <crimsun> ajmitch: hmm, integrating alsa bk will be work due to the struct changes, but the hda changes can be done
[01:54] <Xoritor> and again...
[02:03] <Xoritor> so is breezy borked with pbuilder for amd64 or what?
[02:03] <LaserJock> it should work
[02:03] <Xoritor> err... or am i just not doing something right
[02:04] <Xoritor> it died 3 times so far... im running with --debug now
[02:04] <Xoritor> maybe its the "mirror" im hitting
[02:04] <Xoritor> W: Failure while installing base packages.  This will be re-attempted up to five times.
[02:05] <Xoritor> thats after a few diff things
[02:21] <Xoritor> hahahahahaha\
[02:21] <Xoritor> LaserJock, want to hear the stupid issue that caused all the problems?
[02:23] <Xoritor> LaserJock, i had /var mounted with nodev (duh)
[02:23] <LaserJock> ah
[02:23] <Xoritor> my normal mode of thinking is... /var does not need devices, so nodev is ok
[02:23] <Xoritor> and normally it does not
[02:24] <Xoritor> and it built the 64bit dapper just fine after fixing that
[02:25] <LaserJock> great
[02:26] <Xoritor> question though... can i have my 64bit machine compile the 32bit stuff using pbuilder also?
[02:26] <Xoritor> that should work fine right?
[02:27] <Xoritor> --binary-arch i386 or something should what changes that right?
[02:28] <Xoritor> would i need 2 diff base.tgz setups... or can you have 2 diff ones?
[02:29] <Xoritor> nm... found the answer
[03:08] <Xoritor> yay
[03:08] <Xoritor> yay
[03:08] <Xoritor> hip
[03:08] <Xoritor> hip
[03:08] <Xoritor> horray
[03:50] <Xoritor> interesting
[03:50] <Xoritor> i thought pbuilder was supposed to install all of the things you would need to build stuff
[03:51] <Xoritor> ie... byacc
[03:51] <Xoritor> etc...
[03:51] <ajmitch> it does, if a package specifies the packages needed in its build-depends
[03:52] <Xoritor> aaah
[03:52] <Xoritor> thank you
[03:52] <bmonty> hey ajmitch
[03:53] <Xoritor> odd that i didnt have to specify byacc for 32bit
[03:53] <Xoritor> is that one of the diffs between 64 and 32 bit?
[03:54] <Xoritor> or maybe what im trying to compile needs byacc for amd64
[03:54] <Xoritor> but not for i386
[03:55] <ajmitch> or the source is wonky
[03:55] <ajmitch> & needs fixed up :)
[03:55] <ajmitch> I'd say it's likely that it does need it to build
[03:56] <Xoritor> heh
[03:56] <Xoritor> or the 32bit includes byacc by default, but the 64bit does not
[03:56] <Xoritor> :-/
[03:56] <Xoritor> and adding that fixed it just fine
[04:40] <ajmitch> hi LaserJock
[04:41] <Kyral> yo LJ
[04:42] <LaserJock> hi ajmitch
[04:42] <LaserJock> Kyral: hi
[04:42] <Kyral> sup?
[04:43] <LaserJock> working on a presentation for Tuesday
[04:43] <LaserJock> is LP down?
[04:43] <bmonty> LaserJock: yes
[04:44] <bmonty> they are swapping out the db server
[04:44] <bmonty> is there an openoffice.org package that is all of the help files?
[04:44] <bmonty> instead of just language specific ones
[04:46] <LaserJock> can we still upload if LP is down?
[04:46] <crimsun> yes
[04:46] <crimsun> they'll just be queued, more than likely (like my vlc upload)
[05:13] <bmonty> good night MOTUs
[05:16] <LaserJock> what would be a reasonable amount of time to wait for a Debian maintainer to fix a bug before we do it ourselves?
[05:17] <Lathiat> week or two?
[05:17] <Lathiat> of course if we're close to relase might be easier just to fix..
[05:17] <Lathiat> send patch
[05:17] <Lathiat> i mean sending patches is always a good thing to do?
[05:18] <LaserJock> Lathiat: hmm, thanks
[05:33] <ajmitch> yay, the sort of away message we really want to know about
[05:57] <LaserJock> hi minghua
[05:58] <minghua> evening LaserJock
[06:24] <minghua> Arrgh, launchpad is down
[06:36] <LaserJock> minghua: yeah, until ~0600 UTC I think, moving the db I believe
[06:37] <minghua> LaserJock: bad timing for me, I was expecting to find sponsors for two of my uploads this evening
[06:38] <minghua> but wait, it's 05:37 UTC now
[06:38] <LaserJock> minghua: well, uploads are still possible but they will just be queued I think
[07:17] <minghua> yay, launchpad is back
[07:20] <highvoltage> yay
[07:20] <robitaille> sort of.... https://launchpad.net/distros/ubuntu/+bugs   doesn't work
[07:22] <minghua> hello MOTUs there, does any MOTU have time to sponsor two uploads from me?
[07:23] <minghua> on is for apt-proxy, bug #29267, UVF exception already granted
[07:23] <Ubugtu> malone bug 29267 in apt-proxy "apt-proxy crashes after upgrading" [Normal,Unconfirmed]  http://launchpad.net/bugs/29267
[07:23] <ajmitch> wow, new & improved layout, finally
[07:23] <minghua> one is for scim-hangul, bug #33763, adding automatic start (im-switch) support
[07:24] <Ubugtu> malone bug 33763 in scim-hangul "scim-hangul: Add im-switch support" [Wishlist,Unconfirmed]  http://launchpad.net/bugs/33763
[07:38] <minghua> bad day to ask for sponsors, I suppose
[07:46] <Xnix> howdy, anyone around?
[07:57] <dooglus> hi
[09:07] <sivang> hi motus
[09:07] <sivang> has anyone taken a look at eroastr? it fails even to create the iso right. I think it needs some quick love
[09:41] <tepsipakki> sivang: aren't there better alternatives now? gnomebaker for one..
[09:47] <tepsipakki> for me, eroaster has always been broken..
[10:04] <dholbach> good morning!
[10:04] <Hobbsee> evening dholbach!
[10:07] <sivang> tepsipakki: I was just trying to use it as reference for wrapping cdrecord in python, but the code is so messed :-)
[10:07] <sivang> tepsipakki: does gnomebaker use cdrecord or libnautilus-burn ?
[10:07] <sivang> guten morgen dholbach !
[10:15] <tepsipakki> I believe it uses cdrecord
[10:16] <tepsipakki> at least it depends on it ;)
[10:20] <Tonio__> hello
[10:22] <lifeless> who operates breezy-backports ?
[10:23] <crimsun> Ubuntu does.
[10:24] <crimsun> (requests, along with associated build logs, are sent to the backports mailing list. I think Mez is the conduit.)
[10:24] <freeflying> lifeless: file your request to mailing list or forum
[10:25] <lifeless> freeflying: ECONTEXT
[10:25] <lifeless> crimsun: thanks
[10:25] <lifeless> Mez: ping
[11:39] <allee> siretart: 'Forbidden' You don't have permission to access /revu1-incoming/kdissert-0603041545/<whatever> . Result: nobody can download files fromhttp://revu.tauware.de/details.py?upid=2097
[12:18] <tseng> hi dholbach
[12:18] <dholbach> hi tseng
[12:19] <tseng> dholbach: what do I need to add a 'new' package to universe
[12:19] <tseng> dholbach: (it was actually there before, later removed for bitrot, now fixed)
[12:20] <dholbach> tseng: mail James
[12:20] <tseng> dholbach: no no, all the cool kids tell me i need a top secret exception
[12:20] <tseng> its not a James job
[12:21] <dholbach> tseng: he will tell you what you need.
[12:21] <tseng> I am confused
[12:22] <tseng> I can upload the package fine by myself, it is a MOTU policy that is stopping me
[12:22] <dholbach> which one?
[12:22] <tseng> 'no new packages after FF' now
[12:22] <dholbach> a new upstream version?
[12:22] <dholbach> hmm
[12:22] <dholbach> ask James
[12:22] <dholbach> he'll know
[12:22] <dholbach> or wait - i can ask him
[12:22] <tseng> https://wiki.ubuntu.com/DapperReleaseProcess
[12:22] <tseng> its here
[12:23] <tseng> #
[12:23] <tseng> #
[12:23] <tseng> Since entirely new packages in universe are relatively safe and attract a number of new developers, they will be liberally admitted until FeatureFreeze if they do not require additional or newer dependencies.
[12:23] <dholbach> i talked to james, mail him
[12:23] <dholbach> it's fine
[12:23] <tseng> its not quite entirely new, but sort of
[12:24] <tseng> ok, its not a sync at all
[12:24] <tseng> what am I to mail him?
[12:24] <tseng> its in revu
[12:24] <dholbach> it was removed from the archive, you want it to be included again
[12:25] <tseng> ok.
[01:45] <danboid> Is this the right place to come to request packages for the ubuntu plf repos?
[01:46] <crimsun> I'm not sure what we have to do with PLF. They're an independent entity.
[01:51] <danboid> well, the Ubuntu PLF FAQ said I should come here and ask for a siretart on this channel to request a pack- siretart must be away?
[01:52] <crimsun> if he hasn't responded yet, he will eventually.
[01:55] <siretart> danboid: I'm currently at work, but, what is it?
[01:55] <siretart> danboid: you want to have a package in ubuntu?
[02:16] <danboid> hi siretart- I just posted a message to the ubuntu-plf list requesting lxdvdrip and devede
[02:16] <danboid> both have already been packaged in marillat
[02:19] <azeem> W73
[02:19] <azeem> blah, sorry
[04:29] <raphink> Malone #29895
[04:29] <Ubugtu> malone bug 29895 in cupsys "same action is repeatedly logged" [Major,Fix released]  http://launchpad.net/bugs/29895
[04:32] <ogra>    * Add debian/patches/51_dont_log_ipp_printer_query.dpatch: Do not flood
[04:32] <ogra>      access_log with successful CUPS-Get-Printers and Get-Printer-Attributes
[04:32] <ogra>      queries (which are generated by gnome-cups-icon every 3 seconds). This is
[04:32] <ogra>      a hideous and hackish patch, but it has to do until we dbusify cupsys
[04:32] <ogra>      properly. (Malone #29895)
[04:32] <Ubugtu> malone bug 29895 in cupsys "same action is repeatedly logged" [Major,Fix released]  http://launchpad.net/bugs/29895
[04:32] <ogra> raphink, from latest cupsys changelog ;)
[04:32] <raphink> yes I know ogra
[04:32] <raphink> this is why I was querrying this bug
[04:32] <raphink> to see if it was linked bith kdeprint one
[04:32] <ogra> :)
[04:33] <raphink> s/bith/with/
[04:33] <raphink> desn't seem to be
[04:33] <raphink> but it's worth a try
[04:33] <raphink> when it's built
[06:14] <Xoritor> can anyone here help me figure out why i cant get pdebuild to build 32bit binaries?
[06:14] <Xoritor> i have the 32bit chroot setup
[06:14] <Xoritor> pdebuild -- --basetgz /var/cache/pbuilder/base-i386.tgz  --binary-arch i386
[06:14] <Xoritor> that says i386 is not a valid dsc file
[06:15] <Xoritor>  pdebuild -- --basetgz /var/cache/pbuilder/base-i386.tgz  --binary-arch i386 /var/cache/pbuilder/result/libprelude_0.9.6.1-0ubuntu1.dsc
[06:15] <Xoritor> Command line parameter [i386]  is not a valid .dsc file name
[06:15] <Xoritor> both invocations say the same thing
[06:16] <Xoritor> pbuilder build [options]  .dsc-file
[06:16] <Xoritor> so the dsc should be the last "argument"
[06:17] <Xoritor> pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz --binary-arch i386 /var/cache/pbuilder/result/libprelude_0.9.6.1-0ubuntu1.dsc
[06:17] <Xoritor> Command line parameter [i386]  is not a valid .dsc file name
[06:17] <Xoritor> it never gets past the i386
[06:17] <Xoritor> :-/
[06:19] <Xoritor> do i need the --binary-arch?
[06:19] <Xoritor> or since that chroot is i386 already will it just compile 32bit
[06:19] <Xoritor> nope
[06:20] <Xoritor> its trying to do x86_64
[06:20] <Xoritor> checking build system type... x86_64-pc-linux-gnu
[06:20] <Xoritor> :-(
[06:20] <Xoritor> pdebuild -- --basetgz /var/cache/pbuilder/base-i386.tgz /var/cache/pbuilder/result/libprelude_0.9.6.1-0ubuntu1.dsc
[06:20] <Xoritor> thats what i used
[06:21] <azeem> do you have an amd64 chroot as well?
[06:21] <Xoritor> yes
[06:21] <Xoritor> and i got it working!!!
[06:21] <Xoritor> azeem, i got a him to patch to link against glibcrypt directly!
[06:21] <Xoritor> :-D
[06:21] <Xoritor> yay
[06:21] <Xoritor> thank you by the way
[06:21] <azeem> no problem
[06:21] <Xoritor> and it builds great now
[06:22] <Xoritor> should i setup a pbuilderrc to use the DEBIAN_BUILDARCH=i386?
[06:23] <azeem> so you still have that amd64 issue?
[06:23] <Xoritor> no
[06:23] <Xoritor> everything works great with amd64
[06:23] <Xoritor> :-D
[06:23] <azeem> ok, so what is the problem?
[06:23] <Xoritor> just trying to also compile it 32bit on that same machine
[06:23] <Xoritor> ie... "cross compile" kinda
[06:23] <Xoritor> i have a 32bit chroot and a 64bit croot
[06:24] <azeem> I think you might need to execute something prior to entering the 32bit chroot
[06:24] <Xoritor> and i am trying to get pbuilder to do use the 32bit one
[06:24] <Xoritor> export DEBIAN_BUILDARCH=i386 maybe?
[06:24] <azeem> I never did it myself though, but there surely should be information about this on google
[06:24] <Xoritor> i am not finding much :-(
[06:24] <Xoritor> maybe my search terms are not right
[06:24] <azeem> a lot of Debian people now have amd64 machines and need to build i386 .debs to upload
[06:24] <Xoritor> yea
[06:25] <Xoritor> i found how to make a 32bit
[06:25] <Xoritor> but not how to _use_ it ;-)
[06:25] <Xoritor> heh
[06:25] <Xoritor> i mean with pbuilder that is
[06:25] <Xoritor> pdebuild -- --basetgz /var/cache/pbuilder/base-i386.tgz  --binary-arch i386 /var/cache/pbuilder/result/libprelude_0.9.6.1-0ubuntu1.ds
[06:25] <Xoritor> that was my "best guess"
[06:26] <Xoritor> and it dies saying i386 is not a valid dsc
[06:26] <Xoritor> heh
[06:26] <Xoritor> well... s/ds/&c/
[06:28] <Xoritor> bah!
[06:28] <Xoritor> i think i found it
[06:39] <LaserJock> dholbach: Guten Abend
[06:44] <Mez> lifeless, pong
[07:05] <Xoritor> ok... so that did not do what i thought it did... i did not have a 32bit chroot... it was just named as a 32bit chroot
[07:05] <Xoritor> heh
[07:15] <Xoritor> what the heck
[07:16] <Xoritor> i keeps downloading 64bit even though i have everything set to use 32bit
[07:16] <Xoritor> sudo pbuilder create --binary-arch i386 --basetgz /var/cache/pbuilder/base-i386.tgz
[07:16] <Xoritor> export DEBIAN_BUILDARCH=i386
[07:16] <Xoritor> is there something ELSE i have to do?
[07:17] <Xoritor> cause i dont see it on the man page... nor google... nor any other docs i have searched
[07:19] <LaserJock> Xoritor: do you have a 32-bit chroot?
[07:19] <Xoritor> i was trying to create one with pbuilder create
[07:20] <LaserJock> Xoritor: you could try building a 32-bit chroot and then build a pbuilder in that to see if it works any better
[07:21] <Xoritor> hmm
[07:21] <Xoritor> ok
[07:23] <Xoritor> debootstrap --arch i386 dapper chroot/
[07:23] <Xoritor> that _should_ work right?
[07:23] <Xoritor> http://archive.ubuntu.com/ubuntu is where its coming from
[07:27] <LaserJock> I think so
[07:28] <Xoritor> hmm
[07:29] <G0SUB> can anybody tell me why xscreensaver depends on ttf-freefont?
[07:30] <LaserJock> G0SUB: doesn't appear to directly
[07:31] <LaserJock> G0SUB: must be pulled in from one of the deps
[07:31] <G0SUB> LaserJock IMHO, the cool bullets that are displayed when we type in the passwd in lock screen comes from ttf-freefont
[07:32] <G0SUB> LaserJock it's not a dep in debian though
[07:33] <G0SUB> LaserJock this is a bug in my opinion
[07:33] <LaserJock> why?
[07:34] <G0SUB> the ubuntu xscreensaver should not depend on ttf-freefont ...
[07:34] <G0SUB> it doesn't in Debian
[07:34] <LaserJock> it doesn't
[07:36] <LaserJock> the ubuntu xscreensaver doesn't have ttf-freefont as a direct dependency
[07:36] <ogra> it has ...
[07:36] <ogra> in breezy
[07:36] <G0SUB> aah!
[07:37] <ogra> the lock screen uses a font from ttf-freefont for the dots in the password window
[07:37] <G0SUB> yep! I knew it
[07:37] <LaserJock> breezy, hah, who runs that ;-)
[07:37] <G0SUB> LaserJock :)
[07:37] <LaserJock> thanks ogra
[07:37] <ogra> its a ubuntu specific patch, so it wont draw in ttf-freefont in debian indeed :)
[07:38] <G0SUB> btw, xscreensaver coflicts with xscreensaver-gnome which in turn depends on xscreensaver
[07:38] <G0SUB> [in breezy] 
[07:38] <ogra> i didnt change any deps there ..
[07:38] <ogra> xscreensaver-gnome ?? does that still exist ? i thought that was gnome1
[07:39] <G0SUB> ogra may be none uses it ... but I just noticed the thing
[07:39] <ogra> nope
[07:39] <ogra> its doesnt exist anymore
[07:40] <G0SUB> hmm okay
[07:40] <G0SUB> ogra should I file a bug for the ttf-freefont issue?
[07:40] <ogra> why ?
[07:40] <ogra> the depoendency is needed
[07:41] <ogra> if you would take it away, the lock screen would break
[07:42] <G0SUB> ogra it's an issue with us since ttf-freefont has broken indic fonts [and has higher preference]  ... to view indic text properly, ttf-indic-fonts is not enough, we have to remove ttf-freefont which breaks the whole system
[07:42] <G0SUB> I was just talking to a newbie who removed ttf-freefont which broke his gnome-desktop
[07:43] <ogra> but thats breezy ...
[07:43] <G0SUB> yeah, I get that ... if it's fixed in dapper, then no issues
[07:43] <ogra> we wont fix stuff in breezy unless its dataloss critical
[07:43] <G0SUB> thanks :)
[07:43] <ogra> yes, its fixed in dapper, since we dropped xscreensaver :)
[07:44] <LaserJock> ogra: that's one way of getting rid of bugs ;-)
[07:44] <G0SUB> ogra what are we using in dapper?
[07:44] <ogra> gnome-screensaver
[07:44] <G0SUB> ah, okay
[07:44] <ogra> LaserJock, haha ... given what i trade for it, it was a bad deal
[07:45] <ogra> even the lock screen patch took me nearly a week every release to adjust it and get it right
[07:45] <G0SUB> ogra does gnome-screensaver replace xscreensaver in dapper?
[07:45] <ogra> yup
[07:45] <G0SUB> great ... /me hope nothing will break during a dist-upgrade
[07:45] <ogra> already happened ...
[07:45] <G0SUB> hopes
[07:46] <ogra> nope, not hopes ... we switched weeks ago ... :)
[07:46] <G0SUB> :)
[07:47] <G0SUB> ogra btw, what screensaver will Kubuntu guys use?
[07:47] <ogra> no idea
[07:47] <G0SUB> heh
[07:48] <LaserJock> I think there is a KDE equivalent to gnome-screensaver
[07:48] <LaserJock> I'm sure it starts with a K ;-)
[07:48] <G0SUB> haha
[07:49] <phanatic> hi people
[07:49] <Xoritor> hi person
[07:49] <ogra> LaserJock, Knome-screensaver ?
[07:49] <ogra> naaah
[07:49] <Xoritor> ogra, no ksaver
[07:50] <Xoritor> err... forgot it has to be Ksaver
[07:50] <Xoritor> heh
[07:50] <G0SUB> LaserJock btw, can I join the Motu-Science team?
[07:51] <LaserJock> ogra: that's right ;-)
[07:51] <LaserJock> G0SUB: are you interested in Science related packages?
[07:51] <G0SUB> LaserJock yes, why not! I do a LOT of TeX
[07:52] <LaserJock> G0SUB: well, I'm starting a new member fee of $20 USD to support my Ubuntu habit  ;-)
[07:52] <LaserJock> G0SUB: just kidding of course
[07:52] <G0SUB> LaserJock I wish I could pay :)
[07:53] <LaserJock> G0SUB: but yeah, if you are willing to be a part of the team just join on LP
[07:53] <G0SUB> LaserJock right-away :)
[07:53] <G0SUB> LaserJock I hope you'll give me some work to do
[07:53] <LaserJock> G0SUB: and join the ubuntu-science ML if you haven't already
[07:53] <phanatic> are there any public infos available about the conf after release?
[07:54] <LaserJock> G0SUB: http://tauware.de/cgi-bin/mailman/listinfo/ubuntu-science
[07:55] <G0SUB> LaserJock done
[07:57] <LaserJock> G0SUB: done
[07:57] <LaserJock> G0SUB: now get to work! ;-)
[07:57] <G0SUB> LaserJock give me some work
[07:58] <G0SUB> [please] 
[07:58] <LaserJock> G0SUB: check out the wiki at wiki.ubuntu.com/MOTU/Teams/Science
[07:58] <G0SUB> ok
[07:59] <LaserJock> G0SUB: bug fixing is always nice, see tiber.tauware.de/~laserjock/bug_list.html for a list of science related apps with bugs
[07:59] <G0SUB> okay
[08:14] <Xoritor> LaserJock, yay!
[08:14] <Xoritor> yay!
[08:14] <Xoritor> chroot into my new 32bit chroot and pbuilder seems to be working great
[08:15] <LaserJock> Xoritor: interesting, I would have thought it wouldn't have made much difference.
[08:16] <LaserJock> Xoritor: but as long as it works ;-)
[08:19] <Xoritor> yep
[08:20] <Xoritor> its all good
[08:20] <Xoritor> sweet!
[08:28] <G0SUB> LaserJock is http://picfu.com/s/107/706302624 a good emblem for MOTU-Science?
[08:28] <Xoritor> LaserJock, well i should not have celebrated so early... it did not build the -dev for some reason... odd but im lookin into that now!
[08:28] <Xoritor> hahaha
[08:28] <netzmeister> hello..
[08:29] <Xoritor> and no issues that time!
[08:29] <Xoritor> hah
[08:32] <G0SUB> LaserJock http://zope.gnowledge.org:8080/science.png
[08:40] <LaserJock> G0SUB: well, since I'm a chemist I kinda like that emblem ;-)
[08:41] <G0SUB> LaserJock :)
[08:41] <LaserJock> G0SUB: can we use it?
[08:41] <G0SUB> LaserJock of course!
[08:41] <G0SUB> I took it from openclipart.org
[08:42] <G0SUB> LaserJock the 2nd link has the resized emblem
[08:43] <LaserJock> G0SUB: what about this one: http://openclipart.org/clipart//science/chemistry_flask_matthew__01.svg
[08:43] <G0SUB> LaserJock yeah, good too ... but I kinda like the test-tube beside ...
[08:43] <G0SUB> LaserJock both are equally good
[08:43] <LaserJock> netzmeister: Guten Abend
[08:44] <netzmeister> LaserJock:  Hi ;-)
[08:45] <LaserJock> G0SUB: ok, I'll take to #launchpad about getting it as our emblem, thanks
[08:46] <G0SUB> LaserJock why do you have to talk to launchpad admins?
[08:46] <LaserJock> I don't think that was always there
[08:47] <G0SUB> oh, may be ...
[08:47] <G0SUB> LaserJock you need to scale it to 16x16 px ... that's MAX allowed
[08:47] <LaserJock> G0SUB: the 2nd link is ok, right?
[08:48] <G0SUB> LaserJock yes, if you choose that :)
[08:48] <LaserJock> netzmeister: Wie geht es dir?
[08:48] <LaserJock> G0SUB: looks, good to me. We can always change it if  we don't like it ;-)
[08:48] <G0SUB> yep
[08:49] <G0SUB> it looks awesome
[08:49] <netzmeister> LaserJock:  fine, thx. and you?
[09:41] <lifeless> Mez: hi
[09:41] <Mez> lifeless, hey - sup?
[09:41] <Mez> you pinged me this morning
[09:41] <lifeless> Mez: is there a breezy backport of bzr-dapper ?
[09:41] <Mez> lifeless: not that I know ow
[09:41] <Mez> of *
[09:42] <lifeless> Mez: we'd love for there to be one
[09:42] <lifeless> ;)
[09:43] <Mez> lifeless, I'm sure you would
[09:43] <Mez> however - at the moment
[09:43] <Mez> soyuz doesnt support backports
[09:43] <Mez> :(
[09:45] <lifeless> ah
[09:45] <lifeless> does that mean there are no backports for breezy anymore ?
[09:45] <Mez>  lifeless I hope not ;)
[09:46] <lifeless> just no new ones ?
[10:08] <Kyral> oy...Looks like Riddell got another KDE convert
[10:11] <G0SUB> haha
[10:11] <kiko> hello there
[10:11] <Kyral> lo
[10:11] <G0SUB> kiko :)
[10:11] <kiko> just wanted to check if people found launchpad any slower or faster today than usual
[10:11] <Kyral> In a way I have come full circle
[10:12] <Kyral> Back when I started using Linux with Slack10 about 2-3 years ago I used KDE :P
[10:12] <G0SUB> kiko I see 2% performance boost
[10:12] <kiko> I like the precision, G0SUB
[10:12] <G0SUB> kiko hehe ...
[10:12] <kiko> we moved to a new database server
[10:12] <G0SUB> yes, I got the mail ...
[10:12] <kiko> it has gobs of memory
[10:13] <G0SUB> I gues you are moving to PG 8.1 soon too
[10:13] <kiko> we are indeed
[10:13] <G0SUB> kiko I hope launchpad will perform better under more load ... you won't see much difference with the same load in my opinion
[10:17] <LaserJock> I like the new bug listing format in LP
[10:17] <kiko> I'm happy to hear that
[10:17] <kiko> I think it's nice too
[10:17] <kiko> we're going to knock off the right column for wide pages and only have a left column
[10:17] <kiko> should reduce the stress with wrapping
[10:17] <LaserJock> although I would like to see a somewhat similar thing done to Pakcages
[10:18] <G0SUB> see you guys later ... it's bed time here
[10:18] <kiko> well
[10:18] <kiko> LaserJock, did you note that +packages now has somewhat more useful information?
[10:18] <LaserJock> yes
[10:19] <kiko> I will improve it further time allowing
[10:19] <LaserJock> but I only get about 4-5 packages /screen
[10:21] <LaserJock> for instance https://launchpad.net/people/slomo/+packages has a lot of scrolling
[10:21] <LaserJock> but at this point I just love having that info available
[10:22] <LaserJock> kiko: how hard would it to be to use xml-rpc on Malone?
[10:24] <kiko> LaserJock, I'll reformat that list soon
[10:25] <kiko> LaserJock, it's not that much work but it's really not on the map yet
[10:26] <LaserJock> kiko: is there anything set up yet to do larger scale bug queries? I'd like to be able to get a list of bugs given a list of source packages
[10:26] <kiko> LaserJock, yeah, there's a search and filter spec being worked on
[10:26] <kiko> it needs sign-off but it would make what you want possible
[10:27] <LaserJock> kiko: and that would work for lists of source packages ~500 big?
[10:27] <kiko> mmmm
[10:27] <kiko> no it wouldn't
[10:27] <kiko> what are you trying to do? :-)
[10:28] <LaserJock> I lead a team of MOTUs that look after science related packages, we have a list of ~450 source packages. I want to be able to get a list of all the bugs.
[10:29] <kiko> an interesting use case
[10:29] <kiko> and I have no idea how to help you fix this
[10:29] <LaserJock> I think it will be a popular one here
[10:29] <LaserJock> we have lots of teams
[10:29] <kiko> hmmmm
[10:30] <LaserJock> not usually will as large a number of source packages but still
[10:30] <LaserJock> kiko: for instance, here is the list of MOTU Teams : https://wiki.ubuntu.com/MOTU/Teams
[10:31] <LaserJock> I'm sure each team would like to get a list of bugs given a set of source packages
[10:31] <allee> LaserJock: You can subscribe to pkgs.  On subscribtion you can add your e-mail or the one of the team you are a member
[10:31] <LaserJock> allee: that is a possibility but still requires us to form a list from emails.
[10:32] <LaserJock> allee: which isn't necessarily bad
[10:32] <kiko_> LaserJock, that is easier to do because you can use the X-Launchpad-Bug header
[10:32] <kiko_> other than that I'll ask you to email launchpad-users to describe your use case
[10:32] <LaserJock> sure, the MOTU are already using that header
[10:33] <LaserJock> but I think that large scale query would be a fairly popular use case
[10:34] <LaserJock> allee: but again that would require us to go through all the source packages and subscribe ourselves, doable for sure but not as nice as being able to query Malone.
[10:35] <LaserJock> I'm just interested in the most efficient and effective way of getting bug listings for large numbers of source packages
[10:35] <allee> LaserJock: But telling malone your list of 500 pkg each time you want to query is also not very handy ;)
[10:36] <LaserJock> allee: actually lucas made a script to do that, but it is verrry slow. Parsing each html file I believe
[10:36] <kiko> LaserJock, if you give me a list of source package names I can set a team up as an initial bug contact for them
[10:36] <LaserJock> kiko: well, that is an interesting point to me
[10:36] <kiko> I can fast-track it on the DBA
[10:38] <LaserJock> kiko: the problem for me is that MOTU Science is sort of a subset of MOTU so while MOTU Science is particularly interested in these packages any MOTU can change them and the bug reports should still go to universe-bugs@l.u.c
[10:39] <LaserJock> so I'm not sure if MOTU Science should be the initial bug contact or if MOTU should, does that make sense?
[10:39] <kiko> LaserJock, when you say "change them" what do you mean?
[10:40] <LaserJock> kiko: sorry, I mean upload bug fixes, etc.
[10:40] <LaserJock> kiko: so while MOTU Science would like to have a list of bugs, etc. I don't think we should be taking away from MOTU
[10:40] <kiko> you don't need to take them away
[10:40] <kiko> you can be an additional bug contact.
[10:41] <LaserJock> ah, well that would be a bit more like what I'd like
[10:41] <LaserJock> kiko: is there something in the works to automatically assign bugs on Universe packages to MOTU?
[10:41] <kiko> well, you're in good hands
[10:41] <kiko> not exactly
[10:41] <LaserJock> it seems like I heard that somewhere
[10:42] <kiko> /all bugs/ on ubuntu have the Ubuntu bugs team subscribed to them initially
[10:42] <kiko> some source packages have bug contacts; their bugs have the correct bug contacts subscribed to them
[10:42] <LaserJock> so does the initial bug contact just mean you are automatically subscribed to any bug on that packages?
[10:43] <LaserJock> just to be clear
[10:43] <kiko> correct.
[10:43] <kiko> to any bug /filed/ on the specified package
[10:43] <kiko> it is not retroactive
[10:43] <kiko> and it is not implicit
[10:43] <LaserJock> ok
[10:43] <kiko> but we can subscribe the team to existing bugs
[10:43] <LaserJock> kiko: well, I've sort of done that already
[10:43] <kiko> I'm writing a FAQ entry for you
[10:44] <kiko> then it's cool
[10:44] <kiko> you just need to have the contacts updated for the packages you want
[10:44] <LaserJock> kiko: I actually went through every source package and looked for bugs :(
[10:44] <kiko> lots of clicking
[10:44] <LaserJock> yep ;-)
[10:44] <kiko> next time talk to me first :)
[10:45] <LaserJock> ok, so if I gave you a list of packages can you add motuscience to the initial bug contact?
[10:51] <kiko> yep
[10:52] <LaserJock> kiko: I was thinking that initial bug contact was for assigning by default not subscribing by default. That is why I didn't want to do that
[10:52] <kiko> there are no default assignees in malone
[10:52] <kiko> you need to assign people manually
[10:52] <LaserJock> good
[10:52] <kiko> it is in some ways a feature
[10:52] <kiko> but you need to get used to it
[10:53] <LaserJock> ok, so should I still email a use case to launchpad-users?
[10:53] <kiko> well
[10:53] <kiko> that depends.
[10:53] <kiko> do you want the use case fulfilled, or is having the IBC subscribed enough?
[10:54] <LaserJock> hmmm, I think it would eventually be nice to use xml-rpc to query large numbers of packages but I think the IBC + mailing list is a good solution
[10:57] <LaserJock> kiko: btw, thanks for all the help. LP is still quite mysterious to me ;-)
[10:57] <kiko> it's a bit of a mystery to us all, but we'll keep banging on it
[10:57] <kiko> thanks
[10:59] <LaserJock> netzmeister: gut, danke ;-)
[10:59] <netzmeister> hehe
[11:02] <LaserJock> kiko: ok well, it might take me a bit to get the package list I want (I might weed out some) and then I'll email you, OK?
[11:02] <kiko> sure.
[11:02] <LaserJock> thanks, that should make my life a bit easier
[11:10] <netzmeister> LaserJock:  Do you know a package where i can look how i can spilt a package?!
[11:10] <netzmeister> s/spilt/split
[11:14] <ogra> netzmeister, the debdiff between xscreensaver 4.23-4ubuntu3 and 4.23-4ubuntu4
[11:16] <LaserJock> netzmeister: grass might also be a good example
[11:17] <ogra> ah, sad, ubuntu3 is gone from the archive already
[11:17] <LaserJock> ogra: yeah, seems like they go fast sometimes. that was a problem for MoM
[11:17] <kiko> well, we're at ubuntu 6.04 already, 3 is old news
[11:18] <netzmeister> thx ogra & LaserJock
[11:18] <ogra> LaserJock, the big problem for mom was the crash of snapshot.debian.net
[11:18] <ogra> kiko, ah, come on :)
[11:18] <ogra> 3 is never as old as it seems ...
[11:24] <netzmeister> what is "lintian-overrides"?
[11:24] <ogra> you can use it for weird lintian errors that are not solveable
[11:25] <netzmeister> ah okay..
[11:25] <ogra> have a look at bibshelf, its a wonderful example (the best i've ever had)
[11:25] <netzmeister> for what?
[11:25] <netzmeister> splitting?
[11:25] <ogra> o see a linitan-override and in which cases you should use them
[11:25] <ogra> :)
[11:25] <ogra> s/o/to/
[11:26] <netzmeister> okay..
[11:31] <LaserJock> darn it, my stupid mac is trying to use both i386 and ppc gcc at the same time
[11:33] <ogra> are the binaries called *_i386-powerpc.deb then ?
[11:35] <LaserJock> no, but I keep getting "cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded)"
[11:38] <ajmitch> morning
[11:38] <LaserJock> hi ajmitch
[11:38] <kiko> ajmitch!
[11:41] <tseng> kiko!
[11:41] <ogra> tseng!
[11:41] <kiko> tseng!
[11:42] <kiko> what would the world be without the motu
[11:42] <tseng> ogra: up late?
[11:42] <ogra> tseng, 23:42 ...
[11:42] <ogra> its not *that* late
[11:42] <tseng> i stop working at 5pm :D
[11:42] <tseng> you are still here
[11:42] <ogra> i'm just in a phase where i go to bed ~3
[11:46] <ajmitch> kiko! haven't seen you around here for awhile
[11:46] <LaserJock> kiko was helping me out :-)
[11:47] <ajmitch> ah right
[11:47] <kiko> actually
[11:47] <kiko> I came in to ask if the site felt faster today
[11:47] <kiko> but nobody gave me much of an answer! :)
[11:47] <ajmitch> the main thing I noticed yesterday was a new bug listing, which is much improved
[11:48] <ajmitch> kiko: DB migration went ok?
[11:49] <tseng> kiko: any operation in particular?
[11:49] <tseng> kiko: its pretty resonponsive in general
[11:50] <ajmitch> and we know what they're like
[11:50] <kiko> ajmitch, yeah, it appears that it worked well
[11:50] <kiko> the new server has more memory than the database takes up
[11:51] <ajmitch> for now
[11:51] <ajmitch> I imagine the DB will grow fairly quickly
[11:51] <tseng> kiko: could you put a filter in the model to disallow filing of stupid bugs?
[11:51] <tseng> bayesian
[11:51] <tseng> :P
[11:51] <tseng> 'i built muine from cvs, it doesnt work.'
[11:52] <kiko> heh
[11:52] <ajmitch> match anything that mentions /usr/local
[11:52] <kiko> that would trigger lots of false positives
[11:52] <kiko> "I did NOT install to /usr/local" boom
[11:53] <ajmitch> that's ok
[11:53] <ajmitch> it makes our job easier
[11:58] <ajmitch> and I need to do another upload RSN to fix the dep