[12:10] <LaserJock> hmm, I need to figure out a way to make an RSS feed tracking Debian uploads of a given set of packages
[12:10] <LaserJock> same thing for Ubuntu as well
[12:15] <zul> wtf with vim 7?
[12:37] <fbond> ok, now I am on ubuntu-universe-contributors, but I still need to recover my password from revu... anyone like to help me with this?
[12:37] <zul> might have to ask a revu admin if one is around
[12:38] <LaserJock> fbond: have you uploaded a package yet?
[12:41] <fbond> yes, I've uploaded several
[12:41] <fbond> is it correct that there is revu breakage?
[12:41] <fbond> I'd like to respond to a comment on a package...
[12:42] <LaserJock> fbond: ok, so then put in your email and hit "Login"
[12:42] <fbond> I apologize, I'll keep my password safe from now on, but I had previously just counted on easy recovery
[12:42] <fbond> done that
[12:42] <LaserJock> fbond: and then did you click on "recover"
[12:42] <fbond> yes
[12:43] <LaserJock> and what did you get?
[12:43] <fbond> I reported this problem here the day before yesterday or something
[12:43] <fbond> I get either no encrypted string, or an IOError due to broken pipe
[12:43] <LaserJock> hmm
[12:43] <fbond> it varies between the two
[12:43] <fbond> yes, it is broken
[12:43] <fbond> as far as I can tell, anyway...
[12:43] <LaserJock> and did you email the admins?
[12:44] <fbond> no, I suppose that would be a good next step
[12:44] <fbond> I spoke with someone here
[12:44] <fbond> I understood it to be a known problem
[12:45] <LaserJock> fbond: whether it is know or not it will likely take an admin to fix it :-)
[12:46] <fbond> yes, I thought I had been speaking with siretart, who is an admin, yes?
[12:46] <LaserJock> yes, he's the guy
[12:46] <LaserJock> so as long as he know about it then it is in good hands
[12:47] <fbond> okay I will send him an email, anyway.  don't recall for sure if I had gotten a positive resonse from him that a fix was in progress.
[12:47] <fbond> in any case, it'd be handy to just get the encrypted password, one way or another.
[12:48] <LaserJock> yeah
[12:51] <LaserJock> nice, and I have 2 accounts, only 1 of which is a reviewer :-)
[12:51] <sivang> night motus
[12:51] <LaserJock> cya sivang
[12:51] <sivang> laters LaserJock
[01:38] <Toadstool> g'night everybody
[01:39] <bddebian> Heya gang
[01:42] <jsgotangco> hey bd
[01:43] <ajmitch> hello
[01:43] <jsgotangco> good morning ajmitch
[01:43] <ajmitch> good morning jsgotangco, how are you?
[01:43] <bddebian> Hi jsgotangco, ajmitch
[01:44] <jsgotangco> im good just arrived too early at work though
[01:44] <ajmitch> heh
[01:45] <zul> all the more reason to slack off and doing what you want to do but not suppose to
[01:49] <jsgotangco> heh exactly!
[01:55] <jsgotangco> heh this is the first time i heard of a package named beautifulsoup
[01:59] <TheMuso> Hey MOTUs
[03:16] <TheMuso> How does a non-MOTu go about filing a sync request?
[03:17] <LaserJock> I think the same was as a MOTU, but I'm not sure if that makes sense
[03:19] <LaserJock> imbrandon: ping?
[03:22] <bddebian> Wow LaserJock, that is some power ;-)
[03:23] <LaserJock> hehe
[03:23] <LaserJock> imbrandon_: you actually here? :-)
[03:24] <imbrandon_> kinda ;)
[03:24] <imbrandon_> sup ?
[03:32] <zakame> hi all
[03:32] <zakame> bddebian: how's the x11proto thing? =)
[03:33] <ajmitch> hi zakame
[03:33] <zakame> I'll be bound to manila in a few moments
[03:33] <zakame> heya ajmitch
[03:43] <bddebian> zakame: Hi.  Still b0rked :-(
[03:46] <DarkMageZ> ooo, what application is b0rked?
[03:49] <bddebian> DarkMageZ: No, my pbuilder environment for some reason
[03:49] <DarkMageZ> oh
[03:51] <LaserJock> bddebian: did you try building a new one from scratch?
[03:51] <bddebian> No not yet
[03:52] <bddebian> I've been trying to build your damn scilab-4 for 3 days now :-)
[03:54] <zul> argh...give up
[03:54] <bddebian> I can always count on you for support zul
[03:57] <LaserJock> well, I gave up after ~ 15 min.
[03:58] <bddebian> It shouldn't be that difficult really
[03:58] <bddebian> But the 3.0 packaging is wrong imo and I don't know cdbs for shit :-(
[03:59] <zakame> hmm, do you keep a tee of the pbuildlogs?
[03:59] <bddebian> zakame: For my broken pbuilder or for scilab?
[03:59] <zakame> the broken pbuilder building scilab
[04:00] <bddebian> My broken pbuilder isn't my scilab problem :-)
[04:00] <jsgotangco> zakame: what will you be doing here?
[04:01] <zakame> jsgotangco: school, bookhunting, and laptop
[04:01] <jsgotangco> wow that SoC money sure came in handy :P
[04:01] <zakame> hehe
[04:01] <zakame> well I'm not buying just yet, just looking around
[04:01] <zakame> I might cosider that acer ferrari though :P
[04:02] <jsgotangco> yeah i saw the sale
[04:02] <jsgotangco> its pretty good deal but i hate Acer
[04:02] <zakame> how come?
[04:03] <jsgotangco> their designers don't know anything about form factor
[04:03] <bddebian> zakame: Here is pbuilder problem:  http://pastebin.us/810
[04:03] <zakame> ah
[04:04] <bddebian> But if I do a pbuilder login apt-get update and apt-get install x11proto-gl-dev, I get it ??
[04:04] <jsgotangco> the acer ferrari being sold cheaply is almost 2 years old and already discontinued, the ones they sell now use carbon fiber
[04:05] <zakame> what's scilab's B-D line?
[04:06] <zakame> in debian/control?
[04:06] <zakame> jsgotangco: ah
[04:06] <bddebian> zakame: That's not from scilab, that is from Hobbsee's ksudoku
[04:07] <zakame> bddebian: what's the B-D line anyhow?
[04:08] <bddebian> Hmm, this is interesting
[04:08] <bddebian> bdefreese@bdubuntu1:~/edgy/ksudoku$ dpkg-source -x ksudoku_0.3-4ubuntu1.dsc
[04:08] <bddebian> dpkg-source: error: syntax error in source control file ./ksudoku_0.3-4ubuntu1.dsc at line 22: found start of PGP body but no signature
[04:08] <crimsun> argh
[04:09] <crimsun> (I'm pretty sure I asked you about the source package, the dsc specifically, some hours ago)
[04:09] <bddebian> crimsun: I thought we were talking about scilab?
[04:10] <crimsun> bddebian: that was later
[04:11] <bddebian> Well now at least you all know how stupid I really am so you can stop with the God cracks :-)
[04:11] <crimsun> 15:34 < bddebian> crimsun: If I do an apt-get install from pbuilder login, it
[04:11] <crimsun>                   works fine
[04:11] <crimsun> 15:35 < crimsun> ...but?
[04:11] <crimsun> 15:35 < bddebian> pbuilder build doesn't get it
[04:11] <crimsun> 15:36 < crimsun> got the source package posted?
[04:11] <crimsun> 15:36 < crimsun> dsc would be fine for starters
[04:12] <crimsun> (to be fair, I should have looked at the dsc myself, but I was reading an abstract at that time)
[04:14] <bddebian> It's interesting that the build process actually started..
[04:14] <crimsun> it'll do that.
[04:14] <crimsun> cf. someone's problem with pbuilder foo_source.changes
[04:17] <bddebian> crimsun: Have any patience left for me for scilab? :-(
[04:17] <crimsun> bddebian: got a few dozen things going on atm, try in 1 hr.
[04:17] <bddebian> OK thx
[04:18] <crimsun> (and don't block on me, either.  If a package hasn't had anything in it related to python before, and one wants to add some files that need to be placed in the python site-packages dir, is there a debhelper command or a variable that one can use to copy the files into the right python<version>/site-packages directory?
[04:26] <bddebian> man dh_python ?
[04:27] <TheMuso> No I don't think so. Thats only for working out dependancies.
[04:29] <TheMuso> Or should I just assume a particular python version?
[04:29] <crimsun> we use python-support now.
[04:29] <crimsun> python-<version>/site-packages is the older way
[04:30] <crimsun> now-> Edgy
[04:30] <TheMuso> does python-support put them in the right place?
[04:31] <TheMuso> Hey Hobbsee.
[04:31] <TheMuso> Ah, it has a debhelper hook.
[04:31] <Hobbsee> hi TheMuso
[04:31] <bddebian> Hi Hobbsee
[04:31] <Hobbsee> hi bddebian :)
[04:31] <bddebian> Hobbsee: Did your ksudoku get uploaded?
[04:32] <Hobbsee> bddebian: no idea
[04:33] <Hobbsee> bddebian: it's not on edgy changes yet
[04:33] <Hobbsee> bddebian: i didnt ask anyone else to puload it
[04:34] <TheMuso> crimsun: Thanks.
[04:34] <crimsun> TheMuso: np
[04:34] <crimsun> Hobbsee: do you feel it's ready?
[04:35] <crimsun> I can it for tomorrow morning
[04:35] <Hobbsee> crimsun: um, i think so
[04:35] <Hobbsee> crimsun: that admin/cvs message is still there, even though the directory gets moved in the clean
[04:35] <crimsun> Hobbsee: that's fine, it really should be stripped from the original tarball
[04:36] <crimsun> dpkg-source will ignore deletions
[04:36] <bddebian> Hobbsee: Tsk, tsk, CVS dirs :-)
[04:36] <Hobbsee> yeah
[04:36] <Hobbsee> bddebian: :P
[04:36] <bddebian> The rest of the Lintian stuff is crap :-)
[04:36] <Hobbsee> bddebian: i didnt do it!  it's debian's fault!
[04:36] <Hobbsee> yeah hehe
[04:37] <Hobbsee> crimsun: if you're in an uploading mood, i've got various other packages listed on https://wiki.kubuntu.org/KubuntuEdgyPackageUpdates as done - for syncs or merges
[04:38] <crimsun> Hobbsee: you can file sync requests
[04:39] <crimsun> the template I've been following is to file a bug on the source package entitled "[Edgy MoM]  Please sync source_package version-revision from Debian Sid", then in the bug report I link to MoM's REPORT and say "Ok to override Ubuntu changes"
[04:39] <crimsun> then I subscribe ubuntu-archive
[04:40] <Hobbsee> crimsun: right, yep
[04:45] <sladen> chillywilly: /etc/acpi.d/resume.d/NNfoobar
[04:46] <crimsun> /etc/acpi/resume.d/ , but yeah
[04:54] <Hobbsee> bddebian: did it work this time?
[04:54] <bddebian> Yeah, I'm an idiot
[04:54] <bddebian> I ripped out the CVS dir though.. ;-)
[04:55] <Hobbsee> bddebian: heh, how?
[04:55] <bddebian>  find ./ -name CVS |xargs rm -rf
[04:56] <bddebian> Then took out the rm .admin/CVS from rules :-)
[04:56] <Hobbsee> what, from the .orig.tar.tz?
[04:56] <bddebian> No, just from the extracted source
[04:57] <Hobbsee> oh ok
[05:04] <bddebian> Hobbsee: Uploaded
[05:06] <Hobbsee> bddebian: yay!  thanks!
[05:09] <bddebian> Hobbsee: Well it's good to be of SOME use ;-)
[05:11] <Hobbsee> bddebian: of course you're of use!
[05:15] <Hobbsee> bleh.  it froze.
[05:15] <TheMuso> heh
[05:16] <Hobbsee> my machine isnt behaving very well at the moment
[06:18] <TheMuso> wb Hobbsee
[06:18] <Hobbsee> heya
[06:18] <Hobbsee> trying to mess with teh desktop installer
[06:19] <bddebian2> Damn, I am sooo close
[06:19] <bddebian2> For some reason the libs dir doesn't install to my prefix... :-(
[06:46] <bddebian2> Well she builds, but she's still screwed up a little..
[06:46] <bddebian2> Gnight folks
[07:03] <ajmitch> afternoon
[08:38] <Gloubiboulga> morning
[08:40] <Hobbsee> hi Gloubiboulga
[08:40] <Gloubiboulga> hey Hobbsee
[09:24] <Toadstool> 'morning
[09:25] <Hobbsee> hi Toadstool
[09:25] <Toadstool> hi Hobbsee
[09:29] <Fujitsu> Hi.
[09:29] <Fujitsu> Hmm.
[09:29] <Fujitsu> Lag.
[09:29] <Hobbsee> heh, fun
[10:30] <shawarma> sivang: pong
[10:31] <sivang> shawarma: hi, have you managed to eventually upload libgfshare ?
[10:32] <shawarma> Sure.
[10:32] <shawarma> http://revu.tauware.de/details.py?upid=2522
[02:26] <Hobbsee> hi all
[02:28] <shawarma> hi Hobbsee
[02:29] <zul> hey
[02:29] <Hobbsee> hi shawarma and StevenK
[02:29] <StevenK> Ow!
[02:32] <Kyral> Morning
[02:32] <Hobbsee> heh
[02:32] <Hobbsee> hi
[03:11] <tuxmaniac> bug 51241
[03:11] <Ubugtu> Malone bug 51241 in gaphor "Gaphor fails to run" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/51241
[03:23] <zakame> hi all
[03:23] <Hobbsee> hi zakame
[03:23] <zul> hi zakame
[03:24] <zakame> heya Hobbsee zul, here in Manila now
[03:24] <zakame> heh, I forgot to /away earlier
[03:59] <bddebian> Heya gang
[03:59] <raphink> hi bddebian
[03:59] <Kamping_Kaiser> hey
[04:00] <bddebian> Hi raphink and Kamping_Kaiser :-)
[04:00] <Kamping_Kaiser> :)
[04:00] <raphink> hi Kamping_Kaiser
[04:01] <Kamping_Kaiser> hey mate
[04:01] <raphink> do you guys have an idea if there's a tool to remove all the symbolic links pointing to a file?
[04:01] <bddebian> rm?
[04:02] <raphink> rm only removes the file
[04:02] <raphink> itself
[04:02] <raphink> but it won't remove the symbolic links pointing to it
[04:02] <raphink> it'll just leave them broken
[04:02] <bddebian> Isn't there a remove for ln ?
[04:02] <raphink> I know the symlinks system is only one way
[04:02] <raphink> hmmm
[04:03] <raphink> doesn't seem so
[04:07] <jsgotangco> good evening
[04:07] <raphink> hi jsgotangco
[04:07] <jsgotangco> hello raphink how are you?
[04:07] <raphink> pretty good
[04:08] <raphink> although I'm stuck on something
[04:08] <raphink> but I'll find a way ;)
[04:26] <Hobbsee> http://revu.tauware.de/details.py?upid=2556
[04:26] <Hobbsee> oops
[04:27] <zul> yeah i know i already did one ;)
[04:35] <raphink> I still do my merges manually
[04:35] <raphink> I've tried with the MoM in Dapper
[04:35] <raphink> and somehow I didn't find it easier
[04:36] <raphink> but I guess it is if you take some time to understand how it works
[04:36] <Hobbsee> true
[04:37] <sladen> how do I get a package from  non-free into multiverse?   Just put a sync request into launchpad?
[04:38] <sladen> raphink: you can't find the sym links pointing to a file without doing a full search of the harddisk
[04:38] <raphink> sladen: that's what I thought
[04:38] <raphink> and even fiind might not have an option for that I guess
[04:38] <raphink> sladen: and yes about the non-free
[04:39] <raphink> it seems to be the best way
[04:39] <raphink> if it builds on edgy
[04:39] <sivang> hey slomo :)
[04:39] <sivang> sladen: yo
[04:39] <slomo> hi sivang :)
[04:39] <raphink> hi sivang
[04:39] <sivang> sladen: did you see my PM I left on your detached irc window?
[04:40] <sivang> and sladen
[04:40] <sivang> err, slomo
[04:40] <slomo> sivang: nope :(
[04:40] <sivang> slomo: no, that was for sladen :)
[04:40] <sivang> slomo: so it's okay.
[04:42] <slomo> sivang: oh ok ;) sorry
[04:43] <ivoks> howdy
[04:44] <raphink> hi ivoks
[04:44] <ivoks> i'm having some troubles with one package
[04:45] <ivoks> anyone familiar with dpatch? actully, this is patch issue
[04:45] <ivoks> or isn't :)
[04:45] <ivoks> well, here it is:
[04:45] <ivoks> patch_opts="-g0 -f --no-backup-if-mismatch -F0 -U ${workdir:+-d ${workdir}}"
[04:45] <sivang> ivoks: what's the issue?
[04:45] <ivoks> patch doesn't take -U argument
[04:46] <sivang> ivoks: hmm, I've never had to deal with dpatch special opts like this so far..
[04:46] <ivoks> sivang: do you have any idea what maintaner wanted to do with that -U?
[04:46] <ivoks> sivang: me neither...
[04:46] <sivang> ivoks: let's see in depatch's manual
[04:47] <ivoks> uh
[04:47] <ivoks> i get it
[04:47] <ivoks> he wanted to add arguments to dpatch
[04:48] <sivang> ivoks: how did you find that out?
[04:48] <sivang> ivoks: which package is that btw?
[04:48] <ivoks> but hplip
[04:49] <ivoks> without but
[04:49] <ivoks> :)
[04:49] <ivoks> hm... but -U isn't is neither in patch nor dpatch
[04:49] <ivoks> sivang: this is source from debian unstable
[04:50] <sivang> ivoks: sorry, I've lost you :)
[04:50] <ivoks> sivang: :)
[04:50] <ivoks> i'll just remove -U and see what I get
[04:52] <sivang> ivoks: cool
[04:52] <ivoks> i get compiled package...
[04:52] <ivoks> hm...
[04:52] <ivoks> i'll contact him to find out what's up with that
[05:45] <bddebian> Heya LaserJock
[05:46] <LaserJock> hi bddebian
[06:57] <phanatic> hi people
[06:58] <phanatic> hey Yagisan
[07:02] <bddebian> Yagisan: cmake hates everyone :-)
[07:02] <bddebian> Heya phanatic
[07:02] <phanatic> heya bddebian
[07:04] <Yagisan> bddebian: I have what I think is a simple cmake file
[07:04] <Yagisan> bddebian: but it hates it
[07:04] <Yagisan> bddebian: running make gives me errors out the wazoo
[07:04] <bddebian> :-)
[07:06] <LaserJock> siretart: ping?
[07:07] <phanatic> siretart: ping
[07:07] <phanatic> :)
[07:07] <Yagisan> bddebian: it's blatantly ignoring the include files,
[07:20] <LaserJock> raphink: ping?
[07:21] <raphink> hi LaserJock
[07:21] <LaserJock> raphink: got a REVU problem
[07:21] <raphink> that is bad news
[07:21] <raphink> what is that?
[07:22] <LaserJock> bluekuja just uploaded an upgrade of gtorrent-viewer and it seems stuck in the incoming queue
[07:22] <raphink> ah right
[07:22] <raphink> I'll have a look
[07:22] <raphink> kbarcode
[07:22] <raphink> it's horrible
[07:22] <raphink> the guy who translated this into french (hopefuly he's not here) just can't speak english, nor french
[07:23] <bluekuja> raphink, the package was already inside, but I uploaded a new version
[07:23] <raphink> np bluekuja
[07:24] <raphink> it's fixed now, try it again
[07:24] <bluekuja> raphink, I re-upload it?
[07:24] <raphink> yes bluekuja
[07:24] <bluekuja> oki perfect
[07:25] <bluekuja> done
[07:35] <raphink> bluekuja: please subscribe to the ubuntu-universe-contributors group on LP
[07:35] <raphink> having your GnuPG key in your LP account
[07:35] <raphink> then ping me
[07:35] <bluekuja> ok
[07:43] <LaserJock> bddebian: ubuntu-science is going to start gettting flooded by your bugs? ;-)
[07:44] <bluekuja> raphink, done
[07:44] <bluekuja> waiting approval
[07:45] <raphink> I'll go there blue
[07:45] <bddebian> LaserJock: Of course :-)
[07:45] <raphink> which is your account bluekuja?
[07:45] <LaserJock> smart move
[07:46] <bddebian> Acutally I have it
[07:46] <bddebian> I just have some directory issues to work out
[07:46] <raphink> hop
[07:46] <raphink> let's approve
[07:46] <raphink> now let's wait soem time for the revu-key update
[07:47] <raphink> i'll tell you when it's done bluekuja
[07:47] <LaserJock> raphink: so key issues get stuck in incoming as opposed to rejected?
[07:47] <raphink> no they get stuck in rejected ;)
[07:47] <raphink> the changes file is put into rejected
[07:47] <LaserJock> ah
[07:47] <raphink> which blocks the system for this package
[07:47] <LaserJock> makes sense
[07:48] <bluekuja> raphink, my account is bluekuja
[07:48] <raphink> yes I figured bluekuja :)
[07:48] <bluekuja> great :)
[07:48] <bluekuja> i have to run
[07:48] <bluekuja> will you be on later?
[07:49] <bluekuja> anyway you can leave me a pm when done
[07:49] <raphink> done :)
[07:49] <raphink> hh
[07:49] <bluekuja> lol great
[07:50] <bluekuja> thanks a lot
[07:50] <bluekuja> see you later
[07:50] <bluekuja> LaserJock, will be you here later?
[07:50] <raphink> upload again it should work
[07:51] <bluekuja> ok uploading
[07:51] <LaserJock> bluekuja: yeah, when it's up I'll have a look
[07:52] <bluekuja> perfect
[07:52] <bluekuja> cya guys
[07:52] <raphink> it'll be on in 3 minutes
[07:52] <raphink> should be on :)
[07:52] <raphink> in 3 minutes that is :)
[07:52] <raphink> cya bluekuja
[07:52] <Spec> was there a revu day?
[07:54] <raphink> not yet I think
[07:54] <LaserJock> well, I'm not sure what happened, it looked to me like it was supposed to be yesterday
[07:55] <raphink> LaserJock: ah?
[07:55] <raphink> mayb
[07:55] <Spec> what does compat mean?
[07:55] <raphink> I'm too busy with work
[07:56] <LaserJock> Spec: that's the version of debhelper the package conforms too
[07:56] <Spec> ah, makes sense
[07:56] <LaserJock> so if you are using debhelper 5 then compat should have 5
[08:00] <raphink> this translation is horrible
[08:00] <raphink> never saw that ever before
[08:01] <LaserJock> bddebian: do you know why sometimes debian/tmp is used and other times debian/<packagename>?
[08:01] <Spec> my compat was 4, but debhelper is 5
[08:01] <Spec> lintian doesn't check for that?
[08:01] <bddebian> LaserJock: debian/tmp used to be the default afaik.  It's older.  The new method is debian/$package or whatever
[08:02] <LaserJock> yeah, but both work, right?
[08:02] <bddebian> Yep
[08:02] <LaserJock> do you know if that is a dpkg-buildpackage thing?
[08:02] <bddebian> In fact for a multi-binary package (like scilab ;-) ) sometimes it's easier to build everything in debian/tmp then split out the files with install or foo.install files
[08:03] <LaserJock> hmm, I would have thought debian/$package would have been better for multiple binaries
[08:03] <bddebian> Well if they are "clean" it is
[08:04] <bddebian> If there is the appropriate build targets in the makefiles for example
[08:04] <Spec> raphink: http://revu.tauware.de/details.py?upid=2444  - you say GPL license terms is incomplete, but I don't see why...any clues? :p
[08:04] <LaserJock> you should have a copyright year
[08:05] <LaserJock> like "Copyright (c) 2006 blah blah blah"
[08:05] <Spec> where? in the sourec?
[08:05] <raphink> by the way Spec if  you look closely, I didn't say it, Lionel did :)
[08:05] <LaserJock> in debian/copyright
[08:05] <raphink> I just sponsored his comments
[08:05] <Spec> bah
[08:05] <LaserJock> but in the source too
[08:05] <Spec> i thought for sure you said it this time :p
[08:05] <LaserJock> hehe
[08:05] <Spec> in the source there is a date, 2005
[08:05] <raphink> hehe
[08:07] <LaserJock> k
[08:07] <Spec> so, "Copyright (c) 2005 Roman Kagan<EMAIL_ADDRESS>[08:07] <Spec> in debian/copyright
[08:07] <LaserJock> yeah
[08:08] <LaserJock> at least that's what I think his comment was about
[08:09] <raphink> exactly
[08:09] <raphink> it's the most important part in debian/changelog almost
[08:09] <raphink> without this line, the copyright is void
[08:09] <Spec> in debian/changelgo?
[08:10] <raphink> sorry copyright
[08:10] <raphink> doing too many things at the same time ;)
[08:10] <Spec> oki, just re-uploaded :)
[08:10] <raphink> ok :)
[08:10] <Spec> i was worried i missed a copyright statement in changelog
[08:10] <Spec> but i was thinking to myself ... w-hat :p
[08:10] <LaserJock> lol
[08:11] <Spec> ok, backup tape-rotation time, whee!
[08:11] <Spec> the best part of fridays
[08:21] <Spec> i wish firefox would show a diff of a webpage when you refresh and the content changes
[08:21] <raphink> ok as some of you have noticed, there are key problems on REVU, due to the new system getting the keys from LP
[08:21] <LaserJock> yeah, that would handy
[08:21] <raphink> if you experience upload issues
[08:21] <raphink> please request addition to the ubuntu-universe-contributors gruop
[08:30] <raphink> :)
[08:40] <Spec> how do we request addition to the ubuntu-universe-contributors group?
[08:41] <LaserJock> Spec: you go to the LP page and hit "
[08:41] <LaserJock> join
[08:41] <raphink> :)
[08:41] <raphink> easy, heh?
[08:41] <phanatic> Spec: https://launchpad.net/people/ubuntu-universe-contributors/+join
[08:41] <LaserJock> or that
[08:41] <raphink> if you know how to join group on orkut, friendster or whatever stuff of the kind
[08:41] <raphink> you're good enough to join groups on LP ;)
[08:42] <Spec> wow, that tested my limits of comprehension...it was close, but i managed to click the 'join' button.
[08:42] <raphink> and now it's gonna be hard to deal with the flow ;)
[08:43] <raphink> Spec: yeah :)
[08:43] <Spec> so i do have to resubmit to revu after i get accepted?
[08:43] <raphink> hop
[08:44] <LaserJock> raphink: is the revu-tool thingy automatically run on new uploads?
[08:44] <raphink> nope
[08:44] <raphink> we don't want it to run automatically for now
[08:45] <raphink> we want to be able to check stuff before building the packages
[08:46] <raphink> in case there are some hard links in the makefiles for ex
[08:46] <LaserJock> I see
[08:49] <LaserJock> weird, does this make sense in a clean: rule?
[08:49] <LaserJock> i
[08:49] <LaserJock> bah, that's not it
[08:50] <LaserJock> ii
[08:50] <LaserJock> freaking heck
[08:50] <raphink> ??
[08:50] <raphink> breathe
[08:51] <LaserJock> http://paste.ubuntu-nl.org/16850
[08:51] <Yagisan> any cmake users here ?
[08:52] <raphink> that is very ugly imo LaserJock
[08:53] <LaserJock> seems odd for a clean rule at least
[08:53] <raphink> yes
[08:57] <LaserJock> raphink: this seems odd to me too http://paste.ubuntu-nl.org/16851
[08:57] <LaserJock> why whould you need cross-compiling info in a source package?
[08:58] <raphink> bah
[08:59] <fowlduck> I have an issue while packaging pyflag, and while I have worked out more than a few of them, this one has me stumped: http://paste.ubuntu-nl.org/16852
[08:59] <fowlduck> this is during the pbuild build
[08:59] <fowlduck> anyone have any ideas?
[09:00] <bddebian> Looks like you are missing a header file somewhere
[09:00] <fowlduck> bddebian, thats what i figured, or a python library.
[09:00] <fowlduck> not a clue how to find out which one though
[09:00] <fowlduck> or which one is missing
[09:00] <raphink> hehe
[09:01] <raphink> it's not very clear indeed
[09:01] <bddebian> pyerrors.h
[09:01] <bddebian> But you do have -I/usr/include/python2.4
[09:01] <bddebian> Hmm
[09:01] <fowlduck> hmm, pyerrors.h?
[09:03] <fowlduck> this is pretty fun, otherwise.  fixing the issues and learning to package. :)
[09:03] <bddebian> fowlduck: Check config.log or earlier in the build process and see if something is trying #include pyerrors.h and is failing
[09:04] <fowlduck> ok
[09:04] <fowlduck> quick question, where is the config.log?
[09:05] <bddebian> Oh, is io.c including pyerrors?
[09:05] <bddebian> It should be in the build dir if it is creating one
[09:05] <fowlduck> not seeing the config.log
[09:05] <fowlduck> it must be including it
[09:07] <fowlduck> bangs*
[09:07] <LaserJock> dude, that's going to hurt your keyboard ;-)
[09:07] <raphink> how many keyboards a week do you usually break fowlduck?
[09:07] <fowlduck> don't worry, i have replacements
[09:08] <fowlduck> hehehe ;)
[09:08] <fowlduck> so, any ideas on how to fix this anyone?  something I can look into, or try?
[09:09] <raphink> fowlduck: yes, do whatt bddebian suggested
[09:09] <fowlduck> bddebian, io.c has #include <Python.h> at the top
[09:09] <bddebian> Ah
[09:10] <fowlduck> but there is no Python.h in the lib directory, hmmm
[09:10] <bddebian> No, it's in /usr/include/python2.4
[09:11] <fowlduck> so it should be putting that into the pbuild env
[09:12] <bddebian> ??
[09:12] <bddebian> This line should be taking care of that for you:  -I/usr/include/python2.4
[09:12] <fowlduck> where should that line be?
[09:12] <bddebian> That means include this dir when looking for header files
[09:12] <bddebian> It's already there
[09:13] <bddebian> Is the package build-depending on python2.4?
[09:13] <fowlduck> oh, ok
[09:14] <Spec> now that I'm in ubuntu-universe-contributors, should I re-upload to revu?
[09:14] <fowlduck> is it possible that some of the included header files in Python.h are missing?
[09:16] <Spec> hmm, i suppose i should wait until the .changes file leaves the incoming/rejected folder :-/
[09:17] <phanatic> what can i do if siretart has sponsored an upload to dapper-updates for me, but the package is still not in the archive?
[09:18] <fowlduck> bddebian, do you suppose that building it outside of a pbuilder environment would fix the issue? :)
[09:18] <bddebian> fowlduck: Possible but unlikely.  Most likely it's failing earlier in the process
[09:18] <raphink> Spec: what package is it?
[09:18] <bddebian> fowlduck: Might not hurt to try it
[09:18] <Spec> raphink: cxacrufw
[09:18] <raphink> Spec: the .changes file will not leave the folder unless you ask me to ;)
[09:19] <raphink> ow you can upload again
[09:19] <raphink> s/ow/now/
[09:19] <fowlduck> bddebian, so I should run over the output with a fine-tooth comb then, ok.  Thanks for your help! :)
[09:20] <fowlduck> bddebian, oh, and can you give me a hint at what to be looking for at all?
[09:20] <fowlduck> pleeeeeeeeeeeeease?
[09:20] <bddebian> fowlduck: Any errors :-)
[09:20] <Spec> yay, uploaded :)
[09:20] <fowlduck> bddebian, don't be too specific now! ;D
[09:21] <raphink> great
[09:21] <Spec> so, i get to promote ubuntu next week at a conference in san diego, we have some crazy large number of cds waiting for us already :)
[09:21] <fowlduck> LaserJock, by the way, the packaging docs now are absolutely fantastic.  Well-done, I know you had a hand in them.
[09:22] <LaserJock> oh, thanks
[09:22] <LaserJock> lots of people helped
[09:22] <LaserJock> edgy's will be better
[09:22] <bddebian> fowlduck: sudo dpkg-buildpackage -us -nc > build.log 2>&1
[09:22] <fowlduck> well, cheers to them too.  the rocked the house on that one
[09:23] <fowlduck> bddebian, ooh, i'll pop that right in there.
[09:25] <Yagisan> bddebian: could you take a look at something for me. This look right to you ? http://paste.ubuntu-nl.org/16854
[09:25] <fowlduck> bddebian, doing the same for the pbuilder thing too, i have a doctor's appt to head off to, but I'm sure I'll pester you later.  Thanks for everything again. :D
[09:26] <raphink> LaserJock: that's good to hear :)
[09:26] <raphink> to know that people use the packaging guide :)
[09:26] <LaserJock> yeah
[09:27] <LaserJock> I got a couple of those today
[09:27] <LaserJock> weird
[09:27] <raphink> converted 2 of my colleagues to kubuntu in a week :)
[09:27] <Spec> from?
[09:27] <bddebian> Yagisan: Looks reasonable but I'm certainly no expert
[09:27] <raphink> one from debian
[09:27] <raphink> the other from windows
[09:27] <Spec> nice
[09:27] <raphink> although they're both long time linux engineers
[09:27] <Spec> debian's probably easier than from windows
[09:27] <raphink> Spec: well the windows guy have been a linux system admin for years, but had not tried the linux desktops for years, too ;)
[09:28] <raphink> Spec: so he had stayed with the idea of KDE 2
[09:28] <bddebian> OK, if anyone is bored, has time, wants et help, etc, please check out:  http://www2.bddebian.com:8000/packages/ubuntu/scilab4/
[09:28] <raphink> and GNOME ... not even sure it existed back then
[09:28] <Spec> understandable, i'm on windows right now but work on debian servers :-/
[09:28] <raphink> Spec: :p
[09:28] <raphink> bad guy
[09:28] <Spec> not by choice, of course
[09:28] <bddebian> If you install it, you have to modify /usr/lib/scilab-4.0/bin/scilab and fix the SCI path
[09:28] <Spec> vmware and putty are what i use most on windows, :p
[09:28] <raphink> Spec: my company will try to force us to use windows
[09:28] <raphink> we are about 50 engineers where I work
[09:28] <raphink> 95% using linux or bsd
[09:29] <Spec> hehe
[09:29] <raphink> on our desktops
[09:29] <raphink> and I hope the company won't manage to have any of us switch
[09:29] <Spec> it'd be easier if i used ubuntu as a desktop
[09:29] <Spec> terminals are better than putty
[09:29] <raphink> way better
[09:29] <Spec> and i could do actual work on my system instead of having to ssh everywhre else
[09:29] <Yagisan> bddebian: I thought so too but I end up with this when it runs :( http://paste.ubuntu-nl.org/16855 and I know those files are there
[09:29] <raphink> that's what I showed to my colleague today
[09:30] <Spec> but alas, policy is policy :p
[09:30] <raphink> how easier his life could be with a linux desktop
[09:30] <raphink> instead of 10 putty windows
[09:30] <Spec> and the occasional 'cmd'
[09:30] <raphink> haha
[09:30] <Spec> so bad looking next to putty :-/
[09:30] <raphink> well I test the debian packages i do on my own machines
[09:30] <raphink> before building them on a remote one
[09:30] <raphink> if they have me on windows, I won't be able to do that anymore
[09:30] <Spec> i build my packages in vmware/ubuntu :-/
[09:30] <raphink> argh
[09:31] <raphink> what a shame/waste of time&energy
[09:31] <Spec> but don't worry
[09:31] <raphink> not to talk about money
[09:31] <Spec> i putty to my vmware session
[09:31] <phanatic> bluekuja: i've made some comments to gtorrent-viewer
[09:31] <raphink> lol*
[09:31] <raphink> stupid policy
[09:31] <Spec> can't copy/pate as well into vmware :p
[09:31] <raphink> :(
[09:32] <raphink> and dealing with the ssh keys is horrible with putty iirc
[09:32] <raphink> we should just try to build a network stuff that will be impossible to use on windows
[09:32] <raphink> so they have no choice but to keep us on linux
[09:33] <raphink> otherwise productivity will get down by 90%
[09:33] <raphink> I have some colleagues who almost never used windows
[09:34] <bddebian> Yagisan: I assume you are running this from /tmp/3/ ?
[09:35] <Yagisan> bddebian: of course
[09:35] <raphink> Spec: ok let's try to build your package
[09:35] <bddebian> Yagisan: Dunno man, sorry.  It sure looks like it should work..
[09:36] <bddebian> Yagisan: In this file: /tmp/3/engine/portable/include/de_base.h  what does the include for dd_def.h look like?
[09:36] <Spec> raphink: lintian is giving an error?
[09:36] <Spec> E: cxacrufw; DH_COMPAT is greater than the major version of debhelper depended on.
[09:36] <Spec>  DH_COMPAT is set to a version greater than the major version of
[09:36] <Spec>  debhelper that is depended on. This may cause things to break.
[09:36] <raphink> Spec: I don't know, it's just beginning to build
[09:36] <Spec> sorry, that was linda
[09:37] <raphink> Spec: what version of debhelper does it depend on?
[09:37] <Spec> hah
[09:37] <Spec> 4.0.0 :-/
[09:37] <Spec> i should up it to 5.0.7
[09:37] <raphink> hehe yes
[09:37] <raphink> and the standards verson is too old, too
[09:38] <Spec> what should the Standards-Version be?
[09:38] <raphink> check the verson of debian-policy in edgy
[09:38] <raphink> :)
[09:38] <Yagisan> bddebian: http://paste.ubuntu-nl.org/16857
[09:38] <Spec> the version of debian-policy in edgy....moo?
[09:39] <Spec> hmm, i don't think my pbuilder environment is even edgy
[09:39] <raphink> heh
[09:39] <raphink> Spec: you're building packages for edgy now
[09:39] <raphink> so you should test them in edgy
[09:39] <raphink> either in a pbuilder, a chroot, or an installed environment
[09:39] <raphink> preferably a pbuilder
[09:39] <bddebian> Yagisan: No, I mean de_base.h.  How does it include dd_def.h?
[09:39] <Spec> :o), i just switched it to edgy, it had been dapper
[09:40] <Spec> the package, that is
[09:40] <raphink> ok
[09:40] <raphink> yes
[09:40] <raphink> and the dependencies have to be, too
[09:40] <Spec> how do i find debian-policy in a pbuilder environment?
[09:40] <raphink> so you have to use edgy's dehelper version
[09:40] <raphink> Spec: you don't
[09:40] <Spec> oh, good.
[09:40] <raphink> but you can check packages.ubuntu.com if you don't have a machine on edgy or a chroot
[09:41] <raphink> or you can use motutools imo
[09:41] <raphink> although I never used them
[09:41] <Spec> in pbuilderrc i just change DISTRIBUTION=edgy and update?
[09:41] <Yagisan> bddebian: oops. sorry. This one http://paste.ubuntu-nl.org/16858
[09:41] <raphink> no it's not enough Spec
[09:41] <raphink> and not even necessary
[09:41] <raphink> you have to update your apt.conf/sources.list
[09:41] <raphink> and run update --override-conf
[09:41] <raphink> to force pbuilder reading it's conf again
[09:42] <raphink> s/it's/its/
[09:42] <bddebian> Yagisan: And both of those files are here: /tmp/3/engine/portable/include ?
[09:43] <Spec> "Upgrading for distribution edgy"... :)
[09:43] <Spec> but this doesn't change how dpkg-buildpackage does it's thing, do I have to do anything for that to be edgy-compliant?
[09:43] <raphink> Spec: check that is downloads files for edgy an dnot dapper
[09:43] <raphink> Spec: dpkg-buildpackage?
[09:43] <raphink> you don't build using that
[09:44] <raphink> I mean if you use a pbuilder
[09:44] <raphink> you just debuild -S -sa
[09:44] <raphink> then you pbuilder the dsc
[09:44] <Spec> i use dpkg-buildpackage -sa -S -rfakeroot -kMYKEY
[09:44] <Spec> and pbuilder to actually build it
[09:44] <raphink> hmm ok
[09:44] <Spec> yeap, it's downloading files for edgy
[09:44] <raphink> if you prefer :)
[09:45] <Spec> well, either way, that's fine if i'm using the dpkg-buildpackage on dapper?
[09:45] <raphink> Spec: as long as you build the deb in edgy, yes
[09:45] <raphink> imo
[09:46] <Spec> http://revu.tauware.de/revu1-incoming/cxacrufw-0606301515/lintian
[09:46] <Spec> why does that say unknown target distrobution edgy?
[09:46] <raphink> that's because it checks from breezy
[09:46] <raphink> (it's not even dapper)
[09:46] <Spec> raphink: but in all reality, my built deb doesn't matter because it gets built on revu, right?
[09:46] <raphink> so just ignore it
[09:47] <Yagisan> hmm. X crashed on me :(
[09:47] <Yagisan> bddebian: yes. All the includes needed are there
[09:47] <Spec> better than init crashing i suppose
[09:47] <raphink> Yagisan: was it painful?
[09:47] <Yagisan> Spec: well, I lost all my work anyway, ao it's a moot point
[09:48] <Yagisan> s/ao/so
[09:48] <Yagisan> raphink: yes. My head hurts now
[09:49] <bddebian> Yagisan: Sorry man, I just don't know and I have to head home.. :-(
[09:49] <Yagisan> bddebian: thanks anyway. I might as well go to bed and sleep on it. Unless a cmake guru is around.
[09:51] <Yagisan> right. 6am, I'm off to bed
[09:51] <bddebian> Gnight Yagisan
[09:51] <bddebian> I'm off fo a bit too, later folks
[09:58] <Spec> *slow*, raphink where do i find standards-version in packages.ubuntu.com?
[09:58] <raphink> Spec: search for the debian-policy packages for edgy
[09:58] <raphink> and check the version of this package
[09:58] <Spec> aaah
[09:59] <Spec> so Standards-Version should be <IP_ADDRESS>
[09:59] <Spec> or just 3.7.2 ?
[10:00] <raphink> 3.7.2 is fine
[10:00] <raphink> :)
[10:01] <LaserJock> yeah, i think the last .1 is just for typos or something
[10:01] <raphink> yes it's a small revision
[10:02] <Spec> ok, reuploaded with fixes
[10:03] <LaserJock> phanatic: ping?
[10:03] <phanatic> LaserJock: pong
[10:03] <LaserJock> phanatic: .desktop files are generated durning the build process?
[10:04] <phanatic> yeah, from the makefile
[10:04] <LaserJock> ah
[10:05] <kbrooks> Hi. :-)
[10:06] <Gloubiboulga> evening MOTU world
[10:06] <Gloubiboulga> hello kbrooks
[10:07] <phanatic> hey Gloubiboulga
[10:07] <Gloubiboulga> hello phanatic
[10:12] <Spec> raphink: wanna rebuild it? :o)
[10:12] <raphink> sure let's see
[10:14] <Spec> hehe
[10:14] <Spec>  This package appears to conform to a newer Standards-Version that has
[10:14] <Spec>  been released. One of us is incorrect.
[10:17] <Spec> looks good to me... :o)
[10:17] <Spec> except i can't see the .changes file off revu - i don't have permission, that's odd
[10:18] <raphink> Spec: rebuilt
[10:19] <Spec> whee,
[10:19] <Spec> i'm going to call it a day :p
[10:19] <raphink> hehe
[10:19] <raphink> :)
[10:20] <Spec> i kinda wonder what the security update for gpg involved
[10:20] <raphink> you can read aboiut it in the changelog i'm sure
[10:26] <Spec> crash and possibly arbitrary code execution patch, whee
[10:26] <Spec> okay, g'bye :)
[10:31] <Toadstool> re
[10:31] <raphink> wb Toadstool
[10:31] <Toadstool> hey raphink
[10:31] <raphink> :)
[10:33] <Toadstool> er, I suppose the latest cdbs and debhelper versions will be synced soon, I'd like to use cdbs & python-central for mmpython :)
[10:36] <sivang> Toadstool: what does it enable you to do ?
[10:37] <Toadstool> it installs python modules in /usr/share/python-central/<package> and byte-compiles them for each python version on the system
[10:37] <Toadstool> you don't need python2.X-foo packages anymore
[10:37] <sivang> oh cool,
[10:37] <Toadstool> (short summary but that's the idea)
[10:37] <sivang> is doko going to make this part of the new toolchain ?
[10:38] <sivang> Toadstool: what is mmpython ?
[10:38] <Toadstool> i think since he's the Debian maintainer for pycentral
[10:38] <Toadstool> +so
[10:39] <Toadstool> sivang: http://revu.tauware.de/details.py?upid=2520
[10:39] <Toadstool> :)
[10:39] <sivang> Toadstool: but wouldn't that fill the system with lots of different version of python ?
[10:39] <sivang> oops, I meant
[10:39] <Toadstool> ?
[10:40] <sivang> fill it with many version of the same module per each python version? isn't the previous way of having one python on the system bad?
[10:40] <sivang> s/isn't/it/
[10:40] <Toadstool> nope it creates symlinks to /usr/share/python-central/<package> files for each python version installed
[10:41] <crimsun> not bad but inflexible
[10:41] <sivang> Toadstool: but it has to make sure all modules are executable by the oldest available interpreter on the system? how does it keep ABI ?
[10:42] <Toadstool> it's the maintainer's job to make sure it works
[10:42] <Toadstool> there's a special debian/control field
[10:42] <Toadstool> XS-Python-Versions for source packages and XB-... for binary ones
[10:43] <Toadstool> I'm not an expert, see http://www.debian.org/doc/packaging-manuals/python-policy/ for more info :)
[10:43] <sivang> Toadstool: this is already supported in debhelper in debian?
[10:43] <Toadstool> yep
[10:43] <sivang> or , in dpkg for that matter
[10:44] <Toadstool> in dh_python
[10:44] <sivang> I see. nice to learn about new stuff we're going to get from upstream ;)
[10:44] <Toadstool> heh
[10:44] <Sp4rKy> raphink, thx for planfacile 553 error , works now :)
[10:46] <sivang> laters folks, be back in a bunch
[11:26] <raphink> we need a volunteer to test a bug
[11:26] <raphink> thank you lionelp
[11:26] <raphink> :)
[11:26] <raphink> ok here it is
[11:27] <Hawkwind> lionelp: Brave soul you are :P
[11:27] <raphink> mkdir patch
[11:27] <raphink> chgrp floppy patch
[11:27] <raphink> chmod g+s patch
[11:27] <raphink> cd patch
[11:27] <raphink> apt-get source patch
[11:27] <raphink> ls -l
[11:28] <raphink> :)
[11:28] <raphink> what are the group ACLs on files and folders?
[11:28] <Hawkwind> Heh interesting
[11:28] <raphink> Hawkwind: did you try it?
[11:29] <raphink> dpkg-source breaks the sticky bit rule when extracting the package
[11:29] <raphink> so the extracted folder doesnt get the right group ownership
[11:29] <lionelp> ls -l
[11:29] <lionelp> total 260
[11:29] <lionelp> drwxr-xr-x 5 lionel lionel   4096 2006-06-30 23:28 patch-2.5.9
[11:29] <lionelp> -rw-r--r-- 1 lionel floppy  49672 2004-10-25 18:38 patch_2.5.9-2.diff.gz
[11:29] <lionelp> -rw-r--r-- 1 lionel floppy    564 2004-10-25 18:38 patch_2.5.9-2.dsc
[11:29] <lionelp> -rw-r--r-- 1 lionel floppy<PHONE_NUMBER>-04-06 22:13 patch_2.5.9.orig.tar.gz
[11:29] <raphink> yes lionelp
[11:29] <Hawkwind> drwxr-xr-x 5 hawkwind hawkwind   1856 2006-06-30 16:29 patch-2.5.9
[11:29] <Hawkwind> -rw-r--r-- 1 hawkwind floppy    49672 2004-10-25 11:38 patch_2.5.9-2.diff.gz
[11:29] <Hawkwind> -rw-r--r-- 1 hawkwind floppy      564 2004-10-25 11:38 patch_2.5.9-2.dsc
[11:29] <Hawkwind> -rw-r--r-- 1 hawkwind floppy<PHONE_NUMBER>-04-06 15:13 patch_2.5.9.orig.tar.gz
[11:29] <raphink> and patch-2.5.9 shouldn't be lionel lionel
[11:29] <Hawkwind> Heh
[11:29] <lionelp> raphink: the sticky bit is for new created files
[11:29] <raphink> it should be lionel floppy instead
[11:30] <Hawkwind> Yep.  Did the same here too
[11:30] <lionelp> that is the case for the diff, the ds, the orig.tar.gz
[11:30] <raphink> lionelp: no file should be created in this folder with another group than floppy
[11:30] <raphink> now LaserJock and I are wondering if it's patch's fault
[11:30] <raphink> so let's try that :
[11:30] <raphink> rm -rf patch-2.5.9
[11:31] <raphink> tar xvzf patch_2.5.9.orig.tar.gz
[11:31] <raphink> ls -l
[11:31] <raphink> the extracted folder hsa the right ACL this time
[11:31] <raphink> now
[11:31] <Hawkwind> drwxr-sr-x 4 hawkwind floppy   1784 2003-05-20 11:19 patch-2.5.9
[11:31] <Hawkwind> -rw-r--r-- 1 hawkwind floppy  49672 2004-10-25 11:38 patch_2.5.9-2.diff.gz
[11:31] <Hawkwind> -rw-r--r-- 1 hawkwind floppy    564 2004-10-25 11:38 patch_2.5.9-2.dsc
[11:31] <Hawkwind> -rw-r--r-- 1 hawkwind floppy<PHONE_NUMBER>-04-06 15:13 patch_2.5.9.orig.tar.gz
[11:31] <raphink> gunzip patch_2.5.9-2.diff.gz
[11:31] <Hawkwind> That time it's correct
[11:31] <raphink> patch -p 0 < patch_2.5.9-2.diff
[11:31] <raphink> ls -l
[11:32] <Hawkwind> drwxr-sr-x 5 hawkwind floppy   1856 2006-06-30 16:32 patch-2.5.9
[11:32] <Hawkwind> -rw-r--r-- 1 hawkwind floppy<PHONE_NUMBER>-10-25 11:38 patch_2.5.9-2.diff
[11:32] <Hawkwind> -rw-r--r-- 1 hawkwind floppy    564 2004-10-25 11:38 patch_2.5.9-2.dsc
[11:32] <Hawkwind> -rw-r--r-- 1 hawkwind floppy<PHONE_NUMBER>-04-06 15:13 patch_2.5.9.orig.tar.gz
[11:32] <raphink> Hawkwind: how about ls -l patch-2.5.9 ?
[11:32] <raphink> don't give the details
[11:33] <raphink> just tell me if you get the right ACL _inside_ the dir
[11:33] <Hawkwind> Yes, all hawkwind/floppy
[11:33] <raphink> ok
[11:33] <raphink> I get that too
[11:33] <raphink> but funnily enough, LaserJock doesn't
[11:33] <Hawkwind> Hmmm strange
[11:33] <raphink> I'll report against dpkg-source for now
[11:33] <raphink> there's no reason why dpkg-source should override this rule
[11:34] <raphink> this is a security issue
[11:34] <Hawkwind> No it shouldn't.  Seems strange that it does as that could be a security issue
[11:34] <Hawkwind> Heh :)
[11:34] <raphink> ;)
[11:34] <raphink> found that while hacking on revu to try setting a sticky bit on folders ;)
[11:35] <Hawkwind> Very interesting indeed
[11:40] <raphink> https://launchpad.net/distros/ubuntu/+source/dpkg/+bug/51468
[11:40] <Ubugtu> Malone bug 51468 in dpkg "dpkg-source doesn't respect group sticky bit" [Untriaged,Unconfirmed]
[11:41] <raphink> can you complete/comment?
[11:41] <lionelp> raphink: having a quick look in dpkg-source, it creates a temporary dir and lot of stuff. It is not just an extract
[11:41] <raphink> mhm
[11:41] <raphink> I guess
[11:41] <raphink> dpkg-source is a huge script
[11:41] <lionelp> raphink: this bug should not pushed to Debian ?
[11:41] <lionelp> I saw :-(
[11:41] <raphink> I guess
[11:41] <lionelp> hard to read at this time :)
[11:42] <raphink> hehe
[11:42] <raphink> it's hard to read perl at all times
[11:42] <raphink> commented by a dev :s
[11:43] <lionelp> same on Debian Sid
[11:44] <raphink> lionelp: does the bug exist there, too?
[11:45] <lionelp> yes, it behaves the same (loose acl / sticky bit)
[11:49] <raphink> bugs.debian.org is stuck
[11:49] <lionelp> yep
[11:50] <lionelp> You can reach bugs on packages.qa.debian.org
[11:50] <raphink> that's because we're two people tryin gto access it at the same time
[11:50] <raphink> ;)
[11:50] <lionelp> But you will learn that dpkg have 582 bugs opened :-(
[11:50] <raphink> ouch
[11:50] <raphink> can you find the one we need?
[11:50] <lionelp> I am trying...
[11:54] <raphink> well
[11:56] <Hawkwind> raphink: You still want me to comment on the 51468 bug report or wait ?
[11:56] <raphink> sure you can comment if you have things to day :)
[11:56] <raphink> say
[11:58] <Hawkwind> I've always got things to say.  Just a matter of should I say them or not :)
[12:00] <raphink> can't find anything about sticky bit on debian
[12:00] <raphink> maybe http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=238460 was not fixed properly
[12:00] <raphink> and caused the bugt
[12:00] <Ubugtu> Debian bug 238460 in general "Subject: general: apt-get source: certain files in some packages are owned by a" [Important,Closed]
[12:00] <raphink> although it's not sure
[12:04] <Hawkwind> According to that they feel it's fixed in the latest dpkg, which it doesn't appear to be actually from what we've seen
[12:04] <raphink> yes
[12:05] <lionelp> raphink: this one is better : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341506
[12:05] <raphink> Ubugtu: wake up :p
[12:05] <raphink> grr
[12:05] <raphink> yes I saw this one, too


[04:49]  * johnc4510-laptop tells all: UWN #111 is out: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue111
[13:27] <Rafik> hello
[13:27] <Rafik> I would like to add a meeting on to the Fridge.
[13:29] <Rafik> It's the first meeting of the Ubuntu-Arabic team and will be held on #ubuntu-meeting Friday, October 10, 2008 at 17:00:00 UTC time
[13:36] <Rafik> mail sent. Thank you.
[13:40] <tyche> Rafik: What time does it end, and can you provide a link for the agenda?
[17:47] <tyche> Rinchen: PING.  Sorry about the delay.  I just got done with the Team newsletter.
[17:47] <Rinchen> no worries tyche
[17:48] <Rinchen> tyche, I'll PM you
[17:48] <tyche> kk