[12:13] <niran> anyone with some autotools knowledge want to help me fix some things?
[12:13] <niran> i'm trying to get out a release of gnome-app-install, but i don't know how to configure everything
[12:14] <niran> which i'll eventually learn, but i'd like to get it out there before i do that :)
[12:17] <sistpoty> niran: what's your problem?
[12:23] <niran> sistpoty, well, the original program was already set up to use autotools, but i've added files and folders and i'm not sure what i need to change
[12:23] <niran> or what to put in a Makefile.am
[12:25] <sistpoty> niran: for each new subdir, you need to put that after "SUBDIRS" into Makefile.am of the parent folder
[12:28] <niran> that's it?
[12:28] <sistpoty> not yet...
[12:28] <sistpoty> gnome-app-install is python?
[12:28] <niran> right
[12:29] <sistpoty> hm... sorry, but I don't know the automake-stuff for python... i could explain you some things for c if that would help
[12:30] <sistpoty> basically for c you could build a binary with yourtargetbinary_SOURCES=cfile1.c cfile2.c (and so on)
[12:31] <sistpoty> i assume, that for python some similar macros will exist
[12:32] <sistpoty> after you setup the .am-files, you need to run: aclocal, autoconf and automake, then you can call configure to build the actual makefiles
[12:32] <niran> hm, ok
[12:36] <sistpoty2> sorry, 24h-disconnect :/
[12:41] <herve> night all!
[01:09] <ajmitch> morning
[01:53] <tseng> how can i force dpkg to install missing config files
[01:54] <tseng> --force-confmiss is not helping much
[03:56] <bddebian> Wake up people, there's hackin' to be done! :-)
[04:39] <bddebian> Anyone awake?
[04:40] <ajmitch> nope
[04:40] <bddebian> ajmitch!!!
[04:41] <ajmitch> yes?
[04:41] <bddebian> ajmitch: Hi.  Do you know much about the MOM stuff?
[04:43] <ajmitch> hello
[04:43] <ajmitch> I know a little bit
[04:44] <bddebian> NM, I think I figured it out.  Regardless of whether it's Debian-dropped or Ubuntu-dropped, they need to be added manually if missing right?
[04:48] <ajmitch> yeah, if needed
[04:52] <bddebian> OK, thx, sorry to bother you
[05:10] <bddebian> I really wish someone would check all this work I'm doing.   That should be enough to see if I am causing problems
[06:45] <Burgundavia> ok, just haven't seen you
[06:45] <tseng> yep ive been barely on at all during the day
[06:45] <tseng> and scarce at night
[06:46] <Burgundavia> cheers
[06:47] <tseng> i cant seem to get the attachemnt on the first bug
[06:48] <tseng> hm you are doing a debdiff from the mom merged package to your package?
[06:48] <bddebian> tseng: Yeah, I screwed that one up.  Loaded it as octet-stream instead of text
[06:48] <tseng> im looking at 12561 now
[06:49] <tseng> i have a feeling you intended to debdiff mom-merge + bd work back to the previous ubuntu version
[06:49] <tseng> but it looks like you debdiffed to mom
[06:49] <tseng> http://bugzilla.ubuntu.com/attachment.cgi?id=3052
[06:49] <tseng> just bumped changelog there
[06:50] <tseng> is that what you intended?
[06:51] <bddebian> tseng: There were some debian/control changes I made from debian-dropped
[06:51] <tseng> they are not reflected in the patches you are posting
[06:52] <tseng> it does indeed sound pretty helpful what you are trying to do
[06:52] <tseng> get the merge work done for motu ahead of time
[06:53] <bddebian> You are looking at 12561 right?
[06:53] <tseng> its just not making it across the wire.. double check your debdiff
[06:53] <tseng> 12561, then 12489
[06:53] <tseng> they both only touch debian/changelog
[06:53] <bddebian> Did you read the note on 12561?
[06:53] <tseng> yes
[06:53] <tseng> which is great
[06:53] <tseng> its just not actually in the diff
[06:53] <bddebian> Because I didn't change it.  I didn't apply that part of the patch.
[06:54] <tseng> hm oh
[06:54] <bddebian> If I would have manually added libjack0.100.0 it would break the package
[06:54] <tseng> yes, so mom already took ours rightly
[06:54] <tseng> i see
[06:54] <bddebian> Aye
[06:55] <tseng> then, the changelog bumps arent that helpful
[06:55] <tseng> but the reporting is
[06:55] <bddebian> I probably shouldn't have bothered doing a new version.  That was the first one I did
[06:55] <tseng> yep.
[06:55] <tseng> 12488 is nice
[06:55] <tseng> same thing slomo did for my bugs
[06:58] <tseng> Burgundavia: whats new?
[07:00] <bddebian> Fixed 12562 attachment
[07:00] <tseng> rock
[07:02] <Burgundavia> Burgundavia, not much. More work with docs. Job search
[07:02] <bddebian> And for 12489 it had hoary and I bumped to breezy.  Do I not need a ubuntu+ version for that either?
[07:02] <tseng> if you change something
[07:03] <tseng> you increase the version
[07:03] <tseng> always :)
[07:03] <bddebian> But you just said... ;-)
[07:03] <tseng> i said that the maintainer can easily run dch -i himself
[07:03] <bddebian> Sorry, I'll shut up now.  So is what I'm doing OK?  I want to help but I don't want to cause someone else more work?
[07:04] <tseng> but at that time he will increase the ubuntu version
[07:04] <tseng> it doesnt cause more work for anyone but you
[07:04] <bddebian> Thats good because I have already hit about 10-15 of them :-)
[07:04] <tseng> hm cool
[07:05] <bddebian> BTW, do you happen to know what is up with debdiff?  I upgraded and now it's b0rked
[07:05] <tseng> nope
[07:05] <tseng> sorry.
[07:06] <bddebian> How would I do it by hand?  Just copy the extracted dir and diff -Nurp?
[07:06] <tseng> eh
[07:06] <tseng> i remember the changes I make
[07:06] <tseng> i unpack the debian version and press Replay
[07:07] <tseng> and ignore extraneous bits
[07:07] <tseng> i dont recommend it
[07:07] <bddebian> OK.  Well thanks.  Time for me to hit the sack.  Hopefully I can hit some more tomorrow.
[07:08] <tseng> have a good one.
[07:08] <bddebian> You too, thanks.
[07:25] <ajmitch> hi tseng
[07:25] <ajmitch> good to hear about 1.18.2
[07:32] <ajmitch> tseng: any plans to try & get beagle 0.0.12 in past the UVF committee? or is the same gtk# api instability issue?
[07:51] <ajmitch> yay, new blam bug
[07:53] <Burgundavia> everybody loves blam
[07:58] <ajmitch> yep
[08:03] <ajmitch> at least I see the bug too, which makes it easier to track down
[10:10] <herve> morning
[10:15] <ajmitch> hi herve
[02:19] (ogra/#ubuntu-motu) herve, done
[02:19] (herve/#ubuntu-motu) thanks
[02:20] <slomo> hmm... what to do with a package which needs configured kernel sources?
[02:21] <ajmitch> slomo: usually just needs the kernel headers to build
[02:21] <ajmitch> like hostap
[02:23] <ivoks> ok guys...
[02:23] <ivoks> see you when i get back to zagreb
[02:24] <herve> bye
[02:24] <slomo> ajmitch: linux-kernel-headers? ok... and stuff which builds kernel modules must be built with gcc 3.4?
[02:24] <ajmitch> slomo: afaik, yep
[02:24] <ajmitch> ivoks: see you later
[02:25] <ivoks> images at http://master.grad.hr/~ivoks/summer2005 in couple of minutes :)
[02:29] <tseng> wow
[02:29] <tseng> that place is amazing
[02:31] <herve> slomo, I don't see why we can drop ubuntu for rss2email
[02:32] <herve> debian is still using python2.3
[02:32] <slomo> herve: Nafallo looked at rss2email... mine is the line under Nafallo's ;)
[02:32] <herve> whoops, sorry
[02:32] <herve> Nafallo? :-)
[02:33] <Nafallo> herve: I saw. About to look at the package again now.
[02:35] <ajmitch> time for me to sleep, see you tomorrow :)
[02:35] <slomo> yeah... fixed mol :) is here someone who wants to look at it in maybe 15 minutes?
[02:35] <\sh> *phew*
[02:35] <Nafallo> herve: python == python-2.4 in ubuntu. no need to declare all that stuff.
[02:35] <\sh> warm+ shopping + a lot of to carry == terrible
[02:36] <Mithrandir> heh :-)
[02:36] <slomo> \sh: where do you live? it's cold here ;)
[02:36] <herve> Nafallo, yes but... http://packages.debian.org/unstable/mail/rss2email
[02:36] <herve> asking for a version of Python we don't have
[02:36] <\sh> slomo: nrw :) kerpen
[02:37] <\sh> herve: which one? 2.2? put 2.4 in ,-)
[02:37] <slomo> \sh: i live also in nrw... detmold near bielefeld ;) and it's cold enough to work here :)
[02:38] <\sh> slomo: really? yesterday it was 15 degrees and windy
[02:38] <comadreja> howdy all
[02:38] <comadreja> hey I lived in Oberhausen for three years
[02:38] <\sh> slomo: btw..i worked near bielefeld :)
[02:38] <Nafallo> sh: that's why gothcat and Simira are out shopping and me and Mithrandir is on IRC :-)
[02:39] <\sh> so u send your irls shopping ?;)
[02:39] <slomo> \sh: you think 15 is too warm? oh ok ;) hm, i have to go shopping later, too :)
[02:39] <\sh> +g
[02:39] <\sh> slomo: no now it 25
[02:39] <herve> \sh, python >= 2.3 << 2.4
[02:39] <\sh> herve: replace it
[02:39] <herve> that's my point
[02:39] <herve> we need to merge again
[02:40] <slomo> \sh: it's 15,8 here :P
[02:40] <Nafallo> sh: they sent themselves ;-)
[02:40] <\sh> Nafallo: lol...women ;)
[02:40] <herve> now you tell it, 23 is not much here
[02:41] <herve> ok, I mailed elmo about the sync requests
[02:42] <\sh> herve: ping ogra for editbugs...he's on
[02:42] <eruin> does anyone in here know what's required for nm-vpn-properties to not complain about missing vpn software?
[02:42] <herve> \sh, he did it yes
[02:42] <ogra> \sh, herve already has editbugs
[02:42] <slomo> tseng: btw... i've mailed elmo about the boo sync request 2 days ago... there was no answer :/
[02:42] <Nafallo> eruin: I guess it should support vpnc, and only vpnc
[02:42] <\sh> slomo: i will give u a tip :) go to your favorite turkish restaurant..and order doener+lamacun extra hot'n'strong :)
[02:42] <herve> argh! I could have added it to the list
[02:42] <\sh> ogra: ah ok
[02:43] <eruin> Nafallo, hmm, I have that installed and it still complains about missing VPN software
[02:43] <tseng> slomo: oh. did you tell him i am sponsoring you?
[02:43] <eruin> Nafallo, should I report it as a bug?
[02:44] <slomo> tseng: yes
[02:44] <\sh> ogra: r u in for laptop mission?
[02:44] <slomo> \sh: thanks :) i'll do this evening... the next is just 3 minutes from here ;)
[02:45] <herve> my mistake!
[02:45] <Nafallo> eruin: probably :-)
[02:45] <herve> rss2email can smoothly move to python2.4
[02:45] <herve> there is no version dependency written in hard
[02:46] <herve> slomo, I'll ask for boo to
[02:46] <herve> too
[02:46] <siretart> what is elmo's email?
[02:46] <slomo> thanks :) he has answered on irc and said i should send him a mail
[02:47] <herve> I mail to<EMAIL_ADDRESS>[02:47] <Nafallo> herve: indeed.
[02:47] <ogra> \sh, seems not, i didnt get mail about it
[02:47] <Nafallo> I thought I built it :-P
[02:48] <\sh> ogra: hehe so we have to buy some other stuff ;)
[02:49] <ogra> \sh, i will  do that anyway, the keyboard of this thing here freaks me out
[02:49] <\sh> ogra: why? if you don't want it...you know my address *lol*
[02:50] <ogra> heh
[02:50] <\sh> jesus..
[02:50] <\sh> I ate too much
[02:51] <ogra> \sh, keyboard, only partial working DVD rom and case are the real drawbacks of this lappie... and sine i travel more, 3.5kg are not the best weight...
[02:51] <Amaranth> it's easier to request a sync in #u-d
[02:51] <ogra> since even...
[02:51] <ogra> Amaranth, but not the preferred way
[02:52] <\sh> ogra: so don't buy a hp 6120
[02:52] <Amaranth> ogra: All the canonical employees seem to do it except you. :)
[02:52] <\sh> ogra: it's heavy then mine nc6000
[02:52] <ogra> \sh, my next one will be a lot smaller
[02:52] <\sh> but nicer actually
[02:52] <ogra> Amaranth, i do it too, but the preferred wa is email nevertheless
[02:52] <ogra> way even
[02:52] <herve> I like my dell x300
[02:53] <ogra> \sh, as long as it doesnt swallow half of my typed stuff and is a bit lighter i'm fine
[02:53] <\sh> but at home I prefere a nice workstation with a good tft+crt
[02:54] <\sh> so I have to get to my ex that she has to give it back to me *grmpf*
[02:54] <slomo> oh no... :( i've hacked together a few patches for mol to let it compile... then i noticed that it needs gcc 3.4 (kernel stuff) and all patches could be dropped :(
[02:55] <herve> not when it will move to gcc 4 :-)
[02:55] <herve> upstream may be interested
[02:55] <slomo> ok, i'll mail them later ;) hmm will the kernel be built with 3.4 until breezy release?
[02:55] <\sh> patching kdevelop3
[02:56] <herve> slomo, ask fabbione probably
[02:56] <slomo> ok
[03:02] <\sh> comadreja: ping
[03:02] <\sh> comadreja: I'd uploaded eyed3 with your patches
[03:03] <\sh> comadreja: did u get any reply from katie?
[03:06] <herve> ok, I switch project
[03:07] <herve> I stay here for questions and uploads
[03:08] <\sh> if anybody has time..please have a look on libhid, kwave (flac issues)
[03:09] <\sh> for kwave: debian is using libflac6 we have libfacl7 as I recall
[03:09] <\sh> libhid must use python2.4, and I don't come along with the autotools stuff in there
[03:10] <slomo> waahh... i destroyed the MOTUTOMerge wikipage ;) can someone tell me why it's broken?
[03:10] <\sh> swig/Makefile.am is mentioning 2.3, replaced it 2.4, but any attempt to aclocal,automake,autoconf bla doesn't work
[03:12] <comadreja> \sh: pong yes, thanks !
[03:12] <herve> slomo, nothing much
[03:12] <comadreja> \sh: I saw it on breezy-changes
[03:13] <\sh> comadreja: hmm...i don't have the mail
[03:13] <\sh> :(
[03:13] <comadreja> \sh: I also sent patches for module-assistant
[03:13] <herve> slomo, remove the newline you introduced in your own line
[03:13] <comadreja> \sh: is that mailing list katie ?
[03:13] <\sh> comadreja: no..katie is for upload
[03:13] <slomo> herve: thanks :)
[03:13] <\sh> breezy-changes when it's going to the buildd
[03:13] <\sh> comadreja: check the katie reply
[03:13] <comadreja> \sh: then I didn't receive katie's mail
[03:14] <\sh> comadreja: can u check breezy changes again?
[03:14] <comadreja> \sh: sure
[03:14] <\sh> argl
[03:14] <\sh> it can't go through
[03:15] <comadreja> \sh: now I can't find it... maybe I'm mistaken
[03:15] <\sh> i didn't do a source uploda
[03:15] <\sh> upload even
[03:16] <herve> hehe, I made the mistake too
[03:16] <\sh> but now
[03:16] <slomo> herve: when you're searching for stuff you can upload... look at mine ;)
[03:16] <herve> mol and the like?
[03:17] <slomo> yes... and the rest of the line ;) but leave tomboy and monodevelop alone, i think tseng wants to look at them (and for monodevelop the boo sync is required)
[03:18] <herve> I would have left the mono stuff anyway :-)
[03:22] <\sh> Accepted eyed3 0.6.6-1ubuntu1 (source)
[03:22] <\sh> yay
[03:25] <bddebian> Morning
[03:25] <slomo> bddebian: good morning :) you've forgotten to add pymol to MOTUToMerge ;) i've done that for you :P
[03:26] <\sh> slomo: have an eye on http://people.ubuntu.com/~lamont/buildLogs/byDate/today.html
[03:26] <bddebian> I did about 5 or 6 last night.  Are we supposed to be adding them to MOTUToMerge??  I was just tagging the bugs as pendingupload.
[03:27] <slomo> bddebian: no idea... i do both for my stuff
[03:27] <slomo> \sh: this is nicer: http://hwdb.ubuntu.com/buildlogs/  :)
[03:27] <comadreja> :)
[03:27] <\sh> aeh
[03:27] <\sh> damn
[03:27] <\sh> comadreja: i mean
[03:28] <slomo> bddebian: no, that can't be... it's my job to be confused :)
[03:28] <herve> hello bddebian
[03:28] <bddebian> Heya herve
[03:28] <bddebian> I probably should add them to MOTUToMerge since there is no "good" way to see what I have already done with bugzilla
[03:30] <ogra> bddebian, there is ;)
[03:31] <ogra> bddebian, just take the tinyurl list, click on "edit search" and select only the pending ones....
[03:31] <ogra> like thet:
[03:31] <ogra> https://bugzilla.ubuntu.com/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&component=UNKNOWN&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=PENDINGUPLOAD&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chf
[03:31] <ogra> ieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=product&type0-0-0=substring&value0-0-0=merging&field0-0-1=component&type0-0-1=substring&value0-0-1=merging&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=merging&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=merging
[03:31] <ogra> whee, thats long...
[03:31] <ogra> sorry :)
[03:31] <\sh> lol
[03:32] <bddebian> w00t
[03:32] <bddebian> :-)
[03:33] <ogra> http://tinyurl.com/du8re
[03:33] <ogra> :)
[03:33] <ogra> thats the pending list
[03:33] <herve> the longuest query in the west -:)
[03:35] <Amaranth> i can't believe the logs are still crammed with bogofilter failings
[03:35] <siretart> ogra: I added the url to MOTUToMerge
[03:36] <ogra> thanks :)
[03:36] <siretart> Amaranth: thats because of http://bugzilla.ubuntu.com/show_bug.cgi?id=12536
[03:36] <salgado> hey guys. I'm not sure this is the right place to ask for this, but I'm trying to create a new package, and every tutorial I read talk about dh_make, which doesn't seem to have any installation candidate on hoary
[03:36] <salgado> is there something I'm supposed to use instead of dh_make?
[03:36] <ogra> devscripts
[03:36] <bddebian> OK damnit, who is updating MOTUToMerge?? :-)
[03:36] <tseng> for tomboy
[03:36] <ogra> hey salgado btw :)#
[03:36] <tseng> i think elmo can just sync it
[03:37] <slomo> salgado: apt-get install dh-make ;)
[03:37] <salgado> yo ogra. how's it going?
[03:37] <bddebian> BTW, anyone know why debdiff is b0rked all of the sudden?
[03:37] <Amaranth> siretart: it's been 2 weeks since you filed that though...
[03:37] <ogra> salgado, edubuntu is drawing all my time :)
[03:37] <siretart> Amaranth: I know, but I cannot fix that bug myself
[03:38] <tseng> i mailed elmo to sync tomboy
[03:38] <tseng> MD needs manual
[03:38] <siretart> Amaranth: I don't know what to do else about it
[03:38] <tseng> after boo
[03:38] <tseng> its also in main
[03:38] <Amaranth> siretart: annoy people until they fix it :)
[03:38] <salgado> slomo, I don't seem to be able to do that in any hoary system I have access (it can't find any installation candidate)
[03:39] <tseng> its dh-make not dh_make
[03:39] <tseng> dh-make - Debianizing Tool for debhelper
[03:40] <ogra> while the binary is called dh_make onec its installed
[03:40] <salgado> tseng, then that means something is broken here
[03:40] <herve> maybe it's in universe and you don't have the source list
[03:40] <bddebian> slomo: Fix debdiff will ya?? :-)
[03:40] <salgado> Package dh-make is not available, but is referred to by another package.
[03:40] <slomo> bddebian: what are you talking about? ;)
[03:40] <\sh> yay...ymca is playin in the back....and kdevelop3 is building...does it mean kde is gay? ,-)
[03:41] <herve> bddebian, install latest devscripts from debian and you're set
[03:41] <siretart> salgado: https://wiki.ubuntu.com/DeveloperResources has also a lot of interesting links for you, I think
[03:41] <ogra> herve, dh_make ? in universe ?
[03:41] <herve> no s
[03:41] <herve> just making suggestions :-)
[03:41] <salgado> siretart, yep, I'm looking there
[03:42] <bddebian> herve: Really?  I upgraded last night and it still pukes on me.. :-(
[03:42] <salgado> it's there
[03:42] <bddebian> ACK, what am I doing to MOTUToMerge????
[03:43] <slomo> bddebian: hehe, same happened to me a few minutes ago ;) remove the newline you've inserted... at least that was my mistake
[03:43] <salgado> this is what you get on shared-root machines; someone fucked up my sources.list
[03:43] <bddebian> phew
[03:44] <bddebian> Hmm, maybe I haven't been as busy as I thought :-(
[03:47] <ogra> salgado, worst case, pluu it from here: http://packages.ubuntu.com/hoary/devel/dh-make and install with dpkg -i
[03:47] <ogra> s/pluu/pull
[03:48] <salgado> thanks ogra. I fixed the sources.list and now it's installable. :)
[03:48] <ogra> ah, great :)
[03:48] <bddebian> herve: Ohh, you said from Debian for devscripts.  Missed that part
[03:48] <herve> yes, latest unstable
[03:48] <bddebian> Maybe some nice MOTU should upload that.. ;-)
[03:49] <slomo> herve: can we sync that for breezy?
[03:49] <herve> it's probably in main as ogra told
[03:49] <bddebian> Oh yeah
[03:49] <herve> I saw ftbfs on some archs with the debian package
[03:49] <herve> or maybe just some debian buildds are down
[03:53] <\sh> i did it...
[03:53] <\sh> oh god..what did I du
[03:53] <\sh> s/du/do/
[03:55] <\sh> ogra: your fault
[03:55] <\sh> gna
[03:57] <bddebian> Do we have the source for the new devscripts in the archive?
[03:59] <herve> no
[04:04] <bddebian> Well get to work people!! ;-)
[04:05] <herve> a ubuntu hurd distro, you call that work? :-)
[04:06] <bddebian> herve: Well I'm looking at MOTUToMerge atm but I wanna get going on GNU/Hurd :-)
[04:13] <tseng> does anyone know how to use iptables to forward one port to another
[04:14] <tseng> i want to run ssh on port 22
[04:14] <tseng> and be able to get it at 443 also
[04:14] <siretart> tseng: add a line in sshd_config, no need for iptables
[04:14] <tseng> it can listen to both?
[04:14] <slomo> tseng: $IPT -t nat -A PREROUTING -p tcp -i $ext --dport $port -j DNAT --to localhost:$port
[04:14] <slomo> tseng: that should work ;)
[04:15] <siretart> tseng: jepp
[04:15] <tseng> i use port 443 to trick the proxy at work
[04:15] <tseng> holy crap, thanks siretart
[04:15] <siretart> slomo: then iptables would not be able to accept requests on port 22
[04:15] <tseng> (and slomo)
[04:16] <siretart> nm
[04:16] <slomo> siretart: why?
[04:17] <siretart> slomo: on the second thought, never mind ;)
[04:21] <bddebian> slomo: Oh no, you have work to do.. :-)
[04:23] <slomo> bddebian: sure... but without something to eat i can't work tomorrow :P
[04:25] <bddebian> slomo: Ah, good point :-)
[04:27] <\sh> ok..another build of kdevelop3 before upload
[04:29] <bddebian> I keep meaning to try kdevelop
[04:33] <herve> bddebian, can I go to the bathroom?
[04:36] <ogra> herve, you go to bddebian's bathroom ?
[04:37] <herve> no, I wait for his approval
[04:37] <bddebian> I suppose.    Should I not be?
[04:40] <\sh> bddebian: no its ok..please patch :)
[04:40] <bddebian> The only dropped patches were a build-dep and update Standards version
[04:42] <\sh> bddebian: no..if the build failes. you have to patch :)
[04:43] <bddebian> No I don't, I'm just a slave, not an MOTU ;-P
[04:43] <bddebian> j/k So far it's building it is just taking a while. :-)
[04:58] <\sh> herve: i just read the backlog...what did u say? I supposed to be in the laptop team? ah come on :) I just requested a HP BladeCenter for the other two transitions ,-)
[04:58] <herve> I just read the wiki page
[04:59] <\sh> I'm just on this page...
[04:59] <\sh> herve: which one?
[04:59] <\sh> LaptopTesting?
[04:59] <herve> no, there was Team in the name
[05:00] <\sh> https://wiki.ubuntu.com/LaptopTestingTeam
[05:00] <\sh> ?
[05:00] <herve> yep
[05:00] <\sh> ah..from this page the people were choosen
[05:01] <jsgotangco> right
[05:01] <herve> I'm not sure
[05:01] <\sh> it doesn't mean, that someone will be on for those laptops...
[05:01] <jsgotangco> i received a confirmation email last night
[05:01] <herve> I don't see siretart for instance
[05:02] <tseng> im not on that page
[05:02] <tseng> should I be?
[05:03] <\sh> is siretart in?
[05:03] <jsgotangco> tseng: i think you should you deserve one
[05:03] <tseng> jsgotangco: well, i already got the email
[05:04] <\sh> laptop testing is a hard jo
[05:04] <herve> yeah, especially with a dell
[05:04] <herve> and worst with a compaq
[05:04] <jsgotangco> ouch no compaq please...i'd rather settle with my crappy taiwan no name unit
[05:04] <\sh> well..I think I deleted this mail ,-)
[05:05] <tseng> i asked about ppc/amd64 kit awhile back
[05:05] <jsgotangco> they'll give you an acer hah *joke*
[05:05] <tseng> nah :P
[05:06] <jsgotangco> i saw this ridiculously priced acer ferrari with carbon fiber last night
[05:06] <tseng> yeah
[05:06] <tseng> the Sun guys have them
[05:07] <ogra> jsgotangco, dont but it !
[05:07] <herve> hehe
[05:07] <jsgotangco> ogra: no way, after your warning before...
[05:07] <ogra> jsgotangco, i have the cheap version of it, its the crappiest HW i ever had
[05:07] <ogra> though the ferrari might have a better keyboard
[05:07] <jsgotangco> nice paint job though...as if i have to wax a laptop
[05:08] <bddebian> heh
[05:08] <\sh> ogra: if you don't need it..give it to me..i can create a buildd
[05:08] <\sh> ,-)
[05:08] <ogra> \sh, if i dont use it as laptop i can do that too ;)
[05:09] <\sh> ogra: please provide a chroot, pbuilder and login ,-)
[05:09] <ogra> currently it still has the amd64 advantage... i wont give it up yet :)
[05:09] <\sh> I just calculated.
[05:09] <ogra> \sh, haha... vial mobile link if i'm travelling ?
[05:09] <ogra> s/vial/via
[05:10] <\sh> i'm just working 1 1/2 years for ISH...after another 1 1/2 years it's time to change the company again
[05:10] <\sh> so new company, I hope there will be a new laptop ,-)
[05:10] <ogra> \sh, every time is a good time to leave ISH ;)
[05:10] <\sh> ogra: but not without a new job, dear :)
[05:11] <\sh> ogra: or are u proposing me a room in your house, where I can live for free? ,-)
[05:11] <ogra> \sh, depends, withot job you wont have to pay your ex :)
[05:11] <\sh> ogra: yeah..but without a  jon I can't pay my flat
[05:11] <bddebian> heh
[05:12] <\sh> job
[05:12] <ogra> \sh, you could try to share the cellar with my mental ill landlord, but i doubt that will be fun :)
[05:12] <\sh> is missing
[05:12] <tseng> http://tseng2.ath.cx:3000/admin
[05:12] <tseng> ruby on rails > *
[05:12] <tseng> so far that app has < 10 lines of code I wrote
[05:12] <\sh> ogra: oh no..forget it..
[05:12] <ogra> tseng, so take over maintainershoip
[05:12] <tseng> ogra: i asked elmo to sync it
[05:12] <tseng> ogra: i tested the debian version
[05:13] <tseng> there was a guy in here who wanted to be maintainer of rails stuff
[05:13] <\sh> ogra: behappy, that there r no "VisualBasicForLinux" freaks ,-)
[05:13] <tseng> i havent seen him again
[05:13] <ogra> tseng, we still have no MOTU for the ubuntu maintenance
[05:13] <tseng> ogra: the debian maintainer is fast + good
[05:13] <tseng> we just need syncs now
[05:14] <tseng> i am watching it casually
[05:14] <ogra> tseng, but makes crappy split ruby packages according to allthe complaints
[05:14] <tseng> hm i dont want ruby core
[05:14] <ogra> and i'm not after repackaging it
[05:14] <ogra> exactly
[05:14] <tseng> i will make sure rails stays up to date and working
[05:14] <tseng> thats about it
[05:17] <ogra> btw, the art team is after getting gnome-art in.... anybody interested in maintaining a ruby gtk app ?
[05:17] <bddebian> Crap, octave2.1 is taking FOREVER.  I gotta go get some honey-do's done before she gets home.. :-)
[05:20] <\sh> bddebian: same for kdevelop3
[05:20] <\sh> it's building here since 2 h
[05:22] <lamont> \sh:  http://people.ubuntu.com/~lamont/buildLogs/Test/byDate/today.html is also interesting
[05:23] <\sh> lamont: purpose of Test?
[05:23] <ogra> \sh, complete autorebuild of the archive
[05:23] <\sh> aye
[05:24] <lamont> yeah
[05:24] <lamont> atm, it just has main in it.
[05:24] <lamont> should get universe sometime soonish
[05:24] <\sh> lamont: w8 with universe until the last merges are done and the rest of the transitions...
[05:25] <slomo> reee
[05:25] <\sh> after all...please have a look: libhid, kwave (MoM Merges) ,-)
[05:25] <lamont> \sh: it'll just be run over and over and over and over
[05:26] <lamont> \sh: the big thing that autotest is catching is things that we ahve binaries in the archive, but can't rebuild them.
[05:26] <\sh> I think this is my hp bladecenter what i requested? ,-)
[05:26] <jsgotangco> ok time for me to sleep, good night everyone
[05:26] <ogra> nigh jsgotangco
[05:26] <tseng> bye jsgotangco
[05:26] <\sh> night jsgotangco
[05:31] <slomo> siretart: thanks for uploading the linkchecker package :)
[05:36] <bddebian> OK, octave2.1 is done
[05:38] <slomo> tseng: does the new mono include the debugger?
[05:42] <tseng> slomo: no the debugger is a seperate package
[05:42] <tseng> and is kind of WIP
[05:42] <slomo> tseng: is it somewhere in breezy? would be nice to enable it in monodevelop ;)
[05:42] <tseng> no
[05:46] <\sh> oh no
[05:48] <\sh> libXcursor...
[05:48] <\sh> damn
[05:48] <\sh> again
[05:51] <\sh> rebuild
[05:54] <slomo> \sh: what packages were bugging you? libhid... and?
[05:57] <\sh> kwave
[05:57] <\sh> libhid i have the solution what to do..but autotools is bugging me
[05:57] <\sh> kwave: debian is using libflac6 and we have libflac7 and this is bugging me as well...
[05:58] <slomo> ok, you do libhid and i look at kwave ;)
[05:58] <\sh> libhid i'M too stupid for it...or automake doesn't like me
[05:59] <slomo> hmm... what's exactly the problem?
[06:01] <\sh> in the swig dir...exchange in Makefile.am python2.3 dir with python2.4
[06:01] <\sh> after that, I have to rebuild the files with aclocal automake autoconf..but it doesn't work
[06:01] <\sh> neither in chroot nor in rules files
[06:08] <slomo> \sh: just change it in Makefile.am and Makefile.in ;)
[06:08] <\sh> this is not the right solution...
[06:09] <Burgundavia> ogra, is there a hard fast date for all these main inclusion reports. Is it fine if I work on them over the next week?
[06:10] <ogra> feature freeze is august 11th, until then they should be finished
[06:12] <slomo> \sh: yes, that's not the cleanest solution but it will work until autoreconf works again ;) and the old patch in libhid which can't be applied does exactly the same
[06:12] <Burgundavia> ogra, ok
[06:13] <siretart> slomo: do you have access to ppc hardware and could try building qemu for ppc?
[06:14] <slomo> siretart: sure... i can try on my ibook
[06:14] <siretart> slomo: http://bugs.debian.org/319527 has the patch in question
[06:15] <siretart> it's not urgent, merges are way more important
[06:15] <slomo> siretart: i'm multitasking capable ;) what patch do you mean? isn't this the same patch as you've uploaded?
[06:16] <siretart> slomo: the latest message mentions http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00004.html
[06:17] <slomo> hm seems to be the solution for the problem i had yesterday
[06:17] <siretart> ah, the latest posts are only on my inbox, and not yet on http://bugs.debian.org/319527
[07:23] <\sh> slomo: offlineimap?
[07:23] <slomo> \sh: yes?
[07:24] <\sh> uploaded? i just read the buglist...
[07:24] <\sh> don't find it
[07:25] <slomo> \sh: no... not uploaded but can be uploaded ;)
[07:25] <\sh> ah
[07:25] <\sh> Just upload the mom-merged version... seems fine
[07:25] <\sh> it's a bit strange;)
[07:25] <slomo> hehe... that's just a request for uploading ;)
[07:26] <bddebian> OK darn it.  I just made a small two line change to config.guess and when I do diff -Nurp /foo.old/bar /foo/bar I get much more than just the two lines I changed.  What gives?
[07:27] <slomo> bddebian: is config.{sub,guess} included in the diff?
[07:27] <bddebian> slomo: It is config.guess yes
[07:28] <slomo> ok... i don't know what to do then ;) you can just delete the config.guess stuff from the diff... or add your changes to clean sources ;)
[07:29] <\sh> offlineimap uploaded
[07:31] <slomo> \sh: i'm currently converting kwave to the new flac... can you please run and test it when i'm finished? i have no kde installed
[07:32] <\sh> slomo: sure...send me the patches.
[07:32] <\sh> sh at sourcecode.de ;)
[07:32] <\sh> or put them into the bug entry
[07:32] <slomo> ok
[07:32] <slomo> but i think i don't have enough time this evening... will finish it tomorrow
[07:32] <\sh> no pro
[07:32] <\sh> b
[07:40] <bddebian> w00t, /me breaks the 10 packages mark.  Though I swear I am missing some packages that I already re-built???
[07:47] <\sh> gatos uploaded
[07:52] <\sh> ok..uploading time today...i don't have luck today with patching source
[07:53] <slomo> \sh: thanks :) i think i understood all changes in the flac++ api... you get the patch tomorrow, i'm out this evening ;)
[07:53] <bddebian> To test more packages or not to test.. That is the question
[07:53] <\sh> slomo: u rock...I don't have any clue about flac
[07:54] <\sh> mol uploaded
[07:55] <slomo> \sh: i've known only the C api... but fortunatly the c++ api is almost identical, just everything wrapped in nice classes :)
[07:57] <bddebian> Something doesn't look right with hardware monitor.  apt-get source doesn't get an ubuntuX version but MOM says ubuntu2 ??
[07:58] <slomo> hmm... why is bogofilter built over and over again and fails every time?
[07:59] <\sh> bddebian: hmmm
[08:00] <\sh> bddebian: u sure octave2.1 build ok?
[08:00] <bddebian> \sh: Worked for me(tm)
[08:00] <\sh> cause debuild -S tells me something else
[08:00] <\sh> all patches are failing
[08:01] <\sh> and why nobody is assigning the bugs to themselfs *grrr*
[08:02] <bddebian> \sh: All what patches?
[08:02] <bddebian> I don't assign the bugs to myself because I am not an MOTU
[08:02] <\sh> bddebian: and? now octave2.1 is yours...also in bugzilla...please have a look thx :)
[08:03] <\sh> bddebian: if you're working on a package..it's nice to assign it to you, so we can have a look what work u have done..:)
[08:04] <bddebian> \sh: OK, I just thought that was bad since I wasn't MOTU?
[08:04] <\sh> bddebian: also important to put a nice link on your wiki ,-)
[08:04] <\sh> bddebian: come on..stop with this MOTU stuff...to fix bugs u don't need to be motu :)
[08:04] <bddebian> \sh: This is on i386?
[08:04] <\sh> bddebian: debuild -S works also on amd64 ,-)
[08:05] <\sh> and patches are applied on all archs :)
[08:05] <bddebian> \sh: I am not saying that to be sarcastic, I just didn't think it was appropriate.
[08:06] <\sh> bddebian: i'm not sarcastic :) I'm just trying to get u a nice list of bugs..so you can tell anybody: u see, i did this and that...:)
[08:06] <bddebian> Ahh :-)
[08:06] <\sh> bddebian: and the infos are in the entry https://bugzilla.ubuntu.com/show_bug.cgi?id=12413
[08:07] <bddebian> \sh: You just did apt-get source and then debuild -S ??
[08:07] <\sh> bddebian: no..I just took the merge sources
[08:07] <\sh> got it from scotts page..
[08:07] <\sh> appropriate way
[08:07] <bddebian> Damnit, this is what I keep asking
[08:07] <bddebian> Grr
[08:07] <\sh> apt-get source is "the actual source"
[08:08] <\sh> in the archives
[08:08] <\sh> and I know this builds..
[08:08] <bddebian> I know, which is why I kept asking if that is the appropriate way.  I might as well start over.
[08:08] <\sh> bddebian: ok...some infos...
[08:08] <\sh> try first the sources from scotts page
[08:09] <\sh> if this is not working out properly...take debian source
[08:09] <bddebian> Getting them how?  With wget or some such?
[08:09] <\sh> and try to apply all the patches dropped by ubuntu
[08:09] <\sh> wget sure
[08:10] <slomo> \sh: i have a compiling version of the kwave flac plugin... BUT i don't think it's right at one position... will look at the flac sources ;) what a bad documentation...
[08:10] <bddebian> Any better suggestions than wget, sinc wget won't do wildcards?? :-)
[08:10] <\sh> bddebian: right mouse click-> copy link address
[08:10] <\sh> and then wget "<shift+insert>"
[08:10] <\sh> in your fav. console
[08:10] <\sh> easy
[08:10] <\sh> fast
[08:10] <\sh> reliable
[08:11] <bddebian> :-) OK
[08:11] <\sh> bddebian: u r not..I know it...I know how u feel, friend :)
[08:13] <bddebian> \sh: Do you usually just dpkg -x the dsc?
[08:14] <\sh> yepp
[08:16] <bddebian> dpkg -x wants a target directory??
[08:16] <\sh> dpkg-source -x
[08:16] <bddebian> Ohh duh
[08:20] <bddebian> Ahh, now it pukes.  Gee thanks \sh. ;-)
[08:20] <slomo> \sh: you've mail... please test :) this looks really weird but it seems that this is the right way...
[08:21] <\sh> slomo: kwave?
[08:21] <slomo> yes
[08:21] <\sh> thx :) will check it later..not today anymore :(
[08:23] <slomo> ok, please query me when you test it... or write a mail :) the critical part is the vendor string of the vorbis comments in flac files... just check if they get displayed correctly
[08:25] <slomo> bye bye :) i'll be back tomorrow
[08:25] <bddebian> Bye slomo.  You still ROCK ;-)
[08:43] <bddebian> Shoot, the Debian version of octave doesn't choke like that.. :-(
[08:43] <\sh> ok..trying again to fix kdevelop3
[08:44] <\sh> it's not the debian version...it's a mix of debian and ubuntu
[08:44] <\sh> to get the debian version directly: packages.debian.org and then unstable ,-)
[08:45] <bddebian> \sh: I know, I did and it doesn't choke on the patches the way the Ubuntu version does :-(
[08:46] <\sh> bddebian: the mom version is a mix of debian upstream and ubuntu
[08:47] <\sh> bddebian: so..check debian if it's working..and try to apply the dropped patches of ubuntu ,)
[08:47] <bddebian> Aye.  There are not dropped patches of ubuntu, just debian and they are just build-deps and standards version :-(
[08:48] <bddebian> Interesting.  The 01_gcc4.patch has 2.1.69..
[08:48] <\sh> hmm...
[08:49] <\sh> remove it temporarily
[08:50] <bddebian> Building now..
[08:51] <bddebian> debuild -S works.  Trying debuild -us -tc
[08:55] <\sh> bddebian: please build it until the end in a pbuilder..
[08:55] <\sh> to check if it has no gcc4 issues anymore
[08:55] <{Seb}> hi people
[08:56] <{Seb}> i would love to help out with ubuntu
[08:56] <{Seb}> and someone told me to come here
[08:58] <bddebian> {Seb}: What kind of help do you want to do?  There are many ways to help.
[08:59] <bddebian> Not that I personally am any help :-)
[08:59] <{Seb}> not too sure, what 'positions' are available?
[08:59] <bddebian> I mean do you want to help new users, document, fix bugs, build-packages, what??
[09:00] <{Seb}> i couldn't fix packages
[09:01] <{Seb}> i've had experience with documentation\
[09:01] <{Seb}> done stuff for hula and beagle
[09:03] <bddebian> {Seb}: Well you could check out the doc team on the wiki, or the NuN (New User Network) is trying to do some docs for n00bs.  Their wiki is here: v
[09:03] <\sh> {Seb}: check topic..https://wiki.ubuntu.com/MOTUToMerge 1. prio...check packages from MoM
[09:03] <bddebian> Do
[09:03] <bddebian> https://wiki.ubuntu.com/NewUserNetwork
[09:09] <\sh> ok...I'm gone..need some sleep
[10:54] <ajmitch> morning all!
[10:54] <comadreja> hey ajmitch :)
[10:54] <ajmitch> good to see the merge bug list slowly creeping down
[10:54] <comadreja> indeed
[10:57] <herve> zzz... hu?
[10:57] <ajmitch> hey herve
[10:57] <ajmitch> not asleep yet? :)
[10:58] <herve> it's just 23h here :-)
[11:25] <herve> someone has a version of tla > 1.3.3 ?
[11:25] <herve> *before* 1.3.3
[11:31] <siretart> gn8 folks
[11:31] <herve> night


