[12:18] <pochu> good night folks!
[12:18] <keescook> *fume* I hate squid! why is it sooo broken?
[12:18] <ward_> persia, its a very small file :-)
[12:19] <persia> ward_: structscanner.h?
[12:19] <ward_> persia, yeah
[12:19] <persia> ward_: Should be an easy patch then :)
[12:19] <ward_> like one page
[12:19] <ward_> what is a namespace? :s
[12:19] <ward_> namespace utils
[12:19] <ajmitch> keescook: because it likes to inflict pain?
[12:20] <ward_> and in there there is class StructScanner
[12:20] <ward_> {
[12:20] <ward_> my guess is that's the part u mean?
[12:20] <ward_> persia
[12:20] <keescook> ajmitch: that must be the answer.  It's making me reaaly crazy at the moment.  endless random "connection reset by peer".  gaah
[12:20] <persia> ward_: "namespace utils" is a compiler directive that indicates that any identifiers for which the namespace is not explicitly declared (like std::string) should be considered in the utils namespace (automatic prepending of utils::).
[12:22] <ward_> persia, i'm unfamiliar with notation like std::string, never did c / c++
[12:22] <ward_> this looks a bit odd for me
[12:22] <ward_> but since its so small i sohuld be able to figure it out, but i don't understand what's going wrong yet
[12:22] <ward_> #include "istructtokenlistener.h"
[12:23] <ward_> so i sohuld probably check that header too?
[12:24] <persia> ward_: In your make output, it said there was an extra declaration.  Because namespace utils is already declared, anything with utils:: is probably wrong.  Also, if you're looking at code inside class StructScanner, anything with structscanner:: is probably wrong.
[12:24] <persia> s/declaration/specification/
[12:26] <ward_> persia, that's gonna be quite a chunk
[12:27] <persia> ward_: Take another look at your make output.  There are three declarations that are indicated as having something wrong.  Try those first.
[12:28] <ward_> persia, ok
[12:34] <superm1> Lutin, ScottK: there are packages already in ubuntu's archive that have a lib* source package and create binary packages that aren't lib*.  For example: http://packages.ubuntu.com/feisty/source/libextractor-python
[12:35] <ScottK> superm1: OK.  I'm fine with it.  If you can find another MOTU that agrees, then you're good.  
[12:35] <persia> libjsw2 is another example.
[12:36] <superm1> well persia would you be able to look over this revu then to add comments (and possibly advocate?)
[12:37] <persia> superm1: I need to leave in about 10 minutes, but if nobody else looks at it before I have time, I'll take a look in 12-15 hours.
[12:37] <superm1> Okay persia thanks
[12:37] <persia> ward_: Good luck.  I suspect it won't work the first time (it usually takes me at least 3 times to fix all the compiler errors when building).
[12:38] <ward_> persia, i allready fixed 2 other problems :p
[12:38] <ward_> persia, its time to give me a break :p
[12:38] <persia> ward_: Then this time might be it :)
[12:38] <ward_> persia, i'm fairly confident i erased the right lines though
[12:39] <ward_> how exactly is it possible that some packages are so impossible to build?
[12:40] <ward_> whats the reason that it happens i mean
[12:40] <persia> ward_: Packages get old over time, and standards change.
[12:40] <ward_> that i need to replace ffmpeg with a svn version, use gcc3.4, edit a header, etc
[12:41] <persia> ward_: If you had to do that much, it might just be poor code.
[12:41] <ward_> lol gephex 0.4.4 also has problems (and when u finally fix them, u end up with a GUIu cannot use)
[12:41] <ward_> persia, the weird thing is it works really nice and fast
[12:41] <ward_> (its a live video manipulation tool)
[12:42] <ward_> anyway i hope it works now
[12:46] <ward_> persia, http://paste.ubuntu-nl.org/23339/
[12:46] <ward_> lol
[12:46] <ward_> it says it misses what i removed from the code
[12:47] <persia> ward_: It looks like you deleted the lines.  You just need to remove utils::StructScanner:: from the declarations.  I have to go now, but give that a try.
[12:52] <ward_> allright :-D that error is gone, and i got a new similar one, so i know how to fix it :-)
[01:00] <TheMuso> woohoo!
[01:00] <TheMuso> LP closes bugs from changelogs!
[01:00] <TheMuso> Finally.
[01:00] <ward_> can anyone look at this: http://paste.ubuntu-nl.org/23340/
[01:01] <ward_> could those errors be because i'm using gcc3.4 instead of gcc4 ?
[01:03] <crimsun> no
[01:03] <crimsun> your error is on line 108
[01:03] <crimsun> sorry, 105
[01:04] <ward_> lol omg, thanx crimsun 
[01:04] <ward_> i'm at it too long i think, loosing focus lol
[01:06] <ward_> crimsun, this means its looking for avutils.h in '../../../contrib/ffmpeg/libavcodec/' ?       ../../../contrib/ffmpeg/libavcodec/avcodec.h:30:20: error: avutil.h: No such file or directory
[01:07] <StevenK> TheMuso: Wow! Which bug?
[01:08] <LaserJock> crimsun: turns out the gnuchess stuff in ./configure was used
[01:08] <crimsun> LaserJock: used where and when?
[01:08] <LaserJock> crimsun: the hard-coded stuff I found was a failsafe
[01:09] <LaserJock> it's used at build time to get the path for gnuchess
[01:09] <ward_> how can i tell make avutil.h is in another dir?
[01:09] <LaserJock> then at run time it uses that variable if set, otherwise it has that hardcoded path (which wouldn't work in this case I don't think)
[01:09] <superm1> crimsun, could you comment at all about the source package naming confusion of libhdhomerun above by me, ScottK and Lutin ?
[01:09] <TheMuso> StevenK: You seen -devel-announce?
[01:10] <StevenK> TheMuso: I just got to work. I haven't read mail yet.
[01:10] <TheMuso> StevenK: Ah okk.
[01:10] <TheMuso> mdz posted about it.
[01:10] <leonel> ScottK:  here we go again with   clamav   there's a new version ..
[01:10] <leonel> ScottK:  WARNING: Local version: 0.90.2 Recommended version: 0.90.3
[01:10] <leonel> even there's no official release announce  
[01:16] <crimsun> ward_: do you have the appropriate -dev packages installed?
[01:16] <leonel> ScottK: http://downloads.sourceforge.net/clamav/clamav-0.90.3.tar.gz   here is the tarball
[01:16] <crimsun> superm1: I'll have to read in a bit
[01:17] <ward_> crimsun, yep, but i think i've found something, i'll go try that first
[01:25] <Q-FUNK> hm
[01:26] <Q-FUNK> odd file that "sudo rm -rf" cannot remove and whose attributes appear as:
[01:26] <Q-FUNK> ?--------- ? ? ? ? filename
[01:26] <crimsun> umount and fsck the fs?
[01:30] <Q-FUNK> done.  still not good
[01:31] <Q-FUNK> besides, that files remained form an old backup
[01:31] <Q-FUNK> it apparently stuck during homedir restore to a new server
[01:41] <ward_> http://paste.ubuntu-nl.org/23347/
[01:41] <ward_> what's wrong with the arrays?
[01:42] <ward_> arraytype heeft onvolledig elementtype means "array type has uncomplete element type"
[01:49] <ward_> what does that mean?
[01:49] <ward_> (i'm not a coder)
[01:50] <crimsun> paste the source code lines
[01:50] <crimsun> that would be lines 67 & 71 of common.h
[01:50] <ward_> extern const struct AVOption avoptions_common[3 + 5] ;
[01:50] <crimsun> likely it's a pointer vs. array ...
[01:50] <ward_> extern const struct AVOption avoptions_workaround_bug[11] ;
[01:51] <ward_> that's them
[01:51] <ward_> the only thing i know about an array is that it is sortof a list of more items
[01:51] <ward_> lol
[01:52] <ward_> crimsun, i posted the lines
[01:52] <crimsun> arrays are solely of object types
[01:52] <ward_> crimsun, i don't really know how u mean that
[01:53] <ward_> crimsun, (everything i know about coding is very distant schoolknowledge very far away in my head)
[01:54] <ward_> crimsun, can u give an example on how i could fix them?
[01:55] <crimsun> this is a classic example of gcc4 Doing The Right Thing
[01:55] <ward_> crimsun, i can't use gcc4 because of other errors :(
[01:56] <ward_> Ash-Fox, told me (he helped me earlyer)
[01:56] <ward_> i use gcc3.4 atm
[01:56] <crimsun> you really should get the errors triggered by gcc4 fixed
[01:57] <ward_> crimsun, ok i'll start over then
[01:57] <crimsun> s/trigger/expos/
[01:57] <ward_> what is that? :s
[01:58] <crimsun> I was attempting to disambiguate "errors triggered by gcc4" [which could be misinterpreted as a bug in gcc4]  and "exposed by gcc4" [which strictly means an error in the code you're attempting to compile] 
[02:06] <ward_> crimsun, i'm gonna try it using gcc4
[02:06] <ward_> but i frist need to know how to remove the symlink i made
[02:06] <ward_> and i can't find that on google apperantly...
[02:06] <crimsun> what symlink did you make?
[02:07] <crimsun> (please don't tell me you did this for gcc/cpp/g++ ...)
[02:07] <ward_> one to make it use gcc3.4
[02:07] <ward_> crimsun, oops
[02:07] <ward_> crimsun, correct
[02:07] <ward_> it was Ash-Fox his advice
[02:08] <ward_> crimsun, please don't tell me its unfixable or hard to fix
[02:09] <crimsun> it's not unfixable or hard to fix
[02:09] <crimsun> it's just not the Debian way to do it.
[02:10] <ward_> crimsun, ok
[02:10] <ward_> crimsun, could you tell me how to list and remove a symlink please? (i'll write it down so i wont need google next time)
[02:11] <crimsun> you may use rm to delete a symlink
[02:11] <ward_> is there no way to list all of them?
[02:11] <ward_> lol
[02:11] <crimsun> I don't know which symlinks you set
[02:11] <ward_> crimsun, i can look that up, just a second ;-)
[02:14] <ward_> ln -s /usr/bin/gcc-3.4 ~/bin/gcc
[02:14] <ward_> crimsun, 
[02:14] <ward_> so u just remove the littel icon i see in ~/bin/gcc ?
[02:14] <ward_> with nautilus
[02:15] <ward_> (or rm)
[02:15] <ward_> done
[02:16] <ward_> ok i'm back at normal gcc says gcc --vrsion
[02:16] <ward_> version
[02:16] <minghua> crimsun: just curious, is there a Debian way to change /usr/bin/gcc?
[02:17] <ward_> doing make clean, then ./configure and make again
[02:17] <minghua> crimsun: or the Debian way is just setting CC or PATH, etc.?
[02:18] <leonel> is the Q&A  now ? 
[02:18] <ward_> crimsun, i got the same error with gcc4 ........
[02:18] <ward_> common.h:67: fout: arraytype heeft onvolledig elementtype
[02:18] <ward_> common.h:71: fout: arraytype heeft onvolledig elementtype
[02:18] <crimsun> leonel: yes
[02:18] <ward_> translation:
[02:19] <ward_> "arraytype has incomplete elementtype"
[02:34] <ward_> crimsun, any ideas left?
[02:34] <ward_> same error
 translation:
 "arraytype has incomplete elementtype"
[02:34] <crimsun> I'm busy ATM, sorry
[02:34] <ward_> crimsun, no problem
[02:34] <ward_> anyone else?
[02:50] <crimsun> minghua: gcc-defaults sets it.  exporting/setting CC/CPP/CXX is the preferred way instead of fudging symlinks.
[02:51] <crimsun> ward_: what's the issue?
[02:53] <ward_> crimsun, http://paste.ubuntu-nl.org/23347/
[02:53] <ward_> still the same error
[02:55] <crimsun> ward_: ...but you didn't fix the source code itself.  Surely you didn't expect the error to magically disappear?
[02:56] <minghua> crimsun: thanks
[02:56] <ward_> crimsun, i don't know what to do with the sourc,e sorry
[02:56] <ward_> crimsun, i don't normally code stuff :(
[02:56] <ward_> i don't see what's wrong with the array
[02:59] <ward_> crimsun, you said it was probably solved by using gcc4, thats what i'm using now
[02:59] <ward_> just to make sure u don't think i'm still at gcc3.4
[03:00] <crimsun> err, I said that?
 this is a classic example of gcc4 Doing The Right Thing
[03:01] <crimsun> AFAIR, I said that gcc4 does the right thing.  This means that it's more strict than 3.4, so it will throw more errors.  You need to fix the source code.
[03:01] <ward_> i thought you meant that with this sentence yes
[03:01] <ward_> aaaaah :-)
[03:01] <ward_> crimsun, ok but still i don't know how to fix the arrays
[03:01] <ward_> i'm not a coder
[03:01] <ward_> (but i do understand basics to some level)
[03:19] <superm1> StevenK, is there a class going on tonight for MOTU?
[03:22] <ward__> crimsun, also: the old error is long gone (this one:)
[03:22] <ward__> oops too far away lol, but the one with the wrong path to the ffmpeg file = fixed
[03:22] <ward__> just to make sure you know that
[03:23] <ward__> its only about the arrays
[03:23] <StevenK> superm1: There's a Q&A session on. Apparently.
[03:24] <superm1> ah
[03:24] <superm1> StevenK, seems a bit dead for a Q&A session no?
[03:24] <crimsun> it's over in 6 minutes.
[03:24] <crimsun> (the next Q&A will be at 1200 UTC)
[03:25] <superm1> ah
[03:28] <superm1> crimsun, did you get a chance to look over that discussion earlier today about the naming of that source package?
[03:28] <ward__> what's wrong with this please? extern const struct AVOption avoptions_workaround_bug[11] ;
[03:30] <RAOF> ward__: We'd generally need *some* context.  Why not pastebin the source which has errors?  And the actual errors, too - they generally contain invaluable information.
[03:31] <ward__> RAOF, ok but the actual error i pasted here too
[03:31] <ward__> so, all in a row:
[03:31] <ward__> output make: http://paste.ubuntu-nl.org/23347/
[03:31] <ward__> with the actual error in dutch
[03:32] <ward__> line 17 and 18
[03:32] <ward__> its translated:
[03:32] <ward__> arraytype has incomplete element type
[03:32] <ward__> (Fout = error)
[03:32] <ward__> source is comming up :-)
[03:33] <ward__> source: http://paste.ubuntu-nl.org/23357/
[03:33] <minghua> ward__: run "LANG=C make" can save you a lot of explanations :-)
[03:34] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=5314 ?
[03:34] <ward__> minghua, can you please explain that?
[03:35] <ward__> RAOF, i posted everything in a row now :-)
[03:35] <ward__> RAOF, please tell me if you want more info
[03:35] <RAOF> Well, I think that error tells me exactly what I need to know.  You probably don't have the necessary includes which actually *define* AVOption.  Secondly, I don't think the line should have the arraysize - you're just importing an extern, which is going to be allocated somewhere else, right?  It'll be imported as a pointer.
[03:35] <minghua> ward__: instead of running command "make", you can run "LANG=C make", then the messages from compiler will be English instead of Dutch
[03:36] <ward__> RAOF, i'm not a coder, i'm not evne long into ubuntu
[03:36] <RAOF> ward__: Yup.  You can't allocate something (which is what the foo[11]  says to do - allocate an array of size 11 on the stack) without knowing how big it is :)
[03:36] <ward__> minghua, i'll keep that in mind thanx for the tip :-)
[03:37] <RAOF> ward__: So where is this code coming from?
[03:37] <ward__> gephex
[03:37] <ward__> (www.gephex.org)
[03:37] <ward__> i'm just trying to build it
[03:37] <ward__> got nothing to do with it
[03:37] <RAOF> ward__: Ah, OK.  It's broken.
[03:37] <RAOF> ward__: Go complain to whoever wrote it :)
[03:37] <ward__> lol RAOF nice (not)
[03:37] <ward__> RAOF, i was hoping it could be easily fixed?
[03:38] <RAOF> ward__: Not without some understanding of what it's actually trying to do.  And the person most likely to have that understanding is the guy who wrote it :)
[03:38] <ward__> (i had to correct a header earlyer too :s )
[03:39] <ward__> RAOF, damnit why is it not documented :p
[03:39] <RAOF> Well, you could *possibly* just add and "#include <avutil.h>" (or whatever ffmpeg header includes the AVOption definition)
[03:39] <ward__> *allmost* undocumented
[03:40] <ward__> RAOF, its worth a try
[03:40] <ward__> RAOF, but won't it still complain about those arrays then?
[03:41] <RAOF> No, it shouldn't.  Because it will then actually know how big they are, and be able to allocate them.
[03:41] <RAOF> But it would seem that the guy who wrote that code didn't actually build it, because I can't see how it could ever work.
[03:41] <ward__> RAOF, it just misses variables from other files?
[03:41] <ward__> RAOF, lol its their official source :p
[03:42] <ward__> form the 0.4.3 version
[03:42] <RAOF> Yeah.  You need to have AVOption defined before you can create an AVOption array :)
[03:42] <ward__> and AVOption is in one of the ffmpeg headers
[03:42] <ward__> ?
[03:43] <ward__> so i have a good chance of getting it to work with including the right header :-)
[03:44] <minghua> RAOF: it's an header, so maybe just #include orders
[03:45] <RAOF> Ah, of course.  But it has an explicit forward declaration of AVOption in there, too.
[03:45] <ward__> RAOF, minghua how do i know wich header AVOption is in?
[03:45] <RAOF> As far as I'm aware, there's not situation in which that would help.  Either avfoo.h has been included first, or those arrays can't be allocated.
[03:46] <minghua> also it's enclosed by #ifdef HAVE_AV_CONFIG_H ... #endif
[03:46] <RAOF> ward__: "grep AVOption /usr/include/*.h" ?
[03:46] <minghua> so supposedly that is defined in av-config.h
[03:47] <ward__> RAOF, i'll write it down, so i can't forget it this time :-)
[03:48] <ward__> i'm used to using GUIs
[03:49] <ward__> RAOF, i find no headers :s
[03:50] <RAOF> ward__: Add -R.  "grep -R AVOption /usr/include/*.h"
[03:50] <RAOF> (That makes it recursive, so it'll go into sub-directories)
[03:50] <ward__> RAOF, nothing still
[03:51] <ward__> RAOF, i'll try the ffmpeg source
[03:51] <ward__> nothing
[03:51] <ward__> :s
[03:53] <ward__> how's that evne possible? :s
[03:53] <ward__> its clearly about ffmpeg
[03:54] <ward__> #define AVOPTION_CODEC_STRING(name, help, field, str, val) \
[03:54] <ward__>     { name, help, offsetof(AVCodecContext, field),
[03:55] <ward__> RAOF, minghua i just saw i made a huge mistake
[03:55] <ward__> RAOF, minghua the code is from ffmpeg
[03:55] <ward__> RAOF, minghua i made the mistake because ffmpeg comed with the gephex source...
[03:55] <ward__> sorry
[03:56] <ward__> does that make more sense?
[04:00] <RAOF> Ah, so gephex comes with a copy of the ffmpeg source?
[04:00] <ward__> yep
[04:00] <RAOF> Fair enough.  Grep that source, instead :)
[04:00] <ward__> RAOF, i allready tried, nothing....
[04:00] <ward__> :s
[04:04] <ward__> RAOF, in the meantime i'll try an svnned ffmpeg too
[04:05] <ward__> RAOF, nothing in the svn version either :s
[04:08] <ward__> RAOF, any other suggestion?
[04:11] <ScottK> leonel: I saw the release announcement.  I don't see anything in 0.90.3 to be excited about.  They also announced 0.91 RC 1 at the same time.  At this point I'm thinking we should wait for that and backport that to Feisty (and earlier if we get the policy issues worked out).
[04:17] <RAOF> ward__: Sorry, no, not really.
[04:17] <ward__> RAOF, ok np
[04:17] <ward__> thanx anyway
[04:30] <crimsun> whew, enough flying for me
[04:39] <LaserJock> crimsun: in DC now?
[04:40] <crimsun> LaserJock: no, back home.  Flew to Charlotte for some meetings earlier.
[04:40] <crimsun> I don't move until late June.
[04:40] <LaserJock> oh, right
[04:49] <leonel> ScottK: only the  PDF  security bug
[04:49] <leonel> ScottK:  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2029
[05:46] <Hobbsee> hi all
[05:46] <LaserJock> hi Hobbsee 
[05:47] <ajmitch> hello Hobbsee 
[05:47] <Hobbsee> :)
[05:53] <leonel> see you 
[05:53] <leonel> tomorrow
[05:53] <leonel> apt-get remove leonel ...
[06:06] <joejaxx> hello all
[06:10] <joejaxx> welcome back netsplitters
[06:11] <Hobbsee> hi joejaxx!
[06:11] <joejaxx> :D
[06:11] <joejaxx> hello Hobbsee 
[06:11] <joejaxx> :)
[07:52] <crimsun> gpocentek: ping, cdbs usage in gutsy's xfce4-mixer breaks the build [xfce4-mixer-alsa is never generated, and xfce4-mixer-oss actually contains the ALSA-enabled version] .  I'm going to revert it to non-cdbs.
[07:53] <crimsun> gpocentek: (as a result, xubuntu-desktop will be installable once again, since xfce4-mixer-alsa is currently uninstallable)
[07:55] <crimsun> moreover, I don't feel cdbs buys us anything in this instance, and it's already demonstrated that maintaining such a delta leads to subtle bugs
[07:56] <StevenK> Debian's xfce4-mixer doesn't use CDBS?
[07:57] <crimsun> nope
[07:57] <crimsun> debhelper and quilt
[07:58] <StevenK> Hrm. I'm personally of the opinion that we should be sticking as close as possible to Debian.
[07:59] <crimsun> yep, and dropping cdbs will realign us with Debian with the exception of one additional patch in debian/patches/
[08:00] <StevenK> So the only changes are debian/rules, control and that patch?
[08:04] <crimsun> just debian/{control,changelog} and debian/patches/02_xfce4-mixer-panel-plugin_border.patch
[08:04] <crimsun> err, that's what it will be
[08:04] <crimsun> the current delta is debian/{control,changelog,rules} and said patch
[08:10] <crimsun> xfce4-mixer?
[08:10] <crimsun> I'm looking at it now, but if you'd like it, feel free
[08:11] <crimsun> it'll strike one off http://people.ubuntu.com/~ubuntu-archive/testing/gutsy_probs.html
[08:12] <Hobbsee> 2 actually
[08:12] <crimsun> oh right, the bottom two
[09:05] <Hobbsee> morning dholbach 
[09:05] <dholbach> hiya Hobbsee
[09:08] <Hobbsee> :)
[09:08] <Tonio_> hey Hobbsee
[09:08] <Hobbsee> :)
[09:14] <LaserJock> Hobbsee: like National Instruments Labview?
[09:14] <Hobbsee> LaserJock: yes
[09:14] <LaserJock> I was doing that today too!
[09:14] <LaserJock> trying to figure out how to get the blasted thing to talk to our new oscilliscope
[09:15] <LaserJock> I spent a couple hours digging through the driver
[09:15] <LaserJock> and finally found that the function that checked the oscilliscope model had a '" instead of a " around the name of my particular model
[09:15] <Hobbsee> heh
[09:15] <LaserJock> that stupid ' was all that was preventing me from getting the thing to work
[09:16] <LaserJock> and *my* model was the only one with that proble
[09:16] <LaserJock> +m
[09:17] <Hobbsee> awww
[09:17] <Fujitsu> What does Labview do?
[09:20] <imbrandon> views the lab?
[09:20] <imbrandon> heh
[09:20] <LaserJock> Labview is *the* industry standard for data aquisition many scientific fields
[09:20] <LaserJock> *in many
[09:21] <LaserJock> in fact, I better hope I don't need to get an industry job as I don't know Labview at all
[09:21] <imbrandon> heh
[09:21] <LaserJock> it's like a graphical programming framework
[09:21] <Hobbsee> at least it works on linux.
[09:21] <LaserJock> we just bought a new Dell with XP on it just for Labview
[09:22] <LaserJock> I spent nearlly $3000 to get a Labview system going
[09:22] <imbrandon> Dell with Ubuntu for Labview ?
[09:22] <LaserJock> too bad it was before then
[09:22] <imbrandon> hehe
[09:22] <LaserJock> but I don't think my boss would go for it
[09:22] <LaserJock> he didn't like the idea of running Labview on Linux
[09:23] <Hobbsee> i guess you need teh driver support
[09:23] <LaserJock> Fujitsu: http://www.ni.com/labview/ if you want more info
[09:23] <LaserJock> well, I think mostly my boss doesn't see Linux as a desktop OS
[09:23] <LaserJock> he ran it as a Desktop OS for many many years
[09:24] <imbrandon> he hasent used ubuntu on a dell :)
[09:24] <LaserJock> but he also does everything in Fortran and uses Latex for presentations
[09:24] <imbrandon> heh
[09:24] <LaserJock> even on his Mac
[09:25] <LaserJock> although he does seemed to have started using Excel a bit
[09:25] <imbrandon> calc ? heh
[09:26] <LaserJock> well, he was die hard linux
[09:26] <LaserJock> probably one of the biggest linux advocates in my uni
[09:26] <LaserJock> and still is, to some extent
[09:26] <LaserJock> but OS X got him
[09:26] <Fujitsu> :(
[09:27] <LaserJock> we used to have 6 or so Linux machines
[09:27] <LaserJock> no Windows
[09:28] <LaserJock> now we have 2 Linux machines and 4 imacs running OS X
[09:29] <LaserJock> I wish Ubuntu would've come along a little sooner
[09:29] <LaserJock> FC 1 is what killed him
[09:44] <elkbuntu> crimsun, what is this i hear about nixternal using vista and where is the evidence? kthxbai :
[10:31] <DktrKranz> is "Architecture: linux-any" acceptable in debian/control?
[10:39] <imbrandon> s/linux-//
[10:39] <DktrKranz> ok, thanks :)
[10:40] <imbrandon> elkbuntu, per proper lolcode its KTHXBYE not kthxbai :)
[10:40] <imbrandon> hehe
[11:10] <ajmitch> arg, monitor seems deadish
[11:15] <ajmitch> now I'm stuck with only 1 screen :(
[11:15] <highvoltage> ajmitch: what if you press ctrl+a then c ?
[11:15] <highvoltage> ajmitch: that should give you a new one? ;)
[11:15] <ajmitch> not helpful
[11:16] <highvoltage> ouch
[11:16] <highvoltage> dying hardware is not fun
[11:16] <ajmitch> it was dying for awhile
[11:17] <ajmitch> this was not unexpected
[11:21] <Hobbsee> ajmitch: but you're not out of the country!
[11:21] <Hobbsee> it's not allowed to die.
[11:22] <ajmitch> I know!
[11:28] <dholbach> is there any new contributor who'd like to a first upload and use https://wiki.ubuntu.com/MOTU/Recipes/Debdiff and make gnopernicus build-depends on libgnome-speech-dev instead of libgnome-speech3-dev? :-)
[11:28] <dholbach> same for lsr?
[11:35] <TheMuso> dholbach: I'll do that.
[11:35] <TheMuso> dholbach: I'd rather do the a11y stuff.
[11:35] <TheMuso> I've just been busy with other things.
[11:36] <wolfeon> ajmitch: hehe, yeah. that is what I use, 3200x1200
[11:37] <wolfeon> CRT though..
[11:37] <dholbach> TheMuso: ok
[11:40] <Hobbsee> TheMuso: didnt think you were a new contributor
[11:40] <crimsun> I am!
[11:42] <TheMuso> ~/aw
[11:42] <TheMuso> gah
[11:42] <TheMuso> Hobbsee: heh
[11:42] <TheMuso> Hobbsee: I see that stuff as my pet though.
[11:42] <Hobbsee> (sounds like a bitesize bug)
[11:43] <TheMuso> SO?
[11:43] <Hobbsee> no big problem.  just anyone who was looking for something to do, like the guy from yesterday could do it.  but they havent shown up
[11:46] <DktrKranz> if you want a new contributor, here I am :)
[11:51] <crimsun> off to work.
[11:57] <gnomefreak> anyone have a minute to look at this error and let me know what i can do? http://gnomefreak.pastebin.ca/525318
[11:57] <gnomefreak> it seems like its something that is in my face just cant see it
[11:58] <highvoltage> dholbach: ooh, I just took a peak at the recipes pages and notice that you use bresero as an example. how convenient!
[12:00] <dholbach> highvoltage: it's still not updated in the archive :)
[12:00] <highvoltage> dholbach: I'll get it done this week still, I've been swamped in different ways since getting back home
[12:00] <highvoltage> dholbach: btw, do you have to use American spelling in control files?
[12:00] <dholbach> I can imagine
[12:00] <dholbach> take your time
[12:01] <dholbach> highvoltage: not at all
[12:01] <highvoltage> (I just noticed the s/dolour/color)
[12:01] <highvoltage> *colour
[12:01] <dholbach> highvoltage: it was just a bad joke
[12:01] <highvoltage> aaaaaah :)
[12:01] <highvoltage> shew!
[12:01] <dholbach> maybe I should make that clear :)
[12:02] <dholbach> added a note
[12:15] <Baby> is is possible from debian/rules file to know whether the package is being built for ubuntu? any extra define or something like that?
[12:16] <imbrandon> Baby, not that i'm aware, why would you want to though ?
[12:17] <Baby> for the menu stuff, i heard that there were differences
[12:18] <StevenK> Baby: lsb-release
[12:18] <StevenK> Although it's kind of messy to rely on that.
[12:18] <Baby> yup, that's what i was thinking
[12:21] <Baby> dh_iconcache is specific to ubuntu too, isn't it?
[12:22] <Baby> lunch time for me, i'll ask later about it
[12:25] <Hobbsee> Baby: yes it is
[12:27] <pochu> Baby: Debian #369755. Tomorrow will be its first birthay :/
[12:27] <ubotu> Debian bug 369755 in debhelper "Use dh_iconcache to update GTK's icon cache." [Wishlist,Open]  http://bugs.debian.org/369755
[12:28] <StevenK> Yeah, well, Joey Hess doesn't like Ubuntu much.
[12:30] <imbrandon> he can get over it
[12:37] <StevenK> I can't see him doing so.
[12:37] <StevenK> I can see his point, though.
[12:56] <gnomefreak> after modifing debian/configure.in do i have to run anything other than clean or build?
[12:57] <sacater> if I were to try and use gentoo portage on ubuntu might it break apt?
[12:59] <Amaranth> sacater: almost certainly
[12:59] <sacater> darn it
[01:01] <jmg> goldsarn it!
[01:02] <DarkSun88> Hi all
[01:03] <imbrandon> sacater, it wouldent "break" apt but it would render any package you installed form portage useless in apt and anything that depends on it
[01:03] <sacater> imbrandon: oookkaay
[01:03] <DarkSun88> Hi sacater 
[01:04] <sacater> imbrandon: sooo.... I could install from portage, but apt wouldnt see it and think it is not there, as it was not recorded in the database
[01:04] <imbrandon> sacater, if your bent on a portage type system write some wrappers for "apt-get source -b <package>"
[01:04] <sacater> aha
[01:04] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=5314 ?
[01:04] <sacater> imbrandon: good idea
[01:04] <jmg> sacater, is there a gentoo build script you are trying to port?
[01:05] <sacater> no no
[01:05] <sacater> im just trying portage
[01:05] <jmg> ok
[01:05] <jmg> use a chroot
[01:05] <jmg> ;)
[01:05] <sacater> seeing if it is any better than apt
[01:05] <jmg> or a vm
[01:05] <imbrandon> end users complieing from source is *never* better
[01:06] <imbrandon> developers , yes, powerusers possibly, but end users *never*
[01:06] <sacater> imbrandon: apt-get source is probably better, ill just make some commands
[01:06] <imbrandon> :)
[01:06] <sacater> imbrandon: hell I could even make a new bit of software :P
[01:07] <jmg> based on my recent experiences with gutsy, i have an idea for a new project - daily vm builds of unstable
[01:07] <jmg> distribute a diff against the previous version
[01:08] <jmg> cause having to wait for gutsy to get fixed was a pain.
[01:08] <jmg> oh crap.
[01:09] <sacater> imbrandon: dpkg-buildpackage: source version is 0.5.1-2ubuntu1
[01:09] <sacater> dpkg-buildpackage: source changed by Stephan Hermann <sh@sourcecode.de>
[01:09] <sacater> dpkg-buildpackage: host architecture i386
[01:09] <sacater> dpkg-buildpackage: source version without epoch 0.5.1-2ubuntu1
[01:09] <sacater> dpkg-checkbuilddeps: Unmet build dependencies: python-dev polygen
[01:09] <sacater> dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting.
[01:09] <sacater> dpkg-buildpackage: (Use -d flag to override.)
[01:09] <sacater> Build command cd cappuccino-0.5.1 && dpkg-buildpackage -b -uc failed.
[01:09] <sacater> E: Child process failed
[01:09] <sacater> thats for cappucino
[01:09] <sacater> i can never spell it
[01:09] <geser> apt-get build-dep cappuccino
[01:09] <sacater> of course
[01:09] <sacater> sory
[01:09] <sacater> but..
[01:10] <sacater> that uses apt
[01:10] <sacater> could I do something like apt-get source -b dep
[01:10] <sacater> or something else weird...
[01:12] <geser> and then a packages build-depends on python-all-dev and you start rebuilding python2.4 and python2.5 (and perhaps it's build-deps)
[01:12] <ryanakca> geser: lol
[01:13] <sacater> apt-get build-deps is not what Im after
[01:13] <sacater> i would want them to be compiled too
[01:13] <sacater> apt or a portage-mock
[01:15] <geser> do you really want to rebuild large parts of the system because of one package?
[01:15] <sacater> geser: no no, I just want to have the ability to compile source easily
[01:15] <sacater> gentoo uses portage, which gets all the sources, including dependancies
[01:16] <sacater> then compiles and installs them
[01:16] <sacater> from what imbrandon has told me, I think i could install portage onto my laptop, but any packages that are installed, apt wouldnt detect and ignore, seeing as they were not registered with apt's database
[01:17] <jmg> sacater: you could write a wrapper to register them with debian (equivs)
[01:18] <sacater> jmg: explain :P
[01:18] <StevenK> jmg: No encourging the ricer to do great evil. :-P
[01:19] <jmg> http://www.debian.org/doc/manuals/apt-howto/ch-helpers.en.html
[01:19] <jmg> sacater: yeah, just promise us no insane cflags.
[01:19] <jmg> StevenK: i miss funroll-loops :(
[01:20] <jmg> http://web.archive.org/web/20060513022941/http://www.funroll-loops.org/
[01:20] <gnomefreak> after changing debian/configure.in do i have to run anything or can i just continue to apply a patch and build?
[01:21] <jmg> "I use Gentoo because I'm a speed freak - I can't stand the thought that some of my packages might not be running as fast as they could be."
[01:21] <sacater> thats the negative side of gentoo
[01:21] <sacater> though it does source
[01:21] <sacater> takes longer
[01:22] <sacater> ubuntu uses pre-built binaries :D
[01:22] <jmg> "Yea, I really don't understand all the complaints about the time to install gentoo. It is like complaining about your Ferrari because the dealership was so far away."
[01:22] <jmg> ^^ gold
[01:22] <jmg> "Yet, binary distros are riddled with bugs, and are much more annoying to fix given the the cumbersome edit/build package/install package cycle."
[01:23] <persia> gnomefreak: Check your rules file.  If ./configure is regenerated as part of the build, you don't need to do anything at all.  If it's not, you need to manually rerun autoconf.
[01:23] <StevenK> Personally, I don't want to build the toolchain 3 times when I install. If I wanted that, I'd use LFS.
[01:23] <joejaxx> StevenK: lol
[01:23] <imbrandon> StevenK, exactly
[01:23] <gnomefreak> persia: nothing in rules from what i can tell
[01:23] <gnomefreak> rules file very small
[01:24] <StevenK> And I don't need to keep my hand on it saying "Ohh, ohh, ohh, -O7"
[01:24] <persia> gnomefreak: CDBS?
[01:24] <gnomefreak> yep
[01:24] <gnomefreak> clean::
[01:24] <gnomefreak> 	rm -f data/GNOME_Gwget.server.in data/GNOME_Gwget.server \
[01:24] <gnomefreak> 		data/gwget.schemas
[01:24] <gnomefreak> that is the clean section of rules
[01:25] <persia> gnomefreak: If it includes /usr/share/cdbs/1/class/autotools.mk, you're all set.  If not, you might want to regenerate.
[01:25] <gnomefreak> persia: it doesnt
[01:25] <gnomefreak> can i add it and call it a day?
[01:27] <persia> gnomefreak: If you're not finding it, but you think it should work, try building, and see if your change applied.
[01:28] <gnomefreak> persia: i would think since there isnt a autotools.mk file it wont work
[01:28] <gnomefreak> is taht fairly accurate
[01:29] <gnomefreak> lets try autoconf manually. how would i do that?
[01:29] <gnomefreak> s/try autoconf/try running autoconfig
[01:29] <persia> gnomefreak: That's my thought too, but there may be a mysterious something: GNOME is funny that way.  I'd recommend trying a build before running autoreconf anyway.
[01:36] <gnomefreak> persia: dpkg-buildpackage -rfakeroot -nc fails with some aclocal errors  i will pastebin them
[01:37] <gnomefreak> persia: http://gnomefreak.pastebin.ca/525475
[01:40] <persia> gnomefreak: I suspect you can either add autotools.mk (and adjust build-dep appropriately), or run `autoreconf` in the directory in which the modified configure.in resides to address that.
[01:41] <gnomefreak> ok ill try autoreconf  its easier (this package has beena nightmare
[01:43] <gnomefreak> persia: its not letting me :( it tells me configure.in or configure.ac is required so i ran autoreconf configure.in and givesme same output
[01:50] <persia> gnomefreak: I suspect that you are either suffering from timestamp issues or my understanding of autoreconf is flawed.  It looks to me like you have an outdated aclocal.m4.  Could you check the timestamps?  If it is newer than configure.in, I'm wrong.  If it is older, you might could try running `aclocal` to update it.
[01:52] <gnomefreak> aclocal: configure.in: 13: macro `AM_PROG_LIBTOOL' not found in library  am i missing something?
[01:52] <StevenK> Is libtool installed?
[01:52] <leonel> good  morning every one ..
[01:53] <StevenK> As much as I dislike to suggest it, given libtool's reputation.
[01:53] <gnomefreak> StevenK: ofcourse not :(
[01:53] <gnomefreak> it will be in a sec
[01:55] <persia> gnomefreak: That's often a better place, although it depends on what you are changing.
[01:55] <gnomefreak> just depends
[01:57] <dholbach> MOTU Q&A session in 3 minutes in #ubuntu-classroom
[01:57] <ScottK> jdong: Would you or someone in feisty-backports please have an accelerated look at Bug #117794.  As it stands, the current clamtk package in Feisty is essentially useless and this new one actually works.
[01:57] <ubotu> Launchpad bug 117794 in feisty-backports "Backport of clamtk 2.32-1 from Gutsy to Feisty" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117794
[01:57] <ScottK> leonel: Good morning.
[01:58] <joejaxx> yeah/win 12
[01:58] <joejaxx> bah
[01:58] <leonel> hey  ScottK ..
[01:59] <ScottK> leonel: I'll make you a deal on clamav.  You find the patch from upstream for that PDF issue that's fixed in 0.90.3 and I'll package it up for keescook to publish as a security update for Feisty.  I agree that one should be fixed, but I don't have time to hunt up the patch.
[02:01] <TheMuso> dholbach: Have you fixed orca to use the new gnome-speech?
[02:01] <TheMuso> Thats a yes.
[02:01] <TheMuso> Answered my own question.
[02:02] <StevenK> TheMuso: Best kind. Then you can be sure of the answer.
[02:02] <TheMuso> StevenK: True that.
[02:02] <StevenK> TheMuso: The Q&A session is going in -classroom if you want to help out.
[02:02] <TheMuso> Sure.
[02:02] <dholbach> TheMuso: yes :)
[02:07] <leonel> ScottK: let's smash that bug
[02:08] <ScottK> leonel: Great.  Let me know when you find the patch.
[02:08] <leonel> ScottK: it has another bug but only affects  with  files on  FAT filesystems   
[02:09] <ScottK> It's not a security issue.
[02:09] <leonel> ScottK: I'll  start  in about  3 - 4 hours ...  and let you know the progress 
[02:09] <leonel> ScottK: you are right .
[02:09] <ScottK> leonel: OK.  I should be around then.
[02:09] <leonel> ok
[02:09] <persia> ScottK: Are you sure?  Does nobody scan FAT USB sticks?
[02:09] <leonel> now I got to go  for 1 hour and be back
[02:10] <ScottK> persia: Is it a security issue?
[02:10] <StevenK> persia: My USB stick resents being called fat.
[02:10] <leonel> persia: gets in a loop  when scanning files on FAT filesystems
[02:10] <leonel> I can look at it   ant see what happens  
[02:11] <ScottK> persia: Good.  That'll be one of us then.
[02:11] <persia> :)
[02:11] <leonel> persia: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2650
[02:12] <persia> leonel: That's a great help.  Thanks.
[02:12] <leonel> persia: no problemo 
[02:12] <persia> ScottK: I'd say so.  It can take a machine down if the right MS word document is on a scanned USB stick.
[02:12] <ScottK> leonel: OK.  I'll call that one a security bug then if it's got a CVE.  I think that's lower priority than the PDF bug, but still doable.
[02:13] <ScottK> persia: Agreed.  OTOH, I'm a lot less worried about desktop DoS than server DoS.  On a desktop, you pull out the memory stick and restart.
[02:13] <persia> leonel: Of course, if you can fix both in the same upload, you get bonus points :)
[02:14] <persia> ScottK: You haven't met the same junior sysadmins I have then :)
[02:14] <ScottK> Not saying it shouldn't be fixed, just less important than the PDF one.
[02:15] <xxxxx1> morning people!
[02:16] <effie_jayx> xxxxx1, good morning :D
[02:18] <dholbach> another ping: MOTU Q&A session in #ubuntu-classroom :-)
[02:22] <leonel_> ScottK:   but what about  the  freshclam message that we are using  an outdated clamav version ?
[02:24] <ScottK> leonel_: Nothing to be done about that directly.  Once clamav 0.91 is out (it had it's first release candidate yesterday) and we get that into Gutsy, I'll ask for a backport.  Just ignore it.
[02:31] <Lure> any revu-admin here?
[02:31] <Lure> do I need to do something special to get reviewers right as a motu?
[02:32] <sacater> sigh
[02:32] <sacater> is it possible to install portage on ubuntu
[02:32] <jekil> hello
[02:32] <persia> Lure: You need someone to add you to the list.  Takes about 5 minutes, but requires a REVU-admin.
[02:32] <Lure> persia: thanks, so it is not linked to LP?
[02:33] <TheMuso> sacater: Why would you want to do that?
[02:33] <persia> Lure: Only loosely at this point.  There were plans to make a closer link several months ago, but I haven't heard anything new since January or so.
[02:34] <Lure> siretart, ajmitch, raphink: anybody around? ^^^
[02:34] <sacater> TheMuso: a sort of bet, a sort of challenge, a sort of experiment
[02:34] <sacater> TheMuso: im having an argument with some mates about portage and apt
[02:34] <TheMuso> sacater: Well if you want to screw up your system, go ahead and try it.
[02:34] <sacater> TheMuso: ah
[02:35] <sacater> TheMuso: how would it screw it up
[02:35] <sacater> ive been told databases would be the trouble
[02:35] <TheMuso> sacater: Portage also installs into /usr 
[02:35] <TheMuso> So one package system would tread on another.
[02:36] <sacater> hmm
[02:36] <StevenK> And on a Ubuntu system, I'm of the opinion (and many agree with me), that /usr isn't yours to touch.
[02:36] <sacater> darn it
[02:36] <TheMuso> StevenK: Add me to the agreement list.
[02:36] <sacater> well I already do that myself
[02:36] <persia> sacater: If you're truly bent and determined, search the debian-devel archives for hints on building Debian from source, or be prepared to reinstall after your experiment.
[02:36] <sacater> i compile xfce and fluxbox myself, and they install fine
[02:36] <sacater> and work fine
[02:36] <sacater> hmm
[02:36] <sacater> persia: okies thanks
[02:36] <siretart> Lure: uh?
[02:37] <Lure> siretart: can you enable my reviewers rights on revu?
[02:37] <siretart> your revu id? (email)
[02:37] <Lure> siretart: [14:32]  <persia> Lure: You need someone to add you to the list.  Takes about 5 minutes, but requires a REVU-admin.
[02:37] <Lure> siretart: lure@ubuntu.com
[02:38] <siretart> Lure: done
[02:39] <sacater> persia: i compile lots of software from source, whole desktop enviroments, and they all work fine without any conflicts
[02:39] <Lure> siretart: thanks!
[02:40] <persia> sacater: You have better luck than I.
[02:40] <persia> (assuming "compiling from source" does not include "wrapping in Debian packaging")
[02:41] <StevenK> I've managed to blow up machines by compiling, say, Perl from source.
[02:41] <sacater> persia: configure
[02:41] <sacater> make
[02:41] <sacater> make install
[02:41] <sacater> works fine for me
[02:42] <StevenK> The perl in /usr/local/bin trumps the one in /usr/bin, and the Perl in /usr/local/bin doesn't have the module paths the packaged one has, and therefore can't find anything.
[02:43] <sacater> azeem: su
[02:43] <sacater> sorry
[02:43] <sacater> wrong channel
[02:47] <shawarma> gnomefreak: Does your debian/gwget.install refer to /usr/include/gwget ?
[02:47] <shawarma> gnomefreak: Wow. never mind.
[02:47] <shawarma> gnomefreak: I hadn't noticed my irc window was scrolled *way* up.. :)
[02:49] <effie_jayx> ScottK, ok.. I'm merging clamav right?
[02:50] <ScottK> Yes
[02:51] <ScottK> Have you done merges before?
[02:51] <effie_jayx> ScottK,  nope ... my first one... but I am putting heart to it... 
[02:52] <ScottK> OK.  Do you know where to start?
[02:52] <leonel_> ScottK: but we'll have the same with gutsy  once  0.91.1  is released   I think  we need to work that  out 
[02:52] <raphink> Lure: yes
[02:52] <raphink> I'm around
[02:52] <raphink> if it's not too late to answer
[02:53] <raphink> ah I see siretart answered already :)
[02:53] <Lure> raphink: hello - already fixed by siretart
[02:53] <ScottK> leonel_: There really isn't much to be done.  Clamav always wants to to run the latest and greatest, but distributions will almost always lag.  Backports is the best answer.
[02:55] <leonel_> I'd like to run  the latest and greatest   clamav  and other 2 or 3  packages 
[02:55] <effie_jayx> ScottK,  where could I start... I have checked packaging recipe and I think It doesn't look difficult
[02:56] <ScottK> effie_jayx: Go to http://dad.dunnewind.net/universe.php
[02:56] <TheMuso> um ok.
[02:56] <TheMuso> Whats happened to launchpad?
[02:57] <ScottK> effie_jayx: Get the grab-mergs.sh script
[02:57] <TheMuso> thats why
[02:57] <ScottK> TheMuso: LP is having permissions issues.
[02:57] <TheMuso> I'm ot logged in
[02:57] <ScottK> That'll do it to
[02:57] <ScottK> effie_jayx: make a new working director.
[02:58] <ScottK> effie_jayx: I usualy put grab-merge.sh one level higher than my merging directory.
[02:58] <effie_jayx> ScottK,  got it
[02:58] <leonel_> ScottK:  so if  I patch  freshclam to remove that  message that we are running an outdated  clamav version ?
[02:59] <ScottK> effie_jayx: Then from inside your new directory, run sh ../grab-merge.sh clamav (it will erase anythin in that dir, so make sure you are in the right place).
[02:59] <leonel_> ScottK: outdated will be  when  0.91   is released  not  the security updates ..
[02:59] <ScottK> leonel_: Not a security issue.  Don't do it.
[03:00] <effie_jayx> ScottK,  I got two new files
[03:00] <ScottK> leonel_: If it's outdated, it's outdated.  The warning just means you need to decide if you care.  Except for security stuff, I personally don't.
[03:00] <effie_jayx> ScottK,  merge-buildpackage, merge-buildchanges
[03:01] <effie_jayx> ScottK, merge-genchanges
[03:01] <effie_jayx> sorry
[03:01] <leonel_> ScottK:  ok
[03:02] <ScottK> effie_jayx: Did you get the clamav files too?
[03:02] <effie_jayx> no
[03:02] <ScottK> effie_jayx: Hmmm.  Let me try.
[03:03] <effie_jayx> ok
[03:06] <effie_jayx> ScottK,  I got em
[03:07] <ScottK> OK
[03:07] <StevenK> ScottK: You should tell your kids to not do that.
[03:07] <effie_jayx> ScottK,  no problem... one of the packaes is taking long
[03:18] <ScottK> effie_jayx: I'm back.
[03:18] <effie_jayx> ScottK,  got the files
[03:18] <ScottK> StevenK: No kids home ATM, that's why I can do that.
[03:18] <ScottK> OK.
[03:18] <ScottK> effie_jayx: look at REPORT and see if there are any conflicts.  
[03:20] <effie_jayx> ScottK,  no problems encountered during the merge
[03:20] <ScottK> Then look at debian/changelog and see what's new and how it might relate to the Ubuntu unique stuff.
[03:20] <mruiz> hi all
[03:23] <effie_jayx> ScottK,  where can I find it?
[03:23] <mruiz> hi effie_jayx, congratulations!
[03:23] <effie_jayx> mruiz,  thanks :D
[03:24] <ScottK> effie_jayx: In the dir you downloaded to there should be a clamav-0.90.3 dir, look in there.
[03:28] <mruiz> ping zul
[03:28] <effie_jayx> ScottK,  found the file ... reading it 
[03:31] <effie_jayx> ScottK,  done... 
[03:32] <ScottK> OK.  What's your opinion?
[03:33] <effie_jayx> There are quite a few bug fixes... mostly related to scanning as root and scanning with restrictions
[03:34] <effie_jayx> some memory optimization there too
[03:34] <ScottK> Now go find the Ubuntu unique change and see if it still looks proper.
[03:36] <dholbach> mruiz: just zell zul in here that you want to do his vzctl merge
[03:36] <mruiz> ok :-)
[03:37] <bmm> ...broadcasting... Any comments on http://revu.tauware.de/details.py?upid=5295 are welcome, I'm looking for advocates.
[03:39] <mruiz> dholbach: this is a merge, because the idea is to preserve Ubuntu changes :-)
[03:40] <dholbach> mruiz: right, that's what we do merges for
[03:40] <dholbach> thanks :)
[03:41] <dholbach> TheMuso: seems that dktrkranz did the xawtv merge
[03:41] <TheMuso> dholbach: Yeah I know. I uploaded it.
[03:41] <dholbach> ah ok
[03:42] <dholbach> thanks
[03:43] <effie_jayx> ScottK, where should I be looking at... ?
[03:44] <ScottK> effie_jayx: Look at the last entry in debian/changelog for an ubuntu specific version and see if that tells you where to look.
[03:44] <ScottK> effie_jayx: This gets much easier with practice.
[03:47] <effie_jayx> ScottK,  there is this file 0.90.3-1ubuntu1
[03:47] <ScottK> effie_jayx: That's the version you are trying to make right now.  Look for the Ubuntu entry before that.
[03:48] <effie_jayx> ScottK,  I think I am not looking in the right place
[03:49] <ScottK> effie_jayx: Are you looking in debian/changelog?
[03:49] <ward> can anyone please take a look at this: http://paste.ubuntu-nl.org/23426/
[03:50] <ward> its an error i get from make
[03:51] <ward> i'm making gephex but this error seems to come from the ffmpeg source that comes with gephex
[03:51] <effie_jayx> ScottK,  found it...
[03:51] <ward> but i replaced the ffmpeg that comed with gephex by the latest (because theirs was not working)
[03:51] <StevenK> ward: You should see if you can convince gephex's build system to use the installed ffmpeg.
[03:52] <ward> StevenK, good idea, maybe that's working with ./configure
[03:52] <ward> StevenK, i'll try it right away
[03:53] <dholbach> does anybody have an easy task for vijay2000 at hand?
[03:53] <ward> StevenK, damn, i cna only sitch ffmpeg support on or off (and obviously i want ffmpeg support because this is a VJ application)
[03:54] <dholbach> StevenK: would you mind if vijay2000 does the gdeskcal update?
[03:54] <ward> StevenK, could it help when i replace it with the source of the ffmpeg in the repos?
[03:55] <StevenK> dholbach: Not at all
[03:55] <dholbach> StevenK: thanks a lot
[03:55] <StevenK> ward: You could probably hack configure.in to look for the installed ffmpeg.
[03:55] <dholbach> vijay2000: do you want to do the update of gdeskcal?
[03:56] <ward> StevenK, i'll take a look thanx, but i'm no coder so i'm not sure if i can
[03:56] <vijay2000> dholbach: i have no issues 
[03:56] <dholbach> vijay2000: thanks
[03:57] <effie_jayx> ScottK,  I can't seem to find a file wehre to look.. I check the debian/changelog and reads New Upstream version... and  stop using  killproc... no sign of a file
[03:57] <vijay2000> dholbach: I want to know the procedure for doing the update
[03:57] <ScottK> effie_jayx: Look at the 0.90.2-4ubuntu1 entry
[03:58] <dholbach> vijay2000: I think I mentioned the MOTU/Recipes page yesterday already?
[03:58] <effie_jayx> ScottK,  debian/clamav-freshclam.init.in specify pidfile when starting <----
[03:59] <ScottK> Yes
[03:59] <ScottK> effie_jayx: In the directory you downloaded to there is a proposed patch for the new Ubuntu version.  You can look in there too to get an idea of the exact change.
[04:00] <effie_jayx> ScottK,  clamav_0.90.3-1ubuntu1.patch
[04:01] <ScottK> Yes
[04:03] <leonel> ScottK: are you working with  the clamav patches ?
[04:03] <ward> StevenK, i can only find configure.ac , is it possible thats the right one?
[04:03] <ward> it seems like it
[04:03] <ScottK> leonel: No, you were going to find them for me.
[04:04] <mruiz> dholbach: I sent an email to zul about the merge
[04:04] <dholbach> mruiz: zul is in here :)
[04:04] <leonel> so I'm not going to do the  patching ?
[04:05] <mruiz> yes, I tried with ping as well! ;-)
[04:05] <ScottK> leonel: You can do the patching too.
[04:06] <icf7> Where do I get the debootstrap script to use a gutsy-pbuilder on feisty?
[04:07] <effie_jayx> ScottK,  ok I opened the file .patch
[04:08] <ScottK> What's there makes no sense to me.
[04:08] <leonel> ScottK: ok
[04:09] <ward> StevenK, its not possible i think, because it really needs the sourcefiles to compile gephex itself
[04:09] <ward> StevenK, and if i look at installed files with ffmpeg there's no source there
[04:10] <StevenK> ward: Surely it only needs the headers to compile against?
[04:11] <ward> StevenK, yea probably
[04:12] <ward> StevenK, i'm not a coder, forgive me if i'm being stupid sometimes
[04:13] <mruiz> dholbach: then, I have to wait for zul's answer...
[04:13] <ward> StevenK, yeah i think it only needs the headers but i'm not sure
[04:13] <ScottK> Arghh.
[04:13] <effie_jayx> ScottK,  what happened?
[04:13] <dholbach> mruiz: no, just do it
[04:13] <ward> StevenK, where can i find them on my system? google doest give me usefull info (up till now)
[04:13] <mruiz> dholbach: ok... let's continue!
[04:13] <dholbach> alriht
[04:14] <ScottK> effie_jayx: Looks like something got messed up when I did the last merge.
[04:14] <mruiz> dholbach: now, I have to modify debian/changelog
[04:14] <ScottK> effie_jayx: We'll fix it now.
[04:14] <ScottK> effie_jayx: Open the freshclam init.in file in your favorite text editor.
[04:15] <dholbach> mruiz: link/send the diff to me, once you're done
[04:15] <effie_jayx> ScottK,  it's open
[04:16] <ScottK> OK.  Find the spot in the file mentioned in the patch.
[04:16] <ward> StevenK, i did "apt-get source ffmpeg" instead
[04:16] <ward> and replaced that with the original ffmpeg
[04:16] <ward> StevenK, got the same error
[04:19] <ScottK> effie_jayx: Did you find it?
[04:19] <icf7> How do create a gutsy pbuilder environment in feisty? The corresponding debootstrap script is missing
[04:20] <ScottK> effie_jayx: In the patch file, look at the end.  It shows you the change in the freshclam init.  That's what you want to find.
[04:21] <leonel> ScottK:  once I've found  the bugs and do the patch  do I  apply with  dpatch-edit-patch and  edit the files that need patchin ?
[04:21] <ScottK> leonel: Yes.  It's very much like what you did with squirrelmail.
[04:21] <effie_jayx> ScottK,  found it 
[04:22] <leonel> ScottK: ok thanks
[04:23] <ScottK> effie_jayx: The part of the line that says "$DAEMON clamav-feshclam,init.in -d" should be "$DAEMON $PIDFILE -d"
[04:23] <ScottK> effie_jayx: The Ubuntu change is to tell freshclam to specify a PID file when starting.
[04:24] <effie_jayx> ok
[04:24] <ward> could someone please take another look at this please? http://paste.ubuntu-nl.org/23426/
[04:25] <vijay2000> hi i am doing a update of gdeskcal 
[04:26] <vijay2000> the link provided in the copyright file is not found http://www.pycage.de/software_gdeskcal.htm
[04:26] <effie_jayx> ScottK,  I saw it in the patch
[04:27] <mruiz> dholbach: I have to remove "Merge from debian unstable, remaining changes:" ?
[04:27] <dholbach> vijay2000: but it'S on the same page: pycage.de
[04:27] <dholbach> mruiz: hum, why?
[04:27] <effie_jayx> ScottK,  I changed it
[04:27] <dholbach> mruiz: is there nothing worth keeping
[04:27] <dholbach> ?
[04:28] <ScottK> effie_jayx: Check in debian/control and make sure maintainer is correct (should be MOTU).
[04:28] <mruiz> dholbach: I ask you, because my comment is "Disabled all architectures except i386"
[04:28] <effie_jayx> ScottK,  
[04:29] <dholbach> mruiz: you can have both comments in there
[04:29] <effie_jayx> ScottK,  It reads Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
[04:30] <ScottK> That's correct
[04:30] <mruiz> dholbach: I prefer only one comment ;-)
[04:31] <dholbach> mruiz: "Merge from debian unstable, remaining changes:" is a standard comment we use
[04:31] <dholbach> mruiz: after that we list the changes explicitely
[04:31] <ScottK> effie_jayx: Now go back to debian/changelog and update the current entry.  Describe the Ubuntu unique changes (in this case you can look at the previous entry and copy it).
[04:31] <mruiz> dholbach: I know, but the last uploader (ubuntu) did it (only one comment)
[04:31] <effie_jayx> ScottK,  save changes on the patch?
[04:31] <ScottK> effie_jayx: Also put your name/email in for the bottom line of the changelog entry
[04:31] <dholbach> mruiz: then just stick to the "Merge from debian unstable, remaining changes:" + list of changes
[04:32] <ScottK> effie_jayx: Yes
[04:32] <effie_jayx> ScottK,  no changes to the init.in file?
[04:32] <ScottK> effie_jayx: Just the one you made.
[04:33] <dholbach> vijay2000: rename  gDeskCal-1.01 to  gdeskcal-1.01
[04:33] <ScottK> effie_jayx: When you use grab-merge it's already put in the Ubuntu unique stuff it knows about from the previous release.
[04:33] <vijay2000> dholbach: thanks
[04:33] <effie_jayx> ScottK,  ok
[04:34] <effie_jayx> ScottK,  let me double check... I changed the patch and saved... I didn't touch clamav-freshclam.init.in
[04:35] <vijay2000> dholbach: in the change log the existing version is gdeskcal (0.57.1-1ubuntu2) now the version to which we will be 
[04:35] <dholbach> the upstream version is 1.01
[04:35] <ScottK> OH.  Misunderstanding here.  Change clamav-freshclam.init.in, not the patch.  We'll make a new patch when we are done.  Sorry.
[04:35] <dholbach> as debian does not hav it yet, it will be -0ubuntu1
[04:35] <dholbach> but this is answered on MOTU/FAQ too
[04:35] <vijay2000> dholbach: updating is 1.0.1 so can i write it as (1.0.1-0ubuntu1)
[04:36] <dholbach> no
[04:36] <dholbach> upstream version is 1.01, not 1.0.1
[04:36] <dholbach> that's a difference
[04:36] <effie_jayx> ScottK,  got it
[04:36] <vijay2000> so its 0.1.01
[04:36] <dholbach> no
[04:36] <icf7> How do create a gutsy pbuilder environment in feisty? The corresponding debootstrap script is missing, is there a special package?
[04:36] <dholbach> 1.01-0ubuntu1
[04:36] <vijay2000> ok
[04:36] <dholbach> icf7: I believe it's in feisty-backports
[04:37] <dholbach> icf7: if not, you should be able to download it from http://launchpad.net/ubuntu/+source/debootstrap
[04:37] <ScottK> effie_jayx: Let me know when you are done.
[04:37] <mruiz> icf7: the best way is to install the Feisty's (backports) debootstrap version 
[04:38] <icf7> dholbach: ty
[04:38] <dholbach> anytime
[04:38] <effie_jayx> ScottK,  ok... I just changed it on init.in
[04:38] <mruiz> dholbach: debian/changelog -> done!
[04:38] <ScottK> effie_jayx: Then go spiff up the changelog.
[04:38] <effie_jayx> ScottK,  good
[04:40] <effie_jayx> ScottK,  you said my name and email... which changelo
[04:40] <ScottK> effie_jayx: debian/changelog where it now says Ubuntu DaD
[04:41] <effie_jayx> ScottK,  got it
[04:41] <effie_jayx> ScottK,  I saw yours before this one
[04:41] <ScottK> Yes
[04:44] <effie_jayx> ScottK,  the only change is  clamav-freshclam.init.in just like yours?
[04:44] <effie_jayx> I didn't have to update the mantainers info
[04:44] <vijay2000>  dholbach: i get the following error when i build gdeskcal http://paste.ubuntu-nl.org/23435/
[04:45] <ScottK> effie_jayx: And the maintainer change
[04:45] <effie_jayx> ok
[04:45] <ScottK> effie_jayx: That's a change from Debian, but DaD already did it for you.
[04:45] <effie_jayx> ok
[04:46] <effie_jayx> ScottK,  then same changes as from your merge?
[04:46] <ScottK> Yes
[04:46] <dholbach> vijay2000: you have to check if there's a locale directory or if things changed?
[04:47] <effie_jayx> ScottK,  done
[04:48] <ScottK> effie_jayx: Do you have a Gutsy pbuilder or chroot set up to test build this package?
[04:49] <effie_jayx> no
[04:49] <ScottK> effie_jayx: That's probably the next thing to work on.
[04:49] <effie_jayx> ok
[04:50] <ScottK> Anyone...  Can we create Gutsy pbuilders directly now or do we still have to make a Feisty one and upgrade it.
[04:51] <icf7> ScottK: I just asked a similar question ;) Install the backports' pbuilder and you can directly create a gutsy pbuilder
[04:53] <ScottK> icf7: Thanks
[05:00] <vijay2000> dholbach: there is no locale directory in the new version 
[05:00] <dholbach> ok, then you can remove the line from debian/rules
[05:00] <vijay2000> ok
[05:06] <mruiz> ping dholbach 
[05:06] <dholbach> mruiz: pong
[05:06] <dholbach> just ask your question
[05:06] <mruiz> :-)
[05:06] <dholbach> I'm in a meeting, but I'm sure somebody can answer it too
[05:07] <mruiz> and I had some problems with the connection!
[05:08] <mruiz> MOTU-mentors ML is a very good idea!
[05:08] <vijay2000> after removing a line in debian/rules do we have to debuild and then do a build?
[05:09] <mruiz> dholbach:  now I have to build the merge with merge-buildpackage -rfakeroot -k<mykey> ... 
[05:10] <dholbach> mruiz: I don't think I ever used merge-buildpackage ... better to ask somebody else about that
[05:10] <dholbach> vijay2000: yes, just try it
[05:11] <mruiz> dholbach: what's your recipe ?
[05:12] <dholbach> if you have the merge done, just do     debuild -S -sa -k<keyid>   to build the source package
[05:12] <dholbach> but please ask in the channel
[05:12] <dholbach> I'm in a meeting
[05:12] <mruiz> this script says: exec dpkg-buildpackage -S -v3.0.11-13ubuntu1 -sa "$@"
[05:12] <mruiz> no worries, mate
[05:12] <mruiz> dholbach: sorry
[05:12] <dholbach> np
[05:13] <vijay2000> its not working 
[05:13] <dholbach> debuild -S -sa -v3.0.11-13ubuntu1 -k<keyid>     should work too
[05:13] <vijay2000> it still shows the same error 
[05:13] <dholbach> mruiz: check out    man dpkg-buildpackage     for more options
[05:14] <mruiz> thanks!
[05:15] <mruiz> someone use merge-buildpackage ?
[05:15] <Hobbsee> yes
[05:16] <Hobbsee> mruiz: run it from teh source directory
[05:16] <mruiz> hi Hobbsee. I'm following https://wiki.ubuntu.com/MOTU/School/Merging-and-Syncing, step six. In which directory must I use it?
[05:16] <Hobbsee> as in ../merge-buildpackage
[05:16] <mruiz> ok
[05:17] <dholbach> vijay2000: exactly the same error message?
[05:19] <vijay2000> dholbach: i fixed that ... now the other error is we have file called readme.skins in the older version which is not present in the new version
[05:19] <dholbach> right, then you can change that in debian/* too
[05:20] <vijay2000> you mean in debian/rules
[05:21] <mruiz> Hobbsee: I did it, but 2 warnings appeared: http://paste.ubuntu-nl.org/23445/ (final)
[05:22] <Peaker> ScottK: Are you the one who does the scipy/numpy packages?
[05:22] <ScottK> Peaker: We maintain packages as a team here, but I've worked on them recently.
[05:23] <ScottK> jussi01: Hello.  
[05:23] <Peaker> ScottK: ah, ok.  Wanted to say that the up-to-date scipy/numpy packages don't work even upstream (the tarballs of both compile but don't really work)
[05:23] <ScottK> jussi01: Did you see my comment on your package.
[05:23] <Peaker> ScottK: Actually scipy's doesn't compile out of the box even
[05:23] <ScottK> Peaker: OK.  Then you really need to complain with the upstream.
[05:24] <jussi01> hello ScottK, thanks for your review
[05:24] <ScottK> If it's a packaging problem or some bug fixing, we can help out.
[05:24] <Hobbsee> mruiz: you can ignore them
[05:24] <jussi01> ScottK: yes, i did :D
[05:24] <mruiz> thanks Hobbsee 
[05:24] <mruiz> what's about the Maintainer field in debian/control ?
[05:25] <Peaker> ScottK: Yeah, I know - just wanted to let you know its not a package problem, cause I was complaining about my problems the other day :)
[05:25] <mruiz> Hobbsee: I don't know if I have to modify it when I'm merging
[05:25] <Hobbsee> you dont
[05:25] <mruiz> ok
[05:25] <ScottK> Peaker: OK.  Well the Debian numbpy update in Experimental claims compatiblity.
[05:25] <ScottK> Peaker: Did you find that didn't help?
[05:25] <Hobbsee> mruiz: i dont see where you're meaning?
[05:26] <Peaker> ScottK: No, couldn't get the pmanager to work so I decided to just test the upstream. You say Debian folks fixed the upstream problems?
[05:26] <ScottK> Peaker: Or scipy update.  I don't recall which.
[05:26] <ScottK> Dunno.
[05:26] <ScottK> Peaker: Wait a second.
[05:26] <vijay2000> can anybody help me with this error . since daniel is busy in a meeting http://paste.ubuntu-nl.org/23448/
[05:26] <mruiz> Hobbsee: no worries
[05:27] <ScottK> Peaker: http://packages.debian.org/changelogs/pool/main/p/python-scipy/current/changelog  
[05:28] <ScottK> Peaker: Hard to tell if fixes compatibilty addresses your issue or not, but it might.
[05:28] <Peaker> ScottK: its hard to call it an "issue" -- scipy doesn't compile out of the box :) And then it spouts deprecation warnings when imported and its tests failed
[05:29] <ScottK> Peaker: But the Ubuntu package compiles.
[05:29] <Lutin> bluekuja: ctorrent has been uploaded to unstable, is it ok to request a sync ?
[05:31] <bluekuja> Lutin, it has been uploaded in ubuntu too before unstable :)
[05:32] <bluekuja> Lutin: new packages are synced automatically from debian if they are NEW
[05:32] <jussi01> ScottK: how is your mirror now? still down?
[05:32] <bluekuja> Lutin: until sync close on 20 june
[05:33] <Lutin> bluekuja: it's not going to be autosynced, as it was uploaded in ubuntu before
[05:33] <ScottK> jussi01: I tried it this morning and that one package still 404'ed
[05:33] <bluekuja> Lutin, is the same version both in debian and ubuntu now, why we need a sync?
[05:34] <Lutin> bluekuja: because keeping a different version in debian and ubuntu if there's no reason to do so is just pointless
[05:34] <Lutin> and because if you update your package in debian then it'll get properly autosynced
[05:35] <bluekuja> Lutin, go for a sync then :)
[05:36] <jussi01> ScottK: ok np's
[05:36] <bluekuja> Lutin, thanks for it
[05:36] <Lutin> bluekuja: np
[05:36] <bluekuja> Lutin, you can request a sync for gtorrent-viewer too
[05:36] <mruiz> Hobbsee: afterwards, I have to test the build with pbuilder -> "sudo pbuilder build  file.dsc" . I'm right?
[05:36] <bluekuja> Lutin, you'll find it in the list ;)
[05:37] <pochu> Lutin: so are you in the team?
[05:38] <Hobbsee> mruiz: yes
[05:38] <Hobbsee> if you havent already
[05:38] <Hobbsee> but that merge-buildpackage needs to be the last script that you run
[05:39] <Lutin> pochu: ?
[05:39] <vijay2000> anybody help me please with this error http://paste.ubuntu-nl.org/23448/
[05:40] <mruiz> thanks Hobbsee 
[05:40] <dholbach> vijay2000:     grep -r README.skins debian
[05:40] <dholbach> vijay2000: that will find out the file that mentions README.skins
[05:40] <Hobbsee> cp: cannot stat `README.skins': No such file or directory
[05:40] <dholbach> vijay2000: remove it from there, try again
[05:41] <Lutin> bluekuja: next you upload a new upstream version in ubuntu of a package which is already in debian, please do *not* discard the previous changelog entries
[05:41] <pochu> Lutin: the torrent team :)
[05:41] <pochu> since you're syncing every torrent app... ;)
[05:41] <herzi> dholbach: ping
[05:41] <Lutin> pochu: lol :)
[05:42] <bluekuja> Lutin, yea.
[05:42] <Lutin> pochu: no, I'm not ;)
[05:42] <ScottK> LaserJock: What would you think about us going ahead and syncing python-scipy from Debian Experimental.  The version in Unstable is known not to work with the version of python-numpy we have in Gutsy. http://packages.debian.org/changelogs/pool/main/p/python-scipy/current/changelog
[05:42] <bluekuja> pochu: he pinged me for some syncs 
[05:42] <bluekuja> pochu: for packages I maintain in debian
[05:42] <bluekuja> :)
[05:42] <Lutin> bluekuja: was saying that because of gtorrent-viewer
[05:43] <ward> common.c:48: error: expected ')' before '*' token
[05:43] <ward>      code: void align_put_bits(PutBitContext *s)
[05:43] <ward> can anyone tell me whats wrong with this?
[05:44] <bluekuja> Lutin, which previous entries I dropped, sorry?
[05:44] <Lutin> bluekuja: all the entries from debian
[05:44] <DktrKranz> dholbach, around?
[05:44] <pochu> Lutin: you could join :)
[05:45] <bluekuja> Lutin, those are not official, so I dropped them
[05:45] <Lutin> pochu: yeah, I could . I worked on bittorrent some times ago too, but never uploaded the fixes actually
[05:45] <Lutin> bluekuja: what do you mean by 'official' ? those are debian
[05:45] <bluekuja> Lutin: official = made for upstream purpose
[05:46] <dholbach> DktrKranz: no, in a phone call
[05:46] <dholbach> drop me a mail or ask in here, sorry
[05:46] <bluekuja> Lutin, the first upload was made by me
[05:46] <DktrKranz> ok, I'll wait for you to finish
[05:46] <DktrKranz> or I'll reply to ubuntu-motu ML
[05:46] <Lutin> bluekuja: the first upload to debian ?
[05:47] <bluekuja> Lutin, dont worry about it, I gonna re-apply them (it's not needed but ok)
[05:47] <mruiz> I'm following the last step of https://wiki.ubuntu.com/MOTU/School/Merging-and-Syncing. I built my merged package with pbuilder, but I don't understand why I have to check the contents of the created debs (dpkg-deb -c foo.deb). Any idea?
[05:47] <bluekuja> Lutin, with the next upstream release
[05:47] <Lutin> bluekuja: anyways the package will be synced, don't bother
[05:48] <vijay2000> dholbach: the docs file had the line  README.skins . i removed it 
[05:48] <Lutin> bluekuja: but when you upload a package in debian which is already in debian, please keep the changelog
[05:48] <bluekuja> Lutin, k thanks
[05:48] <bluekuja> Lutin, it wasnt in debian
[05:48] <Lutin> err. in ubuntu which is already in debian
[05:48] <bluekuja> sounds better
[05:48] <bluekuja> ^^
[05:48] <vijay2000> the older version has the README.skins file in the gdeskcal-0.57.1/
[05:48] <bluekuja> Lutin, #ubuntu-motu-torrent if interested in joining :)
[05:48] <Lutin> bluekuja: it was in debian
[05:49] <DktrKranz> mruiz, where exactly?
[05:49] <bluekuja> Lutin, no it wasnt. Please check http://packages.qa.debian.org/g/gtorrent-viewer.html
[05:49] <DktrKranz> forget about it, found :)
[05:50] <Lutin> bluekuja: http://packages.debian.org/changelogs/pool/main/g/gtorrent-viewer/gtorrent-viewer_0.2b-1/changelog => where does all these entries come from ?
[05:50] <mruiz> DktrKranz, ;-)
[05:51] <bluekuja> Lutin, from the package made locally by upstream (not for uploads purposes)
[05:51] <DktrKranz> mruiz, such command shows the content of a debian package
[05:52] <Lutin> sigh. they should never have been part of the debian changelog the imo. anyways, that doesn't matter
[05:52] <bluekuja> Lutin, dont worry
[05:52] <mruiz> thanks DktrKranz 
[05:52] <bluekuja> :)
[05:53] <DktrKranz> I think you have to check if it contains all the files you want to include
[05:53] <DktrKranz> and to verify if documentation, desktop files, and so on, are included
[05:53] <mruiz> I think that's OK ;-)
[05:54] <DktrKranz> I prefer check it by installing it in a virtual machine, though :)
[05:54] <herzi> dholbach: do you want to visit the social event of the linuxtag this evening?
[05:54] <DktrKranz> that way I know if
[05:54] <DktrKranz> 1) installs
[05:54] <DktrKranz> 2) runs
[05:54] <DktrKranz> 3) doesn't bother other packages
[05:58] <dholbach> herzi: yes, I'll be there later
[05:59] <herzi> do you already have a ticket?
[05:59] <dholbach> herzi: juliux organised something
[05:59] <herzi> okay
[05:59] <mruiz> dholbach: I have to alert a MOTU about my merged source package ;-)
[05:59] <dholbach> thanks for asking, I look forward to seeing you all later
[05:59] <dholbach> mruiz: if you can upload it somewhere and announce it here, somebody will take a look at it
[06:00] <dholbach> vijay2000: same goes for you - if you have finished the source package and can upload it somewhere, that'd be great
[06:00] <mruiz> dholbach: ok. Which files do you need?
[06:00] <herzi> dholbach: btw, did you finally find the source code for me?
[06:00] <dholbach> debdiff from the debian to the merged ubuntu version should be fine
[06:00] <dholbach> herzi: I found it, but I failed to make it build
[06:00] <dholbach> herzi: how long will you be in berlin?
[06:01] <dholbach> herzi: I can show you the stuff, but I'm sure you'll be somewhat disappointed
[06:01] <dholbach> vijay2000: if you can upload the .diff.gz .orig.tar.gz and .dsc somewhere, that'd be cool
[06:03] <dholbach> mruiz, vijay2000: please mail me the URL, if you don't find a reviewer here
[06:03] <dholbach> I'll call it a day soon
[06:04] <vijay2000> dholbach: where should i upload
[06:05] <dholbach> vijay2000: do you have a place where you can upload the package?
[06:05] <vijay2000> no
[06:05] <dholbach> vijay2000: if not, look at http://wiki.ubuntu.com/REVU
[06:05] <dholbach> if everything fails, send by mail
[06:05] <dholbach> I'll leave in a bit
[06:06] <jussi01> Hei, if someones got time: http://revu.tauware.de/details.py?upid=5334 a review/advocacy? would be wonderful!
[06:07] <vijay2000> ok 
[06:08] <dholbach> have a nice day and see you tomorrow
[06:08] <jussi01> bye dholbach
[06:12] <ScottK> jussi01: I'm trying to build it again now.
[06:12] <jussi01> ScottK: I uploaded the changed one, did you see?
[06:12] <ScottK> Yes
[06:13] <jussi01> :D
[06:14] <jussi01> ScottK: Ill be away for a little while. Back in about  an hour
[06:15] <leonel> ScottK: for the  2 bugs  I'll try to fix  should I report a bug in launchpad  for each  or  just  1 report  for both ?
[06:16] <ScottK> leonel: One bug is good.  Please link it to the CVE reports.
[06:17] <leonel> ScottK:  ok
[06:25] <leonel> ScottK:  reported ..
[06:25] <ScottK> OK.  Let me know if you need help.
[06:26] <effie_jayx> ScottK,  ping
[06:26] <leonel> ScottK: I will need  and let you know ...
[06:27] <mathiaz> I need some guidance on how to create a preinst script. Is there a template for preinst script ?
[06:27] <ScottK> effie_jayx: Hi
[06:27] <ScottK> effie_jayx: Next step is pbuilder...
[06:27] <effie_jayx> ScottK, :D
[06:27] <ScottK> effie_jayx: Are you running Feisty?
[06:27] <effie_jayx> yes
[06:28] <ScottK> effie_jayx: Make sure you have the feisty-backports repository enabled and then install pbuilder.
[06:30] <evand> pochu: whenever you get a chance, can you take another look at #117834
[06:30] <pochu> bug 117834
[06:30] <ubotu> Launchpad bug 117834 in amule "Please sponsor amule upload" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117834
[06:30] <pochu> evand: sure :)
[06:30] <effie_jayx> ScottK,  got it
[06:30] <evand> thanks a bunch
[06:31] <ScottK> effie_jayx: There is more than one way to set up pbuilder.  The easiest in my book is to use the pbuilder-feisty script found here: http://revu.tauware.de/~laserjock/ - You will want to rename it pbuilder-gutsy before you run it.
[06:33] <nixternal> there is also a write up on the wiki
[06:33] <nixternal> you also need the custom pbuilderrc
[06:33] <nixternal> that is where you make all of the groovy settings
[06:33] <effie_jayx> ScottK,  got it
[06:34] <ScottK> effie_jayx: Put the script somewhere convenient and then run sh pbuilder-gutsy create (it'll ask you for your password, this is normal)
[06:34] <ScottK> effie_jayx: That's going to take a while, so let me know when you have it started.
[06:35] <effie_jayx> ScottK,  I have started it
[06:37] <ScottK> OK.  Now go back to your clamav package.  In the dir that you put it, you will see merge-buildpackage
[06:38] <effie_jayx> ScottK,  got it 
[06:38] <ScottK> Go ahead and run that.  That'll build the source package.
[06:39] <effie_jayx> ScottK,  the sh pbuilder-feisty hasn't finished yet.. I started it a few minutes ago
[06:39] <effie_jayx> ScottK,  shall I wait till that is done?
[06:40] <jussi01> ScottK: Im back, how did the build go?
[06:40] <ScottK> effie_jayx: Did you make pbuilder-feisty or pbuilder-gutsy?
[06:40] <ScottK> jussi01: Just commented.  Have a look.
[06:40] <effie_jayx> gutsy sorry
[06:40] <ScottK> OK.  That's good.
[06:41] <jussi01> ScottK: thanks
[06:41] <effie_jayx> ScottK,   sh pbuilder-gutsy create
[06:41] <effie_jayx> my bad
[06:41] <ScottK> effie_jayx: We can go ahead and make the debdiff while we wait.  Yes.  that's correct.
[06:41] <effie_jayx> ScottK,  ok
[06:42] <jussi01> ScottK: the guy gave me both 2006 and 2007 as the copy right years. should I have put both? or 2007 only?
[06:42] <ScottK> Both
[06:43] <ScottK> effie_jayx: From that same dir, do debdiff clamav-0.90.3-1.dsc clamav-0.90-1ubuntu1.dsc > clamav-merge.debdiff
[06:43] <ScottK> effie_jayx: Once you have that done, pastebin the contents of the output file.
[06:44] <jussi01> ScottK: is there a particular format? or just 2006/2007 ?
[06:44] <ScottK> That's fine. 
[06:44] <jussi01> :D
[06:45] <LaserJock> ScottK: I say go for it, regarding scipy, we have time to stablize it and for sure scipy and numpy need to be matched
[06:45] <ScottK> LaserJock: Thanks.
[06:46] <ScottK> jussi01: Did you know that the mnemosyne predecessor Pyqt memaid has a Debian package?
[06:46] <jussi01> ScottK: no, I did not know that... :(
[06:46] <ScottK> It's not a problem.  It's a good thing.  
[06:47] <ScottK> jussi01: Go hunt up the debian/copyright file in memaid-pyqt and you'll have your missing copyright information.  Google is good like this.
[06:48] <ScottK> jussi01: Also, debian/copyright doesn't necessarily list everyone in the Authors file if not all of them are copyright holders.
[06:49] <effie_jayx> ScottK,  I tried executing the merge-buildpackage
[06:49] <jussi01> ScottK: ok :D
[06:49] <ScottK> jussi01: You will also need to double check that nothing you are doing conflicts with anything installed by that package.
[06:49] <ScottK> effie_jayx: What happened?
[06:49] <effie_jayx> but it says It can't read the debian/changelog
[06:50] <pochu> evand: it looks good to me, I'd upload it if I were a MOTU :)
[06:50] <effie_jayx> and dpkg-configure error cant determine the source file
[06:50] <ScottK> effie_jayx: cd into the clamav dir and then sh ../merge-buildpackage
[06:50] <RainCT> keescook: Hi. Could you sponsor bug 117156 please? This one works (I did a deb with that one and have it installed :P)
[06:50] <ubotu> Launchpad bug 117156 in flobopuyo "Flobopuyo has no icon for the .desktop file" [Undecided,Confirmed]  https://launchpad.net/bugs/117156
[06:51] <evand> pochu: heh, thanks!
[06:51] <mruiz> bye all!
[06:51] <RainCT> keescook: (will look at the other two tomorrow)
[06:51] <ScottK> Yes
[06:51] <stijn_pol> Some newbie stuff: If a bug is reported in feisty and package is also available in gutsy, should I make a debdiff for gutsy, feisty or both??? :s
[06:51] <ScottK> But you're packaging it's replacement.  This is fine.
[06:51] <RainCT> stijn_pol: gutsy
[06:52] <ScottK> stijn_pol: Fix gutsy first and then do an SRU for Feisty if the bug is severe enough to qualify.
[06:52] <effie_jayx> ScottK,  I am there, the file merge-buildpackage isn't there thoug
[06:52] <ScottK> effie_jayx: when you do ../filename it looke in the dir above.
[06:52] <stijn_pol> RainCT, ScottK: thanks, probably not sever enough...:-)
[06:53] <jussi01> ScottK: I want to ask a newbie question... how do I get the source out of the dsc file?
[06:54] <RainCT> jussi01: dpkg-source -x <package_version-...>.dsc
[06:54] <jussi01> RainCT: thanks
[06:54] <pochu> evand: just FYI, some people like you ask them before doing their merges. I'm happy you've done amule's merge, though :)
[06:54] <ScottK> jussi01: Or since it's in our repos you could just do apt-get source packagename.
[06:55] <evand> pochu: Yeah, I realized that this afternoon in the MOTU session.  Sorry about that, but I'm glad you're happy.
[06:55] <jussi01> ScottK: duh... now i fell really silly... but its nice to know that command :D
[06:55] <pochu> evand: btw, you're now an official ubiquity developer, right?
[06:55] <ScottK> jussi01: This is how learning happens.  Don't sweat it.
[06:56] <jussi01> :)
[06:56] <ScottK> effie_jayx: How's it going?
[06:56] <evand> pochu: indeed
[06:57] <RainCT> jussi01: (if you are on Feisty edit the file /etc/apt/sources.list changing feisty with gutsy on all lines that start with deb-src to get the latest package source from Gutsy with apt-get source)
[06:57] <evand> now I just have to crawl up to core-dev so I can upload without sponsorship
[06:57] <evand> thanks pochu 
[06:57] <effie_jayx> ScottK,  I can't get merge-buidlpackage executed
[06:57] <jussi01> RainCT: why would I do that?
[06:57] <Hobbsee> effie_jayx: are you running it in the source directory?
[06:58] <effie_jayx> Hobbsee,  nope
[06:58] <LaserJock> so, I missed both MOTU Q&A sessions, how did it go?
[06:58] <effie_jayx> the file isn't there the file is outside
[06:58] <Hobbsee> effie_jayx: you should be
[06:58] <effie_jayx> Hobbsee,  ok
[06:58] <ScottK> effie_jayx: sh ../merge-buildpackage?
[06:58] <Hobbsee> effie_jayx: from the source dir, use ../merge-buildpackage
[06:58] <pochu> evand: if you want to implement a new feature, I'd be happy if it were this: http://ubuntuforums.org/showthread.php?t=301761 :)
[06:59] <jussi01> ScottK: what do I need to include from here: http://paste.ubuntu-nl.org/23466/ ? 
[06:59] <effie_jayx> ScottK,  got it...
[07:00] <ScottK> jussi01: Looking
[07:00] <RainCT> jussi01: well, that's if you want to get the packages from Gutsy.
[07:00] <effie_jayx> ScottK,  I got an error...
[07:00] <jussi01> RainCT: :D ok...
[07:00] <ScottK> effie_jayx: Please pastebin the error
[07:00] <jussi01> ScottK: if you didnt realise thats th copyright file from memaid... but im sure you did... :D
[07:01] <effie_jayx> ScottK,  http://paste.ubuntu-nl.org/23469/
[07:01] <ScottK> jussi01: Yes.  I'd seen it already via google.  See http://paste.ubuntu-nl.org/23468/
[07:02] <ScottK> effie_jayx: Looking
[07:02] <xxxxx1> LaserJock: we don't have a log?
[07:02] <jussi01> ScottK: thanks
[07:02] <Hobbsee> effie_jayx: add <-rfakeroot> to your command
[07:02] <Hobbsee> without the <>'s
[07:02] <Hobbsee> dh_testroot: You must run this as root (or use fakeroot).
[07:03] <ScottK> effie_jayx: Install the package fakeroot and then do fakeroot ../merge-buildpackage
[07:03] <ScottK> or the way Hobbsee said to do it (it's better)
[07:04] <Hobbsee> seeing as you need to build everything with -rfakeroot
[07:05] <jussi01> ScottK: does this look better? http://paste.ubuntu-nl.org/23471/ (I thought better to do this than upload to revu... again...)
[07:06] <ScottK> effie_jayx: What's your launchpad ID?
[07:09] <ScottK> jussi01: Much better, but see http://paste.ubuntu-nl.org/23472/ and a question?  Where does upstream say you can use a later version of GPL?
[07:09] <ScottK> Hobbsee: Yes, I tend to use dbuild when not merging, so I often forget about the fakeroot bit.
[07:11] <effie_jayx> ScottK,  effie-jayx
[07:12] <ScottK> effie_jayx: OK.  I'm assigning you the Gutsy task for the clamav vulnerabilities this merge will fix.
[07:12] <leonel> ScottK:  looks it's gonna be easy ...
[07:12] <ScottK> leonel: Great.
[07:13] <effie_jayx> ScottK,  ok
[07:16] <jussi01> ScottK: hmmm, I copy pasted that bit from another package thinking it was standard.... :(
[07:16] <ScottK> jussi01: Copyright stuff you need to be very careful with.
[07:17] <jussi01> ScottK: yes... :( I was under the impression that there was something in the gpl about that, but i havent read it closely enough to be sure...
[07:18] <ScottK> jussi01: The program is licensed as it is licensed.  Look in the upstream LICENSE file
[07:18] <jussi01> ScottK: ok :D Ill fix it :D
[07:20] <effie_jayx> ScottK,  http://paste.ubuntu-nl.org/23474/
[07:23] <ScottK> effie_jayx: Let me look into that.
[07:23] <effie_jayx> ok
[07:23] <keescook> RainCT: I updated that bug report (117156); it still needs some tweaking.  you're very close, though!  good work.  :)
[07:25] <ScottK> effie_jayx: Very strange.  I don't get that.
[07:26] <RainCT> keescook: ok thanks, will try to finish it this night (I've to go soon)
[07:26] <jussi01> ScottK: My legal english skills suck, but what exactly does section 9 of the gpl2 say about this? ie. http://paste.ubuntu-nl.org/23475/ My interpretation is that it means that I can have that bit there...but I could be completely wrong...
[07:27] <effie_jayx> ScottK,  probably me... :S
[07:28] <RainCT> btw, do you guys keep the source of the packages you did until they are uploaded or only the debdiff?
[07:28] <ScottK> jussi01: If the Program specifies ... "any
[07:28] <ScottK> later version" - Where did they specify and any later version?
[07:28] <Hobbsee> effie_jayx: could you pastebin workk/clamav/clamav-0.90.3/debian/patches/24_nullmailer_ftbfs somwhere?
[07:28] <effie_jayx> sure ..
[07:28] <Hobbsee> if it's dying
[07:29] <jussi01> ScottK: no, it doesnt specify a version so any version will do...
[07:30] <ScottK> jussi01: That's not how I read it.  I read it you have to specify a later version is OK.  As I understand it that's the usual interpretation.
[07:31] <jussi01> ScottK: 
[07:31] <jussi01> If the Program does not specify a version number of
[07:31] <jussi01> this License, you may choose any version ever published by the Free Software
[07:31] <jussi01> Foundation.
[07:31] <ScottK> keescook: Are you going to be around to upload leonel's clamav fixes when he has it done?
[07:31] <effie_jayx> Hobbsee, http://paste.ubuntu-nl.org/23477/
[07:31] <keescook> ScottK: I think so, sure.  I should be online for the next 6 or 7 hours.
[07:32] <Hobbsee> effie_jayx: does it work if you patch it with patch -p1...?
[07:32] <ScottK> jussi01: The way I read that is that they included GPL V2 in LICENSE, so they specified.  It's better to be conservative about what rights the author gives than liberal.
[07:32] <effie_jayx> Hobbsee,  how can I check?
[07:33] <jussi01> ScottK: ok :D sorry for being so annoying about it.... 
[07:33] <ScottK> Hobbsee: I think effie_jayx's copy got corrupted somehow as it builds fine for me.
[07:33] <ScottK> jussi01: No problem.
[07:33] <Hobbsee> ahh
[07:33] <effie_jayx> ScottK,  I must have messed it up :S
[07:33] <ScottK> Hobbsee: Help is welcome here.
[07:34] <ScottK> OK
[07:34] <ScottK> effie_jayx: Here's what I think we should do...
[07:34] <effie_jayx> ok
[07:34] <ScottK> effie_jayx: Make a new dir somewhere else and grab the package from DaD again.
[07:35] <ScottK> Then copy your changelog and clamav-feshclam.init.in files from the old one to the new.
[07:35] <effie_jayx> ok
[07:35] <ScottK> Then try to build it again.
[07:35] <ScottK> You are running a current Feisty, right?
[07:35] <Hobbsee> ScottK: you're doing well, keep ti up :)
[07:36] <jussi01> ScottK: http://paste.ubuntu-nl.org/23479/ better?? :D 
[07:36] <ScottK> jussi01: To whom does the phrase Original Author apply?
[07:36] <effie_jayx> ScottK,  yes
[07:37] <evand> pochu: https://wiki.ubuntu.com/UbiquityForumIdeas :)
[07:37] <ScottK> OK.  Just checking, because that's what I have too.
[07:37] <effie_jayx> ScottK,  I am already downloading throyg the grab-merge
[07:37] <jussi01> ScottK: gah, i thought i removed that... oops :D
[07:37] <ScottK> effie_jayx: Great.
[07:41] <jussi01> ScottK: Im going to have a sauna, back soon :D
[07:41] <ScottK> jussi01: Enjoy
[07:44] <effie_jayx> ScottK,  same mistake
[07:44] <effie_jayx> it must be my file
[07:44] <ScottK> Very strange
[07:44] <ScottK> try this instead then ...
[07:45] <ScottK> debuild -S -uc
[07:45] <effie_jayx> same mistake
[07:46] <ScottK> Hmmm...  Anyone else got ideas on this (Hobbsee??)
[07:47] <effie_jayx> ScottK,  am I missing any packages?
[07:49] <nixternal> ScottK: what is it?
[07:50] <ScottK> nixternal: effie_jayx is trying a merge of clamav, but can't get the source package to build.  Works here for me.
[07:50] <ScottK> effie_jayx: What was the pastebin for the error again?
[07:51] <nixternal> are you building it in a pbuilder or with debuild
[07:51] <effie_jayx> ScottK,  http://paste.ubuntu-nl.org/23474/
[07:51] <leonel> ScottK:  do I have to update the pbuillder ?
[07:51] <ScottK> nixternal: Building the source package
[07:51] <ScottK> leonel: It'd be a good idea
[07:51] <nixternal> ahh, just with ./configure && make && make install?
[07:52] <nixternal> ahh merge
[07:52] <nixternal> ahhhhhhhh
[07:53] <ScottK> effie_jayx: If you get to the point where you've had enough, let us know.  These sort of complications are unusual.
[07:53] <nixternal> unexpected operator..does that have to do with any weird chars?
[07:53] <effie_jayx> ScottK,  I ma patient
[07:53] <nixternal> I had a similar issue with chars that were hyphenated or not abcdef...
[07:53] <nixternal> ScottK: exactly
[07:53] <ScottK> effie_jayx: OK.  Don't want to scare you off.
[07:54] <nixternal> I can't think of the proper words damnit ;)
[07:54] <ScottK> nixternal: We'll wait while you boot out of Vista
[07:54] <nixternal> effie_jayx: look at the file that 24_* is trying to patch
[07:54] <ScottK> ;-)
[07:54] <nixternal> see if the line that is causing the problem has <F4> or something similar
[07:55] <nixternal> instead of the character as displayed in the patch, or vice-versa
[07:55] <nixternal> the funny thing is, the custom ascii chars will show fine in vi and emacs, but if you cat the file, they show up as <F4>
[07:57] <effie_jayx> nixternal,  looks fine on vi
[07:57] <nixternal> I just worked on a package that had a similar issue, but I can't remember what it was
[07:57] <effie_jayx> shall use cat
[07:57] <nixternal> effie_jayx: look at it...yes
[07:57] <nixternal> or less rather
[07:58] <effie_jayx> nixternal,  looks fine to me
[07:58] <nixternal> the patch and the file that is supposed to be patched?
[07:59] <effie_jayx> nixternal,  the pactch looks ok...
[07:59] <nixternal> check the file that is supposed to be patched with less
[08:00] <nixternal> I am trying to remember exactly the error I got that was similar
[08:01] <superm1> nixternal, would I be able to get a second opinion from you on a package that ScottK and Lutin were looking over yesterday?  There was some questioning as to if the naming is OK to use
[08:01] <jussi01> hello again... :D
[08:01] <nixternal> heh, I am probably the worst person to ask, I am a packaging no0b..but I would give you my 2 cents still :)
[08:02] <superm1> nixternal, http://revu.tauware.de/details.py?upid=5325.
[08:02] <nixternal> speaking of naming, I need to rename my Debian package libhttp
[08:02] <nixternal> revu looks broke to me
[08:02] <nixternal> mod_python error
[08:03] <superm1> http://revu.tauware.de/details.py?upid=5325 (maybe that period threw it)(
[08:03] <nixternal> heh, silly me..I didn't even catch that
[08:04] <nixternal> is it a library?
[08:04] <effie_jayx> nixternal,  they look fine to me :S
[08:04] <nixternal> effie_jayx: hrmm...
[08:05] <effie_jayx> shall I do this without using locales ...
[08:06] <effie_jayx> nixternal,  I gotta run... I will keep at this latter tonight...
[08:07] <nixternal> roger that
[08:07] <effie_jayx> cool :D
[08:07] <effie_jayx> ScottK,  I owe you... 
[08:08] <ScottK> I've got to run.  I'll be back later.
[08:08] <leonel> ScottK:   I have no patch  or difff   I will apply the patch to the source   but dpatch-edit-patch  asked for a patchname  I ran  with   dpatch-edit-patch pdf-ole-bugfix.patch
[08:09] <leonel> is this right ?
[08:10] <nixternal> libhdhomerun is actually a set of utilities right? or does it create .so, .la and such library files?
[08:10] <nixternal> it won't make here
[08:11] <superm1> nixternal, it just makes a utility
[08:11] <superm1> but it used to make .so files that were used too
[08:11] <superm1> they have since then removed this functionality
[08:11] <nixternal> let me guess, they had an issue using lib*?
[08:11] <superm1> exactly
[08:11] <superm1> whereas there are packages that do this
[08:12] <nixternal> ya, I don't think it should be lib either
[08:12] <superm1> and the reason i wanted to name it that is because of upstream
[08:12] <superm1> they call it libhdhomerun there
[08:12] <nixternal> you could ask in #debian-mentors possibly on OFTC
[08:12] <superm1> oftc?
[08:12] <nixternal> I notice Red Hat has it as libhdhomerun as well
[08:12] <nixternal> OFTC IRC where Debian hangs out
[08:13] <nixternal> there should be a document somewhere that explains Debian package naming
[08:13] <superm1> given redhat having it as libhdhomerun, I would think it only makes sense for us to do the same thing
[08:13] <superm1> and the resultant binary package is still hdhomerun-config (not libhdhomerun)
[08:15] <nixternal> the package name should carry the same name as the binary...seeing as this is being built as a single binary, then it should possibly be hdhomerun
[08:15] <nixternal> http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Package
[08:16] <superm1> which it does; its just the source package that does not
[08:16] <nixternal> you could always email the Debian Mentors email list asking for their opinion on it as well
[08:16] <superm1> I just poked in there , without any immediate responses
[08:18] <nixternal> I just asked in the mentors channel for an opinion on it
[08:19] <superm1> am i in the wrong mentors channel.... ##debian-mentors is where freenode directed me
[08:19] <nixternal> yes, you should be using the irc.oftc.net
[08:19] <superm1> oh... OFTC
[09:22] <leonel> ScottK: clamav  0.90.2 patched ... and debdiff sent  to lauchpad .
[09:33] <fretchen> Hello
[09:34] <fretchen> if  i have a problem with a package in the universe and i dont get a answer for a question in the forum, where should i ask then?
[09:34] <fretchen> is the time to post a bug in the launchpad then?
[09:35] <LaserJock> fretchen: if it's a bug and not a user issue
[09:35] <LaserJock> either bugs.launchpad.net/ubuntu or answers.launchapd.net/ubuntu for the latter case
[09:36] <fretchen> i think that it is a bug
[09:37] <fretchen> because an official example in the doc does not work
[09:37] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=5314 ?
[09:37] <LaserJock> fretchen: for what app?
[09:37] <fretchen> building an python-extension with boost does not work
[09:38] <fretchen> and i found absoultly no solution anywher
[09:41] <nixternal> ryanakca: are you planning on maintaining the package in Debian at all?
[09:42] <theCore> fretchen: perhaps, I could you help you with your extension problem (I'm working on Python core, right now)
[09:45] <fretchen> i described the problem here: http://ubuntuforums.org/showthread.php?t=459853
[09:45] <fretchen> i hope i am not to fast with asking here
[09:47] <theCore> fretchen: just to be sure, you installed boost development libraries, right?
[09:47] <ryanakca> nixternal: ummm... I could...
[09:47] <ryanakca> nixternal: why?
[09:48] <nixternal> that way there you can just sync it with Ubuntu
[09:48] <nixternal> I have started doing new packages in Debian and then just requesting a sync to Ubuntu
[09:48] <fretchen> i have installed the libboost-dev, the libboost-python-dev and boost-build
[09:49] <theCore> fretchen: ok, let me see then ... 
[09:49] <ryanakca> nixternal: hmm... but then, I suppose I'd need a debian comp? or someone with free vmware-server hosting?
[09:49] <nixternal> or how about a pbuilder-sid ;p
[09:50] <ryanakca> nixternal: yes, but to test?
[09:50] <theCore> ryanakca: pbuilder login?
[09:51] <nixternal> you can setup Debian in VirtualBox as well
[09:51] <ryanakca> theCore: hmm. wont that mess up my pbuilder image? or will it just erase once I log out?
[09:51] <theCore> ryanakca: I don't know. I will have to test it out
[09:52] <ryanakca> nixternal: I said vmware-server hosting because my box doesn't have enough RAM to run VirtualBox or vmware-server ... :(
[09:52] <theCore> ryanakca: but I strongly suspect that it doesn't change your image
[09:52] <ryanakca> theCore: cool
[09:52] <nixternal> I don't use dvorak otherwise I could help test it
[09:53] <ryanakca> theCore: login  Logs into the chroot, and cleaned up afterwards.  Any changes you make will not be kept.  Only use this for temporary and debugging purposes.
[09:53] <nixternal> ryanakca: you can create another pbuilder image, separate from the one you use
[09:53] <nixternal> I have Dapper, Edgy, Feisty, Gutsy, and Sid
[09:53] <theCore> oh, ryanakca you are a Dvorak user now :)
[09:53] <ryanakca> nixternal: hmmm. I'll create a sid one, and if it works, could you try getting it into debian?
[09:53] <ryanakca> theCore: Yeah
[09:54] <nixternal> ryanakca: I will show YOU how to get it into Debian :)
[09:54] <theCore> good luck with laptops :)
[09:54] <ryanakca> theCore: lol, much better than QWERTY :P
[09:54] <ryanakca> why?
[09:54] <ryanakca> nixternal: cool, thanks
[09:54] <theCore> ryanakca: most (if not all) are Qwerty
[09:54] <ryanakca> nixternal: if it's long, feel free to go shower and get ready for the meeting first
[09:54] <fretchen> thecore: the problem is also discussed there:http://mail.python.org/pipermail/c++-sig/2007-January/011783.html
[09:55] <fretchen> but i can add this too in my post
[09:55] <theCore> and using the shell with a Dvorak layout is painful
[09:55] <ryanakca> theCore: so... you just change the keyboard map and ignore the printed keys
[09:55] <nixternal> ryanakca: all you do is create the package, file an ITP bug, put it on mentors.debian.net and make sure it states in the changelog that it closes the ITP bug, and then you file an RFS and seend it to the debian-mentors mailing list
[09:55] <nixternal> oh ya, I need to shower yet
[09:55] <ryanakca> cool
[09:55] <ryanakca> lol
[09:56] <nixternal> it is 3pm here, I leave for class at 5pm
[09:56] <nixternal> meeting at 4pm
[09:56] <nixternal> jeesh
[09:56] <ryanakca> theCore: It also adds a small layer of security here... nobody in my house knows how to use Dvorak... so they can't write anything and they'd have a hard time logging in...
[09:57] <ryanakca> nixternal: Chicago isn't EST
[09:57] <ryanakca> ?
[09:57] <nixternal> CST
[09:57] <nixternal> -0500 during daylight savings
[09:57] <ryanakca> hmm. learn something new every day :)
[09:57] <nixternal> ya, if it wasn't for Ubuntu last year, I would have never known that either
[09:58] <ryanakca> ah
[09:58] <nixternal> I would have always thought we were -0600 all the time
[09:58] <theCore> ryanakca: eh, I got a Das keyboard for that :)
[09:58] <theCore> ryanakca: no key labels at all
[10:02] <nixternal> theCore: you are hardcore
[10:02] <theCore> well ...
[10:02] <nixternal> I bought one of the letterless keyboard back in the late 90s, and I realized I wasn't all that elite
[10:03] <nixternal> it would be hard for me to change from qwerty. I have been using it for more than 20 years...and currently I can hit up to 180 words per minutes
[10:03] <theCore> I been using mine for now about 5 months  
[10:03] <nixternal> 201 is the fastest I have ever hit during a timed typing test at a job fair
[10:04] <nixternal> I hit 201 for like 5 seconds
[10:04] <theCore> ouch, I don't type that fast, though
[10:05] <nixternal> holy smokes..I just wanted to see who is the fastest typer in teh world
[10:05] <nixternal> I am 11 words off from the record, however I can't maintain it
[10:05] <nixternal> this woman typed at 150wpm for 50 minutes
[10:05] <nixternal> holy smokes
[10:05] <nixternal> after a minute my hands are done
[10:06] <theCore> I bought a letterless keyboard to free myself from always peeking at my keyboard
[10:06] <nixternal> 170wpm with a dvorak
[10:06] <theCore> yeah, she is crazy
[10:06] <nixternal> I learned young to not peak at it...my mom and dad would get annoyed when I would hunt and peck on the trs80
[10:06] <nixternal> I do peak when shift+number though
[10:06] <theCore> she also one of the most wanted secretary in the U.S. 
[10:06] <nixternal> every now and then
[10:08] <theCore> ok, back to fretchen's problem 
[10:08] <nixternal> hehe
[10:08] <theCore> fretchen: that certainly looks like a bug 
[10:09] <theCore> fretchen: I never used boost, so you will have to give a few minutes to learn the basics
[10:09] <fretchen> no prob
[10:11] <_MMA_> Sorry. OT but this is cool. http://www.youtube.com/watch?v=bjxVXKEJnM4&mode=related&search= Sorry if Im late.
[10:12] <crimsun> you crazy Vista user, you.
[10:13] <crimsun> I can type maybe 20 WPM.
[10:13] <nixternal> wait a second
[10:13] <nixternal> I should put Vista on highlight, that way there I can find out when you are talking badly about me ;p
[10:14] <crimsun> ah...social engineering at its finest/worst.
[10:14] <theCore> fretchen: ok ... I am getting the same error
[10:16] <ryanakca> nixternal: ITP == http://www.debian.org/Bugs/ ?
[10:17] <fretchen> this is good
[10:17] <nixternal> ryanakca: www.debian.org in docs look at the new maintainer guide and policy for all of your info
[10:17] <beuno> ryanakca: http://www.debian.org/devel/wnpp/
[10:17] <fretchen> ...or not i am not sure :D
[10:17] <nixternal> and with debian bugs, you file them via email
[10:17] <nixternal> wnpp, ya thanks beuno 
[10:17] <beuno> :D
[10:17] <ryanakca> nixternal: ah, thanks
[10:17] <ryanakca> nixternal: hmm. that's wierd
[10:17] <nixternal> hehe
[10:18] <beuno> ryanakca: there's a reason why they went to all the trouble of building a new system from scratch   :D
[10:18] <nixternal> ryanakca: there is also reportbug, but for some reason ours doesn't report to debian
[10:21] <crimsun> oh thank deity, 1.0.14 is finally out.
[10:22] <hendrixski> every time I think I have this packaging thing figured out, turns out  I don't
[10:23] <crimsun> packaging is easy, just ask nixternal.
[10:23] <crimsun> in fact, if you have any questions about anything, just ask nixternal.
[10:23] <nixternal> heh, I know absolutely nothing about packaging
[10:24] <crimsun> (he's obviously lying, since he maintains packages in Debian)
[10:24] <hendrixski> well... I'm here to ask... I gather this is the right place to do so :-)~
[10:24] <nixternal> I don't maintain anything in Debian, so nannynannybooboo
[10:24] <hendrixski> :-( I made a first.py and a setup.py, then ran python setyp.py bdist which made a tar.gz ... ran dh_make -e myaddress -f dir/location.tar.gz
[10:25] <hendrixski> so it ran... it made a debian/ directory, and even a .orrig.tar .. but no .dsc file :-(
[10:25] <nixternal> hendrixski: dh_make doesn't create the dsc file
[10:25] <nixternal> you need to fix up the debian directory first
[10:26] <nixternal> and then in the root dir (i.e., from the debian/ dir cd ../) and then build it with either debuild or dpkg-buildpackage
[10:26] <hendrixski> oh.. ok, so I didn't do anythong _wrong_ yet, just missing the last step?
[10:26] <nixternal> dh_make just debianizes the package and creates the orig file
[10:26] <nixternal> hendrixski: you got it :)
[10:26] <hendrixski> oh... Ok... I just realized there's another page to this manual I'm looking at
[10:26] <hendrixski> LOL
[10:27] <fretchen> the ubuntu packaging guide was a nice help
[10:27] <crimsun> (I toldya he knows.)
[10:27] <nixternal> hehe
[10:27] <nixternal> crimsun: I know the minimal stuff, like how to ask crimsun for help when packaging :p
[10:27] <fretchen> for me until now(but i didn't had to pack anything until now ;) )
[10:28] <crimsun> psht, I know nothing.
[10:28] <nixternal> ya, I wish I could say that about you crimsun, but ummm...I can't ;)
[10:28] <nixternal> debian-mentors is a champ as well when it comes to learning how to package
[10:29] <hendrixski> nixternal, I've mastered the art of asking crimsun too... I've been here a few times before and he's helped me out
[10:29] <nixternal> I need to work on my library package and rename it
[10:29] <hendrixski> ooh... debian mentors ...  nice  :-) that's Debian wide, not just Ubuntu right?
[10:30] <theCore> LaserJock: btw, do you still maintain the packaging guide?
[10:31] <crimsun> hendrixski: correct
[10:31] <crimsun> theCore: he welcomes patches
[10:31] <superm1> nixternal, still no response in debian-mentors.  would it not be enough to let it go on the basis that other packages have source packages named as such. (Like libextractor-python)
[10:35] <crimsun> what's the issue?
[10:36] <superm1> the naming of the source package on http://revu.tauware.de/details.py?upid=5325
[10:36] <superm1>  silicon dust names it libhdhomerun
[10:36] <superm1> so the source package is also named as such
[10:36] <hendrixski> :-( debuild failed ...  "unrepresentable changes to source"
[10:36] <theCore> crimsun: eh
[10:36] <superm1> but produces a binary package called hdhomerun-config
[10:36] <fretchen> theCore: should i do anything else and which way will it go?
[10:36] <theCore> I should send a couple then
[10:37] <crimsun> superm1: it doesn't actually generate a library?
[10:37] <superm1> Not anymore
[10:37] <superm1> older versions did afaik
[10:37] <superm1> so historically its been named libhdhomerun
[10:37] <theCore> fretchen: it seems bjam is nasty when it's used outside of boost build tree 
[10:37] <crimsun> superm1: we're not tied to upstream's naming schema
[10:38] <theCore> fretchen: so you probably want to try to build boost by yourself
[10:38] <xxxxx1> bye guys
[10:38] <superm1> nixternal also mentioned that red hat named their source package libhdhomerun as well though
[10:39] <fretchen> =-Oi have never packed anything until now
[10:39] <fretchen> but well there is always a first time
[10:39] <LaserJock> theCore: depends on the definition of "maintain"
[10:39] <theCore> LaserJock: ah hello!
[10:40] <theCore> LaserJock: maintain = writing stuff for it 
[10:40] <theCore> fretchen: you won't need to package it
[10:40] <LaserJock> theCore: I haven't for a while
[10:40] <fretchen> okay
[10:40] <fretchen> write
[10:40] <LaserJock> theCore: I've got a pile of 7 bugs to get fixed
[10:40] <fretchen> right
[10:40] <theCore> fretchen: just download libboost, and compile in your home dir
[10:41] <fretchen> my mistake
[10:41] <LaserJock> theCore: I just haven't found a lot of time lately
[10:41] <leonel> ScottK: dapper's  clamav  can be done  too  but will be  88.2   but   how  usefull can  this  be ?
[10:41] <LaserJock> theCore: and lately I mean, so far this year ;-)
[10:41] <theCore> LaserJock: same here
[10:42] <theCore> the Google Summer of Code is demanding for me, right now
[10:42] <fretchen> well thx for help
[10:42] <fretchen> i will look at it
[10:42] <fretchen> bye e1
[10:42] <crimsun> superm1: a bit odd, but I don't see anything majorly wrong with the source package on revu
[10:42] <theCore> fretchen: good luck
[10:42] <crimsun> superm1: might want to fix up the minor bits, like the misspelling in debian/control
[10:43] <fretchen> should i describe the success our failure at the forum or is it senseless?
[10:43] <superm1> crimsun, misspelling?
[10:43] <crimsun>   * Performing scans
[10:43] <crimsun>   * Peforming firmware upgrades
[10:43] <hendrixski> I don't see a command in "man pbuilder" for deleting the existing pbuilder and starting again?
[10:43] <superm1> oh yup :)
[10:44] <hendrixski> oh... or can I just run pbuilder create again, and it'll replace the existing one?? :-)
[10:44] <theCore> hendrixski: why delete, when you can update?
[10:44] <superm1> crimsun, i was particularly concerned with the man page that I wrote - was it written correctly and includes correct info?
[10:44] <hendrixski> theCore, I tried... it hit a wall and just wouldn't go
[10:45] <superm1> erg better wording s/correct info/necessary info for a man page/
[10:45] <theCore> hendrixski: then just smash /var/cache/pbuilder/base.tgz in the outer space :)
[10:45] <crimsun> superm1: please clarify in hdhomerun_config.1 under what terms it is distributed
[10:45] <joejaxx> Hello ALl
[10:45] <joejaxx> All*
[10:46] <superm1> Ok crimsun.
[10:46] <LaserJock> is there an easy CLI tool to check the amount of network activity?
[10:47] <fargiolas> Lamego: thanks for the new gnome-mastermind package :)
[10:47] <crimsun> LaserJock: ntop, darkstat
[10:47] <hendrixski> theCore, I'll try that... deleteing the base.tgz and creating a new one.
[10:47] <crimsun> although "amount of network activity" is ambiguous regarding what the target is
[10:48] <Lamego> fargiolas, yw :)
[10:48] <theCore> oh, sweet. I just found a good free book on assembly programming with GNU as/ld
[10:49] <theCore> ok, I need to get back to my project
[10:50] <theCore> later guys
[10:50] <ScottK> leonel: Very useful for those that don't have backports enabled.
[10:51] <superm1> crimsun, i'll make those two changes later - but you would say the source package name is going to be OK right?
[10:51] <crimsun> superm1: right.
[10:51] <crimsun> 16:42 < crimsun> superm1: a bit odd, but I don't see anything majorly wrong with the source package on revu
[10:52] <ScottK> leonel: For your debdiff, version should be ubuntu1.1, not ubuntu2 and security is misspelled.
[10:52] <superm1> oh right :).  Thanks
[11:00] <anji> hi, does anyone know how I can force overlapping subtitles in mplayer? -overlabsub does nothing :( .. using latest feisty build
[11:00] <anji> err, wrong channel
[11:00] <anji> sorry
[11:18] <leonel> ok
[11:18] <leonel> ScottK: how can I fix it  without redoing everything ?
[11:19] <hendrixski> :-) ok, so re-installed pbuilder and now that works :-) 
[11:19] <hendrixski> but the .dsc still generates problems saying there's no makefile found :-( I don't see a makefile in other python packages so... what can I be doing wrong?
[11:54] <ScottK> leonel: Fix debian/changelog, make a new source package, make a new debdiff.  Or, since it doesn't change the number of lines, CAREFULLY edit the existing debidff and re-upload it to LP
[12:00] <YokoZar> When's the next MOTU meeting where I can get MOTU status?
[12:01] <leonel> ScottK:  clamav (0.90.2-0ubuntu1.1) feisty-security; urgency=low
[12:03] <YokoZar> Or does this happen entirely over mail?
[12:05] <ScottK> Yes
[12:05] <ScottK> Then ping keescook when it's ready
[12:06] <keescook> what bug #?
[12:06] <pochu> YokoZar: https://wiki.ubuntu.com/MOTU/Hopeful/Recruitment
[12:07] <YokoZar> Yeah I'm reading that now, thanks
[12:08] <leonel> ScottK:  uploaded
[12:08] <YokoZar> So this is a bit tricky, since my sponsor (Stephen Hermann) just left the project.  Now there's no one to upload the Wine packages I've been making.
[12:08] <LaserJock> people can still sponsor you
[12:08] <LaserJock> it's just going to be a bit more difficult
[12:08] <LaserJock> as they won't be as familiar with it
[12:09] <YokoZar> Honestly he was more or less straight importing the packages, and I've been "should be MOTU" since MOTUs started existing, heh
[12:11] <blueyed> Hi masters of the universe :)
[12:11] <blueyed> I'm one of the upstream developers for b2evolution, which has a very old release in Debian.
[12:12] <blueyed> It gets imported from Debian to Universe. What's the best way to take over maintainership for it?
[12:12] <Hobbsee> hey blueyed :)
[12:12] <LaserJock> blueyed: do you want to maintain it in Debian or Ubuntu?
[12:13] <blueyed> LaserJock: rather in Ubuntu, as I'm using it. But of course, I'd like the changes to be available in Debian, too.
[12:13] <LaserJock> blueyed: well, in Ubuntu we team maintain things
[12:14] <LaserJock> so anybody can touch any package, more or less
[12:14] <LaserJock> blueyed: so have at it
[12:14] <blueyed> So I could provide a debdiff for the current stable release to update it?
[12:14] <LaserJock> you'll just need to get a MOTU to sponsor the upload for you