[12:03] <mr-russ> bug day... oh exicitng.
[12:03] <Nafallo> baah
[12:03] <Kyral> mmm
[12:03] <Kyral> chinese buffet
[12:03] <Nafallo> good thing I have to be away 8:15-15:45 tomorrow :-P
[12:04] <Nafallo> (traveltime included)
[12:04] <mr-russ> do devs really hate bugday?
[12:04] <ajmitch> no
[12:04] <ajmitch> we loves it
[12:04] <tseng> we do?
[12:04] <ajmitch> sure
[12:05] <ajmitch> don't you love all those beagle bugs?
[12:05] <tseng> nope.
[12:05] <tseng> i like them even less when i dont have much chance of fixing
[12:05] <tseng> like evo-sharp not supporting eds 1.5
[12:06] <tseng> it builds fine, it just explodes at runtime
[12:06] <tseng> haha there is a huge thread on mono on ubuntu-dev
[12:07] <tseng> funny
[12:07] <Riddell> aren't bug days on thursdays?
[12:08] <psusi> why is there no man page for ulimit?
[12:08] <psusi> what was the flag to enable core dumps?
[12:08] <ajmitch> tseng: yes, why don't we have beagle in the desktop seed for dapper then?
[12:08] <ajmitch> support 0.1.4 for the next 3 years
[12:09] <tseng> yes brilliant
[12:09] <tseng> we wanted to build stuff with libbeagle
[12:09] <tseng> and leave the daemon in universe
[12:09] <ajmitch> hm
[12:09] <chninkel> psusi: ulimit is a bash builtin I think
[12:09] <ajmitch> amazing questions in #mono
[12:10] <chninkel> psusi: you'll find it with man bash
[12:10] <psusi> ohh
[12:11] <psusi> there we go... ulimit -c
[12:11] <ajmitch> I wonder if the debian mirror I'm using is only half-updated
[12:12] <cyberix> http://www.inari.fi/kunta/sosterv/itsehoito/31.unettomuus.gif
[12:12] <cyberix> This is a brilliant picture
[12:12] <ajmitch> please don't randomly spam urls in channel
[12:13] <cyberix> Well, Ubuntu is UNIX based, and I've started to feel a sosial relation to this channel.
[12:14] <cyberix> But I do admit that the image is not very important for universe to expand
[12:15] <tseng> https://launchpad.net/malone/bugs/3768
[12:15] <tseng> ajmitch: is this a 500 for you?
[12:15] <Ubugtu> Error: Could not parse data returned by Malone: Connection to Malone bugtracker failed: The read operation timed out
[12:15] <tseng> ajmitch: ( i cant believe we are pretending to switch to malone again )
[12:15] <ajmitch> I think it's the DB server that's down
[12:15] <tseng> i give it a week
[12:16] <mr-russ> a week, what sort of project is this!
[12:16] <ajmitch> ETA was 'at least 5-10 minutes' about 15 minutes ago
[12:16] <ajmitch> mr-russ: excuse me?
[12:17] <mr-russ> you get eta's cool.
[12:17] <Nafallo> elmo is on it :-)
[12:18] <thierry_> am I the only one that has problem getting on the ubuntu wiki?
[12:18] <ajmitch> responses like 'what sort of project is this?' can really be taken the wrong way
[12:18] <ajmitch> thierry_: see above
[12:18] <Nafallo> thierry_: the DB server is down
[12:18] <raphink> hello motus :)
[12:20] <LaserJock> hi raphink
[12:20] <raphink> hi LaserJock
[12:20] <raphink> :)
[12:21] <raphink> how are you doing ?
[12:22] <LaserJock> good, busy
[12:23] <LaserJock> raphink: I am trying to get my first package into Debian and I have been working on some MOTUScience stuff and I need to work on the Ubuntu Packaging Guide a bit too
[12:23] <Nafallo> woohoo! xserver-xorg-input-synaptics builds on amd64 :-)
[12:23] <raphink> ok
[12:24] <raphink> I'll think I'll go to bed pretty soon :)
[12:24] <raphink> full day ;)
[12:31] <ajmitch_> joy
[12:32] <lifeless> lp is back
[12:33] <\sh> lifeless: what is changed?
[12:34] <Nafallo> \sh: the database lives again ;-)
[12:34] <\sh> oh a crash?
[12:35] <lifeless> hardware issue - rectified.
[12:35] <Nafallo> kewl :-)
[12:36] <LaserJock> sweet LP works again
[12:46] <psusi> hrm... the bins in this package are being built with -g, and I set the -k flag to dh_strip, but the package still doesn't contain the debug symbol files... is there another step needed to get them to be included?
[12:48] <womble> psusi: Use --dbg-package instead.  Much easier.
[12:49] <ajmitch_> morning womble
[12:49] <womble> Hey ajmitch_
[12:49] <psusi> womble: how do you use that?  don't you have to specify another binary target in the control file and give the name of that target to that option?
[12:49] <psusi> sounded like -k would just add the symbol files to the main package when installed
[12:49] <womble> psusi: See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315240 for an example of a patch to add a -dbg package
[12:49] <Ubugtu> Debian bug 315240: "build a -dbg package" Package: libneon24, Version: 0.24.7.dfsg-2., Severity: wishlist, Maintainer: Laszlo Boszormenyi  http://bugs.debian.org/315240
[12:50] <psusi> ty
[12:50] <womble> Holy crap, I can't believe other people are using that bug as an example now  <grin>
[12:50] <womble> psusi: Is -k not putting the symbols in /usr/lib/debug/wherever?
[12:52] <psusi> looks like a very nice example
[12:52] <psusi> and no, they aren't appearing in the package when I build it with pbuilder and dpkg -c it
[12:53] <womble> psusi: fakeroot debian/rules binary in your source tree, and have a look in debian/$PKG/usr/lib/debug
[12:53] <womble> and debian/tmp/usr/lib/debug
[12:53] <womble> It's entirely possible that dh_strip is making the symbol files, but your build process isn't including the files in the final built package
[12:54] <psusi> womble: that's what I'm thinking... what else needs to be in the build process to include them in the built package?
[12:54] <womble> a dh_install or dh_movefiles to make sure they end up in debian/$PKG/usr/lib/debug/foo/bar/baz
[12:54] <womble> This is the reason why we all use --dbg-package
[12:55] <psusi> any special flags to those needed to get them to move the debug syms?
[12:55] <womble> As the manpage says about -k: "--dbg-package is
[12:55] <womble>  easier to use than this option, but this option is more flexible."
[12:59] <psusi> isn't sig #32 used for posix aio?
[01:10] <psusi> womble: damnit... the symbols aren't in the -dbg package either
[01:10] <womble> psusi: Where are they?  stuck in debian/tmp somewhere?
[01:11] <psusi> I dunno... I usually build with pbuilder... tyring the debian/rules binary ow
[01:11] <psusi> now
[01:14] <womble> I got hooked on pbuilder for a while, and had lots of the same sorts of problems -- "where the hell are my files?" so I've re-learnt the value of debian/rules binary (or debian/rules install in some cases, even)
[01:14] <womble> Still rebuild using pbuilder for uploads, though.
[01:14] <womble> And build-dep spec testing
[01:16] <psusi> aye
[01:18] <Kyral> whee...my first CDBS package
[01:19] <raphink> reverse compatibility with ifup/ifdown would have been a nice feature
[01:19] <raphink> :s
[01:20] <psusi> is there an easy way to create a temp file or other area you can store output in a bash script?  I've got a rather verbose script I'd like to modify so it stores teh output and discards it if no errors happened
[01:20] <psusi> but dump it to stdout if something goes wrong
[01:22] <psusi> womble: no debug syms in debian/$pkg
[01:23] <womble> psusi: anything laying around in debian/tmp/usr/lib/debug?
[01:23] <psusi> there is no debian/tmp
[01:23] <womble> or in debian/$pkg-dbg?
[01:23] <womble> Perhaps something is stripping your binaries before dh_strip gets at them?
[01:24] <psusi> unless it's some other dh_ I don't see what... all the gcc lines have the -g
[01:24] <womble> You can set CFLAGS=-g, but if the Makefile has a strip target in it's install or something, you're still toast
[01:25] <psusi> how about dh_clean?
[01:26] <psusi> don't see any strip commands
[01:26] <womble> psusi: dh_clean isn't related
[01:26] <psusi> last g++ -o -g is followed by the dh_ stuff
[01:27] <womble> Comment out the dh_strip call in rules, rerun debian/rules binary, and see if the binary in the final location is stripped or not with file
[01:27] <psusi> ok
[01:28] <psusi> does dh_installdirs need any arguments for the syms?
[01:29] <psusi> son of a bitch... they are stripped
[01:29] <psusi> unless... it didn't appear to rebuild them when I re ran rules binary
[01:29] <psusi> just did the dh stuff over
[01:30] <Kyral> hmm....
[01:30] <Kyral> which section...
[01:30] <psusi> eh?
[01:30] <Kyral> this
[01:30] <Kyral> http://www.gnomefiles.org/app.php?soft_id=1235
[01:34] <womble> psusi: You didn't run debian/rules clean before rebuilding?
[01:34] <psusi> no.. just did that... wish I could just rebuild the binaries though... the objects all had syms
[01:34] <psusi> waiting for the full rebuild now
[01:35] <psusi> where exactly does dh_strip put the symbols?  is another step required to put them in the installed dir?
[01:44] <Kyral> whats the package for pyGTK 2.6?
[01:45] <crimsun> I don't know of one for 2.6, but there's python2.4-gtk2, which is for 2.8.2
[01:45] <Kyral> yah
[01:45] <Kyral> I meant >= 2.6
[01:46] <Kyral> ...*STAB!&
[01:46] <Kyral> I put python2.4-gtk as a build dep are you blind...grr
[01:47] <Kyral> its failing because it says it needs PyGTK 2.6
[01:47] <Kyral> or greater
[01:48] <crimsun> you b-d on the -dev, package.
[01:48] <crimsun> python-gtk2-dev
[01:48] <ajmitch> crimsun: is that really needed?
[01:49] <crimsun> I don't know what prog he's trying, so I don't know :)
[01:49] <ajmitch> I guess it could have the .pc file..
[01:50] <ajmitch> /usr/lib/pkgconfig/pygtk-2.0.pc
[01:50] <ajmitch> might be the only thing worth using
[01:51] <ajmitch> hm, probably not
[01:51] <Kyral> wait...in Depends if its Python don't I need to include soething else?
[01:51] <ajmitch> that looks like something for linking with pygtk headers
[01:51] <ajmitch> Kyral: depends on how badly you're mangling this
[01:51] <Kyral> I'm not
[01:52] <ajmitch> sure
[01:52] <Kyral> I just hit it with dh_make as cdbs and used the python-distutils thing
[01:54] <Kyral> BTW its this
[01:54] <Kyral> http://www.gnomefiles.org/app.php?soft_id=1235
[01:57] <cyberix> Kyral: I wonder how you pipe commands with such.
[01:58] <Kyral> huh?
[01:59] <cyberix> ls | grep `echo music`
[01:59] <Kyral> such what?
[02:00] <cyberix> How do you tell everygui to do that
[02:00] <cyberix> :-)
[02:00] <Kyral> I dunno
[02:00] <Kyral> I can't even get the damn thing to build
[02:00] <cyberix> Oh
[02:00] <Kyral> Today is the first I saw of it lol
[02:00] <cyberix> But the idea is good
[02:00] <Kyral> I loaded my Google Home with the GnomeFiles.org RSS feed and it looked interesting
[02:01] <Kyral> I'm wondering why it doesn't like me
[02:01] <cyberix> Enought preconfiguration for commands and it could be really usefull
[02:01] <Kyral> yah
[02:03] <Kyral> if it would build...
[02:10] <Kyral> *Stab*
[02:10] <Kyral> should I just pastebin the control file?
[02:12] <ajmitch> or you could get it working ;)
[02:12] <Kyral> I would if I knew how
[02:12] <Kyral> I have the right deps
[02:12] <Kyral> that I can see
[03:16] <thierry_> what is the package for  X11 headers files ?
[03:21] <crimsun> anything more specific?
[03:21] <crimsun> there are a slew of them...
[03:22] <crimsun> (e.g., x11proto*)
[03:28] <thierry_> crimsun : well that's what the speeX apps says it's needed... http://www.gnu.org/software/speedx/speedx.html
[03:29] <thierry_> speedX*
[03:30] <hub> anyone packaging gnash?
[03:30] <bmonty> hub: does it make sense to package gnash?
[03:30] <bmonty> according to their website it is still in development
[03:31] <hub> does it make sense to not package it?
[03:31] <crimsun> it certainly doesn't make any sense for Dapper.
[03:31] <crimsun> Perhaps feasible for Dapper+1, though.
[03:31] <bmonty> I don't think it is ready to be packaged
[03:32] <hub> but I was just asking
[03:32] <hub> because dholbach bet me for two packages recently
[03:32] <hub> so I was wondering if I should
[03:32] <bmonty> hub: in my opinion, I would say no
[03:32] <bmonty> but that is my opinion
[03:33] <crimsun> (and I've already stated my stance)
[03:34] <\sh> hey zakame
[03:35] <thierry_> if a app is free but not opensource, is it packageable?
[03:35] <crimsun> generally, no.
[03:35] <thierry_> k
[03:36] <crimsun> and if it's not open-source it really isn't DFSG-free at all, which precludes it being in universe at all.
[03:38] <thierry_> k
[03:39] <zakame> gaah, non-free
[03:46] <hub> multiverse?
[03:48] <zakame> hm I do believe we try to minimize uploads to multiverse, right?
[03:48] <crimsun> it might be able to go into multiverse depending on the licensing.
[03:50] <zakame> ah
[03:52] <poningru> thierry_: what do you mean free but not open source?
[03:52] <poningru> thats not possible
[03:52] <poningru> if its free by definition it has to be open source
[03:52] <zakame> poningru : free as in free beer
[03:52] <poningru> oh
[03:52] <poningru> OH
[03:53] <poningru> my mistake
[03:54] <\sh> zakame: what about njam...there is one guy who wanted to package it
[03:55] <zakame> \sh : it's already in Debian's NEW queue
[03:56] <\sh> zakame: i didn't see it in incoming :)
[03:56] <thierry_> crimsun : Can I package if the compilation is only made with gcc and a .c file
[03:57] <zakame> \sh : http://ftp-master.debian.org/new.html
[03:57] <crimsun> thierry_: sure, you can package it for yourself. Whether it can be distributed in multiverse is another decision altogether. I will cite precedence, however, that more than likely it's acceptable: see eagle.
[03:57] <crimsun> thierry_: it really depends on the license.
[03:57] <\sh> zakame: oh well..not build right now..do you actually know if he took our package?
[03:58] <zakame> \sh : if nothing happens by next week I'll ping him and ask politely ;)
[03:58] <minghua> \sh: since you've been uploading qt3...  do you know what those "src/.moc/debug-shared-mt/*.moc" files in qt3's .diff.gz are for?
[03:59] <\sh> minghua: yes...shit from me....I'm cleaning it up somehow...
[03:59] <zakame> bbl
[04:00] <minghua> zakame: any words on the octave2.1 sync?  maybe time to ask again? ;-)
[04:00] <minghua> crap, I missed zakame
[04:00] <zakame> minghua : none yet
[04:00] <crimsun> minghua: I asked yesterday
[04:00] <minghua> \sh: thanks :-)  I was just reading the diff (curious about the immodule patch) and found that out accidentally
[04:01] <zakame> gaah, elmo's gonna be mad
[04:01] <crimsun> minghua: I presume it's in elmo's queue; otherwise I'll refresh when I send him my next batch of syncs
[04:01] <zakame> anyhow, bbl :)
[04:01] <crimsun> 8 days til UVF.
[04:02] <minghua> crimsun: thanks, I hope one inquiry per week won't make elmo mad :-)
[04:07] <martinex> hello - anyone?
[04:09] <crimsun> martinex: hi
[04:10] <martinex> crimsun, hi... I got a problem
[04:10] <martinex> crimsun, and sorry to bother 'cause it should be #ubuntu thing...
[04:10] <martinex> crimsun, but... I just would like to ask if is there any known issue with new dapper kernel?
[04:10] <martinex> crimsun, and/or bind/dns libraries?
[04:11] <\sh> martinex: what exactly? every bug about kernel and/or bind you will find in our bugzilla
[04:11] <martinex> crimsun, I apt-getted my dapper yesterday and now it seems to work... but partially - it hangs on "detecting hardware"
[04:12] <martinex> and if I hit Ctrl-C than I can boot
[04:12] <martinex> but then network connections doesn't work
[04:13] <martinex> and I downloaded current install/live DVD from 20060110
[04:13] <martinex> then installed fresh breezy... network started
[04:14] <martinex> but I just wanted to use breezy as a base for dapper
[04:14] <martinex> so I changed repositories in sources.list - and apt-get dist-upgrade - it installed packages mainly from current DVD
[04:15] <martinex> and few from network (kernel image)
[04:15] <martinex> then after reboot - kernel hangs on "detecting hardware"
[04:20] <martinex> propably related to #21752
[04:21] <\sh> ok...i'm off to bed...
[04:28] <ajmitch> looks like it - doing the same on the laptop
[04:30] <ajmitch> except if I wait it does proceed
[04:35] <LaserJock> hi minghua
[04:36] <minghua> Hi LaserJock
[04:36] <ajmitch> minghua: reboot worked for you? ;)
[04:36] <LaserJock> I sent a Request For Sponsor today
[04:36] <hub> for sponsor for what?
[04:37] <minghua> ajmitch: yeah, :-)  didn't know which upgrade asked for the reboot, though, perhaps udev
[04:37] <psusi> I'm trying to make sure that if any part of this shell script fails, it exits immediately rather than try to continue... I do set -e, but it looks like foo | bar is considered not to fail if foo fails but bar does not..
[04:37] <ajmitch> minghua: latest udev/initramfs/kernel is causing issues for me & others, so it's an older kernel for me still
[04:37] <psusi> any way to fix that?
[04:37] <minghua> hub: I think some gtk frontend of gnuplot
[04:37] <martinex> ajmitch, so you can confirm that there is some kind of problem with new kernel?
[04:37] <ajmitch> martinex: no
[04:38] <LaserJock> hub: plotdrop
[04:38] <ajmitch> martinex: I cannot say that it is the kernel
[04:38] <martinex> ajmitch, btw - how long do you need to wait?
[04:38] <ajmitch> I waited less than 30 seconds
[04:38] <minghua> ajmitch: kernels after -9 seems to have been serving me well :-)
[04:38] <ajmitch> minghua: I suspect udev in this case anyway
[04:38] <martinex> ajmitch, and network interfaces are ok?
[04:39] <ajmitch> martinex: no
[04:39] <psusi> oh wait... it isn't becaus eof the pipe... hrm..
[04:39] <ajmitch> this isn't really the place for it
[04:39] <ajmitch> since it's not universe
[04:39] <psusi> FOO=`foo`... foo fails and returns non zero... set -e is in effect, yet the script continues...
[04:39] <psusi> hrm...
[04:39] <martinex> ajmitch, so.. #ubuntu-devel?
[04:39] <ajmitch> psusi: probably because the assignment still works
[04:39] <psusi> ajmitch, but the `foo` fails?  any failure should fail the whole script with set -e no?
[04:39] <minghua> ajmitch: yeah, my feeling is that udev is more error prone, too.  although I've never digged deep, if it doesn't boot, I go back to the old kernel :-P
[04:40] <ajmitch> psusi: I would have thought so, but probably not
[04:40] <ajmitch> psusi: test with FOO=`/bin/false`
[04:41] <psusi> ohh my... it seems that `foo` was returning 0.. even though it failed... hrm... yet another patch for pktsetup it seems
[04:41] <ajmitch> heh
[04:41] <ajmitch> bad program
[04:41] <martinex> ajmitch, anyway just please tell me - your laptop can boot if you will wait about 30 sec.. on "detecting hardware" and then everything is ok? ( are network interfaces up and running correctly?)
[04:41] <ajmitch> martinex: I said, no
[04:42] <martinex> ajmitch, heh then I got the same problem...
[04:42] <ajmitch> I can see that
[04:42] <martinex> ajmitch, although I waited about 4-5 minutes and nothing happens
[04:43] <martinex> ajmitch, I had to hit Ctrl-C to boot (but without network.. it doesn't make any sense)
[04:43] <bmonty> hi LaserJock, ajmitch
[04:43] <martinex> ajmitch, anyway - thanks for info
[04:43] <martinex> off to bed
[04:47] <bmonty> a simple reboot solves most of my problems after a kernel upgrade....except for blutetooth which hasn't worked since a couple upgrades back
[04:48] <ajmitch> hey bmonty
[04:49] <ajmitch> I'd *love* it it people on the forums used malone instead of just reporting bugs solely on the forums
[04:49] <bmonty> ajmitch: I fear that is a symptom of how people are used to using the internet
[04:50] <ajmitch> sadly
[04:50] <bmonty> they understand forums and not the bug tracking systems
[04:50] <ajmitch> yep
[04:50] <ajmitch> and they expect everyone else to see their feature requests, bug reports & general whining
[04:50] <bmonty> it would be nice if there was a "Report a bug in this application..." option on the help menu
[04:50] <ajmitch> umm
[04:50] <ajmitch> there isn't? :)
[04:51] <bmonty> the isn't on my dapper install
[04:51] <ajmitch> there should be for apps built with the launchpad integration
[04:51] <LaserJock> hi bmonty
[04:52] <bmonty> hey LaserJock
[04:52] <ajmitch> the 'how to file bugs' topic on the forums is amazingly complex
[04:52] <ajmitch> including rebuilding the packages with debugging symbols
[04:52] <ajmitch> and using gdb
[04:53] <bmonty> yeah getting a non-devel type to rebuild a package with debug symbols is realistic :)
[04:53] <bmonty> I haven't looked at the forums in a long time
[04:54] <ajmitch> I do when I'm feeling particularly masochistic
[04:54] <bmonty> though I noticed that typing "ubuntu" in google will almost always get you a forum link on the first page
[04:55] <ajmitch> the forums are incredibly popular
[04:55] <ajmitch> and full of lots of bad info at times
[04:56] <bmonty> the forums are not run by canonical, right?
[04:57] <ajmitch> no, they're not
[04:57] <ajmitch> they are 'official' though
[04:58] <bmonty> irc is definately not as sexy as the forums though :)
[04:59] <ajmitch> no, it's not
[05:00] <bmonty> ok, the "Get help online..." option links to launchpad (I tried from xchat), but it definately isn't what I would call user friendly
[05:04] <bmonty> oh well...time for bed, good night everyone
[05:09] <LaserJock> what app would I use to see what ports are open on a remote computer?
[05:09] <Kyral> nmap?
[05:11] <Yagisan> LaserJock: nmap definitely. Worls on i386 - amd64 version seems flakey
[05:11] <LaserJock> k, I'll try that. It seems that every time I try to do something my university network has the ports blocked
[05:11] <Yagisan> s/Worls/Works
[05:11] <Kyral> but ehh
[05:11] <Kyral> be careful lol
[05:11] <LaserJock> so I wan't to know which ones are and which ones aren't
[05:11] <Yagisan> LaserJock: nmapfe for graphical. BTW - We can detect you scanning with it
[05:12] <LaserJock> hmm, we maybe I could just talk to our admin and see if he can tell me
[05:12] <Yagisan> LaserJock: I use it for work :) so I'm familiar with it
[05:13] <Yagisan> LaserJock: when I get back soon, feel free to ask me questions about it - like how to be stealthy about it
[05:13] <Yagisan> be back soon
[05:13] <LaserJock> well, right now I just want to be able to download a .torrent
[05:13] <LaserJock> it used to work but now it looks like it is blocked
[05:14] <Kyral> a lot of colleges block Torrents
[05:14] <Kyral> Most use an adaptive thing
[05:14] <Kyral> believe me I know
[05:17] <crimsun> many universities use packeteer
[05:17] <crimsun> ours was one of the first, unfortunately
[05:17] <LaserJock> I hate that. I have to use a different port for chat, I can't get .torrents of linux isos
[05:17] <LaserJock> at least I can still ssh in
[05:18] <crimsun> do you have an external shell?
[05:18] <crimsun> I have ssh tunnels running everywhere. Yay for holes in the 'wall.
[05:19] <Kyral> anyone ever have Irssi not backspacing when run in Screen?
[05:19] <LaserJock> what do you mean by external shell?
[05:19] <LaserJock> Kyral: I don't think so
[05:19] <Kyral> hmm
[05:19] <Kyral> its odd
[05:20] <Kyral> if I run Irssi normally I can backspace
[05:20] <Kyral> but if I run it in Screen I cannot
[05:20] <ajmitch> Kyral: sounds like a question for #ubuntu ;)
[05:20] <crimsun> sounds like your termcap is screwed, echo $TERM
[05:21] <Kyral> yah I was just field it here before I go into the maelstrom
[05:21] <ajmitch> as is probably safe
[05:21] <crimsun> LaserJock: a host accessible via ssh outside your uni's firewall
[05:21] <ajmitch> Kyral: you could always ask on the forums
[05:21] <Kyral> crimsun: its set to xterm
[05:22] <LaserJock> crimsun: don't know, I only have windows on the outside. I was able to do vnc over ssh though.
[05:24] <Yagisan> re
[05:24] <Yagisan> LaserJock: use port 443, for your torrent
[05:24] <veganpops> https://launchpad.net/distros/ubuntu/+source/cernlib/+bug/6588
[05:24] <Ubugtu> Malone bug 6588: "PAW - Segmentation violation - Traceq lun = 0, level = 99" Fix req. for: gcc (upstream), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/6588
[05:25] <Yagisan> LaserJock: Azureus works - and 1) it's not blocked on most networks, 2) its not throttled
[05:25] <Kyral> crimsun: should my $TERM be xterm?
[05:25] <veganpops> Following the guidance of the original Debian package maintainer I fixed a serious bug in the cernlib [universe]  packages.
[05:26] <veganpops> How do I go about getting this fix propagated into the official versions?
[05:26] <Kyral> file a bug
[05:26] <Kyral> attach debdiff?
[05:26] <veganpops> I did, see above.
[05:26] <veganpops> debdiff?
[05:27] <crimsun> Kyral: xterm should suffice. Are you doing anything odd in screen?
[05:27] <Kyral> crimsun: nope
[05:27] <Kyral> I just do screen irssi
[05:28] <veganpops> All of the fixed Breezy packages are in http://renfield.physics.utah.edu/cernlib.tar.bz2 (44 MB)
[05:28] <Kyral> brb, gonna restart in screen
[05:29] <crimsun> gcc-3.3?
[05:29] <crimsun> ugh. doko ain't gonna like that.
[05:29] <Kyral> Gak I see it
[05:29] <veganpops> crimsun: I know, the bug affects all gcc up to and include 4.0.1
[05:29] <Kyral> somehow Backspace isn't sending ^H
[05:29] <Kyral> while in screen
[05:30] <crimsun> Kyral: hmm, it works here?
[05:30] <Kyral> crimsun I set Backspace to send ^H in xterm prefs
[05:30] <crimsun> Kyral: try ``TERM=vt100 screen irssi''
[05:30] <veganpops> crimsun: The original maintainer says it is fixed in 4.0.2??
[05:30] <Kyral> okay brb
[05:31] <crimsun> gcc version 4.0.3 20060104 (prerelease) (Ubuntu 4.0.2-6ubuntu1)
[05:31] <crimsun> root@mika:/#
[05:31] <Ubugtu> Error: Could not parse XML returned by Ubuntu: not well-formed (invalid token): line 189, column 1
[05:31] <crimsun> not an issue in Dapper
[05:32] <veganpops> crimsun: True - it should be OK in Dapper.
[05:32] <Kyral> nope
[05:33] <crimsun> Kyral: as in "still doesn't work"?
[05:33] <Kyral> crimsun: doesn't work
[05:33] <crimsun> sounds like an xterm boog
[05:33] <Kyral> I had to set XTerm to interpret Backspace as ^H
[05:33] <crimsun> (I use rxvt-unicode-lite myself)
[05:33] <Kyral> but why would it only take effect when Screen runs?
[05:34] <crimsun> no idea
[05:34] <crimsun> are you using Dapper's xterm?
[05:34] <Kyral> yah
[05:35] <Kyral> hmm
[05:35] <Kyral> lemme see what $TERM is in screen
[05:35] <Kyral> ...its echoed as "screen"
[05:55] <LaserJock> Yagisan: you sure about port 443 ?
[05:59] <Yagisan> LaserJock: should be https port IIRC
[05:59] <Yagisan> LaserJock: it's like running it out port 80
[05:59] <LaserJock> oh, ok
[06:00] <Yagisan> LaserJock: my isp seems to throttle torrents, so I run them over other ports
[06:01] <Yagisan> Yagisan: they need to do layer7 filtering to stop your torrent, if you run over a standard port
[06:07] <Kyral> hmm
[06:07] <LaserJock> why?
[06:07] <Kyral> Dunno
[06:07] <Kyral> for those GUI oriented developers?
[06:07] <Kyral> (Yes they exist)
[06:08] <Yagisan> Kyral: would that support multiple pbuilders ?
[06:08] <Kyral> Yagisan: yup yup
[06:09] <Kyral> I just need to learn PyGTK first lol
[06:10] <crimsun> Kyral: screen, if xterm -e irssi  works fine
[06:10] <Kyral> xterm -e?
[06:11] <Yagisan> ooh, I feel silly now. How do I filter out [ and ]  with sed ? It thinks they are special characters, and I want them to be treated literally
[06:11] <Kyral> \[?
[06:12] <Kyral> what does xterm -e do?
[06:15] <LaserJock> arghhh, stupid torrents :(
[06:16] <Yagisan> Kyral: nope. Didn't work. s/[[] //g got rid of the first one though
[06:16] <Yagisan> Kyral: fixed it with a two pass sed
[06:17] <Yagisan> LaserJock: still not going ?
[06:18] <LaserJock> no, I get NAT error
[06:21] <LaserJock> I think I will just give up and use windows at home even though it's a DSL connection
[06:23] <Yagisan> LaserJock: you can't get incoming connections ?
[06:27] <LaserJock> oh, maybe it is
[06:30] <Yagisan> LaserJock: the little yellow face is ok. not ideal, but ok. eg right now on 3 torrents I'm doing, I have yellow faces, but I know there no nat error, as sometimes they turn green (assuming you use azureus)
[06:32] <Yagisan> G'day zakame
[06:33] <zakame> heya Yagisan :)
[06:33] <psusi> well.... this is a shitload of fun
[06:33] <psusi> I blew up my dvd/rw drive tonight
[06:33] <LaserJock> Yagisan: I just have a black face
[06:33] <Yagisan> psusi: how ?
[06:33] <psusi> I was working on the packet cdrw stuff, trying to get it all plug and play with hal and everything
[06:34] <Yagisan> LaserJock: that means you have not started the torrent
[06:34] <psusi> and it started getting a bunch of IO errors
[06:34] <Yagisan> psusi: power off, let it cool down, try again
[06:34] <psusi> so I shutdown and reboot, and now the drive is toast... put in any cd media... cdrom, cd-r, cd-rw, and it pukes
[06:34] <psusi> tried that
[06:34] <psusi> it makes funny noises and finally reports no media
[06:34] <psusi> though.. and this is the really fucked up part...
[06:34] <psusi> it plays dvds fine
[06:35] <Yagisan> psusi: oh - reflash firmware - see if that helps
[06:35] <psusi> did that... no dice
[06:35] <psusi> even had to boot into windows for that one
[06:35] <Yagisan> psusi: how old is the drive ?
[06:35] <psusi> my windows install is all kinds of fucked up
[06:35] <psusi> made in oct 2004
[06:35] <psusi> I already sent in the request for an RMA
[06:36] <psusi> we'll see what happens
[06:36] <Yagisan> psusi: is it under warrenty ? put on a sweet face and say - "I won't read cd's"
[06:36] <Yagisan> *It
[06:36] <psusi> I don't get how it plays dvds fine, but when you put in a cd, it starts making "oh-no" sounds
[06:37] <psusi> Yagisan, yep... I did that... hopefully will find out tomorrow if it is under warrenty
[06:37] <Yagisan> psusi: laser may be stuffed. drive should two lasers, 1 for cd, 1 for dvd
[06:37] <psusi> I thought so...
[06:37] <psusi> seems the cd one burned up
[06:37] <LaserJock> Yagisan: hmm, well somehow the iso got downloaded from something I did
[06:38] <LaserJock> Yagisan: maybe it wasn't azureus though, I have tried a bunch of things
[06:39] <psusi> I need to build a new machine soon... this one is 2 years old now... blew out the dvd/rw... keyboard randomly craps out and I have to unplug and replug it... windows install is 9 kinds of fucked
[06:39] <Yagisan> psusi: many years ago, I was a hardware tech. It wasn't uncommon for a laser to die
[06:39] <Yagisan> LaserJock: as long as it works, it's fine ;)
[06:40] <LaserJock> Yagisan: yeah, I just wish I knew what worked :-)
[06:40] <psusi> Yagisan, I've never seen a cd drive go bad before... I've not seen it in some time now, but back around 1994 I got oen fo the first 4x cdrom drives on the market... mitumi...
[06:40] <Yagisan> psusi: I still use pentium 2's here
[06:40] <psusi> in 1996 I used it in an old machine to setup up a bbs
[06:40] <psusi> the pc speaker had been torn off, and the wires accidently brushed up against that drive
[06:40] <psusi> made a nice light show and a burn on the drive
[06:40] <psusi> it was still working in 2000
[06:41] <Yagisan> psusi: heat and humidity tend to break cd/dvd drives most often. I've had quite a few die like that
[06:41] <psusi> I live in Florida.... heat and humidity are my breakfast and lunch ;)
[06:42] <psusi> I wish I could debug the firmware in the damn drive... I hate firmware... allways screws the pooch as soon as something unusual happens
[06:43] <psusi> in my last computer I had a plextor plexwriter 4x cd-r... scsi... once I tried to overburn a cd by a wee bit too much and it just freaked out
[06:43] <psusi> kept seeking the head and wouldn't respond to commands from the os
[06:44] <psusi> or the eject button
[06:44] <psusi> finally I just reached into the case and pulled out the power cord from the drive
[07:04] <psusi> holy shit
[07:04] <psusi> it isn't even worth it to repair this thing... newegg has an even nicer drive for only $42!
[09:06] <cyle> anybody out there?
[09:08] <lucas> yes
[09:08] <ajmitch> barely
[09:08] <cyle> * hears crickets *
[09:08] <cyle> i was on here last weekend
[09:09] <cyle> i got my pgp key, started my wiki page
[09:09] <cyle> joined ubuntu-devel mailing list
[09:09] <cyle> but was never able to pick a package to start working on
[09:09] <lucas> ah
[09:10] <lucas> what do you want to do ? merges/syncs ? packaging ?
[09:10] <cyle> merges are bringing over debian packages right? i wouldn't really wanna do that
[09:10] <cyle> preferably packaging
[09:10] <lucas> you want to start reading http://wiki.ubuntu.com/MOTU
[09:11] <lucas> and ask questions if you don't understand something, so we/I can improve the wiki
[09:12] <cyle> i looked at that quite a bit last weekend
[09:12] <cyle> i've been over the debian developer guides too
[09:13] <lucas> ok
[09:13] <lucas> if you want to start packaging, pick up a package on the UniverseCandidates page
[09:13] <lucas> package it
[09:13] <lucas> upload it to REVU
[09:13] <lucas> but I personally feel that the most noble part of MOTU work is merging, not packaging (we should fix the existing before considering the new)
[09:14] <cyle> what types of problems get fixed in merging?
[09:15] <lucas> read https://wiki.ubuntu.com/MOTUMerging
[09:19] <cyle> i understand what it's saying
[09:19] <cyle> but there's a lot that seems like you would have to know some history about what's going on to understand
[09:20] <cyle> like regarding gcc4 patches
[09:20] <cyle> gl/glut patches
[09:20] <cyle> doesn't say what the glut patches are
[09:20] <lucas> ok
[09:21] <lucas> usually, you just pick a package from the merge lsits
[09:21] <lucas> and see if the ubuntu patches are still necessary
[09:21] <lucas> so knowing exactly how to fix gcc4 problems isnt mandatory
[09:21] <cyle> what kinds of reasons do we do ubuntu specific patches
[09:22] <lucas> read "Some reasons for divergence between Debian and Ubuntu"
[09:23] <lucas> on MOTUMerging
[09:23] <lucas> and follow the "this thread" link
[09:24] <cyle> duh
[09:24] <cyle> i skipped right over that link
[09:24] <lucas> edit the page to make it more visible ;)
[09:26] <cyle> so the gcc4 thing
[09:26] <cyle> is it a dapper requirement that all packages compile with gcc4?
[09:26] <lucas> yes
[09:27] <cyle> so if for some reason debian's package can't do so we will make a patch/apply a patch for it?
[09:28] <lucas> exactly
[09:28] <cyle> one thing i noticed
[09:28] <cyle> in dapper, there's no stable 1.5 firefox, is this because debian hasn't put out a 1.5 stable package?
[09:29] <lucas> I dunno
[09:29] <lucas> firefox is main, not universe
[09:29] <cyle> i know that
[09:29] <cyle> it was more of a question about how that works
[09:29] <lucas> there was a thread about a firefox/epiphany debate on ubuntu-devel
[09:29] <lucas> but I haven't read it
[09:29] <cyle> will we ever package a newer version of an app than debian does?
[09:29] <lucas> since it went into the usual vi/emacs stuff
[09:30] <lucas> sometimes
[09:30] <siretart> WAAAAH. whats going on with tiber?!
[09:30] <lucas> there are several packages in this case
[09:30] <siretart> morning folks
[09:30] <cyle> i saw that, they basically told the guy he's an idiot and firefox will continue to be the main browser
[09:30] <lucas> hi siretart
[09:30] <lucas> siretart: dunno, it has been down for ~30 minutes I think
[09:31] <siretart> lucas: lets hope it is 'just' a broken router
[09:31] <cyle> and my understanding is that right now breezy packages will not be updated right?
[09:31] <cyle> so like if dapper ships with firefox 1.5, it will never be updated with firefox 1.6
[09:32] <siretart> cyle: well, the main reason why we don't is lack of ressources
[09:32] <siretart> cyle: and we want 'stable' releases, so we are very very carefully when updating releases
[09:33] <cyle> i understand that, most users don't care about having the latest and greatest, as long as what they have works
[09:33] <siretart> for newer crack, we have ubuntu-backports
[09:33] <lucas> somebody has an example of a wiki page with an image ?
[09:35] <siretart> lucas: the tracelog output makes me think this is a router misconfiguration (I see a packet loop)
[09:38] <cyle>  is there a guide to making a source package on the wiki
[09:38] <cyle> i've packaged binaries before
[09:38] <cyle> but never had to do a source package
[09:48] <lucas> siretart and others: can you comment on https://wiki.ubuntu.com/MOTUMeetingTeamReorg
[09:49] <siretart> lucas: I don't quite get the arrow directions. what do the arrows say?
[09:49] <siretart> ah
[09:50] <siretart> lucas: hm. I have some concerns about it, but I need to think about that.
[09:51] <lucas> ok, np
[09:51] <siretart> my biggest concern is this: what happens with administrative emails to the 'leaf' teams, e.g. MOTUReviewers. if someone tries to join MOTUReviewers ALL but MOTUMergers get spammed with the request to join
[09:52] <lucas> no, only the admins of MOTUReviewers
[09:53] <lucas> (who can be ogra + dholbach for example)
[09:56] <siretart> lucas: ok, in this case, could you please be more verbose in the diagramm not only on membership but also on maintainership? (e.g. which group administers whom and which group is maintained by whom)?
[09:56] <lucas> also the teams can be set as 'Restricted teams'
[09:56] <lucas> ok
[09:56] <siretart> thanks
[09:57] <lucas> siretart: I added a note about maintainership
[10:02] <lucas> cool
[10:11] <crimsun> gah, merging never ends!
[10:16] <lucas> crimsun: nice job on flashplugin-nonfree
[10:22] <dholbach> hello MOTUs!
[10:23] <siretart> huhu dholbach
[10:23] <lucas> hello dholbach
[10:23] <crimsun> siretart: please remove ax25-tools from the merge list; I merged it yesterday before looking at the page today
[10:23] <dholbach> hey siretart, lucas!
[10:24] <dholbach> it's the HUG DAY! :)
[10:24] <lucas> dholbach: when you'll have had breakfast, you can read and comment on https://wiki.ubuntu.com/MOTUMeetingTeamReorg ;)
[10:26] <dholbach> lucas: what will effectively change?
[10:27] <dholbach> lucas: apart from organisational launchpad representation
[10:27] <dholbach> lucas: i mean, it *looks* nice :)
[10:28] <lucas> dholbach: lots of people removed from some teams and added to others
[10:28] <siretart> lucas: great job on the MergeNOTES wiki page. I assume you update your scripts from that wiki page via cron?
[10:28] <lucas> it would mean that, for example, motureviewers would have no direct members
[10:28] <lucas> same for motu
[10:28] <siretart> I slowly recover from my vacation and operation :)
[10:28] <lucas> siretart: yes (it is MOTUNotes)
[10:29] <dholbach> siretart: operation? what happened? how are you?
[10:30] <siretart> dholbach: it was an incarnated nail in the foot, nothing serious (but painful)
[10:30] <siretart> I'm fine and back now :)
[10:31] <StevenK> An ingrown toenail? I've had that operation done to both my feet.
[10:31] <Treenaks> "Legacy code"
[10:31] <StevenK> When you said nail, I thought nail, like the one you hammer. :-)
[10:33] <dholbach> siretart: i'm glad to hear you're fine
[10:36] <siretart> StevenK: oh. yes, its a toenail. we don't differ that much in german. :)
[10:37] <StevenK> Well, I thought a nail in the foot, like you stood on one.
[10:37] <dholbach> lucas: i'll have to review it in-depth - because it's not just "membership", it's also "assigned bugs, ..." - maybe we should talk to the launchpad guys about this
[10:38] <dholbach> lucas: it's also about polls on launchpad and so on
[10:38] <lucas> yup I know
[10:38] <lucas> should I raise the issue on ubuntu-motu ?
[10:38] <siretart> and support requests
[10:38] <lucas> and cc launchpad-something ?
[10:38] <siretart> lucas: I think that would be best
[10:38] <dholbach> yes
[10:42] <Yagisan> ajmitch: around ?
[10:42] <dholbach> so who will be involved in today's BUG DAY? :)
[10:43] <Yagisan> I can find bugs
[11:01] <lucas> dholbach: I really have to do some real life work today
[11:01] <dholbach> lucas: good luck and 'Bon courage!' with that :-)
[11:17] <dholbach> about the bug day: it'd be great if we could make an effort to go through 'motu' bugs and see if new upstream versions fix the bugs, because as you might know: UpstreamVersionFreeze is in 8 days already
[11:17] <dholbach> so i think this is a great time to get started on this
[11:20] <Gloubiboulga> dholbach, I'd like to help on this, could you tell what to do, or give an url where I could find explainations
[11:21] <dholbach> http://launchpad.net/people/motu/+assignedbugs has the motu bugs
[11:21] <dholbach> for some of them we could investigate, if a new upstream version of the package fixes the issues mentioned by the reporters
[11:22] <dholbach> if you have trouble doing this, just ask here
[11:23] <Gloubiboulga> ok
[11:23] <Gloubiboulga> 'new upstream version' means already packaged version I guess ?
[11:23] <dholbach> the debian/copyright of the package in question should have the place it was downloaded from
[11:23] <dholbach> no, upstream version
[11:23] <dholbach> (version from the authors)
[11:24] <Gloubiboulga> oh, ok
[11:32] <martinex> hi all
[11:33] <martinex> is there any way to track changes in dapper repository without apt?
[11:33] <dholbach> read the dapper-changes mailing list
[11:34] <martinex> my dapper is currently unworkable ... I can boot but it hangs on 'detecting hardware' part and can boot after Ctrl-C but unfortunately without network interfaces configured at all
[11:34] <martinex> so it is pretty hard to fix it without network...
[11:34] <dholbach> do you have "auto eth0" in /etc/network/interfaces=
[11:34] <dholbach> ?
[11:34] <dholbach> or whatever device it is?
[11:36] <martinex> dholbach, everything is configured properly
[11:36] <dholbach> does the network driver not get loaded automatically?
[11:37] <martinex> dholbach, as I said before - it doesn't want to work because dapper hangs on "detecting hardware" and I got to skip it with Ctrl-C
[11:38] <dholbach> you tried a different kernel?
[11:38] <martinex> dholbach, well kind of
[11:38] <martinex> dholbach, I tried breezy
[11:38] <dholbach> did that work?
[11:38] <martinex> dholbach, I just installed fresh breezy on /
[11:39] <martinex> dholbach, then changed repos in apt and dist-upgraded to dapper
[11:39] <dholbach> and then?
[11:39] <martinex> dholbach, same thing again - hangs and no network
[11:39] <dholbach> *Strange*
[11:39] <dholbach> can you modprobe the driver and ifconfig eth0 up?
[11:40] <martinex> dholbach, and I'm not alone with this problem .... ( I think so) take a look at #21752
[11:40] <dholbach> you maybe should follow up on the bug in #ubuntu-kernel
[11:41] <martinex> dholbach, ok... but I'm not sure if it's kernel bug
[11:41] <dholbach> yeah, might be udev/... too
[11:42] <martinex> dholbach, anyway I'll reboot (I'm on my favourite 'windows' now) and try again
[11:42] <dholbach> ok
[11:42] <martinex> dholbach, but I just would like to find some info if something changed in packages that could be cause of this problem
[11:43] <martinex> dholbach, since yesterday...
[11:44] <dholbach> dapper-changes mailing list might be helpful
[11:44] <martinex> dholbach, reading now
[11:45] <martinex> hmm no changes in kernel and udev...
[11:45] <martinex> reboot and'll see
[11:56] <Gloubiboulga> dholbach, if a new upstream release fixes the bug, what do I need to add/change on the malone page ?
[11:57] <dholbach> Gloubiboulga: best thing would be to package the new version and add the revu link to it, maybe subscribe motureviewers team as well
[11:57] <dholbach> well done, which packages is it?
[11:57] <Gloubiboulga> eagle-usb, malone 3314
[11:57] <Ubugtu> Malone bug 3314: "usb (Ubuntu) - no connection to internet" Fix req. for: eagle-usb (Ubuntu), Severity: Normal, Assigned to: MOTU, Status: Unconfirmed http://launchpad.net/bugs/3314
[11:58] <dholbach> great
[11:59] <martinex> dholbach, unfortunately it doesn't want to work
[11:59] <martinex> dholbach, but it propably isn't kernel bug
[12:00] <martinex> dholbach, because I got breezy kernel on this machine too, and this kernel hangs just like this from dapper
[12:00] <dholbach> martinex: unfortunately i'm not a kernel/hardware/udev/... guru - you'd better ask the #ubuntu-kernel guys, they might know about the bug, if you ask them
[12:00] <martinex> dholbach, unfortunately modprobe didn't work too
[12:01] <ogra_ibook> its a known and announced udev regression
[12:01] <martinex> dholbach, I had to modprobe [myNICmodule]  right?
[12:01] <ogra_ibook> but modprobing the driver and ifupping the interface should works
[12:01] <ogra_ibook> -s
[12:01] <martinex> ogra, I did it
[12:01] <martinex> ogra, modprobe 8139too
[12:02] <ogra_ibook> whats the eroor if you do this ?
[12:02] <ogra_ibook> *error
[12:02] <martinex> ogra_ibook, there is no error....
[12:02] <martinex> ogra_ibook, but then
[12:02] <ogra_ibook> so it gets loaded fine
[12:02] <martinex> ogra_ibook, I did mii-tool
[12:02] <ogra_ibook> does it show up in lsmod ?
[12:02] <dholbach> dmesg | tail
[12:02] <ogra_ibook> why ?
[12:02] <martinex> ogra_ibook, yes it was in lsmod
[12:03] <ogra_ibook> fine
[12:03] <martinex> ogra_ibook, but mii-tool said that: SIOCGMIIPHY on eth0 failed
[12:03] <ogra_ibook> so if you ifup it, it doesnt come up (without playing with the physical layer with mii-tool) ?
[12:03] <martinex> ogra_ibook, no MII interfaces found
[12:04] <ogra_ibook> does it come up with: sudo ifup eth0 (forget about mii-tool for now)
[12:04] <martinex> ogra_ibook, ehhh I got to reboot again to test it ;)
[12:04] <ogra_ibook> try it
[12:04] <ogra_ibook> it should work
[12:04] <martinex> ogra_ibook, could you tell me what should I do to make it workable before reboot?
[12:05] <martinex> ogra_ibook, modprobe [module]  ?
[12:05] <martinex> ogra_ibook, and then ifup eth0 ?
[12:05] <ogra_ibook> the module should be loaded on boot already, check with lsmod
[12:05] <martinex> ogra_ibook, (forget sudo part because I'm lazy and I always do sudo -H -s ;) )
[12:05] <ogra_ibook> its only the upping of the iface that fails afaik
[12:06] <martinex> ogra_ibook, it wasn't
[12:06] <martinex> ogra_ibook, I verified this with lsmod and dmesg | grep eth or dmesg | grep rtl
[12:07] <martinex> ogra_ibook, maybe it's because I have to hit Ctrl-C to boot
[12:07] <ogra_ibook> might be ...
[12:07] <martinex> ogra_ibook, boot procedure hangs on "detecting and configuring hardware" (or something like this) and I got to Ctrl-C to boot
[12:08] <ogra_ibook> how long did you wait before ctrl-c ing ?
[12:08] <martinex> uuuh long
[12:08] <ogra_ibook> and do you have any scsi adapter in this machine ?
[12:08] <martinex> about 4-5 min
[12:08] <martinex> ogra_ibook, well no, I don't
[12:08] <ogra_ibook> scsi is set to wait up to 2 min for the devices to initialize
[12:09] <martinex> ogra_ibook, only card reader connected via USB
[12:09] <martinex> ogra_ibook, but I disconnected this when trying to find what is the problem
[12:10] <ogra_ibook> anyway, if you dont get the iface up with modprobe and ifup, please file a bug, assigned to udev
[12:10] <martinex> ogra_ibook, this card reader mounts 4 "drives" as sd....something I don't remember...
[12:10] <ogra_ibook> yu can also try to get hold of Keybuk in #ubuntu-devel to debug this further if he has the time ...
[12:11] <martinex> ok I'll try to reboot now and we'll see then
[12:11] <martinex> thanks for help
[12:51] <Gloubiboulga> dholbach, I've sent the package on REVU: http://revu.tauware.de/details.py?upid=1469
[12:55] <dholbach> cool
[12:58] <raphink> hi
[12:58] <Gloubiboulga> salut raphink
[12:59] <raphink> a roule?
[12:59] <Gloubiboulga> yep :)
[12:59] <raphink> cool :)
[01:03] <raphink> hmmm
[01:04] <raphink> grrr usbview has no MoM report
[01:04] <raphink> :s
[01:08] <StevenK> crimsun: Bah, you win again!
[01:12] <raphink> hmm anyone with a PPC here?
[01:17] <raphink> dholbach: you have a ppc ?
[01:17] <raphink> ;)
[01:18] <martinex> ogra_ibook, ping
[01:22] <crimsun> martinex: he's in an Edubuntu meeting atm
[01:22] <martinex> crimsun, ok...
[01:23] <martinex> crimsun, thanks
[01:40] <dholbach> raphink: no, sorry
[01:41] <raphink> dholbach: ok ;)
[01:41] <dholbach> i'm out for getting food - bbl
[01:41] <raphink> hi btw dholbach :)
[01:41] <raphink> ok
[01:52] <Czessi_away> raphink: You can try to ask Amu (is in #kubuntu-devel) for ppc. he build kde 3.5 packages for ppc
[01:52] <raphink> no it's fine
[01:52] <raphink> :)
[01:52] <raphink> thanks Czessi_away
[02:59] <Gloubiboulga> hello thierry_
[03:01] <thierry_> hi Gloubiboulga
[03:04] <zakame> evening MOTUs :)
[03:04] <Gloubiboulga> hi zakame
[03:06] <zakame> heya Gloubiboulga
[03:07] <thierry_> zakame : could you review my package, you already advocated it before but I had some changes to add, I changed the name, now it's libfxscintilla
[03:09] <zakame> thierry_: link? :)
[03:10] <thierry_> zakame : http://revu.tauware.de/details.py?upid=1459
[03:11] <thierry_> zakame : and the one you advocated http://revu.tauware.de/details.py?upid=1298
[03:13] <zakame> thierry_: I think you don't need to have a versioned libfxscintilla17-dev, a libfxscintilla-dev should be fine
[03:14] <zakame> wb Kaloz
[03:14] <zakame> er Kyral
[03:14] <Kyral> morning
[03:14] <Kyral> well, this is interresting
[03:15] <Kyral> gkrellm runs...but doesn't show up in X
[03:15] <zakame> huh?
[03:15] <thierry_> zakame : well the debiand librairy packaging guide says it's better and sistpoty toot
[03:15] <thierry_> too*
[03:16] <Kyral> I dunno
[03:16] <zakame> thierry_: well, that would be so if you're willing to keep multiple versions of the same lib
[03:16] <Kyral> X seems borked...wierdly
[03:16] <zakame> in dapper/dapper+1
[03:17] <thierry_> zakame : well I do, when the new version of the lib will be released, I'll add it
[03:18] <thierry_> and anyway it had to follow the the SONAME no?
[03:18] <zakame> thierry_: I presume you'll also notify persons building on your lib to chase transitions as well ;)
[03:18] <zakame> for libfoo-dev not really
[03:19] <zakame> thierry_: in debian/rules, isn't the lib built as shared?
[03:19] <thierry_> yes
[03:19] <zakame> then why the explicit --enable-shared?
[03:19] <zakame> I think you can turn that off
[03:20] <thierry_> zakame : I had big problems with .so files and the upstream author told me to do that anyway
[03:21] <zakame> wb \sh :)
[03:21] <zakame> thierry_: ah, k
[03:21] <thierry_> zakame : so, if I change for libfxscintilla-dev, you advocate?
[03:23] <zakame> thierry_: I could go on any way actually :) looks nice
[03:24] <thierry_> k then I'll leave it this way to follow sistpoty tips
[03:25] <\sh> re
[03:27] <Kyral> Now there is a wierd hiccup
[03:28] <thierry_> zakame : k then I'll leave it this way to follow sistpoty tips
[03:28] <zakame> ok
[03:29] <thierry_> zakame : so feel free to advocate anytime you want
[03:33] <\sh> Czessi: ping
[03:42] <thierry_> zakame : so I should only change Package: libfxscintilla17-dev to Package: libfxscintilla-dev and take off provides and conflicts
[03:42] <thierry_> ?
[03:42] <zakame> yes
[03:44] <thierry_> k
[03:45] <thierry_> zakame : rebuilding and I'll reupload
[03:47] <Yagisan> \sh: ping
[03:47] <\sh> Yagisan: pong
[03:48] <Yagisan> \sh: you most likely have noticed wine FTBFS as 64bit native by now
[03:48] <\sh> Yagisan: no i didn't because I never build it..but will do later this day
[03:48] <Yagisan> \sh: oh - just a sec then
[03:49] <\sh> I'm just coming home and had to sort out some more important stuff :)
[03:49] <Yagisan> \sh: http://bugs.winehq.org/show_bug.cgi?id=4281
[03:49] <Ubugtu> Error: Unknown bugtracker
[03:50] <Yagisan> \sh: reported it yesterday. I spoke with #winehq
[03:50] <zakame> bad Ubugtu
[03:50] <\sh> Yagisan: glibc issue?
[03:50] <\sh> in thread management?
[03:50] <Yagisan> \sh: and they think wine64 would be ok if you just mv * *-64 all the binaries for the 64bit native build
[03:51] <Yagisan> \sh: actually - they haven't written part of it - that's why it FTBFS
[03:51] <\sh> Yagisan: hum? what they didn't write?
[03:52] <\sh> glibc.c:56: warning: cast to pointer from integer of different size
[03:52] <\sh> this is a nice one :)
[03:53] <\sh> this would cause a nice segfault somehow...
[03:54] <Yagisan> \sh: anyway - as 64bit native is currently a no-go, I was going to just finish off the wine32 package, and set normal wine to [!amd64] 
[03:54] <Yagisan> \sh: unless you have other changes you'd like to do
[03:55] <\sh> Yagisan: getting wine64 running
[03:56] <\sh> if we go on with the amd64 adventure we should provide all possibilities...even 64bit wine for running non-existent win64 apps
[03:57] <Yagisan> \sh: yes - but as that dosen't work, I was just going to comment that out in the rules file, until the next upstream release before trying again
[03:58] <Yagisan> personally, I'd like to see all apps that can run on amd64, running on it, even if it is a 32bit compatibility app  - otherwise amd64 as an arch is a waste of time
[04:00] <\sh> Yagisan: ok...move the 32bit stuff then into a wine64-compat package and create an empty wine64 package, with amd64 only so we have at least all preparations done for the ongoing project
[04:02] <Yagisan> \sh: I have the package set up as wine = native compile, wine32 = 32bit compile. the rules are there, and just need a quick toss through pbuilder to make sure they work
[04:02] <Yagisan> \sh: 1 issue is I need to work out what version wine is from inside debian/rules
[04:03] <Yagisan> \sh: so I can correctly sed debian/files at build time
[04:06] <\sh> Yagisan: check debian/changelog :)
[04:12] <thierry_> zakame : could you readvocate? I uploaded the last change... this will probably be the last time you have to advocate it
[04:12] <zakame> thierry_: yeah, just got the mail
[04:13] <crimsun> would someone with main upload privs please request a sync from Sid of ttf-dejavu?
[04:14] <crimsun> it's preventing me from diagnosing a bug report on cacti, because rrdtool is uninstallable due to the dependency on ttf-dejavu
[04:15] <\sh> crimsun: did u test the fontpackage?
[04:15] <\sh> I wonder why there is a ubuntu version of this
[04:16] <crimsun> it's a -0ubuntu1 because of new upstream version
[04:16] <thierry_> I need one more advocate to have my package accepted anyone who would like to review it? ajmitch maybe? http://revu.tauware.de/details.py?upid=1470
[04:16] <\sh> and which version is the new sid package?
[04:17] <thierry_> zakame : could you delete libfxscintilla1.6 and libfxscintilla17 entries please in REVY ?
[04:17] <\sh> hehe...2.1-1
[04:17] <\sh> crimsun: you have to merge it manually
[04:17] <\sh> crimsun: i think we have a different orig.tar.gz for this version....as always with 0ubuntu1 versions
[04:18] <zakame> thierry_: hm they're already archived, and I don't know how to delete ;)
[04:20] <\sh> thierry_: just upload again :)
[04:21] <crimsun> d'oh, it is a different tar.gz
[04:21] <\sh> crimsun: as I said :)
[04:21] <thierry_> \sh : upload what gain?
[04:21] <\sh> crimsun: you don't mean the mail on ubuntu-users about "[Dapper-i386]  Package "cacti" error messages on install/uninstall & won't uninstall."
[04:22] <\sh> thierry_: libfxscintilla*
[04:22] <\sh> thierry_: if you need to
[04:22] <crimsun> \sh: yes, that one
[04:22] <thierry_> \sh : no no it just that I changed two times of package name so want that someone delete the old ones
[04:23] <\sh> thierry_: will look into it...
[04:24] <\sh> terminate called after throwing an instance of 'std::logic_error'
[04:24] <\sh>  what(): basic_string::_S_construct NULL not valid
[04:24] <\sh> Aborted
[04:24] <\sh> crimsun: but this looks more like an dpkg or debconf problem
[04:29] <crimsun> \sh: that's my impression, too, but I need to ensure it's not in my merge
[04:29] <\sh> crimsun: what is the build error because of ttf-dejavu?
[04:29] <crimsun> \sh: not a build error, an uninstallable rrdtool
[04:30] <crimsun> \sh: which is another issue that puzzles me: the user _somehow_ got cacti to attempt to upgrade despite the unmet dependency in rrdtool
[04:31] <crimsun> the whole thing just stinks of --force-depends and such
[04:32] <\sh> crimsun: yepp
[04:32] <\sh> let me fix librrd2 first
[04:34] <crimsun> \sh: great, thanks
[04:34] <\sh> crimsun: I move the build-dep towards our version, which should be the same somehow as debians, but 0ubuntu1
[04:35] <crimsun> \sh: yep, that's sufficient
[04:38] <Nafallo> hehe, "to reproduce, try register some domains".
[04:38] <Nafallo> :-)
[04:38] <\sh> lol
[04:46] <thierry_> is sunbird a too big package for cdbs?
[04:50] <dholbach> thierry_: why should it be?
[04:51] <thierry_> don't know... I tough cdbs was for small package only, anyway forget it, sunbird is far too complex for me
[04:51] <thierry_> dholbach : but I have a package be reviewed, would like to do it? I need one more advocate and it's ok to upload
[04:51] <thierry_> to be reviewed*
[04:52] <dholbach> no, cdbs should not be the issue
[04:52] <dholbach> about the review, not
[04:52] <dholbach> about the review, please ask somebody else - i was just about to leave
[04:52] <dholbach> sorry
[04:53] <thierry_> k no problem
[04:53] <thierry_> raphink : are you a MOTU?
[04:54] <raphink> not yet ;)
[04:54] <thierry_> slomo : could you review my package?
[04:54] <raphink> ;)
[04:56] <thierry_> siretart : could you review my package?
[05:58] <psusi> what is this buisness about compatibility levels I read about in the man pages for the dh_ scripts?  how do you check/set which level a package is using?
[05:59] <psusi> nevermind.... looks like compat contains a 4... that explains why dh_strip --dbg-package isn't doing what it should...
[06:01] <Yagisan> \sh: I'm about to head to bed, hopefully only thing left to do with wine is my changelog sed foo. I'll finish testing tommorow. Do I send you a debdiff, post a debdiff to malone, or upload to revu for comments ?
[06:06] <\sh> send me the debdiff
[06:12] <LaserJock> when is the MOTU meeting?
[06:13] <\sh> tomorrow?
[06:15] <siretart> boah, finally my laptop is running dapper, after near endless struggle with 2.6.15
[06:15] <siretart> only oops is broken like hell :/
[06:15] <siretart> hi Fuddl
[06:15] <Fuddl> hi siretart!
[06:16] <Fuddl> siretart: how's your foot?
[06:16] <siretart> Fuddl: better, thanks
[06:17] <mgalvin> hi all, non-package question... i started working on DapperFlight3 and would like to mention some high level notes about some of the more significant *verse improvements, is there anything you guys would like to see mentioned? I looked through the various reports and such but thought i would just ask anyway
[06:18] <Fuddl> siretart: that's good to year, hope you'll be as fast as usual, soon again ;)
[06:19] <Fuddl> siretart: btw. /me bought some cheap but f**cking loud party-speakers. first try-out will be on schloss-lan *smiiiile*
[06:19] <segfault> mgalvin: can you please ping me at segfault@ubuntu.com when its done? i'd like to translate it to pt_BR.
[06:21] <mgalvin> segfault: sure
[06:21] <segfault> thanks
[06:22] <mgalvin> np
[06:26] <Czessi> \sh: ping
[06:29] <dholbach> hey Fuddl
[06:30] <Fuddl> hi dholbach
[06:30] <Fuddl> dholbach: wasn't it you, who had a quake3 loki cd?
[06:30] <dholbach> Fuddl: no, i shouldn't think so :)
[06:31] <Fuddl> ah ok.... but somebody spoke to me in this channel, he/she had problems with quake3-data, installing from the loki quake3 cd...
[06:31] <Fuddl> who was it?!? HANDS UP! ;)
[06:31] <Gloubiboulga> Riddell, could you have a look at http://revu.tauware.de/details.py?upid=1468 again when you hot time? Thanks
[06:32] <\sh> Czessi: pong
[06:32] <Riddell> Gloubiboulga: yes, but not just now so poke me again if I forget
[06:32] <Gloubiboulga> Riddell, np
[06:32] <Czessi> \sh: hi \sh
[06:33] <\sh> Czessi: did you read the remarks on kiso?
[06:33] <Czessi> \sh: in revu? yes i did
[06:37] <\sh> Czessi: can u fix it? I have the ok from sistpoty to upload...he will advocate later :)
[06:39] <Czessi> \sh: what must i fix? http://revu.tauware.de/details.py?upid=1464 the lintian overwrites?
[06:39] <\sh> Czessi: 1. the orig.tar.gz is changed...
[06:40] <\sh> Czessi: you changed the contents of the original upstream source tarball and repackaged it...in this case it shouldn't happen :)
[06:40] <\sh> Czessi: try to fix the issues in the orig source tree with patches or directly modify the debianized source tree and move the changes into diff.gz
[06:40] <Czessi> \sh: i build a completd new package and upload it the last night
[06:41] <\sh> Czessi: oh shit...I just didn't see it...damn blindness
[06:43] <Czessi> \sh: hehe, i will contact the author of kiso, that he fix the source problems in the next release
[06:44] <\sh> Czessi: why is this happening? what causes those broken files?
[06:44] <\sh> Czessi: could you remove them directly from source and move the removals into diff.gz...
[06:46] <\sh> grmpf
[06:46] <siretart> chninkel_away: I just uploaded your ifplugd patch, please check the buildlogs and close the bug afterwards
[06:53] <\sh> grampf..currently kdelibs4 is broken
[06:55] <\sh> Czessi: anyways..advocated..we can have a look later when kdelibs is installable again :)
[06:57] <Czessi> \sh: I wanted to delete the files, at the end of the build i became an error. cause debuild try to delete this files a second time
[06:58] <Kyral> Screen...mmm
[06:58] <Kyral> lol
[06:58] <\sh> Czessi: but what causes the creation of those files? the "autoreconfigure" call?
[07:02] <\sh> Czessi: are you whitelisted for dapper-changes?
[07:03] <\sh> Czessi: because you should get a "katie" mail when elmo moves your package out of NEW...and your name will be announced on dapper-changes..please document your work as well on your personal wiki page on wiki.ubuntu.com :)
[07:04] <Czessi> \sh: whitelisted?
[07:04] <\sh> Czessi: and congratulation for your first package in the official archives of ubuntu :)
[07:04] <\sh> Czessi: I just uploaded your package
[07:04] <Czessi> \sh: thanl
[07:04] <Gloubiboulga> bbl
[07:04] <Czessi> \sh: thanks and i update my Wiki page :)
[07:05] <\sh> Czessi: kewl...then we can go "The Way Of The MOTU" :)
[07:40] <crimsun> bed time after 84 hours
[07:40] <crimsun> *z
[07:41] <\sh> crimsun: good night sleep tight :)
[07:43] <markuman> crimsun: 84 hours ....what are you doing? good night ;-)
[07:53] <dholbach> poor crimsun - you rock!
[07:54] <\sh> crimsun: which list are you working on for the merges?
[07:58] <LaserJock> can I get somebody to look at a Makefile (http://paste.ubuntu-nl.org/6971) for me? I am trying to figure out if DESTDIR and PREFIX are used correctly
[08:00] <azeem> LaserJock: PREFIX should be configurable, if possible
[08:00] <azeem> is that program using autoconf?
[08:00] <LaserJock> no
[08:01] <LaserJock> it is just a make make install
[08:01] <azeem> then maybe it should default to /usr/local, and Ubuntu should patch that to say /usr
[08:01] <azeem> but that might be cosmetic
[08:01] <LaserJock> that is what I am doing ;-)
[08:02] <LaserJock> I pasted the patched Makefile
[08:03] <azeem> ah :)
[08:03] <azeem> I don't have time to look at the rest, but from a first glance, it looked OK
[08:03] <azeem> off to a party now, laters
[08:03] <LaserJock> cy azeem
[08:06] <\sh> Czessi: did you get a katie mail? kiso is just approved for NEW :)
[08:07] <\sh> someone, please tell seth that md5deep is uploaded
[08:08] <lfittl> \sh: Do you have some time to review a package?
[08:08] <\sh> lfittl: when I'm getting up again :) I wanted to sleep a couple of hours now....
[08:08] <lfittl> \sh: k, gn8 then ;)
[08:09] <\sh> lfittl: but I'm doing in the moment some more reviewing stuff :) while others are working on merges :) (normally it's the opposite :))
[08:10] <lfittl> \sh: well, the REVU list is long, so that's a good thing to do :)
[08:16] <raphink> \sh_away: :)
[08:17] <azeem> LaserJock: install -s strips the program while installing, it might be better to install unstripped and then let dh_strip handle it based on DEB_BUILD_OPTIONS
[08:19] <LaserJock> azeem: would that be something that I should patch or should upstream change that?
[08:19] <psusi> you should patch
[08:19] <azeem> you can ask upstream whether that change is acceptable
[08:20] <psusi> upstream wants it to strip when you build and install directly from source, which is generally correct
[08:20] <azeem> opinions probably vary on that, but I think normal automake/autoconf programs do not get installed stripped by default
[08:20] <psusi> they usually do, though sometimes there's a makefile variable that controls stripping
[08:22] <LaserJock> ok, I will patch it since I will already patch to change the PREFIX
[08:24] <LaserJock> anything else needing tweaking? Upstream is nice enough that he will include the changes I need into the next release.
[08:26] <Kyral> hmm
[08:26] <Kyral> is this worth packagaing?
[08:26] <Kyral> http://www.gnomefiles.org/app.php?soft_id=1065
[08:26] <Kyral> the deb he has listed isn't in the repos
[08:39] <Kyral> Can't hurt
[08:44] <raphink> bugs in LP about merges are confusin
[08:44] <raphink> hmm well actually no
[08:44] <raphink> it's just lucas' interface that lists bugs that have been fixed for previous merges
[08:44] <raphink> so this is confusing
[08:48] <Kyral> Always nice to ask Upstream before packaging something
[08:48] <Kyral> just in case
[08:49] <LaserJock> in case what?
[08:50] <raphink> anyone to sync packages?
[08:50] <raphink> yop Tonio_
[08:51] <Gloubiboulga> bye
[08:51] <Tonio_> raphink: re ;)
[08:51] <Kyral> LaserJock: In case they were gonna do it
[08:51] <raphink> I need someone to sync packages please :s
[08:51] <LaserJock> Kyral: that makes sense I guess
[08:52] <Kyral> I just randomly go through GNOMEFiles and look for things now lol
[08:53] <LaserJock> Kyral: me too although I am going through kde-apps.org as well since I installed kubuntu-desktop a while back
[08:53] <Kyral> Actually I have to email the upstream for Yamysqlfront and ask him when his next version is coming out...
[09:18] <hub> ajmitch: while you are here, why dotGNU when there is Mono? just curious
[09:28] <spacey_ki> argh, how does one get the latest source tree from a bazaar/arch ?
[09:29] <lifeless> moin
[09:29] <ogra_ibook> bzr get  ?
[09:30] <spacey_ki> ogra, baz
[09:30] <ogra_ibook> oh, bazaar
[09:31] <ogra_ibook> but baz get should work as well
[09:31] <spacey_ki> yeah just tried
[09:31] <spacey_ki> seems to do something
[09:31] <spacey_ki> yup
[09:31] <spacey_ki> great, thnx
[09:32] <tseng> ogra_ibook: hm did we switch to gnome-screensaver?
[09:32] <tseng> ogra_ibook: i see that xss is removed
[09:33] <ogra_ibook> we are about to, yes
[09:33] <tseng> coo
[09:33] <tseng> l
[09:33] <tseng> ive been using it for awhile
[09:33] <tseng> and g-p-m
[09:33] <tseng> gpm seems to suspend alot slower than just acpi-support
[09:34] <ogra_ibook> might be d-bus in the way
[09:35] <ogra_ibook> hmm, no, actually not
[09:35] <ogra_ibook> currently it uses gdm directly for suspend and hibernate ... shouldnt differ from the logout dialog
[09:44] <LaserJock> what would be the Debian versioning for a small change in packaging?
[09:44] <LaserJock> -X to -X+1 ?
[09:51] <slomo> LaserJock: yes... even for big changes in packaging :)
[09:52] <LaserJock> slomo: but not -X to -X.1 or something like that?
[09:53] <slomo> that's for NMU
[09:55] <LaserJock> oh, ok
[09:55] <slomo> why do you ask? :)
[09:55] <LaserJock> well, I just got my first package in Debian and I found a small mistake in debian/rules
[09:56] <LaserJock> I'm not sure if I should bother fixing it now or wait for a new upstream release
[09:56] <slomo> which package? ;) and how critical is the bug?
[09:58] <LaserJock> plotdrop and the bug is tiny (I think). I set up the makefile to use DESTDIR and for some reason my corresponding change to debian/rules didn't make it in.
[09:58] <LaserJock> It doesn't change anything as far as the binary package is concerned
[09:59] <slomo> then i would wait for the next upstream version
[09:59] <slomo> is it already out of NEW?
[09:59] <LaserJock> no, I don't think so
[09:59] <LaserJock> I just got an email from katie
[10:00] <slomo> hehe
[10:02] <siretart> huhu slomo, hi LaserJock
[10:02] <slomo> hi siretart :)
[10:02] <LaserJock> hi siretart
[10:02] <siretart> slomo: did you catch siggi?
[10:03] <slomo> damn... i forgot to write the mail :( sorry...
[10:04] <siretart> no problem
[10:05] <slomo> i hate my memory... i need a memory upgrade ;) i'll try to write it tomorrow... or do you want to do it now?
[10:07] <siretart> I'm currently busy, I'll do it tomorrow aswell..
[10:07] <siretart> I'd do it tomorrow..
[10:10] <slomo> siretart: hmm, then you better do it... i could do it only in the evening :/
[10:10] <lucas> hi all
[10:11] <LaserJock> hi lucas
[10:21] <thierry_> anyone who could review my package for a second advocate? http://revu.tauware.de/details.py?upid=1470
[10:22] <lfittl> dholbach: ping
[10:31] <LaserJock> I am interested in if/how people use revision control for packaging
[10:32] <siretart> LaserJock: I like svn and svn-buildpackage
[10:34] <LaserJock> ok, that sounds about like what I want to do. I've just never set up a svn repo before :(
[10:36] <siretart> thierry_: done
[10:39] <LaserJock> siretart: what about bzr, would that work well for packages do you think?
[10:40] <siretart> LaserJock: I'd still love to see a 'bzr-buildpackage' and it already has some very promising aspects. But imo, it lacks some more features which I'd really love to see for packaging issues
[10:44] <LaserJock> ok, so do you make a svn repo that holds all your packages and then checkout a local copy when you want to work on something?
[10:44] <dholbach> lfittl: pong
[10:45] <thierry_> siretart : with 2 advocate I get commited to universe no? what else could I need?
[10:46] <lfittl> siretart: do you have some time to review http://revu.tauware.de/details.py?upid=1467 ?
[10:52] <siretart> thierry_: I just uploaded it for you. if you have been whitelisted, you should get an email from katie
[10:53] <ajmitch> morning all
[10:53] <poimen> ?
[10:53] <siretart> lfittl: nautilus svn scripts? what that?
[10:53] <siretart> huhu ajmitch
[10:53] <hub> hey ajmitch
[10:53] <ajmitch> hey siretart, hub, how's it going?
[10:53] <lfittl> siretart: as the name says, nautilus scripts to manage a subversion working copy
[10:53] <hub> ajmitch: fine
[10:54] <siretart> huhu hub!
[10:54] <ajmitch> LaserJock: I've started using bzr for nearly all my packages
[10:54] <siretart> lfittl: something like tortoise for windows?
[10:54] <tseng> ajmitch++
[10:54] <lfittl> siretart: exactly
[10:54] <siretart> ajmitch: do you use nested debian/ dir?
[10:54] <ajmitch> siretart: yes
[10:55] <ajmitch> sometimes that's the only branch I have
[10:55] <ajmitch> eek, why did jane attach a large pdf to her mail? :)
[10:56] <siretart> to some list?
[10:57] <ajmitch> to ubuntu-devel-announce
[10:59] <ogra_ibook> ajmitch, because evince starts faster than ooo2 ;)
[10:59] <ajmitch> obviously
[10:59] <LaserJock> ajmitch: do you know of any documentation on using bzr for packaging?
[10:59] <ajmitch> I think vista on an old pentium would start quicker than ooo2
[11:00] <ogra_ibook> lol
[11:00] <ajmitch> LaserJock: nope, there's very little to it
[11:00] <lucas> who is usually doing the FTBFS checks ?
[11:01] <LaserJock> ajmitch: ok, well I feel totally lost, should I maybe try svn until I know what I'm doing?
[11:03] <ajmitch> LaserJock: if you want, but bzr it stuff like bzr init; bzr add; bzr commit -m 'Importing that debian packaging stuff'
[11:03] <ajmitch> in the debian/ dir
[11:03] <lfittl> siretart: just noticed a small debian/copyright bug and uploaded the package again
[11:09] <raphink> lucas: hi
[11:09] <raphink> lucas: the LP column on your merges table is pretty nice, but it lists the bugs reported and already fixed on previous merges, which is confusing.
[11:10] <LaserJock> ajmitch: so do you have a bzr repo for each upstream version? or just one for each package
[11:10] <lucas> raphink: I just use the info sistpoty gave me ;)
[11:10] <raphink> lucas: hehe ok ;)
[11:10] <siretart> ajmitch: how do you share your nested bzr archives?
[11:10] <raphink> lucas: well just lettin gyou know I find this confusing
[11:11] <raphink> because it doesn't help finding out whether a package is already being merged or not
[11:11] <siretart> ajmitch: I find it very annoying that bzr get $url doesn't fetch nested archives :(
[11:12] <LaserJock> btw, I found a good svn-buildpackage wiki at http://workaround.org/moin/SvnBuildpackage
[11:13] <siretart> yes, that one is quite nice
[11:14] <lucas> raphink: can you give an example of bug where it is a problem ?
[11:14] <lucas> err of package
[11:14] <raphink> lucas: example: pstoedit
[11:14] <raphink> the 3rd in the list of merges to do
[11:15] <raphink> https://launchpad.net/distros/ubuntu/+source/pstoedit/+bug/5034
[11:15] <Ubugtu> Malone bug 5034: "pstoedit: libstdc++ new allocator build" Fix req. for: pstoedit (Ubuntu), Severity: Normal, Assigned to: MOTU Merge Team, Status: Fix Committed http://launchpad.net/bugs/5034
[11:15] <raphink> this bug is months old
[11:15] <raphink> and fixed
[11:16] <lucas> it's a problem with sistpoty's database
[11:16] <raphink> oki
[11:16] <lucas> it also shows as Accepted on http://tiber.tauware.de/~sistpoty/MoM/index.py?state=accepted
[11:16] <ajmitch> LaserJock: I branch off a new debian/ branch for a new upstream version at the moment
[11:16] <ajmitch> siretart: sharing is something I'm not too concerned about at the moment :)
[11:17] <ajmitch> since it's mostly for me to keep track of things
[11:18] <siretart> yes. for local use, bzr is indeed nice. but for shareing and collaborating I think svn-buildpackage is best
[11:18] <ajmitch> hm
[11:18] <ajmitch> short notice for motu meeting
[11:18] <siretart> perhaps darcs-buildpackage, but I'm not that used to darcs
[11:18] <LaserJock> so will there be a bzr-buildpackage?
[11:18] <ajmitch> yes, some day
[11:20] <lucas> raphink: please report the problem to sistpoty
[11:20] <raphink> hmm ok
[11:20] <lucas> I can't do any filtering for this
[11:20] <raphink> when he's here
[11:23] <siretart> lfittl: I read you wanted to change the name of the motutools package? whats the new name?
[11:24] <LaserJock> I think I hit a new personal record of 21 firefox tabs open at the same time ;-)
[11:24] <lfittl> siretart: where did you read that?
[11:24] <siretart> argl
[11:24] <LaserJock> siretart: I think you mean lucas
[11:24] <siretart> s/lfittl/lucas/
[11:24] <siretart> yes
[11:24] <lfittl> k :)
[11:24] <thierry_> siretart : how do I get whitelisted?
[11:25] <lfittl> thierry_: https://wiki.ubuntu.com/Uploads
[11:25] <lucas> ah
[11:25] <siretart> thierry_: ask elmo, better via email
[11:25] <lucas> multidistrotools
[11:25] <lucas> (alias mdt)
[11:25] <lucas> but it's not uploaded to REVU
[11:26] <lfittl> thierry_: send a request to get whitelisted to keyring@ubuntu.com
[11:26] <siretart> lucas: do I assume right, you are motu but not added yet to the keyring?
[11:26] <lucas> I'm a member, not a ubuntu-dev memeber
[11:26] <siretart> ah, ok
[11:26] <poimen> hi all
[11:27] <poimen> how can be xdvdshrink added to the multiverse rep?
[11:27] <poimen> i meant universe
[11:27] <thierry_> lfittl : if I already sent my gpg key to keyring@ubuntu.com before, I am whitelisted?
[11:28] <lfittl> thierry: you should get a notification that tells you your RT ticket number (if I remember correctly), and that ticket will be processed by elmo
[11:30] <LaserJock> don't you need to email upload@ubuntu.com to get whitelisted?
[11:31] <thierry_> siretart : what is the elmo e-mail?
[11:31] <siretart> I'd guess elmo gets the email anyway
[11:32] <lucas> james.troup@u.c
[11:33] <lfittl> LaserJock: you are right, that was upload@ubuntu.com and not keyring@ubuntu.com :)
[11:34] <LaserJock> lucas: I don't know that your just added Meeting item is relevent for MOTU since it is community maintained
[11:34] <lfittl> siretart: did you found some time to review my package, or should I ask you tomorrow?
[11:34] <LaserJock> or did you have something else in minde?
[11:35] <lucas> LaserJock: I think uploaders should understand that they cannot just upload a package and then go away
[11:35] <lucas> it's dangerous
[11:35] <siretart> lfittl: just a sek
[11:35] <lucas> we already have >300 packages in universe which are not in debian
[11:35] <lfittl> siretart: k :)
[11:36] <lucas> and we don't have any orphaning process, or way to determine which packages are important
[11:36] <LaserJock> I am more concerned with what happens when we want to get those >300 packages into debian, who is going to be the maintainer?
[11:36] <lucas> we don't do security support, but it doesn't mean universe packages should just be big black holes
[11:36] <lucas> some might need to be dropped in the process
[11:37] <LaserJock> I wouldn't think it would be a problem so much for us since somebody will come along to take care of orphaned packages I suppose
[11:37] <LaserJock> but I think having teams would help
[11:39] <LaserJock> I started looking at this issue yesterday (thanks to mdt) for the MOTUScience team
[11:39] <chninkel> siretart: thanks for the ifplugd upload, where can I check the build logs ?
[11:40] <LaserJock> I got a package that hadn't built in over a year working again (actually Riddell did it)
[11:41] <LaserJock> but it came in through apt-get.org so there it wasn't being maintained
[11:41] <chninkel> pending upload bug status doesn't exist anymore ? replaced by fix commited ?
[11:41] <lucas> I think so
[11:41] <siretart> chninkel: http://people.ubuntu.com/~lamont/buildLogs
[11:43] <chninkel> siretart: thks
[11:46] <siretart> lfittl: did you see this one? http://revu.tauware.de/revu1-incoming/nautilus-svn-scripts-0601101710/lintian
[11:47] <lfittl> siretart: I was told by several people that cdbs and debhelper should be build-depends because of debian/rules clean
[11:47] <lfittl> and that lintian is wrong in this case
[11:47] <siretart> ah, ok
[11:48] <siretart> ok, I'm happy. will advocat
[11:48] <siretart> e
[11:49] <lfittl> thanks :)
[11:49] <ajmitch> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344609
[11:49] <Ubugtu> Debian bug 344609: "better build-depends-indep check" Package: lintian, Version: lintian/1.23.14., Maintainer: Debian Lintian Maintainers  http://bugs.debian.org/344609
[11:49] <ajmitch> marked as pending upload change for lintian
[11:49] <dholbach> hope we get this in before uvf ;)
[11:49] <ajmitch> why, it's only a check :)
[11:50] <lfittl> siretart: make sure you upload the newer package, as you commented on the old one
[11:51] <siretart> lfittl: oh, thanks for noticing
[11:52] <lucas> who is Yann on the wiki ?
[11:52] <lucas> raphink: ?
[11:52] <raphink> yes lucas ?
[11:52] <chninkel> it's me
[11:54] <siretart> lfittl: just uploaded
[11:54] <lfittl> siretart: thanks :)
[11:57] <lucas> ah
[11:57] <lucas> chninkel: is it motureviewers
[11:57] <lucas> on MOTUMerging
[11:58] <lucas> fixing it, but wanting to make sure you knew your spelling was wrong
[11:58] <chninkel> lucas: I just changed PendingUpload to Fix Commited
[11:58] <lucas> I saw one of your bugs which was Fix Committed but not assigned to motureviewers
[11:58] <lucas> ah ok
[11:58] <lucas> no pb
[11:58] <chninkel> lucas: didn't change anything else... or did I make a mistake ?
[11:59] <chninkel> lucas: which bug ?
[11:59] <lucas> it's no big deal anyway :-)
[11:59] <lucas> I dunno
[12:00] <chninkel> lucas: oups I forgot a t in committed
[12:00] <lucas> ah
[12:00] <lucas> fix it ;)
[12:01] <chninkel> lucas: will fix the motureviewers mispelling also
[12:01] <lucas> I did it I think
[12:01] <lucas> https://launchpad.net/distros/ubuntu/+source/gnome-backgrounds/+bug/6684
[12:01] <Ubugtu> Malone bug 6684: "backgrounds (Ubuntu) - gnome-backgrounds: merge new debian version" Fix req. for: gnome-backgrounds (Ubuntu), Severity: Normal, Assigned to: MOTU Merge Team, Status: Unconfirmed http://launchpad.net/bugs/6684
[12:01] <lucas> I think you certified it was a sync, but forgot to fix the status/Assignment
[12:01] <lucas> raphink: same for you here: https://launchpad.net/distros/ubuntu/+source/usbview/+bug/6661
[12:02] <Ubugtu> Malone bug 6661: "usbview: merge new debian version" Fix req. for: usbview (Ubuntu), Severity: Normal, Assigned to: MOTU Merge Team, Status: Unconfirmed http://launchpad.net/bugs/6661
[12:02] <raphink> oh thanks lucas I will
[12:02] <raphink> I thought lpbugs would do it