[01:21] <wgrant> cprov, cjohnston: people.canonical.com/~wgrant/launchpad/almost-final‽.png
[01:22] <cprov> wgrant: hey hey
[01:24] <cprov> it is coming up very nicely and since the new layout is more flexible (div) it will be easier to increment.
[01:24] <wgrant> I hope so.
[01:25] <cprov> wgrant: I've just opened an asana task about finding a way to materialise the IC threads, specially in emails
[01:25] <wgrant> I've also dropped the "draft" and "publish" terminology. It nows says "Unsaved comment", and then "Include X inline comments" next to the "Save Comment" button.
[01:25] <wgrant> Yeah, I've been wondering about how to do that.
[01:25] <wgrant> It's a bit awkward, as they're all at different depths potentially.
[01:25] <cprov> wgrant: it's annoying to to read the reviews right now
[01:27] <cjohnston> looks good wgrant
[01:27] <wgrant> Someone want to review? https://code.launchpad.net/~wgrant/launchpad/ic-js-cleanup/+merge/219531
[01:28] <cprov> wgrant: I will
[01:29] <cprov> wgrant: can you review https://code.launchpad.net/~cprov/launchpad/delete-branches-with-ics ?
[01:30] <wgrant> Hm
[01:30] <wgrant> What do you guys think about renaming "inline" to "diff"?
[01:30] <wgrant> That pretty much just affects the "Include X inline comments" checkbox
[01:31] <wgrant> Makes it clearer what it refers to.
[01:31] <cprov> wgrant: I wonder if I can just add few other 'ouch' in your MP and let you figure them out ;-)
[01:31] <wgrant> Heh
[01:31] <cjohnston> +1, more ouch
[01:31] <cprov> wgrant: +1 on "diff comments"
[01:32] <cjohnston> if you do that you should probably do the same in the email
[01:32] <cjohnston> what about 'View inline comments'
[01:32] <wgrant> Oh yeah, email and link too, forgot those.
[01:33] <cjohnston> I would argue that 'regular' comments are diff comments too..
[01:33] <cjohnston> IC is actually inline
[01:34] <cprov> wgrant: table-layout: fixed, not only predictable but also faster/easier for browsers. Nice one!
[01:35] <cprov> had to look it up ...
[01:36] <wgrant> It's pretty useful here, since divs expand to fill their container, and tds expand to fit their contents.
[01:38] <cprov> wgrant: what about the TextWidget for review_type ? what does it bring ?
[01:38] <wgrant> cprov: I narrowed it from 20 characters to 15, to ensure that the widgets all fit on one line.
[01:39] <cprov> ah, cool
[01:45] <wgrant> cprov: The rename is pushed.
[01:54] <cprov> wgrant: what does the CSS added in the BMP template do ?
[01:55] <wgrant> cprov: That's a variation on cjohnston's. It adds a bit of space before the publish checkbox.
[01:55] <wgrant> Also, I've just pushed a regression fix for something that seems to have broken a few days ago: the publish checkbox was being added unconditionally, so inline comments crashed and failed to load for anonymous users.
[01:57] <cprov> I think I had fixed that in 17011, on top of cjohnston fixes ...
[01:57] <wgrant> Oh, so you did
[01:58] <wgrant> I'll uncommit and merge
[02:02] <wgrant> cprov: Have you seen any more issues on (qa)staging since those firewall fixes a few hours ago?
[02:02] <cprov> wgrant: wait, there were 2 problems, you have to manually merge the conflicting hunks.  I will review my config
[02:09] <cprov> jslint should have exploded in my face when I try to commit, that's how we should setup project for dummies (like me)
[02:10] <wgrant> Heh
[02:15] <wgrant> cprov: The line-no col is wide enough to contain five digits plus the add sprite.
[02:17] <cprov> up to 99999 lines diffs then, not at problem
[02:17] <wgrant> Well, if you go back to your old days... :P
[02:17] <cprov> wgrant: so, you really want new methods on CRICSet ...
[02:18] <wgrant> cprov: All the other manipulation code (apart from person merge) is in codereviewinlinecomment.py
[02:18] <wgrant> I really don't want it to get like various other LP model classes, where there are ten different modules that alter them.
[02:19] <wgrant> Makes it very difficult to change anything.
[02:20] <cprov> right, you think I should implement also the removal on CRICSet methods, or should I return ResultSet to be removed on the callsite ?
[02:21] <wgrant> I think you should just implement a remove method. We don't expose any ResultSets from CRICS at the moment, and I can't really see any valid reason for someone to want one.
[02:23] <cprov> wgrant: agreed, also the removal() should really consider both CRIC and CRICD as it is implemented in BMP, right ? they are likely to be removed together every time.
[02:25] <wgrant> cprov: Right, that might well be a good thing to do.
[02:25] <wgrant> I can't see much of a reason to split them.
[02:32] <cprov> wgrant: code moved and pushed
[02:39] <wgrant> cprov: I'd rename the method to removeFromDiffs or similar, but that looks great otherwise. Thanks.
[02:41] <cprov> wgrant: no problemo, renamed version pushed
[02:42] <wgrant> cprov: How much longer are you likely to be around? I think I might implement a quick fix to only include commented files (not just hunks, at least not yet) in emails.
[02:42] <cprov> longer enough.
[04:36] <cprov> wgrant: http://lpbuildbot.canonical.com/builders/lucid_lp_lxc/builds/1172/steps/shell_9/logs/summary is that old spurious failure, right ?
[04:36] <wgrant> cprov: Yup, already forced.
[04:36] <cprov> wgrant: thanks
[04:37] <cprov> wgrant: how is the ic-email improvement ?
[08:20] <cjwatson> wgrant: Any luck with the livefs reviews?  I know there's been the whole pg9.3 thing, and lots of work on IC ...
[08:20] <cjwatson> I've put the remaining things people are asking for on the shelf for now, since I reached the point where I could do a touch image build with an added PPA
[08:22] <wgrant> cjwatson: Sorry, busy with staging and postgres and inline comments and PPA microservice and ephemeral PPAs and Malta... Three of those are coming to a close tomorrow, so I might actually have some time.
[08:24] <cjwatson> OK, thanks
[08:26] <wgrant> cjwatson: Is Laney's cron.germinate change sane? I saw some debate over what the name should be.
[08:57] <cjwatson> Oh, that bit of the naming is fine.  I was meaning to review and land that for him today.
[08:58] <cjwatson> It will cause tasks to appear for sdk-libs or something like that, but they were actually wondering why they weren't there anyway
[08:58] <cjwatson> And it will cause cron.germinate to take that bit longer, of course, but I've been looking at parallelising it ...
[09:14] <cjwatson> Laney: Could you please set a commit message for https://code.launchpad.net/~laney/launchpad/germinate-ubuntu-touch/+merge/220233 ?
[09:14] <Laney> cjwatson: Oh right, yes
[09:15] <Laney> try that
[09:17] <cjwatson> Laney: Thanks, landing
[09:17] <Laney> cheers
[12:05] <cjohnston> wgrant: have the new IC changes been released?
[12:05] <cjohnston> I guess maybe it's DC changes now? ;-)
[12:06] <wgrant> cjohnston: In progress.
[12:06] <cjohnston> cool
[12:06] <cjohnston> How'd the DB stuff go?
[12:06] <wgrant> Not quite uneventful, but eventually successful.
[12:06] <cjohnston> cool
[12:06] <wgrant> The master is now 9.3, and the slaves are rebuilding on 9.3.
[12:07] <cjohnston> oh nice.. so the upgrade was done..
[12:10] <wgrant> Yep
[12:10] <wgrant> I poked the comments stuff pretty thoroughly this evening, and fixed a few bugs
[12:11] <wgrant> Including a hilarious off-by-one error in the email formatter, where comments were showing up a line later, and the first line of the diff was always missing.
[12:16] <jelmer> wgrant: is launchpad really going to do inline comments on code reviews?
[12:17] <wgrant> jelmer: On Monday, with a bit of luck.
[12:17] <jelmer> wgrant: good stuff
[12:20] <cjohnston> by "with a bit of luck" he means pencil and paper
[12:21] <cjohnston> wgrant: take a look at https://code.launchpad.net/~ursinha/uci-engine/ts-add-mp-support/+merge/220275  I think we may need to rethink the design of my "comment" a little... cjohnston a moment ago: (and then nothing)
[12:21] <cjohnston> the way it is it looks really odd without any sort of review or comments or anything
[12:21] <wgrant> cjohnston: Yeah, I think we probably want to move the "Show diff comments" link into the body somewhere. We really need space on the bottom of each comment to have links
[12:22] <wgrant> Show diff comments, Reply, and Save/Cancel in the case of the inline editor.
[12:22] <wgrant> There's no way to have actions today.
[12:22] <wgrant> Also the Delete button, and possibly a future Edit feature
[12:22] <cjohnston> edit!
[12:22] <wgrant> It's all really awful atm, no consistency. And the inconsistent bits are dreadful anyway.
[12:58] <wgrant> cjohnston: prod's all up to date now, if you want to prepare that email.
[12:58] <cjohnston> ack. thanks
[23:02] <cjohnston> wgrant: cprov, what do you think about moving the 'Add comment' stuff to below the diff...
[23:02] <cjohnston> I think it would improve workflow
[23:02] <cjohnston> If you are replying to a comment you may not need to see the diff, but otherwise, your probably going to be adding a comment after reading the diff
[23:02] <cjohnston> so instead of having to click a link to go back up, why not just have the box below
[23:46] <wgrant> cjohnston: The problem is that the diff is enormous.
[23:46] <wgrant> This is why other sites have it on a separate tab.
[23:47] <cjohnston> it apparently isn't completely discoverable That you have to click save comment
[23:49] <wgrant> Yeah, that's one of the big remaining issues.
[23:49] <wgrant> But moving the comment form below the diff would make it very difficult to find.
[23:49] <wgrant> Even for MP-wide comments.
[23:50] <cjohnston> personally i would expect it to be at the bottom and not Where it is
[23:50] <cjohnston> it seems odd to have to scroll back up after scrolling to the bottom
[23:51] <wgrant> Sure, but then you have to scroll through 5000 lines of diff.
[23:51] <wgrant> Just to find the comment form
[23:51] <wgrant> + it separates the comment form from the comment thread
[23:51] <wgrant> Which is weird
[23:51] <cjohnston> or scroll 10k lines to read the diff and then go back up
[23:53] <cjohnston> what do you think about changing the new bottom link to be either 'return to add comment' or 'return to save comments' depending on if drafts are present or not
[23:54] <cjohnston> that may help discoverability slightly


