[12:49] <bddebian> re
[12:50] <slomo_> hi bddebian
[12:50] <bddebian> Heya slomo_
[12:51] <bddebian> slomo_: Got any others for me? :-)
[12:56] <slomo_> bddebian: choose one and tell me :)
[12:56] <bddebian> Heh
[01:10] <slomo_> Riddell: please push your hal changes to the bzr branch on LP
[01:11] <bddebian> slomo_: Ack, what happened to the list?
[01:11] <slomo_> it works? :)
[01:12] <bddebian> I get an empty page
[01:12] <slomo_> refresh... maybe it was regenerated last time you tried :)
[01:12] <bddebian> Hmm, now it's back
[01:14] <slomo_> babytrans, chaplin, echelon, gtkpod-aac, ksubtitleripper, mpglen, mythplugins, mythtv, pgmfindclip, qdvdauthor, qvamps, ripmake, submux-dvd, subtitleripper, video-dvdrip, xvattr, xvid4conf
[01:15] <slomo_> i think those are all we maybe want
[01:15] <slomo_> not sure about mythtv*
[01:15] <slomo_> you might want to ask mdz for mythtv
[01:15] <slomo_> and after those are done we could look together at the NEW list
[01:16] <bddebian> mdz hates me :-)
[01:17] <azeem> are you sure?
[01:17] <bddebian> No :)
[01:18] <slomo_> mdz would thank you for caring for this package
[01:18] <slomo_> nobody looked at it for a very long time and he was too busy afaik
[01:19] <Riddell> slomo_: where's that?
[01:19] <bddebian> What, mythtv?  I was looking at it back in breezy but I think someone else was checking it out
[01:20] <slomo_> Riddell: https://launchpad.net/products/hal/+branches
[01:22] <crimsun> bddebian: I /think/ FunnyLookinHat was looking at mythtv 0.19x
[01:22] <bddebian> OK
[01:31] <bmonty> here is a good error message:
[01:31] <bmonty> *** YOU'RE USING autoconf (GNU Autoconf) 2.60.
[01:31] <bmonty> *** KDE requires autoconf 2.53 or newer
[01:32] <toma> bmonty: kde fixed that, it is a simple patch
[01:32] <slomo_> there was a thread on debian-devel about this already... seems like most of kde checks for autoconf 2.5X
[01:33] <bmonty> I'm trying to build kboincspy...is it a KDE patch, or a per-package patch?
[01:33] <toma> per-package, the admin folder needs a patch
[01:34] <bmonty> toma: do you have a pointer to the patch?
[01:35] <slomo_> http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
[01:35] <slomo_> bmonty: ^
[01:36] <bmonty> thanks slomo_ and toma
[01:36] <toma> np
[01:51] <toma> if i create package B with version 1~dapper1 and package B depends on A>=1~dapper1, at installation time it complains package A is not >=1. (loosing the ~dapper1 part). Why is that?
[01:52] <bmonty> toma: it can't find your package B, do you have it in a local repo or something?
[01:53] <toma> Yes, it is installed
[01:53] <slomo_> toma: 1.2.3~1 is less than 1.2.3
[01:53] <bmonty> are you using a pbuilder?
[01:53] <slomo_> that's the use of the ~
[01:53] <toma> slomo_: yes, so i set a dependency on ~1
[01:54] <toma> made a typo, the first B should be an A btw
[01:56] <bddebian> slomo_: babytrans is a sync
[01:57] <slomo_> bddebian: so ask for one :)
[01:57] <bddebian> slomo_: Already done
[01:58] <slomo_> bddebian: thanks :)
[02:05] <bddebian> slomo_: chaplin sync requested also
[02:06] <slomo_> bddebian: thanks :) there should really be karma for uploads... you would probably be in the top 5 :)
[02:08] <crimsun> no kidding.
[02:09] <slomo_> who wants to file a wishlist bug on launchpad? :)
[02:09] <crimsun> you do!
[02:15] <slomo_> ok, if someone cares: bug #54596 :)
[02:15] <Ubugtu> Malone bug 54596 in launchpad "karma for uploads" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/54596
[02:16] <slomo_> crimsun: do you also know a bit about the alsa kernel modules?
[02:18] <crimsun> slomo_: which ones?
[02:18] <slomo_> crimsun: snd-ymfpci
[02:19] <crimsun> slomo_: not my usual stomping grounds, but I can try. What's the issue(s)?
[02:19] <slomo_> crimsun: bug #51281
[02:19] <Ubugtu> Malone bug 51281 in linux-source-2.6.17 "snd-ymfpci fails to load at boot, works fine later" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/51281
[02:21] <crimsun> hmm, I'll need to look at the source later to check if does strange spinlock* stuff.
[02:22] <crimsun> if it does ^
[02:22] <slomo_> thanks crimsun :)
[02:22] <crimsun> seems to be an irq issue; it's probably not calling spinlock_irq{save,restore} appropriately
[02:25] <slomo_> crimsun: if you have any patches for me to try... :)
[02:26] <crimsun> right, I'll have to look later this week (already subbed ubuntu-audio)
[02:27] <slomo_> crimsun: i won't be online from the 2nd until the 10th or something, no need to hurry :)
[02:27] <ajmitch> hi
[02:27] <bmonty> hey ajmitch
[02:27] <crimsun> slomo_: ok.
[02:27] <crimsun> morning, ajmitch; evening, bmonty
[02:28] <bmonty> hi crimsun
[02:29] <bmonty> slomo_, toma: that KDE patch worked great, thanks
[02:29] <slomo_> bmonty: np :)
[02:45] <bddebian> Heya ajmitch, bmonty, crimsun
[02:45] <bmonty> evening bddebian
[02:46] <bddebian> bmonty: Are you going to hit your merges?
[02:46] <bmonty> bddebian: thats what I'm doing right now :)
[02:47] <bddebian> Ah cool, thanks
[02:50] <bddebian> slomo_: echelon sync requested
[02:50] <bddebian> Damn the archive admins are going to kill me :-)
[02:51] <slomo_> bddebian: i already have a million open sync requests and NEW is going to explode soon too ;)
[02:51] <Kyral> Yo
[03:08] <bddebian> Heya Kyral
[03:45] <zul> hmm?
[03:49] <bmonty> grrr....a package I already merged is back on the list :(
[03:49] <ajmitch> that happens
[03:50] <bmonty> ajmitch: for your SoC project...what do you think of making sure the network is up before udev assigns perms to the devices it creates?
[03:50] <bmonty> is that possible/
[03:50] <bmonty> ?
[03:51] <bmonty> I've found some very subtle breakage from the setup I have
[03:51] <ajmitch> it's hard
[03:51] <ajmitch> I'd have to ask keybuk about it
[03:51] <ajmitch> but I doubt it'll be easy
[03:51] <bmonty> if it could be done, it would make life a lot easier
[03:51] <bmonty> otherwise you are stuck with gids in the udev perm files, would ubuntu ship with that?
[03:52] <bmonty> or your package would have to change them all :)
[03:52] <ajmitch> eeevil
[03:52] <bmonty> maybe have something like a udev and udev-sso packages?
[03:52] <bmonty> that conflict with each other
[03:53] <ajmitch> that's just getting nasty
[03:53] <Hobbsee> hi all
[03:53] <ajmitch> hello
[03:54] <Laser_away> hmm, -devel just seems to go from one annoying thread to the next
[03:54] <bmonty> Laser_away: you mean like the thread on mono?
[03:56] <Laser_away> yeah
[03:56] <bmonty> Laser_away: hi BTW :)
[03:56] <Hobbsee> Laser_away: yeah, i noticed that.  remind me why i shouldnt have rejoined
[03:56] <Hobbsee> Laser_away: and you're clearly *not* away :P
[03:56] <Laser_away> we moved from zeroconf to tracker to zeroconf to mono to ...
[03:57] <Laser_away> bmonty: hi
[03:57] <Laser_away> Hobbsee: gmane is a good idea :-)
[03:58] <^ohoel> slomo_: you wouldnt have the -ubuntu3 package of mplayer handy would you?
[04:05] <bmonty> what is a good way to easily strip the .DEBIAN off a bunch of files?
[04:07] <bddebian> Heya Hobbsee
[04:08] <zul> Hobbsee: something like borland c++?
[04:08] <ajmitch> bmonty: a for loop in bash & sed & mv, or use mmv
[04:09] <Hobbsee> zul: dev c++
[04:09] <Hobbsee> 3.4.2 compiler, from 3.3.3
[04:09] <Hobbsee> ajmitch: what's mmv?
[04:10] <ajmitch> apt-cache show mmv
[04:11] <Hobbsee> ajmitch: oh cool
[04:18] <Hobbsee> siretart: did you want to request a sync for oops, or did you want me to do it?  i'm just browsing thru the merges list
[04:22] <bddebian> Heya Laser_away
[04:27] <Hobbsee> siretart: dont worry.  seems to ftbfs.
[04:28] <bddebian> Hobbsee: What does?
[04:28] <Hobbsee> bddebian: oops
[04:28] <bddebian> Ah
[04:41] <bddebian> Heya imbrandon
[04:42] <imbrandon> heya bddebian
[04:42] <imbrandon> ;)
[04:42] <imbrandon> how go's it tongiht
[04:46] <bddebian> OK thanks, you?
[04:56] <zul> night..
[04:56] <bddebian> Gnight zul
[05:04] <bmonty> night all
[05:07] <bddebian> Gnight bmonty_away
[05:08] <ajmitch> bddebian: btw, I'm doing some of charles majola's merges
[05:08] <ajmitch> those that matter, anyway
[05:09] <bddebian> ?
[05:09] <ajmitch> !
[05:09] <ubotu> I know nothing about ! - try searching http://bots.ubuntulinux.nl/factoids.cgi?db=ubuntu
[05:09] <bddebian> Oh shut up ubotu :-)
[05:11] <bddebian> FunnyLookinHat: ping?
[05:23] <bddebian> Wow, oops is jacked
[06:40] <bddebian> Gnight folks
[08:08] <imbrandon> ajmitch , crimsun , either one ping? ( sorry for the ping in -devel )
[08:08] <imbrandon> thought i was in here
[08:09] <crimsun> hi.
[08:10] <imbrandon> heya crimsun i got a question , i dont think you can give me a definate awnser but i would like your input since your more experinced in FOSS than I
[08:10] <imbrandon> ok ....
[08:11] <imbrandon> there is an upstream project i put into ubuntu but upstream is unresponsive after weeks of emails but i have pactches i would like to see everone get ( including ubuntu )
[08:11] <imbrandon> what would be the "right way" to go about it? a fork ? and i just stick my own repo up on sf.net or somesuch ?
[08:12] <imbrandon> i'm not a sf.net fan but you get the idea
[08:12] <crimsun> imbrandon: the best solution, particularly if the project has a public mailing list, is to break out your patches into logically applicable (small) pieces and attach them to e-mails sent to the public mailing list.
[08:13] <imbrandon> ahh no ther is no public list, tbh its a small project not used by many i dont think
[08:13] <imbrandon> but is very usefull and thus far uptodate but there are things i have inproved ( its only a perl script in reality )
[08:13] <imbrandon> the apt-mirror thing specificly is what i'm talking aobut
[08:14] <imbrandon> but yea i have sent the patches to the current maintainer and qurey emails reguarding if he is still actively maintaing it etc
[08:14] <imbrandon> and no response ( although the email dont bounce either )
[08:15] <crimsun> my approach is fairly "anti-fork", meaning that there doesn't seem to be a reason to "fork" apt-mirror. Instead I would host a page providing links to my patches for apt-proxy. Perhaps at a later date, you may take up upstream maintenance of the project, whereupon you'll become 'upstream' upstream.
[08:15] <crimsun> On the other hand, real life often gets in the way of a part-time project, so give it a couple months before doing anything like that.
[08:15] <crimsun> s/apt-proxy/apt-mirror/
[08:16] <imbrandon> right ok, so for now just host a page somewhere with patches to the sf proj and include them in ubuntu and post on the sf page bboard ( that still seems semi active ) pointing ppl to the patches if they want them ?
[08:16] <crimsun> well, if it's a sf project it should have a bug tracker, no?
[08:16] <crimsun> you can file bugs in that bug tracker and attach your patches to them.
[08:16] <imbrandon> yes and i have fixed all open bugs so far
[08:16] <imbrandon> and a few not listed
[08:16] <imbrandon> ahh ok
[08:17] <imbrandon> sounds like a good plan
[08:17] <imbrandon> then revisit in a few months if nothing comes of it right ?
[08:17] <imbrandon> ( the idea )
[08:17] <crimsun> I would also file bugs in Debian's BTS with the same "attach patch" idea.
[08:17] <crimsun> (and please fix the broken versioning!)
[08:17] <imbrandon> yea i dont really like forks either, just not had much experince with this kinda thing
[08:18] <crimsun> frankly there's no reason to fork, since if maintenance is the real issue, and you have resources to devote to maintaining it, you could become the upstream maintainer in the future.
[08:18] <imbrandon> yea definatley but why debian bts , its not in debian yet, but i WOULD like to see it get into debian just havent looked into getting someone to sponsor me
[08:18] <ajmitch> there are random DDs floating around
[08:19] <crimsun> ah, ok. I was operating under the assumption that it was in Debian, but I remember the package now.
[08:19] <imbrandon> yea i just havent looked into it yet, ubuntu was my first foray into the debian world ( was a suse guy before here )
[08:19] <imbrandon> yea its only in ubuntu and sf.net
[08:19] <imbrandon> afaik
[08:20] <imbrandon> unless it very reciently made it into unstable from someone else
[08:21] <imbrandon> ok here is my .plan then i guess, clean up my patches a bit and attache them to the sf tracker , also get them updated in ubuntu ( thats the easy part ) then look into someone sponsoring it into unstable
[08:21] <imbrandon> that pretty much what your saying would be the "right thing" atm ?
[08:21] <crimsun> yes
[08:21] <imbrandon> kk sounds good
[08:23] <imbrandon> crimsun / ajmitch thx btw like i said some things i'm just ignorant on ;)
[08:23] <crimsun> s/ignorant/newer/
[08:23] <imbrandon> heheh yea
[08:27] <ajmitch> crimsun: I don't know, ignorant can be accurate - it's just a state of not knowing something yet :)
[08:28] <ajmitch> hey dholbach
[08:28] <crimsun> ajmitch: true :)
[08:28] <crimsun> 'lo dholbach
[08:28] <dholbach> good morning
[08:28] <dholbach> hey ajmitch, crimsun!
[08:29] <imbrandon> moins dholbach
[08:29] <dholbach> hey imbrandon
[08:30] <Hobbsee> hi dholbach!
[08:30] <dholbach> hey Hobbsee
[09:22] <bjp> goodmorning everybody!
[11:15] <phanatic> morning
[11:17] <Gloubiboulga> morning phanatic
[11:17] <phanatic> hi Gloubiboulga
[11:38] <frandavid100> hiya
[11:39] <frandavid100> where could I get the packaging guide in pdf? https://help.ubuntu.com/pdf/ubuntu/C/packagingguide.pdf is not available, and I'd rather print it out than reading the whole thing onscreen
[11:40] <rob> you should be able to find it in the Ubuntu help menu, under System I think
[11:40] <rob> but it will be docbook, which is not what you want
[11:40] <rob> help.u.c seems to be down for me too
[11:41] <rob> you can buy a professionally printed copy at lulu.com though, pretty cheap
[11:41] <rob> $US6 + postage..
[11:41] <rob> ish
[11:41] <rob> or you could just wait until the site comes back up :)
[11:42] <frandavid100> yep I think I'll do that
[11:42] <frandavid100> how long does it take to learn how to package stuff anyway? considering I'm quite a noob
[11:43] <frandavid100> I'd like to contribute, but I don't have too much time or talent for IT
[11:43] <frandavid100> I mean, can I do a decent job with just some basic knowledge, or should I learn like hundreds of terms I don't know now?
[11:46] <Gloubiboulga> you hve to learn, but not hundred of terms
[11:46] <Gloubiboulga> hundreds
[11:46] <frandavid100> I wouldn't like to bite more than I can chew
[11:47] <frandavid100> anyway I'm reading the guide now
[11:47] <frandavid100> hopefully I'll learn something useful :)
[11:47] <Gloubiboulga> I'm sure you will :)
[12:03] <zakame> hi
[12:08] <frandavid100> I have a doubt with the part about creating a pbuilder... if I want any packages I create to be included in Edgy, must I create a special pebuilder?
[12:09] <Gloubiboulga> an edgy pbuilder :)
[12:10] <frandavid100> aham... so unless I do this, any packages I create would be essentially useless as long as MOTU are concerned right?
[12:11] <zakame> not really
[12:11] <Gloubiboulga> hi zakame
[12:11] <zakame> a pbuilder-built package serves as a guarantee that a package can be built against a particular suite
[12:11] <zakame> hi Gloubiboulga :)
[12:12] <frandavid100> sorry to be a nuisance... but, for example, supposing I want this package on the official repos: http://timesaver.sourceforge.net/
[12:13] <frandavid100> the right thing to do would be to build it, then hand it over to you guys, right?
[12:16] <frandavid100> but obviously it should be compiled for Edgy because Dapper repos are closed already
[12:16] <frandavid100> am I right?
[12:18] <zakame> yup, that pkg will go to edgy
[12:18] <zakame> if it has some security fixes against the previous version, it might make it into dapper-security or d-updates though
[12:21] <frandavid100> I was thinking about a previously inexistant package, so it would be backports at most
[12:22] <frandavid100> so, where it says sudo pbuilder create --distribution <distro>, would <distro>=<edgy>?
[12:23] <Gloubiboulga> if you're using edgy, yes
[12:24] <Gloubiboulga> on dapper it'll fail, since the dapper pbuilder doesn't know about edgy
[12:24] <frandavid100> actually I'm on dapper, the guide says "If you want to create a pbuilder for a release newer than the one you currently have installed"
[12:25] <Gloubiboulga> on dapper you can create a dapper chroot, then dist-upgrade it
[12:26] <Gloubiboulga> s/chroot/pbuilder
[12:27] <frandavid100> right, I'm getting really lost now. Let me further look at the guide to have a wider view, I don't want to bother you with basic questions :S
[12:27] <Gloubiboulga> ok, but you don't bother us ;)
[12:28] <frandavid100> I could of course upgrade my system to edgy... do you think it's safe enough already?
[12:28] <frandavid100> I've been tempted
[12:29] <Gloubiboulga> I'm running edgy, but really you can keep dapper to build edgy packages
[12:30] <tseng> not _really_.
[12:31] <Gloubiboulga> tseng, "not _really_." for testing?
[12:32] <frandavid100> I'll install it anyway, I started my holidays already so I can afford my computer not to work properly.
[12:32] <tseng> unless you are religiously testing in a chroot with an xnest
[12:32] <tseng> not _really_
[12:33] <Gloubiboulga> right :)
[12:33] <frandavid100> gotta go guys, thank a lot for your patience and I'll see yoy later... (and I hope I'll know what a chroot is by then)
[12:33] <frandavid100> bye!
[02:33] <Hobbsee> hi all
[03:45] <bddebian> Heya gang
[04:44] <Gloubiboulga> hi Hobbsee, hi bddebian
[04:44] <Hobbsee> hey Gloubiboulga :)
[04:45] <Toadstool> good $time_of_the_day everybody :)
[04:45] <bddebian> Heya Gloubiboulga, Toadstool
[04:46] <Gloubiboulga> good 16:46 Toadstool
[04:46] <bddebian> Hi Yagisan
[04:46] <Toadstool> Gloubiboulga: :p
[04:47] <Yagisan> bddebian, have you noticed that edgys mplayer crashes more often on dvd's ? I think it's because of ffmpeg
[04:47] <slomo_> Yagisan: yes that's known
[04:48] <slomo_> Yagisan: we need a newer ffmpeg
[04:51] <Yagisan> slomo_, ah. ok, no need for me to let you know then ;) and of course, there is no newer ffmpeg @ debian
[04:51] <slomo_> Yagisan: should be soon
[04:51] <Hobbsee> any REVU admins around?  maybe raphink?
[04:51] <raphink> yep
[04:52] <Hobbsee> raphink: can you delete amarok_1.4.2beta1-0ubuntu1* for me please?
[04:52] <Hobbsee> raphink: realised i uploaded it natively, and cancelled the upload without thinking
[04:52] <raphink> sure
[04:52] <Hobbsee> raphink: thanks
[04:53] <Yagisan> slomo_, hope so. I'm looking forward to comparing new libavcodec & xvid soon
[04:53] <raphink> done
[04:53] <Hobbsee> raphink: thanks a lot :)
[04:58] <Hobbsee> raphink: sorry, can you repeat that please?
[04:59] <raphink> repeat what??
[04:59] <raphink> oh
[04:59] <raphink> ok
[04:59] <raphink> done
[05:00] <Hobbsee> raphink: sorry...i just figured the bug out, so canned the upload
[05:00] <raphink> ok
[05:01] <Gloubiboulga> *long sigh*, girls... :p
[05:01] <Hobbsee> Gloubiboulga: :P
[05:02] <Hobbsee> Gloubiboulga: no, *long sigh* @ upstream maintainers who go and rename things.  seems that the FTBFS was easier to fix than i'd first thought
[05:02] <Gloubiboulga> hehe
[05:07] <Yagisan> Hobbsee, but we like renaming things
[05:08] <Hobbsee> Yagisan: heh
[05:08] <Yagisan> Hobbsee, I even changed a whole build system without notice
[05:08] <Hobbsee> Yagisan: heh.  they did that too, i think
[05:09] <Hobbsee> well, changed from needing automake1.9 to automake1.7
[05:09] <Yagisan> Hobbsee, I stripped autotools out compltely
[05:10] <Hobbsee> Yagisan: nice
[05:10] <Yagisan> but I updated the documemnation on how to build it. Nobody read the docs though
[05:10] <Hobbsee> heh
[05:16] <slomo_> bddebian: ok so just get the packages from marillat :)
[05:20] <bddebian> :-)
[05:40] <bddebian> Sooo many merges, so little time :-(
[05:42] <Hobbsee> bddebian: hehe, yeah.  get going :P
[06:11] <LaserJock> bddebian: do we actually know how many merges need to be done?
[06:11] <bddebian> LaserJock: For which?
[06:11] <LaserJock> Universe/Multiverse
[06:11] <bddebian> I have been using the merge pages assuming they are "up to date"
[06:16] <bddebian> LaserJock: I think I finished up the multiverse syncs except for afbinit which fabbione is doing and a couple of updated merges.
[06:16] <bddebian> There are still about 200+ for Universe :-(
[06:16] <LaserJock> I don't think the list has been updated for a while though
[06:17] <bddebian> LaserJock: The syncs I just requested yesterday are off the list today.. ?
[06:17] <LaserJock> really?
[06:17] <LaserJock> hmm
[06:17] <hub> is there a way to grab the package version we are currently building to use in the build files?
[06:18] <hub> like and ENV veriable
[06:18] <bddebian> Yeah, xbattbar, xdigger, xcolorsel, etc
[06:35] <hub> ok looks like it is not possible
[06:36] <hub> and looks like deb maintainers on this package have messed up
[06:38] <Toadstool> hub: maybe using some sed magic on the changelog helps
[06:38] <hub> hackvalue++
[06:38] <Toadstool> :)
[06:38] <hub> I'll report the bug anyway
[06:39] <Toadstool> VERSION=$(dpkg-parsechangelog | grep Version | sed 's,^Version: \(.*\)\-.*$,\1,g') <-- just found this in trac :)
[06:41] <hub> Toadstool:  but it strips the real package version
[06:41] <hub> but it is a good clue
[06:41] <Toadstool> yep
[06:42] <hub> dpkg-parsechangelog | grep Version | sed 's,^Version: \(.*\-.*$\),\1,g'
[06:43] <Toadstool> et voil ;)
[06:43] <hub> and then I can upload the modified package
[06:43] <hub> ;-)
[06:49] <bddebian> Here we go again...
[06:53] <LaserJock> ?
[06:53] <bddebian> LaserJock: #u-bugs
[06:56] <Yagisan> lemmings!
[07:04] <LaserJock> bddebian: see, even seb128 loves you :-)
[07:04] <bddebian> Yeah right
[07:07] <bddebian> slomo_: Just xvid4conf and the myth* packages and I will be done with the list you gave me :-)
[07:07] <slomo_> bddebian: cool :) then we can go through the NEW list on that page together if you want... but that will be next week ;)
[07:08] <bddebian> No worries
[07:08] <bddebian> Apparently I'm just a troublemake anyway ;-P
[07:08] <bddebian> LaserJock: Are you doing vflib3 merge?
[07:09] <LaserJock> yeah
[07:09] <LaserJock> well, I was using it for a Mentoring project
[07:10] <bddebian> Ah great OK
[07:12] <LaserJock> bddebian: I
[07:12] <LaserJock> I'm regenerating the MOTU Science list right now
[07:12] <LaserJock> it looks like your syncs went through
[07:15] <bddebian> Sweet
[07:16] <LaserJock> I need to figure out how to make this a cron job
[07:17] <LaserJock> bddebian: it's update. way to go dude.
[07:21] <bddebian> Ack, why the hell are there still 42 packages there..
[07:22] <LaserJock> because of minor changes in Debian
[07:22] <LaserJock> no biggy
[07:22] <bddebian> Ah :-)
[07:22] <LaserJock> you should have seen the list right before dapper was released
[07:22] <LaserJock> it was pretty much all in that section
[07:23] <bddebian> Yikes
[07:23] <fowlduck> LaserJock: hey, just an off-question, how can you reconfigure your system completely like it was being installed for the first time?
[07:24] <LaserJock> wipe your drive and reinstall ;-)
[07:24] <fowlduck> wow, thanks! ;D
[07:26] <LaserJock> fowlduck: how do you mean exactly?
[07:26] <LaserJock> you could use a chroot or vmware/qemu perhaps
[07:26] <fowlduck> LaserJock: as in redetect all hardware and reconfigure the system based on what is found
[07:26] <LaserJock> ah, I'm really not sure how that is done
[07:27] <fowlduck> LaserJock: this happens to be a VM we just moved to a new system
[07:27] <fowlduck> but it needs direct access to the hardware apparently
[07:27] <fowlduck> so we need it to detect and configure it, if that's possible
[07:34] <Yagisan> fowlduck, the point of a vm is so it doesn't need direct hardware access ...
[07:41] <LaserJock> ok, quick packaging question. my upstream released a bug-fix release with version 0.51 when the previous version was 0.5
[07:41] <tseng> ugh
[07:41] <tseng> can your upstream not count?
[07:41] <LaserJock> should I version it -0.51- or 0.5.1-
[07:42] <tseng> do they expect to go make 0.6?
[07:42] <LaserJock> yes
[07:42] <tseng> because then you would be screwed
[07:42] <tseng> sigh
[07:42] <tseng> you should lart them
[07:42] <tseng> politely as you can
[07:42] <LaserJock> I have pretty good communication with upstream so maybe we can "have a talk" ;-)
[07:43] <tseng> good.
[07:43] <lucas__> you can also version it 0.51, and, if they decide to go for 0.6, use epoch
[07:44] <LaserJock> can I just version it 0.5.1 and talk to upstream?
[07:44] <tseng> you could, if its not in Debian
[07:44] <LaserJock> it is in Debian
[07:44] <tseng> as 0.5.1?
[07:44] <LaserJock> that's what I'm packaging it for
[07:44] <tseng> oh.
[07:44] <LaserJock> this is one I maintain in Debian
[07:44] <tseng> reversioning things really sucks
[07:46] <LaserJock> hmmm, maybe I'll email the author and see if he is close to doing another release, which he can version right
[07:46] <tseng> yeah that would be nice
[07:46] <LaserJock> and I'll skip the minor release
[07:46] <tseng> multiplying your version by 10 and adding one is a pretty shit way to do a point release
[07:49] <LaserJock> hehe, what's in a . ? ;-)
[07:49] <ajmitch> common sense
[07:51] <Yagisan> ajmitch, if it really is common, why don't many people have it ?
[07:52] <LaserJock> because it *should* be common?
[07:55] <bddebian> MORE SYNCS!!!
[07:55] <Yagisan> LaserJock, aye. common sense tells me gcc-4.1 needs that versioned libc6 dependency. actual practice shows it seems to be quite happy with dappers libc6. I hate it when they clash like that
[08:03] <kmilo> Hi
[08:04] <bddebian> Hello kmilo
[08:09] <Gloubiboulga> hum, gtk docs are broken
[08:09] <Gloubiboulga> well, gtk tutorial
[08:10] <slomo_> Gloubiboulga: known bug ;)
[08:10] <Gloubiboulga> slomo_, ok :)
[08:10] <slomo_> Gloubiboulga: bug 54504
[08:10] <Ubugtu> Malone bug 54504 in gtk+2.0 "faq and tutorial unusable on devhelp" [Medium,Rejected]  http://launchpad.net/bugs/54504
[08:11] <Gloubiboulga> Rejected?
[08:11] <Gloubiboulga> ah yes
[08:43] <yosch> hey MOTUs :-)
[08:43] <yosch> anybody for bug 53787?
[08:43] <Ubugtu> Malone bug 53787 in Ubuntu "Please sync ttf-sil-abyssinica 1.0-1 from Debian Sid" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/53787
[08:45] <kozz> if I modify a package and create a new ubuntu release number, am I supposted to create some kind of patch to put in the archive or modify the files I want to change directly?
[08:46] <kozz> I mean, how do folks usually do
[08:48] <LaserJock> kozz: hmm, you mean you want to change a file in the package?
[08:48] <LaserJock> kozz: and you are wondering the best way to do that?
[08:49] <kozz> yes, I downloaded the source and what to change an option in the Makefile and create a new ubuntu version
[08:49] <cbx33> should we use LP to submit usability suggestiong bugs
[08:50] <cbx33> epiphany, when you create a new tab, I think, should put the cursor in the address bar for you to type in the address like FF?
[08:50] <kozz> I have figured out I can use debchange and debuild, but just want to know the "correct" way to go
[08:50] <LaserJock> kozz: if the current source package uses a patch system use that, if it doesn't just modify the file
[08:51] <kozz> right, so it is different in different packages
[08:51] <LaserJock> yeah
[08:51] <kozz> ohh..
[08:51] <kozz> but thanks
[08:51] <LaserJock> kozz: what package are you working on?
[08:52] <kozz> mkvmlinuz
[08:52] <kozz> yeah, it's in main I know
[08:53] <kozz> but need to get used to the debian packaging system
[08:53] <LaserJock> kozz: is this in edgy?
[08:53] <kozz> only for powerpc
[08:53] <kozz> but it is in all releases
[08:54] <kozz> not sure about hoary, but since breezy at least
[08:54] <LaserJock> kozz: have you looked to see if edgy has fixed it?
[08:54] <kozz> yes, the problem occured in edgy :)
[08:55] <LaserJock> kozz: what file do you want to change?
[08:56] <kozz> I have already built the new package with the fix and it works, but people seems slow to read the bug reports, though it maybe was possible to make a sponsored upload
[08:57] <kozz> just add -fno-stack-protector in the Makefile
[08:57] <kozz> in the directory boot
[08:58] <LaserJock> kozz: yeah, that's a debian-native package
[08:58] <LaserJock> kozz: so you changed the file, then did you make a changelog entry?
[08:58] <kozz> yes
[08:59] <LaserJock> k
[08:59] <kozz> and then used dpkg -i to install it
[08:59] <LaserJock> ok
[08:59] <LaserJock> so did you run debuild -S ?
[09:00] <kozz> no
[09:01] <LaserJock> what did you run to build a .deb?
[09:01] <kozz> fakeroot dpkg-buildpackage
[09:01] <LaserJock> hmm
[09:02] <kozz> ? :)
[09:02] <LaserJock> ok, try running debuild -S to create a source package
[09:02] <LaserJock> it's generally not a great idea to build a .deb like that. it can mess around with the source package
[09:03] <kozz> ok, maybe should clean it first then
[09:03] <LaserJock> it might be a good idea
[09:08] <kozz> ok, seems to work fine
[09:08] <kozz> so would it be possible for me to upload it as a sponsored upload?
[09:09] <LaserJock> ok, so now you've got a new source package?
[09:09] <kozz> yes
[09:09] <kozz> mkvmlinuz_23ubuntu2.tar.gz
[09:09] <LaserJock> run debdiff <oldpackage>.dsc <newpackage>.dsc > diff
[09:11] <kozz> cool, but seems like I changed to much in the changelog :) hold on
[09:14] <kozz> that was better
[09:14] <kozz> done
[09:15] <LaserJock> kozz: can you pastebin the diff for me?
[09:17] <kozz> http://www.copypot.com/333
[09:18] <LaserJock> kozz: great, now attach that debdiff to the bug
[09:20] <micahcowan> Q: what's a debdiff: diff from the debian/ dir as a refpoint?
[09:20] <kozz> https://launchpad.net/distros/ubuntu/+source/mkvmlinuz/+bug/53460
[09:20] <Ubugtu> Malone bug 53460 in mkvmlinuz "mkvmlinuz fails to create kernel" [Untriaged,Unconfirmed] 
[09:21] <LaserJock> micahcowan: a debdiff is an actual diff between source or binary packages
[09:22] <LaserJock> micahcowan: it does various things, I believe, that makes is smarter than just diff oldsource newsource
[09:22] <LaserJock> kozz: excellent, good work
[09:22] <bddebian> slomo_: mythtv needs libiec618383 from the NEW list :-)
[09:23] <slomo_> bddebian: not my fault... i uploaded it half a week ago, unfortunately our NEW is slower than debian's atm ;)
[09:23] <bddebian> slomo_: Oh, you already threw that one up?
[09:23] <slomo_> yes
[09:25] <bddebian> slomo_: So poke someone ;-)
[09:25] <slomo_> won't help ;)
[09:25] <slomo_> there are already 70 packages or so in NEW
[09:26] <bddebian> F' them ;-P
[09:26] <crimsun> well if you'd stop filing syncs, maybe they could process NEW ;-p
[09:26] <crimsun> you can't have both ;-p
[09:26] <bddebian> Oh ouch
[09:26] <bddebian> ;-P
[09:26] <crimsun> uh oh, I'll get hobbsee to whip you back to work ;-p
[09:27] <bddebian> heh
[09:27] <zul> crack that whip...break your mothers back
[09:33] <bddebian> zul is now known as Devo ;-P
[09:41] <CarlFK> Wireshark source has a debian/ dir - is there a dpkg-buildpackage parameters that has a chance of working with ubuntu?
[09:41] <LaserJock> hm?
[09:42] <CarlFK> wireshark is the new name for Ethereal
[09:42] <LaserJock> k
[09:42] <CarlFK> svn co http://anonsvn.wireshark.org/wireshark/trunk/ wireshark
[09:42] <LaserJock> k
[09:42] <CarlFK> got the source, and in there is a debian/ dir
[09:43] <LaserJock> k
[09:43] <CarlFK> was hoping this might "just work" dpkg-buildpackage -rfakeroot -uc -b
[09:43] <LaserJock> sure, why not
[09:43] <CarlFK> applying patch 01_idl2deb to ./ ... failed.
[09:44] <CarlFK> but at least I know it might have worked, so this might be a "bug" that someone in wireshark land wants to know about
[09:45] <LaserJock> sure, if upstream wants to do the packaging, then they can get all the bugs ;-)
[09:46] <CarlFK> I didn't want to piss anyone off and get a reply "what made you think that would work?"
[09:49] <bddebian> Grr it pisses me off that so many of these merges are syncs that someone used ubuntuX versions for rather that buildX..
[09:49] <LaserJock> what?
[09:50] <bddebian> Oh, nevermind, this one was actually a clean merge, I didn't see the other ubuntu changelog entries :-(
[10:05] <bddebian> hu hu siretart
[10:27] <bddebian> Who is in MOTUGames team?
[10:28] <LaserJock> https://wiki.ubuntu.com/MOTU/Teams/Games
[10:28] <bddebian> Thx LaserJock
[10:52] <CarlFK> wireshark tarbal seems to build a .deb ok on edgy.  how do I find the ubuntu Ethereal package maintainer/builder so I can tell them?
[10:55] <crimsun> ?
[10:55] <crimsun> we don't have maintainers or builders per se
[10:57] <CarlFK> changelog has Sebastian Drge <slomo@ubuntu.com>  Mon,  8 May 2006 13:47:30 +0200
[10:57] <crimsun> that being the last person who touched it, probably?
[10:57] <CarlFK> so I am guessing that would be someone who cares
[10:57] <slomo_> hi CarlFK :)
[10:58] <CarlFK> ta da!
[10:58] <CarlFK> are you the person who cares?
[10:59] <crimsun> for reference: http://packages.qa.debian.org/w/wireshark/news/20060731T170302Z.html
[10:59] <slomo_> CarlFK: partially... well, i think we should do the following:
[10:59] <slomo_> a) get wireshark in, sync from debian probably
[10:59] <slomo_> or no
[10:59] <slomo_> get wireshark from debian and add a transitional ethereal package to it
[10:59] <slomo_> and b) get ethereal removed from the archive
[11:00] <slomo_> damn, only sync it :) there is a transitional package but it isn't on p.qa.d.o ;)
[11:01] <slomo_> CarlFK: want me to care for this or do you to do it?
[11:01] <CarlFK> you better
[11:01] <crimsun> crap, yet another one
[11:01] <CarlFK> I am not to savvy in these things :)
[11:01] <slomo_> CarlFK: ok :)
[11:01] <slomo_> CarlFK: thanks for reminding me
[11:01] <crimsun> my todo queue for security patches is /huge/
[11:02] <bddebian> :-(
[11:02] <bddebian> OK, back in the pool, later folks
[11:02] <LaserJock> bddebian: pool?
[11:02] <crimsun> yeah, like swimming...water...
[11:02] <bddebian> Yeah, just a small little 12'x20' inflatable type thing
[11:03] <LaserJock> what the heck, it can't be *that* bad there :-)
[11:03] <LaserJock> although I though my laptop was going to melt when it hit 90 in the house and 104 outside
[11:04] <crimsun> balmy 55F in here.
[11:04] <LaserJock> I was trying to go easy on the pbuilder
[11:04] <LaserJock> so my keyboard wouldn't warp or something
[11:21] <crimsun> slomo_: I recommend we consider backporting wireshark to dapper from edgy. There are a slew of security fixes, and upstream hasn't made it terribly straightforward to see "breakout patches" for those CVEs.
[11:21] <slomo_> crimsun: first let us get it into edgy... then we can backport :)
[11:21] <crimsun> (right.)
[11:56] <bddebian> OK merges are getting boring, maybe I need to go back to "bugfixing" for a while?
[11:57] <crimsun> knock yourself out
[11:57] <LaserJock> bddebian: there are certainly a lot to fix
[11:57] <bddebian> Aye :-(
[11:59] <LaserJock> I, in the mean time, am compiling firefox in fink
[11:59] <LaserJock> :/
[12:04] <bddebian> Joy :-)
[12:05] <hub> that what I'd call masochism
[12:05] <hub> to build firefox it is
[12:05] <hub> buidling it on Mac is worse
[12:05] <hub> but in Fink....
[12:05] <crimsun> well he could attempt to build KDE.
[12:05] <LaserJock> all in the pursuit of yelp :-)
[12:06] <LaserJock> I think KDE actually builds, unlike Gnome
[12:06] <crimsun> yep.
[12:06] <hub> KDE coders are better :-)
[12:06] <LaserJock> all I want is yelp
[12:06] <LaserJock> and it has taken me months to get it
[12:06] <bddebian> brb