[00:03] <Patrickdk> heh? isn't that normal?
[00:03] <Patrickdk> look up dkms
[00:12] <Hydr0p0nX> yea, couldn't remember what it was called :)


[20:59] <CrustyBarnacle> Release 105: Contents and Index not being added to PDF
[21:01] <CrustyBarnacle> c7p: should there be a 'main.ind' file?
[21:02] <c7p> unfortunately i don't know the technical datails :/
[21:03] <CrustyBarnacle> That was the error that caught my eye...
[21:04] <c7p> i'm afraid i can't get you
[21:04] <c7p> i pushed the 105 revision, what's the issue ? should i add a .ind file ?
[21:17] <CrustyBarnacle> I'm doing 'make clean && make'. The resulting PDF is missing the TOC and Index.
[21:34] <CrustyBarnacle> c7p: emailed the log and error to godbyk :-)


[14:27] <melodie> hi hibana Kilos ubuntulo13 WaVeR :) o/
[14:28] <Kilos> hi melodie
[14:28] <Kilos> these guys did not come back after we switched to libera
[14:29] <Kilos> https://loco.ubuntu.com/teams/
[14:29] <Kilos> all those locos from africa
[15:22] <melodie> hello everyone!
[15:22] <melodie> Kilos, are you looking?
[15:23] <Kilos> old but still alive, how are you
[15:50] <melodie> Kilos, good, thanks!!!
[15:51] <melodie> I have been also putting up new isos for old computers. Bento antiX : no systemd in it, so sometimes it is good, and sometimes not, as I have met with a driver for an Epson printer that would not install without Systemd.
[15:52] <melodie> the ISOS are available at https://downloads.linuxvillage.org and soon I will be publishing a full description for each.
[15:52] <Kilos> oucch
[15:52] <melodie> hopefully all who need them will be able to get them.
[15:53] <Kilos> all of africa has gone quiet, maybe covid is helping
[15:53] <melodie> I'll come  back on all IRC chans I know to announce them more widely when the presentations will be online.
[15:53] <Kilos> i would like to read the descriptions please
[15:53] <melodie> Kilos, covid or not covid people ought to learn how to strengthen their defense immunity...
[15:53] <melodie> I can send the files to you by mail
[15:54] <melodie> or a link? Wait
[15:54] <Kilos> yes please
[15:54] <Kilos> people are sheep let by the media and tv and do not think for themselves about staying healthy
[15:55] <melodie> https://nextcloud.orditux.org/s/pkabQQwzG9KJp5e
[15:55] <melodie> for i486
[15:55] <Kilos> thank you
[15:56] <melodie> https://nextcloud.orditux.org/s/7e6343HiKW7WNCZ
[15:56] <melodie> for amd_64
[15:57] <melodie> and as for the i686 it's about the same, just it has a i686 PAE kernel
[15:57] <Kilos> thank you
[15:58] <melodie> all need to add the gstreamer codex packages and some more to have a full blown, all antiX come with Snapshot which allows you to make your own version, for personal use or redistribution, which is an option to choose when you start the Snapshot program (from the menus)
[15:58] <melodie> and you can get all help at the antix forum:
[15:58] <Kilos> great
[15:59] <melodie> https://www.antixforum.com/
[15:59] <melodie> there is this 'respin' section
[15:59] <melodie> keep on well!
[15:59] <melodie> I'll bbl
[15:59] <Kilos> look after yourself
[16:02] <melodie> sure! Thanks!
[21:16] <melodie> someone here does have a perfect English? I'd like a review for this text: https://etherpad.linuxvillage.org/p/page-statique-bento


[00:58] <hggdh> ping for LP operator
[00:59] <wgrant> hggdh: You might do better to just ask your question now.
[00:59] <wgrant> Then people can ping the appropriate people if necessary..
[00:59] <hggdh> please block launchpad user<EMAIL_ADDRESS>-- opening a series of non-sensical bugs
[00:59] <wgrant> Again!?
[00:59] <hggdh> yes...
[01:00] <wgrant> spm: Didn't you kill two instances of him already?
[01:00] <wgrant> hggdh: What's the username?
[01:00] <hggdh><EMAIL_ADDRESS>[01:00] <wgrant> That's not a Launchpad username.
[01:00] <wgrant> The bit in the URL.
[01:00] <Hobbsee> username, not email.
[01:00] <spm> wgrant: whackamole.....
[01:00] <hggdh> damn!
[01:00] <wgrant> There are at least two accounts i know of with that display name.
[01:01] <hggdh> rutadeevacuacion
[01:01] <wgrant> Hmmmm
[01:01] <wgrant> So these accounts are coming back to life? Wonderful.
[01:01] <hggdh> it actually looks like an automation gone bad
[01:02] <wgrant> Ooh.
[01:02] <wgrant> Creative.
[01:02] <wgrant> Linking to blueprints now.
[01:03] <hggdh> yes... and subcribing other ppl
[01:03] <wgrant> Oh dear.
[01:03] <angusthefuzz> ironically some are linked to spamassassin and clamav blueprints
[01:04] <wgrant> Hmmmm.
[01:04] <spm> hggdh: can you shoot me a link to one of the bugs - verify I've zapped the right accounts again
[01:04] <wgrant> Bug #299331 is one of his that I can't see.
[01:04] <wgrant> At least, I presume it's his.
[01:04] <hggdh> https://bugs.launchpad.net/ubuntu/+bug/300479
[01:04] <wgrant> Because it's on his pet blueprint.
[01:04] <wgrant> Bug #300475
[01:04] <wgrant> That's one of his that I *can* see.
[01:04] <hggdh> darn. wgrant, are you not in bug-control?
[01:05] <wgrant> hggdh: I am.
[01:05] <spm> wgrant: hggdh: ta - that's them
[01:06] <hggdh> we have to give him/her at least a bit of credit for being creative
[01:06] <persia> Or at least persistent
[01:06] <wgrant> What's that other project that he's filing things like #299331 on?
[01:06] <wgrant> persia: No, there's a few different types of spam produced by that user.
[01:07] <persia> wgrant, Yes.  I see that.  The persistent comment was about account creation.
[01:07] <hggdh> someone should tell her/him we are already over 300,000 bugs, so the bet (of when) is gone
[01:08] <wgrant> persia: I only know of 2 accounts... but they come back to life after spm kills them.
[01:08] <wgrant> LP doesn't kill accounts hard enough, it would seem,
[01:08] <persia> Hrm.  Frustrating that.
[01:08] <wgrant> https://answers.edge.launchpad.net/ubuntu/+question/51951
[01:08] <wgrant> What the.
[01:10] <Hobbsee> can't you just block his IPs or something?
[01:10] <wgrant> spm: You might want to remove the bugs links that I can't from https://blueprints.edge.launchpad.net/ubuntu/+spec/3g-networking-intrepid
[01:10] <spiv> Possibly they're using unique strings so they can try them in search engines later, to see how useful LP as a place to spam?
[01:11] <wgrant> spiv: But then they make them private...
[01:11] <wgrant> After they file them.
[01:11] <hggdh> should we remove the links from the blueprint?
[01:11] <spiv> But bug notification emails get sent first?
[01:11] <wgrant> Hmm, some of them are after an hour or two.
[01:11] <wgrant> Good ppoint.
[01:11] <spiv> And publically archived...
[01:12] <wgrant> hggdh: I've done those I can, but spm will have to do the rest.
[01:12] <wgrant> Kill kill kill.
[01:12] <spm> wgrant: if only it was that easy.....
[01:12] <hggdh> yes, I see...
[01:12] <wgrant> spm: You're in ~admins, so you can surely see all of them...
[01:12] <spm> see != delete :-(
[01:12] <wgrant> Huh?
[01:13] <wgrant> Why not?
[01:13] <wgrant> I can delete any links I see.
[01:14] <spm> wgrant: then clearly I am being UI challenged. :-) Where/how?
[01:14] <wgrant> spm:
[01:14] <wgrant> Gah.
[01:14] <wgrant> 'Remove bug link' or similar in the actions menu on the blueprint.
[01:14] <spm> ah *insert rude words*
[01:14] <spm> ta
[01:14] <wgrant> You'll then get checkboxes for the links to all the bugs you can see.
[01:14] <Ursinha> want to see too
[01:14] <wgrant> Blueprint has needed some love for too many years.
[01:14] <spm> wgrant: much appreciated - abolsute power doesn't equal cleverness :-)
[01:15] <Ursinha> or you mean just the remove bug link
[01:15] <Ursinha> oh, ok
[01:15] <spm> wgrant: right -how's that look?
[01:16] <wgrant> spm: That blueprint looks much better. But there might be others around.
[01:17] <hggdh> well. I guess I found a boring way to improve my karma
[01:17] <wgrant> Did the discussion about bug deletion overnight that branched from the dev meeting come to a reasonable conclusion?
[01:17] <wgrant> hggdh: I think spm should be about to make those bugs invisible by removing all subscribers.
[01:18] <hggdh> ah, even better. Thank you, I was getting tired
[01:18] <hggdh> (but if they are kept open they will pollute the stats)
[01:19] <wgrant> hggdh: No they won't, because the user generating stats isn't in ~admins, so won't be able to see that they exist.
[01:19] <hggdh> k, thanks
[01:20] <spm> https://blueprints.edge.launchpad.net/ubuntu/+spec/clamav-spamassassin-in-main - cleanedup
[01:23] <wgrant> spm: Thanks.
[01:24] <hggdh> pfui
[01:24] <hggdh> thanks, folks
[01:41] <jml> Depressing fact: Gobby is one of the most useful tools I have.
[01:50] <lszyba1> hello,
[01:50] <lszyba1> mysql source browsing doesn't work:  http://bazaar.launchpad.net/~mysql/mysql-server/mysql-5.0/files
[01:51] <lszyba1> Sorry, there was a problem connecting to the Launchpad server.
[01:51] <Hobbsee> what, again?
[01:52] <Hobbsee> spm: do you know why?
[01:52] <spiv> mwhudson: ^
[01:52] <Hobbsee> oh
[01:53] <spm> usually means codebrowse needs bouncing
[01:53] <spm> lszyba1: give it a few minutes and should be ok again
[01:54] <lszyba1> k
[01:54]  * spm switches from Jean Michel Jarre, to Wolfmother as I begin the rollout prep :-)
[01:57]  * Hobbsee wonders if a queue fix got rolled out in the latest release.
[02:00] <jml> wolfmother
[02:00] <jml> of coures
[02:01] <jml> that's what I've been missing :)
[02:02] <spm> jml: it was that or creed - and I'm feeling more.. wolfmotherish today :-)
[02:02] <spm> Led Zepplin just doesn't work for release prep work
[02:07]  * wgrant was amused to see lots of the 'now playing' in RF commit messages.
[02:09] <spm> likewise - I tend to leave it on DI Trace - less "distracting", but some tasks need "loud and rock" :-)
[02:09] <jml> I'm not a huge fan of that habit...
[02:09] <jml> we should store that information in revision properties.
[02:09] <wgrant> Hahah.
[02:10] <wgrant> Yes, abusing commit messages for metadata... tsk tsk.
[02:10] <jml> wgrant: so, where can you see the RF commit messages?
[02:10] <wgrant> jml: On the testing pages on dev.launchpad.net
[02:10] <jml> ahh, that makes sense.
[02:19] <thumper> abentley: back
[02:19] <thumper> hmm
[02:19] <thumper> not the channel I thought I was on
[02:19] <abentley> thumper: Hee.
[02:55] <spm> FYI All, running a bit slow on the release - be delayed rolling out by ~15 minutes - hopefully
[02:58]  * Hobbsee turns spm's music up
[02:58] <spm> Van Halen. 1984. Hobbsee - thank you :-)
[02:59] <Hobbsee> :)
[03:37] <spm> FYI All, release is postponed - to when is currently undetermined.
[03:41] <Hobbsee> ouch?
[03:41]  * thumper raises hand
[03:41] <thumper> my fault
[03:55] <wgrant> spm: Does edge's proxy need its icing reverted?
[03:55] <spm> wgrant: chasing atm
[03:56] <wgrant> spm: Thanks.
[04:18] <spm> wgrant: should be fixored
[04:23] <wgrant> spm: It would appear so. Thanks.
[08:28] <nomed> hi all
[08:28] <nomed> a quick question
[08:28] <nomed> is there any way to download trasnlations from launchpad
[08:28] <nomed> i'd need to create a cronjob
[09:37] <gouki> Hi everyone. Just a quick question ... PPAs or only given to teams, and not projects, correct?
[09:38] <wgrant> gouki: Teams and people, yes.
[09:38] <gouki> wgrant, thank you.
[10:50] <persia> fta, About?
[13:44] <oldman> I had a weird "Your message was rejected" e-mail from launchpad-bugs-owner about my vcs-imports request
[13:44] <oldman> https://code.launchpad.net/~vcs-imports/zquake/trunk
[13:44] <oldman> but it still says 'Pending review' on the page
[13:44] <oldman> any idea what's up?
[13:45] <kiko> oldman, can you put the message in a paste?
[13:46] <oldman> Your message was rejected
[13:46] <oldman> ---------- Forwarded message ----------
[13:46] <oldman> From: oldman<EMAIL_ADDRESS>[13:46] <oldman> To<EMAIL_ADDRESS>[13:46] <oldman> Date: Thu, 20 Nov 2008 13:46:51 -0000
[13:46] <oldman> Subject: New code import: zquake/trunk
[13:46] <oldman> A new code import has been requested by oldman: https://code.launchpad.net/~vcs-imports/zquake/trunk
[13:46] <oldman> --
[13:46] <oldman> You are getting this email because you are a member of the vcs-imports team.
[13:46] <oldman> ^ literally just that :)
[13:47] <kiko> that's weird.
[13:47] <kiko> you're sure you didn't mis-send that yourself?
[13:47] <oldman> heh
[13:47] <oldman> Received: from chlorine.canonical.com (chlorine.canonical.com [<IP_ADDRESS>])
[13:47] <oldman> *shrug*
[13:48] <kiko> that's kinda what I was looking for in the paste, but ok
[13:48] <kiko> I'll forward this to mwh and thumper
[13:48] <kiko> actually
[13:48] <kiko> oldman, can I ask you to ask a question up on answers.launchpad.net/launchpad-bazaar and stick the message in there?
[13:48] <oldman> i can paste the full headers if you want
[13:48] <oldman> ok sure
[13:48] <kiko> oldman, that way it gets tracked properly and you get notified that we fixed it
[13:49] <kiko> thanks really appreciate your effort bringing it to my attention
[13:55] <oldman> kiko-fud: seems like someone has already asked
[13:55] <oldman> kiko-fud: https://answers.launchpad.net/launchpad-bazaar/+question/51619
[13:55] <oldman> :)
[14:35] <kiko-fud> oldman, dupefinder strikes again! thanks twice
[14:35] <oldman> :)
[14:36] <oldman> feel free to do the review for my vcs-import though :)
[14:38] <kiko-fud> oldman, done
[14:39] <oldman> wow thanks
[14:39] <oldman> btw off topic, but bazaar plugins, do they need to be python?
[14:40] <kiko-fud> oldman, practically speaking yes, though you can get creating with the C python API and bust out of that..
[14:41] <oldman> I currently have some bash --> cmdline stuff do push changes to CMVC
[14:41] <oldman> but i'd need to learn python better to write it up as a proper plugin
[14:42] <kiko-fud> but python is so easy, and bzrlib is /really/ easy
[14:42] <oldman> :-
[14:42] <kiko-fud> oldman, so I don't think it's that hard a project
[14:42] <oldman> :)
[14:43] <kiko-fud> okay, afk for a few hours!
[14:43] <oldman> unfortunately some of the code base I work with has a silly 'top of the file' changelog
[14:43] <oldman> and that always conflicts during merge
[14:44] <kiko-afk> hmm. you might be actually able to write a plugin to handle that better
[14:44]  * kiko-afk thought such a thing actually existed
[14:46] <kiko-afk> oldman, can you give me a URL with the full email with headers of that weird email response you got?
[14:46] <oldman> kiko-afk: sure, give me 1 minute
[14:48] <kiko_> oldman, can you give me a URL with the full email with headers of that weird email response you got?
[14:48] <oldman> kiko_: sure, give me 1 minute :)
[14:48] <kiko_> thanks
[16:37] <mrooney> Is there a way to have one username forward to another?
[16:38] <mrooney> In an incredibly longstanding issue with Canonical-Sysadmins, I have to change my LP username to get an @ubuntu email forward, but if I lose the old one it will be rather invasive to my identity and projects and thus far.
[16:43] <matsubara_> why do you have to change your LP username to get an @ubuntu email?
[16:43] <matsubara_> mrooney: ^
[16:43] <mrooney> matsubara_: someone already has the forward that corresponds to my LP username
[16:44] <mrooney> and apparently there is no way for me to get a non-matching forward
[16:45] <mrooney> so the only way to get one is to change my LP username to something for which a forward doesn't exist
[16:48] <matsubara_> yeah, I think that's the only way then. It'd be quite suprising for people emailing foo@ubuntu expecting those emails to arrive to foo, when in fact they arrive to you.
[16:48] <matsubara_> what's your concern in changing your current LP username to something that the sysadmins can generate an @ubuntu email for you?
[16:49] <mrooney> Because I already have been using it for over a year on wiki pages, emails, logged chats, and released code.
[16:50] <mrooney> ...blueprints, etc.
[16:50] <mrooney> now all those links will be broken
[16:55] <matsubara_> mrooney: I see, and yeah, that's unfortunate.
[16:56] <mrooney> matsubara_: so you don't know of any way to accomplish a 'forward'?
[16:58] <matsubara_> mrooney: nope. I'm thinking of a way to help you
[16:59] <mrooney> Okay :)
[17:02] <matsubara_> mrooney: only way I can think of is for you to create a new profile. rename your existing one to something else that's an acceptable @ubuntu email, and then rename the new profile to your current profile and add a notice there pointing to your new nick.
[17:02] <matsubara_> that way you keep your karma, bug reports, etc attached to your new nickname, and people following links outside of LP will know how to reach you
[17:02] <matsubara_> after some time you can merge the two
[17:03] <mrooney> that makes sense
[17:03] <matsubara_> mrooney: and yes, that's quite a horrible workaround, but...
[17:03] <mrooney> But why make a new profile then rename it once I rename my current one? Can't I just make a new one with the old name, once I rename my current one?
[17:05] <matsubara_> mrooney: yeah, as long nobody registers it in the mean time :-)
[17:05] <mrooney> Hm, renaming works faster then creating a new account?
[17:06] <matsubara_> well, when you rename, you're freeing up the old name. if someone register a new account in the mean time and take that name, you lose it.
[17:07] <mrooney> Right
[21:46] <synic> is there a way to delete a project?
[21:46] <mwhudson> synic: ask a question at answers.launchpad.net/launchpad
[21:47] <synic> k
[22:21] <bmm> Yeah! I joined the channel to ask wether and when Jaunty would be available to build to in my PPA, but it looks like it's already there. So anyway, loving that PPA!


[21:54] <mbiebl> Keybuk: hi, remember my problem I had with bridge devices on karmic?
[21:55] <Keybuk> yes
[21:55] <Keybuk> remember that I said they don't work? :p
[21:55] <mbiebl> I thought I turn the libvirt-bin sysv init script into an upstart job
[21:55] <mbiebl> and use start on (net-device-up IFACE=br0 and net-device-up IFACE=br1 and filesystem)
[21:55] <mbiebl> but that didn't work as expected
[21:55] <Keybuk> you'd still have the fundamental problem that br0 and br1 won't come up
[21:56] <mbiebl> /etc/init/networking.conf only seemed to bring up br0
[21:56] <mbiebl> although I had both br0 and br1 configured as auto in /e/n/i
[21:57] <Keybuk> you were lucky it even did that
[21:57] <mbiebl> what happens is, that "initctl emit" in /etc/network/if-up.d/upstart is blocking
[21:57] <mbiebl> so ifup -a hangs at that point
[21:57] <Keybuk> you know how mountall carefully waits for devices, and has code to know that it needs two or more devices, and then only fscks and mounts devices when they are ready?
[21:58] <Keybuk> we need an equivalent for network devices
[21:58] <Keybuk> which we don't have
[21:58] <mbiebl> I used -n in the if-up.d hook and now it works fine for me
[21:58] <Keybuk> yes, the -n will break other things
[21:58] <Keybuk> (most particularly, the UEC images iirc)
[21:59] <Keybuk> the right fix is to get rid of "ifup -a" as a "bring up anything we forgot" tool
[21:59] <mbiebl> yeah
[22:00] <mbiebl> the -n hack is just a workaround for my particular setup


[07:30] <dholbach> good morning
[07:34] <bkerensa> dholbach: Hopefully will have a interview with Leann finished this week or next
[07:35] <dholbach> awesome!
[07:35] <dholbach> I'll get to posting a few more things soon too
[20:39] <nhandler> pleia2: I might have some time (long car ride this weekend) to work on the fridge script. Would you prefer me to work on the mailing list script or the blog script first?
[20:56] <pleia2> nhandler: mailing list first :)
[20:56] <pleia2> there aren't many interviews on other blogs really
[21:07] <nhandler> pleia2: Will do. Could you possibly email me a copy of the interview script we are currently running? I think the version I have here is an older one
[21:09] <pleia2> yep, just a moment
[21:10] <pleia2> there we go
[21:12] <nhandler> Thanks pleia2
[21:14] <pleia2> posting the info about the communite sites downtime on fridge
[21:19] <nhandler> :)


[05:14] <coz_> hello all
[05:15] <coz_> lae evening here aout 11:14 PM
[05:16] <coz_> I will try this again , any moderator responsible for art.ununtu.com..Please remove my gallery and my name from your server. i go under coz and cosimo
[05:16] <coz_> i am going online at this moment to se if it was already done so if ti has then nevermind :)
[05:18] <coz_> i see it has not been removed , so again Please remove my gallery and my name from your server thanks
[05:34] <BHSPitLappy> still going emo over ubuntu not being a nude exhibition, eh
[09:33] <TuxCrafter> hello people
[09:34] <TuxCrafter> I have a question: Why is the space above and beneath a separator in a menu different and not equal?
[09:55] <TuxCrafter> no one?


[10:19] <floam> is there any possibility of getting CONFIG_USB_SUSPEND set to y in dapper?
[10:20] <floam> linux-usb people are saying that it being off is the reason some USB devices can't turn off while plugged in.
[12:26] <CataEnry> hi :)
[03:39] <BenC> floam: cool, my kids want you for christmas
[03:40] <BenC> floam: and as for USB_SUSPEND, it's marked experimental...if it isn't, then maybe they should get that fixed :)
[03:40] <fabbione> hey Ben
[03:40] <BenC> hey fabio
[03:41] <fabbione> BenC: i just tested hppa stuff
[03:41] <fabbione> .12-mckinley is no good
[03:41] <fabbione> sorry i mean ia64
[03:42] <BenC> you have a mckinley?
[03:42] <fabbione> i am gonna have to play with it to see what's wrong
[03:42] <fabbione> apparently i do
[03:42] <fabbione> at least the installer detect it as such
[03:42] <BenC> sweet, mines itanium, so I know that works
[03:42] <BenC> cat /proc/cpuinfo just to be sure
[03:42] <fabbione> it's turned off now.. let me see if i have it in the scrollback
[03:43] <fabbione> fabbione processor  : 0
[03:43] <fabbione> fabbione vendor     : GenuineIntel
[03:43] <fabbione> fabbione arch       : IA-64
[03:43] <fabbione> fabbione family     : Itanium 2
[03:43] <fabbione> fabbione model      : 0
[03:43] <fabbione> fabbione revision   : 7
[03:43] <fabbione> fabbione archrev    : 0
[03:43] <fabbione> fabbione features   : branchlong
[03:43] <fabbione> fabbione cpu number : 0
[03:43] <fabbione> fabbione cpu regs   : 4
[03:43] <fabbione> fabbione cpu MHz    : 900.000000
[03:43] <fabbione> fabbione itc MHz    : 900.000000
[03:43] <fabbione> fabbione BogoMIPS   : 1347.58
[03:43] <fabbione> fabbione siblings   : 1
[03:43] <BenC> I2 I guess is mckinley
[03:43] <fabbione> the error anyway was related to SCSI missing symbols
[03:44] <fabbione> so it might be either a bad initrd or a broken kernel
[03:44] <BenC> hmm, I should be able to see that for myself
[03:44] <fabbione> i will look at it one of the next days
[03:44] <fabbione> i didn't really have much time to debug, because i have only one console cable to share with 4 machines
[03:44] <fabbione> and sparc doesn't like to stay without console
[03:44] <BenC> if it's missing symbols, it's not because of t he kernel
[03:45] <fabbione> i plan to go out and buy them tomorrow
[03:45] <BenC> the builds show no missing symbols
[03:45] <fabbione> yeah i think it's a missing module in the initrd
[03:45] <fabbione> but that was .12
[03:45] <fabbione> i have to check .15 too
[03:45] <fabbione> http://www.fabbione.net/new_office.jpg
[03:45] <fabbione> check out the local datacenter :)
[03:46] <fabbione> the sparcbuildd is under the cisco switch ;)
[03:46] <Mithrandir> you need to rotate the image
[03:46] <fabbione> http://www.fabbione.net/new_ws.jpg
[03:46] <fabbione> this is my ws :)
[03:46] <fabbione> Mithrandir: i just took a pic on the fly
[03:46] <fabbione> -ENOCARE :)
[03:47] <fabbione> there is a black tower on the left, but you can barely notice
[03:48] <fabbione> see now i should be maintaining the kernel.. now that i can test on arch: all
[03:49] <fabbione> not when i only had i386
[04:11] <zul> heylo
[04:48] <BenC> fabbione: still getting bug reports that claim broken 2.6.12-10, but work with 2.6.12-9...one was a amd64 bug about GPF's at random, another is hibernation randomly broken
[04:48] <BenC> I think I know the patch that is probably the cause
[04:48] <BenC> I think it's the procfs patch
[04:49] <fabbione> hmmmmm
[04:49] <fabbione> for now just reassign the bugs to me
[04:49] <fabbione> i am going to do the pending security stuff this week
[04:49] <fabbione> and i can ask people to pre-test a kernel with reverted proc-fs
[04:51] <BenC> ok
[04:57] <BenC> yeah, the procfs one seems like the only one that could cause random issues (and lockups)
[05:14] <zul> does anyone have a ccis raid card with dapper?
[05:18] <zul> i guess not
[06:58] <jbailey> zul: lamont might have access to one.  They're common in HP gear.
[06:59] <zul> hmm...ill ask him then
[07:38] <BenC> avahi+daapd == music heaven
[08:03] <floam> BenC: want me for christmas?
[08:03] <floam> I'm playful
[08:13] <BenC> floam: hehe
[08:13] <BenC> I didn't even know what floam was until my kids asked for it
[08:14] <floam> heh.
[08:15] <floam> I had this name before that goo stuff came out
[08:15] <floam> I should sue 'em.
[08:17] <floam> BenC: I didn't know what floam was until I got a letter from some guy on behalf on Nickelodian asking me if I want to sell floam on my website and make money (or hand my website over to them)
[08:17] <floam> I had the #1 spot on a google search for "floam" at the time
[08:17] <BenC> did you make any money for it?
[08:17] <floam> I said no, and now it seems like they've gone nuts with search engine optimization and are above me now
[08:17] <floam> BenC: nah, I didn't do it
[08:18] <floam> I think their first email I have somewhere...
[08:18] <floam> http://floam.sh.nu/files/misc/floam
[08:19] <floam> it seemed like a ripoff, the letter looks mostly canned
[08:22] <BenC> yeah, they didn't really make that look legit enough
[08:23] <floam> BenC: so Ubuntu's policy is nothing EXPERIMENTAL?
[08:23] <floam> maybe I'll try to get them to change that flag for 2.6.15, the feature has been there for 9 releases or so
[08:24] <floam> with nothing bad reported that I've seen on lkml at lease
[08:24] <BenC> well, we have some stuff from exp, but I personally I don't like enabling new things from exp without good cause
[08:25] <floam> Idealy I was hoping I could get that enabled, and then I could make a patch to eject that would use it
[08:26] <floam> so that when people unmount volumes through gnome the device would actually do what it's supposed to do (like in windows)
[08:28] <floam> in windows, if you've got a USB device plugged in, before unplugging it you go to some "safely remove hardware" dialog and hit a button, which not only unmounts it but suspends it
[08:29] <floam> some devices wait for the suspend signal before believing that they are "safe to disconnect"
[08:30] <BenC> let me talk to gregkh and see if he thinks its safe enough
[08:30] <BenC> since I don't personally know
[08:32] <floam> he would, he added the feature I think
[08:32] <floam> BenC: thanks :)
[08:33] <BenC> but if he thought it was safe, he wouldn't mark it exp :)
[08:34] <floam> maaaaybe
[08:34] <floam> there are other exp things that are generally agreed upon to be stable
[08:35] <floam> more of a "this is new" flag than "this is broke" sometimes
[10:42] <dilinger> wow
[10:43] <dilinger> permissoins on my breezy box are severly hosed since upgrading to dapper's udev
[10:55] <makx> hehe
[10:55] <makx> may $deity with you dilinger
[11:19] <HrdwrBoB> may you be touched by his noodly appendage
[11:31] <fs> dapper?
[11:31] <fs> ECHAN =)


[09:45] <davlefou> Bonjour,
[12:38] <elacheche> Thisi s awesome! ping nzoueidi praisethemoon volkovmqx https://www.youtube.com/watch?v=1qlLUf7KtAw
[12:38] <u-la-la> [ Container Hacks and Fun Images - YouTube ] - https://www.youtube.com
[12:38] <praisethemoon> thanks for sharing elacheche! i'll check it once i'm home :)
[12:56] <nzoueidi> This is awesome elacheche!! But really I hate how they came to this stage where they containerized _almost_ everything
[12:57] <elacheche> :D
[13:59] <volkovmqx> i can containerize my life i guess now :D
[15:18] <elacheche> x)


[02:20] <DHR> I think that it is really important to build a 32-bit UEFI installer.  There are a tonne of new 32-bit only tablets and netbooks that require UEFI.  It is a shame that no mainstream Linux distro can be installed on them
[02:21] <DHR> Here's an unofficial Fedora for at least the Asus T100 and the Dell Venue 8 Pro.
[02:21] <DHR> What prompts me to come here is http://summit.ubuntu.com/uos-1411/meeting/22353/when-should-we-stop-making-32-bit-images/
[02:21] <DHR> Is there a better place for me to raise this point?
[15:50] <DHR> Is this the right place to advocate for a 32-bit UEFI installation method?
[16:09] <xnox> DHR: sure.
[16:09] <xnox> DHR: most of those are 64-bit CPUs though, thus what we really need/want is to enable dual-installation of 32-bit UEFI and 64-bit UEFI on the installation media
[16:09] <xnox> and correctly detecting that uefi-arch.
[16:10] <xnox> however most of the new generation stuff is actually using 64-bit uefi these days.
[16:10] <xnox> "There are a tonne of new 32-bit" - you mean like with new atom SoCs? e.g. latest atom SoCs should be using 64-bit uefi in fact.
[16:12] <cjwatson> We already know about the 32-bit UEFI need, thanks
[16:12] <cjwatson> The advocacy has been heard and the very meeting that you linked to above included some ideas on progressing things
[16:13]  * xnox will rewatch that video
[16:13] <xnox> my understanding is that 32-bit uefi is on the decline after a short usage on certain systems. I might be wrong though.
[16:15] <DHR> I know as a consumer that there are a whole raft of new 32-bit uefi systems, mostly tablets.  It might be a passing fad, but it is really strong right now.
[16:16] <DHR> I fear that the limitation is intentional (by Intel and possibly Microsoft) and hence is not going to end with a technical solution.
[16:17] <DHR> Is it true that a 64-bit kernel cannot currently make UEFI calls (whatever that might be?  ACPI??) to a 32-bit UEFI firmware?
[16:18] <cjwatson> that's my understanding
[16:18] <cjwatson> not ACPI, UEFI Runtime Services
[16:18] <cjwatson> ICBW, that's why I flagged it as something that needed to be checked when I mentioned it in the meeting
[16:19] <DHR> Ahh.  I'll google that to understand.
[16:19] <cjwatson> if I am wrong it simplifies things :)
[16:20] <DHR> Has Intel released 64-bit UEFI firmware that does the magic power management on the atom SoCs?  It's been a year or so waiting, I think
[16:20] <cjwatson> things may have changed, e.g. https://lkml.org/lkml/2014/3/4/242
[16:20] <cjwatson> I really think that is not likely to be an installer area of expertise
[16:21] <cjwatson> #ubuntu-kernel might know better
[16:35] <xnox> DHR: cjwatson: enabling CONFIG_EFI_MIXED should be sufficient, however it is currently known to me that things do not end up working on fedora/ubuntu with such kernels(64-bit)/firmware(32-bit)/bootloader(32bit efi grub)
[16:35] <xnox> which is being troubleshooted, i can followup on the latest state of affairs around this internally here.
[16:53] <DHR> (sorry, was away).  xnox: that would be great, I think.    They are limited in RAM by Intel (market segmentation game?  surely no good technical reason)
[16:55] <DHR> they have limited "disk" too.
[16:56] <DHR> typical right now: 2G RAM, 32G eMMC.  A flood of 1G / 16G tablets coming with Win 8.1
[16:57] <DHR> Mainstream distros seem to be sitting on the sideline.
[16:58] <DHR> I'd really love Linux to be the answer for some of those who discover how bad Win8.1 is on 1/16 tabs.  Wishful thinking?
[16:59] <DHR> I naively don't understand why a simple 32-bit-only UEFI install isn't a perfectly fine placeholder until some kind of mixed support can be engineered.
[17:02] <DHR> cjwatson: my understanding is: a pure 32-bit Ubuntu exists (obviously), but no UEFI installer for it.  I naively would have thought that creating a new .iso with a 32-bit UEFI installer ought to be just turning a crank.
[17:02] <DHR> That's why I thought that this might be an installer questsion.
[17:03] <cjwatson> I was replying specifically to your question about power management.
[17:04] <cjwatson> Adding an additional image is technically not that hard, but increases our QA load non-trivially, which is a very scarce resource.  So we're not going to do that.
[17:05] <cjwatson> We would much prefer to add the capability to one of our existing images.  The problem is that historically attempting to do this to the i386 image broke other hardware.  As I said in the meeting, it's possible that the trade-offs are different now.
[17:06] <DHR> cjwatson: thanks for the LKML link.  With interruptions, I just got to it now.  It adds a piece to the puzzle.  I wonder why it isn't working on fedora/ubuntu.
[17:06] <cjwatson> And if the hardware in question in fact has long mode (i.e. a 64-bit CPU) despite having 32-bit UEFI, then that potentially simplifies the problem considerably.  We were not clear in the meeting on whether this is in fact true.
[17:06] <cjwatson> It may be working.
[17:06] <cjwatson> I can't claim authoritatively that it doesn't.
[17:07] <DHR> the hardware I know about is advertised has being 64-bit.
[17:07] <cjwatson> In that case the next step that we arrived at in the meeting will likely work.
[17:08] <cjwatson> That is, add grub-efi-ia32 to the EFI System Partition on the amd64 images.
[17:08] <cjwatson> Although that only helps for booting the images themselves; somebody is also going to need to figure out how to detect this situation at run-time and install grub-efi-ia32 on the target system as well.
[17:08] <DHR> disk space is at a premium on these systems currently.  Isn't a mixed 32/64 system significantly fatter than a pure 32-bit system?
[17:09] <cjwatson> It wouldn't be particularly mixed.
[17:09] <cjwatson> 32-bit boot loader, 64-bit everything else.
[17:09] <DHR> As I said, 16G and 32G are the normal size.
[17:09] <cjwatson> That hardly seems likely to be problematic.
[17:10] <cjwatson> If we were talking about 4G or something then that might be more of an issue.
[17:11] <cjwatson> We appear to have CONFIG_EFI_MIXED=y now.
[17:11] <cjwatson> But I'd defer to xnox's internal knowledge.
[17:13] <cjwatson> I think infinity was going to see if somebody on the development team could expense a suitable system and make it work.
[17:13] <DHR> If that approach can work, is there a way to get a generally usable experimental image out very soon?  About detection: dunno, worst case, let the user tick a box (experimental!)
[17:13] <cjwatson> No
[17:13] <cjwatson> (to "tick a box")
[17:13] <cjwatson> I'm quite sure there's a better option than that :-)
[17:14] <cjwatson> We're not adding new UI, because, bear in mind, that would logically have to be shown to everyone installing on any UEFI system, i.e. most users, and we're not doing that to people installing vivid.
[17:14] <DHR> They are REALLY cheap.  I'd donate one if it would get things moving.  For example, $200 buys you an Asus x205.  $100 buys you one of several tablets (I can name names if that matters).
[17:15] <cjwatson> I can't speak for timelines because I'm moving out of mainline Ubuntu development at the end of the year.
[17:15] <cjwatson> Hence redirecting to infinity ...
[17:15] <DHR> Oh, but I'm an impatient user :-)  Doing it before the end of the year is important :-)
[17:17] <ogra_> send a patch then :)
[17:17] <ogra_> (or multiple)
[17:17] <cjwatson> ogra_: I don't think that's a helpful answer.
[17:18] <cjwatson> Please don't answer if that's all you're going to say.
[17:18]  * ogra_ shuts up
[17:18] <cjwatson> Because this is too complicated for most people to know where to start ...
[17:19] <cjwatson> Information on how to detect the UEFI machine type (ia32 or x86-64) at run-time would be genuinely helpful though.
[17:19] <cjwatson> https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface says that "ioreg -l -p IODeviceTree | grep firmware-abi
[17:19] <cjwatson> " works on Mac OS
[17:19] <cjwatson> And gives a non-Mac answer which is sadly inapplicable following CONFIG_EFI_MIXED
[17:20] <DHR> cynic: every time you ask a PC about whether it conforms to some standard, it lies.
[17:20] <cjwatson> infinity: http://kernelnewbies.org/Linux_3.15#head-e6cf8178e4d5eafc23b0abda81974d2b71ffecf4
[17:21] <cjwatson> Hmm, need to fix grub2 to make linuxefi (for SB) build on i386_efi too then
[17:21] <DHR> The base line assumption: if you were installed (or perhaps booted) by a 32-bit UEFI, you are on a machine in which you should use 32-bit UEFI runtime.
[17:21] <cjwatson> DHR: I'm asking how to discover the former from userspace
[17:26] <DHR> Maybe that needs to be part of what CONFIG_EFI_MIXED adds to the mix.
[17:26] <cjwatson> There may well be information there already, but I don't know it.
[17:28] <cjwatson> But I'm suggesting that if somebody wants to help move this forward more quickly, then that's a critical-path thing we need to know that could be investigated independently.
[17:29] <DHR> OK.  Thanks for the suggestion.  What kind of interface would be good for userland?  Something in /proc or /sys?
[17:29] <cjwatson> I'd expect something in /sys
[17:30] <DHR> yeah, /proc shows how long ago I did any kernel hacking.
[17:31] <cjwatson> I think once we have that information, the steps are to make grub-installer use it, to make grub2 build linuxefi on i386 as well, to build 32-bit shim binaries (I may not like Secure Boot, but we probably need to do it here), and to add all the relevant things to our amd64 images
[17:34] <DHR> thanks for taking the time!  I'll see if I can find a hook in the patch you pointed me at.  I guess that's a bit stale now, but it's a starting point.
[17:35] <DHR> How can I best return the results (if any)?  This channel?
[17:35] <cjwatson> DHR: The kernelnewbies link above has links to the commits that actually landed, but they're probably best used as starting points for grepping current kernel source.
[17:35] <cjwatson> DHR: Probably as good as any, yes.
[17:35] <cjwatson> Thanks for looking.
[17:38] <DHR> thinking out loud: something needs to record whether the efi64_thunk needs to be used.  So the info must be represented in the kernel.
[17:39] <infinity> cjwatson: Appreciate the redirect, but on VAC until next week. :)
[17:44] <cjwatson> infinity: Oh good point.  Feel free to park it until then
[17:49] <DHR> type efi_system_table_t has a member "is64".  Seems to be  a start.


[01:49] <robert_ancell_> duflu, did you see the resizing issues that Chris and bregma have been getting?
[01:50] <duflu> robert_ancell_: I know there are still resizing bugs and it's a bit hackish. But I'm not aware of the conversation in question
[01:51] <duflu> robert_ancell_: Oh I see. Yes I know what that is
[01:52] <robert_ancell_> duflu, bug 1501039
[01:52] <ubot5`> bug 1501039 in xorg-server (Ubuntu) "Xmir from overlay PPA no longer tells client about resize events in non-rootless" [Undecided,New] https://launchpad.net/bugs/1501039
[01:53] <duflu> robert_ancell_: Yeah I half expected that. Although non-rootless is almost dead I know what it is
[01:53] <robert_ancell_> Non-rootless should not be dead...
[03:21] <duflu> Woo, Mir 0.16 in vivid+overlay too
[08:39] <duflu> anpok_: Do we ever bypass android InputReceiver?
[09:14] <anpok_> duflu: not soon
[09:15] <anpok_> hm i think replacing it isnt complex at all... apart from the ugly resampling bits
[09:16] <anpok_> i try to remove the input reading bits today
[09:16] <anpok_> I still havent looked how good or bad the actual encoding is.. but the times that we measure dont look problematic..
[09:19] <duflu> anpok_: I'd love to be rid of the resampling bits but even today finding they're very beneficial
[09:20] <anpok_> well i meant replacing them with something easier to consume
[09:41] <tsdgeos> alan_g: so it's nullptr what mir expects there?
[09:41] <tsdgeos> makes much more sense :D
[09:44] <alan_g> tsdgeos: '0' like 0 and nullptr is a null pointer constant
[09:44] <alan_g> But the code was confusing
[09:44] <tsdgeos> agreed, i wasn't thinking and just did a "let's fix the code to compile"
[10:08] <alan_g> duflu: did you get a chance to try lp:~alan-griffiths/mir/fix-1308133 with your xmir WIP?
[10:09] <duflu> alan_g: No, sorry. Thought about it then forgot
[10:09] <duflu> And was busy anyway
[10:12] <alan_g> np


[12:29] <czajkowski> tdr112: airurando http://skycon.skynet.ie/2012/timetable.php
[12:30] <czajkowski> timetable is up
[12:36] <airurando> czajkowski: nice one, looking forward to it.
[16:37] <airurando> ebel: slashtom: decided on go/no go for Skycon'12 yet?
[16:41] <airurando> whoops that should have been slashbel
[19:38] <airurando> ebel: slashbel: decided on go/no go for Skycon'12 yet?
[19:49] <zmoylan> airurando: might be quicker to tweet them
[20:00] <airurando> zmoylan thanks but no rush, just curious.
[20:00] <zmoylan> tickety boo
[20:07] <czajkowski> aloha
[20:07] <czajkowski> zmoylan: you coming down
[20:08] <czajkowski> hows' patrick you seen him lately
[20:08] <zmoylan> my mobility is still an issue so unfortunately not.
[20:09] <zmoylan> haven't seen patrick in ages.  we keep meaning to meetup but just keep miss timing our meetups.
[20:16] <czajkowski> zmoylan: does he know about skycon ?
[20:16] <zmoylan> he's fairly plugged in.  will poke him tomorrow and see.
[20:38] <Victor9098> Hello room!
[20:38] <czajkowski> Victor9098: aloha
[20:39] <Victor9098> :-)
[20:41] <czajkowski> Victor9098: where are you based?
[20:41] <ebel> airurando: yeah I saw you asking earlier. i dunno, prob. not, only started paying attention to things in last few days
[20:41] <Victor9098> Enfield (Meath)
[20:42] <czajkowski> Victor9098: you coming to skycon weekend after next in limerick
[20:43] <Victor9098> czajkowski: Originally I was hoping I would, but I do not think so now. Down to funds more then anything else
[20:48] <czajkowski> <-- dinner
[20:48] <czajkowski> bbiab
[20:51] <Victor9098> Anyone come across this 'garda siochana' ransomware? Friend gave me a call this afternoon saying their PC had a big garda notification on it, popped over to have a look and its a ransomware that has been doing the rounds. Using Kaspersky to try to fix now
[20:52] <ebel> Contact the guards? they might not be keen on someone impersonating them
[20:52] <Victor9098> Yes, done that. Been in touch with Phoenix park. they said not to provide any payment details that it asks for
[20:53] <Victor9098> They said they have been aware of it for a few months, even Irish versions of it out there
[20:55] <Victor9098> Have a bad feeling Kaspersky has frozen...clock stuck at 9.26 :-D
[21:25] <airurando> ebel: no prob. Would have been nice to meet up again.  Hopefully soon!
[21:26] <airurando> hi czajkowski and Victor9098
[21:27] <Victor9098> Howdy airurando
[21:31] <airurando> pity you can't make skycon Victor9098
[21:31] <airurando> had hoped to meet you there
[21:38] <Victor9098> I was looking forward to it, but do not think its going to happen now
[22:12] <airurando> nn


[04:31] <Unit193> https://lists.ubuntu.com/archives/community-announce/2013-August/000012.html meh.
[18:38] <wrst> Unit193: just saw the link... what does all that mean?
[18:39] <Unit193> Kind of looked easier, but not sure.
[18:42] <wrst> sounds to me like the other system wasn't working at all