[00:20] <the_belgain> another quick question - i'm using debhelper for packaging, and it's not quite calculating all the dependencies i'm expecting
[00:21] <the_belgain> in particular, i have liblame-dev as a build-depends, but it's not adding liblame or lame as a runtime dependency (which i think it does need) - is this a common gotcha?
[00:21] <the_belgain> obviously I can add it manually...
[00:22] <mok0> the_belgain: you don't have to. The -dev package will pull in the other ones
[00:23] <the_belgain> it does for most of the -dev libraries, but not for lame it seems
[00:24] <slangasek> the_belgain: you probably want to look at the build log and at the ldd output of your program first, to confirm whether liblame is being pulled into the build the way you're expecting
[00:24] <mok0> Why do you need lame?
[00:25] <the_belgain> the program i'm packaging (fuppes) is upnp media server / renderer which does transcoding - it uses lame to transcode audio to mp3
[00:26] <mok0> the_belgain: so it needs to check for lame during the build, I guess.
[00:26] <mok0> the_belgain: you have to specify lame in build-depends, then
[00:26] <slangasek> mok0: he already said that he did
[00:27] <the_belgain> i've specified liblame-dev in the build depends, yes
[00:28] <mok0> but if configure (?) checks for the lame binary, then you need to put it in build-depends, and with a Recommends: in the binary package
[00:28] <the_belgain> is the problem that the packages are called "liblame-dev" and "liblame0", which is confusing debhelper?
[00:29] <slangasek> the_belgain: there are two overall explanations for not getting the dependency on liblame that you expect: 1) the library isn't being linked in during your program build the way you expect, 2) liblame0 doesn't have a proper shlibs file and therefore the dependency isn't being autocalculated even though the library is used
[00:29] <mok0> liblame0 contains the shared libraries, if your binary is linked to that, dh_shlibs should find it
[00:29] <slangasek> I've just verified that liblame0 does have a proper shlibs file, which leaves the other case to examine
[00:30] <the_belgain> ok, i'll check the compile output to see if it looks like it's being pulled in correctly.  thanks
[00:30] <the_belgain> pbuilder builds take forever to run... :(
[00:31] <mok0> the_belgain: use cowbuilder
[01:19] <zul> evening
[01:39] <bddebian> Heya gang
[01:41] <ScottK> Heya bddebian
[01:42] <bddebian> Heya ScottK
[02:03] <wolfger> Got a question about my lintian results... How do I resolve the following:
[02:04] <wolfger> gpg: Can't check signature: public key not found
[02:04] <ScottK> That's not a lintian result
[02:04] <ScottK> Don't worry about it.
[02:04] <wolfger> ok, cool
[02:05] <wolfger> is that due to pbuilder, that my public key isn't found?\
[02:05] <Hobbsee> hi wolfger
[02:05] <Hobbsee> Fujitsu: ping
[02:05] <wolfger> Hi Hobbsee
[02:05] <Hobbsee> wolfger: my c-n-f bug really isn't on crack.  you just didn't read it.
[02:06] <wolfger> Hobbsee: right... I didn't read closely enough the first time to recognize the package assigned was c-n-f.
[02:07] <wolfger> then when I looked c-n-f up, it said it was for bash, so I assumed it did not apply to zsh. Incorrectly assumed, as it turns out ;-)
[02:07] <wolfger> live and learn
[02:07] <Hobbsee> wolfger: readme says it does zsh too.
[02:10] <leonel> sʞɔoɹ nʇunqn   nice
[02:31] <wolfger> ???
[02:31]  * wolfger wonders how the heck leonel did that
[02:32] <_MMA_> http://www.revfad.com/flip.html
[02:33] <wolfger> I feel like I am missing something when it comes to building a package. I now have a .dsc that passes linitian with no errors, and I'm done with the guide.... how does this become a .deb?
[02:34] <bddebian> pbuild it? :)
[02:37] <wolfger> bddebian: as opposed to the "sudo pbuilder build ../*.dsc" I already ran?
[02:38] <bddebian> Ah, that should have produced a .deb
[02:38] <bddebian> DId you look in your results dir?
[02:39] <bddebian> Or did it possibly fail to build?
[02:39] <wolfger> maybe I'm just too tired to be doing this right now... It built okay (finally), but I am at a loss for where the "results dir" would be.
[02:40] <wolfger> hm
[02:40] <wolfger> dpkg-deb: building package `memaker' in `../memaker_0.1-r134-1_i386.deb'
[02:40] <Hobbsee> wolfger: wherever you set it in your pbuilderrc
[02:40] <Hobbsee> usually /var/cache/pbuilder/result/
[02:40] <wolfger> ah
[02:40] <wolfger> Thanks, Hobbsee
[02:45]  * wolfger is getting nervous.... this is taking far too long to install
[02:46] <wolfger> oh, never mind. It's done. Been done for who knows how long... :-P
[02:46] <bluefoxicy> siiiigh.
[02:47] <bluefoxicy> vmware won't do any sound at all
[02:47] <bluefoxicy> and there's nothing holding /dev/dsp
[02:48]  * bluefoxicy can rmmod the module but can't insmod it, hrm
[02:49] <bluefoxicy> er.  Can't write to the device with it insmoded...
[02:53] <leonel> wolfger: http://www.en.fliptext.net/
[03:09] <Fujitsu> Hobbsee: Pong.
[03:12] <_MMA_> Im trying to find the bug about GDM not using the background color set in gdmsetup. Any help?
[03:15] <_MMA_> Got it.
[03:23] <LucidFox> Where can I find a plaintext version of CC-BY 2.5?
[03:25] <alephant> Hi all... is there a well-formatted feed (RSS?) of package updates which I can use to feed my "validate updates before they break production" RHN clone?
[03:27] <alephant> I'd prefer to parse a machine-friendly format like RSS, than to combine ``apt-get upgrade'' with a screenscrape of Launchpad.
[04:09] <nxvl_work> if a bug is duplicated it's needed to be marked as invalid, didn't it?
[04:11] <StevenK> If it's duplicated, mark it as a duplicate?
[04:51] <Hobbsee> Fujitsu: nvm, i found out.
[06:52] <LaserJock> hmm, can you tell an app to use a different path for a lib at runtime?
[06:53] <LaserJock> I've got devel libraries installed to /usr/local/ and normal apps are picking them up ... and crashing
[07:10] <dholbach> good morning
[07:11] <gpocentek> hello dholbach
[07:11] <dholbach> hey gpocentek
[07:11]  * dholbach hugs gpocentek
[07:13]  * gpocentek hugs dholbach back
[07:15] <minghua> LaserJock: Won't LD_LIBRARY_PATH work?
[07:15] <minghua> LaserJock: If not, maybe LD_PREPLOAD, but I've never used that.
[07:16] <minghua> LD_PRELOAD, of course.
[07:25] <jscinoz> hmm
[07:26] <jscinoz> i'm working on packages for the semifree game UrbanTerror, the game engine is GPL (with some components under other free licenses) and the data files are all free to distribute except for one file which is under the Quake3 SDK license. if i say excluded this file from the source package and had the binary package download it (its only 1.3mb) in the preinst, would this be acceptable?
[07:30] <liri> morning
[07:36]  * minghua likes persia's proposal of allowing (Debian's) Original-Maintainer and Uploads to do uploads for main packages. 
[07:41] <freeflying> anyone would like give any suggestion about Bug #181029
[07:41] <ubotu> Launchpad bug 181029 in scim-bridge "[FTBFS] scim-bridge (0.4.14-1) fails to build in hardy" [Medium,Confirmed] https://launchpad.net/bugs/181029
[07:42] <man-di> minghua: I dont follow Ubuntu lists, can you give me a link to persia's proposal?
[07:43] <slangasek> freeflying: I agree with minghua, removing it is the best way around the error.  Or are you looking for something more?
[07:47] <minghua> man-di: Sure, https://lists.ubuntu.com/archives/ubuntu-devel/2007-December/024886.html
[07:47] <freeflying> slangasek: actually, I don't want to maintain two version in Debian and Ubuntu :P
[07:47] <minghua> man-di: To be precise, it's (MOTU) and (Debian's maintainer and uploaders).
[07:47] <man-di> minghua: thanks
[07:48] <slangasek> freeflying: so, why could you not simply remove the .pot file in an upload to Debian, and allow this to propagate to Ubuntu?
[07:48] <slangasek> freeflying: if the .pot file is empty it doesn't benefit the Debian package either, so removing it at build time also won't hurt Debian
[07:50] <minghua> slangasek: I think missing POT file will cause FTBFS on Ubuntu buildd as well, though I'm not sure.
[08:11] <hstraub> Hallo, my name is Herbert Straub and I ask about the re-sync of the REVU uploaders keyring. I followed the instructions MOTU/Packages/REVU. My launchpad account is herbert.
[08:26] <Fujitsu> hstraub: I'll resync it.
[08:31] <slytherin> Hi all, is there any way to identify java related packages in universe/multiverse that need fixing (apart from FTBFS)?
[08:32] <Fujitsu> slytherin: What do you mean by 'fixing'?
[08:33] <slytherin> Fujitsu: any sort of problems, bugs, watch files, unmet deps. I am looking for an easy way to locate java apps/libs with problems. Because I can only help in that area
[08:34] <dholbach> slytherin: you should talk to doko (once he's back from Holidays again) and man-di - looks like a Java team is coming up :)
[08:35] <Fujitsu> It'd be nice to have something like packages.qa.d.o at some point, collating all of the QA information per-package.
[08:36] <slytherin> dholbach: as of now I have helped fix few FTBFS. But now I am looking for something different. I will still try to fix FTBFS though.
[08:37] <slytherin> my next target is lucene2
[08:38] <man-di> slytherin: when you want to fix something in java packages please send the report to Debian BTS, I will look into it, do an upload and then you can sync
[08:38] <slytherin> man-di: ok
[08:43] <Fujitsu> hstraub: It's done.
[08:44] <slytherin> man-di: On 'batik' front, I think it should now compile with GCJ except JPEG and TIFF codecs part. But I think latest version has an additional dependency. Should I file a bug for this in debian?
[08:45] <huats> morning everyone
[08:46] <slytherin> oops, bug is there already
[08:46] <man-di> slytherin: problem is that we have software in the archive that depends on batik providing TIFF codec, and it does only when its compiled with SUN JDK
[08:46] <man-di> icedtea will probably work too, but I dont checked that yet
[08:47] <slytherin> man-di: icedtea won't make a difference from gcj. It doesn't have those sun specific classes.
[08:48] <man-di> so no option to moving to another JVM for building for now
[08:48] <slytherin> man-di: which software are you referring by the way which depend on codecs? I will take a look if they work with latest version
[08:48] <man-di> btw: batik is currently actively worked on it debian
[08:48] <man-di> slytherin: I think it was fop
[08:49] <man-di> problem was that GCJ built batik fine, but fop dont build with the new batik anymore
[08:50] <slytherin> hmm. I hope batik developers move away from sun specific apis soon
[08:50] <man-di> slytherin: I think there is no other API providing that specific feature
[08:50]  * Fujitsu thinks there is - in languages other than Java.
[08:51] <Fujitsu> Silly Java.
[08:51]  * man-di slaps Fujitsu 
[08:51]  * Fujitsu preempted that.
[08:52] <man-di> ...we could integrate JRuby or Jython and use Ruby or Python to implement it...
[08:52] <man-di> there was also some PHP interpreter written in Java...
[08:53] <slytherin> I wonder why Apache Commons' developer have not developed an alternative yet
[08:53] <Fujitsu> That sounds worse than normal PHP, and that's pretty bad.
[08:53] <Fujitsu> No buffer overruns, I guess.
[08:53] <hstraub> Fujitsu, thank you...
[08:54] <man-di> slytherin: they dont saw the need, tiff is not so widely used. You need a critical mass of users who need a feature...
[08:55] <slytherin> hmm
[08:55] <man-di> Fujitsu: its for cases when you want to run everything in a Java Application Server
[08:55] <man-di> that has its benefits, but also its troubles
[09:09] <freeflying> slangasek: its not a dfsg issue, so i don't think it is a best way to remove it directly from upstream tarball
[09:17] <rzr> talking about java ... what's news about openjdk ?
[09:17] <rzr> s/what's/what are the/g
[09:18] <slytherin> rzr: news as in? icedtea is in Ubuntu. Hopefully it will make into Debian soon.
[09:19] <rzr> great
[09:19] <rzr> so tuxguitar will quit contrib to main
[09:20] <slytherin> rzr: depends on it's dependencies. openjdk/icedtea can not fully replace Sun's JDK as of yet
[09:21] <rzr> that's what i am reading at http://icedtea.classpath.org/wiki/FrequentlyAskedQuestions#Functionality_and_Testing
[09:21] <rzr> no sound yet ..
[09:24] <man-di> rzr: we (Debian) are a bit reluctant to move pcakges from contrib to main just because of icedtea, it should better work with another free runtime too.
[09:25] <man-di> rzr: after all icedtea is i386, amd64 and powerpc only
[09:25]  * pochu waves
[09:25] <man-di> and powerpc is limited
[09:25] <rzr> I plan to make a nativebuild (in debian) of tuxguitar in next upstream release
[09:26] <man-di> rzr: for what? What do you gain by this?
[09:27] <geser> good morning
[09:28] <rzr> then it will not requiere sun jvm
[09:28] <rzr> and can be in main
[09:29] <man-di> rzr: I really doubt that
[09:29] <man-di> rzr: that will only work when it works with GCJ as byteocode too
[09:29]  * minghua can't believe someone is proposing Ubuntu to adopt Gobolinux's filesystem layout because it "sounds like fun"...
[09:30] <slytherin> man-di: The problem with lucene2 in Ubuntu is some unit tests for contrib libraries are failing, not the core. Can we bypass this failure? Or how about unit testing only core.
[09:30] <Fujitsu> minghua: That's what people do...
[09:30] <Fujitsu> minghua: ubuntuforums?
[09:30] <rzr> man-di: It will , if we wrap the sound layer to alsa
[09:31] <minghua> Fujitsu: No, some list, should be -devel-discuss.
[09:32] <Fujitsu> Oh gawd, they've migrated to there now!?
[09:32]  * Fujitsu screams.
[09:32] <Fujitsu> I thought we kept that kind of person in the forums.
[09:33] <minghua> Heh.
[09:33]  * Fujitsu is behind on -devel-discuss by several hundred messages, fortunately.
[09:34] <man-di> rzr: ah, you meant providind an additional JNI library to access also, I thought you meant compiling tha jars to native code with gcj
[09:34] <minghua> Fujitsu: Me too.  I just browse my inbox through the web interface now and then before I download them via POP3, and such messages always intrigues me.
[09:34] <rzr> minghua: we do both
[09:35]  * minghua has been more and more happy about the -devel and -devel-discuss split.
[09:35] <Fujitsu> Ah, so there is some sanity to it.
[09:35] <Fujitsu> /Variable/tmp
[09:36] <pochu> DarkSun88: congrats! :)
[09:37] <dholbach> DarkSun88: congratulations! :)
[09:38] <slytherin> man-di: Can you please reply to my question. It is about lucene2. May be you missed it.
[09:39] <minghua> man-di: I think rzr meant to speak to you a few lines above.
[09:40] <man-di> slytherin: good question
[09:40] <man-di> minghua: I guessed that
[09:41] <man-di> slytherin: so it does FTBFS on Ubuntu?
[09:41] <slytherin> man-di: Yes.
[09:41] <man-di> slytherin: do you have a link to a log?
[09:42] <slytherin> man-di: just a minute
[09:42] <rzr> man-di: minghua is right
[09:42] <rzr> :)
[09:42] <slytherin> man-di: Some problem with my network. Can you please check this page - http://qa.ubuntuwire.com/ftbfs/
[09:43] <man-di> the host seems down
[09:44] <slytherin> man-di: I will be back after a coffee break. We will discuss after that.
[09:45] <man-di> I need to do some customer work here too...
[10:00] <geser> man-di: http://launchpadlibrarian.net/11125011/buildlog_ubuntu-hardy-i386.lucene2_2.2.0-2_FAILEDTOBUILD.txt.gz
[10:02] <man-di> geser: thx
[10:03] <man-di> slytherin: I cant test currently if that fails in Debian too
[10:03] <man-di> slytherin: if not I would be for an ubuntu-only patch
[10:03] <man-di> slytherin: if yes we should patch debian and sync
[10:19] <slytherin> man-di: I am ok with this approach.
[10:23] <man-di> slytherin: can you work on this? I'm currently on limited time
[10:23] <amarillion> I'd like to request a REVU review for my package speed-game please: http://revu.tauware.de/details.py?package=speed-game
[10:24] <slytherin> man-di: I don't have access to any Debian machine. And I am doing all this in my free time in office. No net connection at home presently. :-(
[10:24] <slytherin> man-di: I can try setting up debian pbuolder chroot. But it will take time
[10:27] <amarillion> are you all already running hardy on your machines?
[10:27] <man-di> slytherin: hmm, can test on Debian but not yet, tonite I can
[10:27] <slytherin> man-di: No problem. I will wait.
[10:28] <slytherin> amarillion: why are you asking that? :-)
[10:28] <amarillion> I'm on gutsy, I have to keep remembering to adjust the target distribution to hardy before uploading my package
[10:29] <amarillion> Which is a pain
[10:29] <amarillion> also, I'd like to redirect some friends to my ppa to test some of the packages I'm working on
[10:29] <amarillion> but they are running gutsy of course
[10:30] <amarillion> so I'm feeling rather schizophrenic about gutsy/hardy
[10:31] <slytherin> amarillion: You can use dch command to add an entry to changelog and use -r option to set release. You can set an alias as follows 'alias dch="dch -i -r hardy"'
[10:31] <amarillion> ah that will help, thanks
[10:32] <amarillion> so which release are you running then? Is hardy too unstable for day to day use?
[10:34] <Fujitsu> ........
[10:34]  * Fujitsu looks at KmosReport.
[10:34] <Fujitsu> Why is #164166 marked as a positive?
[10:35] <slytherin> amarillion: I am not using it on my office machine. But using it at home.
[10:35] <man-di> I wonder why people are making such a hard time to Kmos regarding cyphesis-cpp
[10:36] <man-di> I guess for everyone else it would be synced already
[10:38] <Fujitsu> dholbach: Can you please clarify why you thought that was a positive?
[10:38]  * pochu enjoys his first requestsync bug :)
[10:42] <dholbach> Fujitsu: ok... just read up on the irclogs
[10:42] <Fujitsu> It could have probably been explained better on KmosReport, sorry.
[11:11] <minghua> dholbach: Speaking of KmosReport, I don't see any solution proposal in bug 181029.
[11:11] <ubotu> Launchpad bug 181029 in scim-bridge "[FTBFS] scim-bridge (0.4.14-1) fails to build in hardy" [Medium,Confirmed] https://launchpad.net/bugs/181029
[11:12] <\sh> moins
[11:13] <minghua> hello
[11:13] <minghua> hello \sh.
[11:14]  * minghua grumbles at his new keyboard that has \ key in a different place.
[11:14] <dholbach> minghua: the bug report is about a FTBFS - Marco says "It needs a cleanup of empty files in po/ directory."
[11:15] <dholbach> minghua: if you want to re-word "solution proposal" to something else indicating that he analyzed the problem, that's fine with me
[11:15] <minghua> dholbach: But how?  And I remember that a missing POT file will cause a similar FTBFS.
[11:17] <dholbach> minghua: really? most apps ship without .pot files and build OK - we explicitly have to run     cd po; intltool-update -p   for some to get the .pot file for rosetta
[11:20]  * dholbach -> break
[11:20] <minghua> Okay, something is seriously wrong with pidgin here...
[11:21] <minghua> dholbach: I may well be wrong.  I just remember seeing some building problem with missiong POT file before, around the dapper days.
[11:21] <mok0> minghua: yes I've seen that too...
[11:22] <minghua> dholbach: I'll change it to "correct analysis" on the wiki, regardless.  I believe that's okay for you?
[11:22] <minghua> mok0: Pidgin crashing, or build problem with missing POT file? :-P
[11:22] <mok0> minghua: pidgin randomly crashing
[11:24] <mok0> minghua: On amd64/gutsy
[11:25] <persia> mok0: I encountered that from about october 15th to around november 15th.  Might be worth looking at the changelogs.
[11:25] <mok0> persia: you mean the problem was solved in a newer version?
[11:26]  * minghua cancels apport crash report sending, seeing there is no usable backtrace.
[11:26] <minghua> mok0: hardy i386 here.
[11:27] <persia> mok0: pidgin was remarkably unstable for a while, especially when interacting with IRC.  It seems to have settled now, but my system typically has the unstable and broken bit inverted, so it's not always a good indicator of real issues or real solutions.
[11:27] <mok0> minghua: what pidgin version?
[11:28] <minghua> mok0: 1:2.2.2-1ubuntu1
[11:28] <mok0> persia: the problem we saw was in jabber
[11:28] <mok0> minghua: same version here
[11:28] <persia> mok0: See.  That's why I only report bugs when I can reproduce them in sterile environments :)
[11:29] <mok0> persia: good point :-)
[11:29] <minghua> mok0: Huh?  But changelog says that's a hardy version.
[11:29] <minghua> Anyway, pidgin has been stable for the past few weeks until tonight's upgrade.
[11:29] <mok0> minghua: Ah, sorry, 1:2.2.1 here
[11:29] <minghua> So I doubt it's pidgin's fault.
[11:31] <minghua> (pidgin was not in tonight's upgrade)
[11:31] <mok0> minghua: could be coincedental
[11:42] <pochu> \o/ My first upload :-)
[11:44] <persia> Hurrah!
[11:45] <\sh> pochu: congrats :)
[11:45] <\sh> btw...pidgin and jabber is aweful...just use gajim as jabber client and search for a jabber server with many transports available ;)
[11:46] <rzr> i use biltbee
[11:47]  * persia doesn't think pidgin or gajim integrate with biltbee very well...
[11:52] <DarkSun88> dholbach: pochu Thanks a lot.
[11:52] <DarkSun88> :)
[11:52] <\sh> hmm...I'm searching for someone in germany who wants to have a new job as IT Projectmanager :)
[11:53] <\sh> Karlsruhe Area ;)
[11:57] <Nafallo> \sh: naah. using lots of servers is more fun.
[11:58] <Nafallo> \sh: I use my own server in London for jabber, slomos brothers server (de) for yim, norweigan for icq, swedish and danish for msns :-)
[11:58] <\sh> Nafallo: lol ;)
[12:00] <ion_> I use my own server for jabber as well. :-)
[12:00] <rzr> \sh: bring the job in france and we'll talk
[12:02] <\sh> rzr: that's a problem :)
[12:02] <\sh> rzr: come to germany...karlsruhe is next to strassbourgh (sp?)
[12:04] <dholbach> minghua: sure, that'S ok
[12:04] <sectech> I wouldn't mind re-packaging gusty applications for hardy, I was wondering if someone out there could walk me though it once first though. I am totally new to packaging
[12:04] <sectech> I did read the documentation
[12:05] <sectech> Is there anyone willing to give me a hand?
[12:05] <persia> sectech: In many cases, the gutsy packages were just reused for hardy entire, unless there had been an update in the meantime.  At this point, we're mostly looking at bugfixes, although there are still a few candidates for consideration for an update.  What sort of thing would you like to do?
[12:07] <sectech> I'm trying to find a way to contribute... I have enough programming experience just get by... I figured there must be something that I could work on
[12:07] <sectech> believe me I have plenty of time (I lost my job a while back haha)
[12:08] <ion_> Note to self: I should check whether sync is enough or a merge is required to get ruby1.9 from sid to hardy.
[12:09] <persia> sectech: Well, there are basically three classes of work that might be a good introduction to the process.  Finding and fixing bugs (many have patches that just need review & integration), working on some of the QA tasks, and addressing integration issues.  Also, some people like to focus on a specific programming language or set of application functionality.
[12:10] <sectech> Okay.... How about bug fixes and patching...I could give that a shot
[12:10] <Kmos> when we've 0ubuntu1 and it mention about the maintainer field spec in changelog, it still needed at 0ubuntu2 revision ?
[12:10] <Kmos> i need to mention about the spec in 0ubuntu2 changelog
[12:10] <Kmos> ?
[12:10] <persia> Kmos: We only rephrase all the "Retained changes" during a merge.  An update just needs new changes.
[12:10] <\sh> grmpf...never test afterstep in a running gnome desktop session...
[12:10] <Kmos> persia: ah ok =) thanks
[12:11] <sectech> Basically I would reproduce the bug, apply the patch and see if it's still there right?
[12:11] <persia> sectech: https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_contact=&field.bug_commenter=&field.subscriber=&field.component
[12:11] <sectech> k
[12:11] <persia> That horrid URL will provide a list of all the bugs that have a patch candidate.  Where the patch isn't a debdiff, or the sponsors aren't subscribed, it frequently needs review & testing.
[12:12] <sectech> ok... I'll look through that and see if I can make sense of it
[12:13] <persia> Also, you might try https://launchpad.net/ubuntu/+bugs?field.tag=bitesize or https://launchpad.net/ubuntu/+bugs?field.tag=packaging, or even https://launchpad.net/ubuntu/+bugs?field.tag=patch as additional sources of things that tend not to be too hard (and the sort of thing for which  people here may be happy to help if you get stuck)
[12:13] <\sh> persia: could you do me a favour and catch the debdiff for afterstep from bug #174252 and upload please?
[12:13] <ubotu> Launchpad bug 174252 in libungif4 "transition to libgif" [Undecided,In progress] https://launchpad.net/bugs/174252
[12:14] <persia> \sh: I've promised myself no sponsoring tonight in the hopes of catching up on a couple other things :(
[12:14] <\sh> persia: ok :) np...
[12:14] <\sh> pochu: you can do it now ,-)
[12:14] <persia> Could anyone else please help \sh with this?  I'm guessing it's needed now to resolve some alpha 3 goal.
[12:14]  * \sh 's fixing emacs21 now
[12:15] <\sh> but before that..I'll upload the patch to debiqan
[12:16] <pochu> \sh: looking
[12:16] <\sh> pochu: thx..
[12:17] <minghua> \sh: It would be nice if you can avoid those timestamp changes in the patch...
[12:17] <minghua> \sh: But since pochu is looking now, you can ignore my opinion. :-)
[12:19] <pochu> minghua: that'd mean more work since those are autogenerated by autofoo, aren't they?
[12:19] <sectech> What about installing hardy and searching for bugs? just to begin with so I can get used to the QA system?
[12:19] <\sh> minghua: well, that comes from a simple thing...the afterstep package needs some magic before working with dbs-edit-patch
[12:20] <\sh> minghua: to use dbs-edit-patch you need to run make -f debian/rules debian/vars and this will introduce those changes
[12:20] <pochu> sectech: if it's not a critical box and you aren't afraid of breaking it or killing your cat, go for it :)
[12:20] <\sh> minghua: I talked to robert (the debian maintainer) and it's normal
[12:20] <pochu> sectech: but keep an stable install somewhere just in case ;)
[12:20] <sectech> I think I have another hard drive around here.
[12:22] <\sh> minghua: and yes, you can remove those changes from the diff but it's so trivial we can live with it somehow...
[12:23] <mruiz> hi all
[12:23] <minghua> \sh: Ah, I see it's not easily avoidable.
[12:24] <minghua> \sh: Then I say it's not worth the effort.  I am not the sponsor anyway. :-)
[12:28] <persia> sectech: Just in case, it's worth reviewing https://wiki.ubuntu.com/MOTU/Contributing.  I'm guessing you've already read it from your earlier statement about documentation, but it might help give some hints about processes.
[12:28] <sectech> persia Yeah I did read that...
[12:33] <pochu> \sh: uploading
[12:45] <\sh> pochu: thx a lot
[12:46] <\sh> pochu: I'm adding a debdiff for emacs21 just now
[12:47] <sectech> When I start with horde... what's the URL where I would post the bugs to?
[12:48] <\sh> sectech: horde bugs or ubuntu bugs?
[12:48] <persia> sectech: Likely https://bugs.launchpad.net/ubuntu/+source/horde/+fielbug, but I'm just guessing.
[12:48] <sectech> ubuntu horde
[12:48] <\sh> sectech: launchpad
[13:04] <TheMuso> Hey pochu. Whielding the super upload opwers I see. Congratulations!
[13:04] <TheMuso> powers
[13:08] <mruiz> hahaha
[13:09] <TheMuso> DarkSun88: Congratulations!
[13:09] <DarkSun88> Thanks a lot Luke :)
[13:09] <DarkSun88> At all my sponsors and not naturally :D
[13:10] <\sh> DarkSun88: yeah congrats from me too :)
[13:10] <DarkSun88> :D
[13:10] <DarkSun88> Thanks
[13:11] <\sh> well, camlimages, emacs21 and just now driftnet will be fixed too :)
[13:12] <\sh> good afternoon jono and jdstrand :)
[13:13] <jdstrand> hi \sh!
[13:17] <jono> hey \sh
[13:19] <\sh> grmpf../me should get ready for the gym...
[13:38] <minghua> Can anyone stop this "Daniel Moyne" person's reporting bugs?
[13:39]  * minghua points at #181475 (and -76, -77, -81, -82, -83, -84).
[13:40] <man-di> minghua: he must have done a break at -78, -79, -80...
[13:40] <persia> minghua: most of the earlier bugs on https://bugs.launchpad.net/~dmoyne/+reportedbugs don't seem quite so egregious.  Perhaps just a multiple submit issue?
[13:41] <minghua> persia: Yeah, I meant temprarily.  Not a ban.  I assume bona fide here.
[13:42] <persia> Seems to have stopped, anyway.
[13:44]  * minghua wonders why persia is so fast at marking duplicates...
[13:44]  * persia has practice :)
[13:45] <tuxmaniac> Can somebody please review http://revu.tauware.de/details.py?package=alliance and give their valuable feedback? Thanks in Advance.
[13:45] <persia> minghua: Simple recipe: go to the submitters +reportedbugs, open all the bugs in tabs, click "Mark as duplicate" in successive tabs, grab the bug number into the X buffer in the last tab, iterate back middle-clicking and submitting.  Reload +reportedbugs to ensure that you caught them all.
[13:46] <persia> Actually, this works for a package bug page too.
[13:46] <persia> tuxmaniac: Is it lintian and linda clean, with maxiumum verbosity and hardy versions, for both source and binary?  (these generate >60% of my comments on packages on REVU).
[13:49] <mok0> persia: did you upload theseus this morning?
[13:49] <persia> mok0: I don't remember uploading anything this morning.  Why?
[13:50] <mok0> I patched it last nigth and it is already built. Just wondering who to thank
[13:50] <minghua> persia: I'm doing similar things here.  But LP is not really very responsive for me...
[13:50] <persia> mok0: The bug didn't get an assignee when it was sponsored?  You can check the signature on the .dsc or on the mail to -hardy-changes if you like.
[13:52] <pochu> TheMuso: heh, yeah, and thanks :)
[13:52] <\sh> pochu: http://launchpadlibrarian.net/11229263/emacs21_21.4a%2B1-5ubuntu5.debdiff http://launchpadlibrarian.net/11229512/camlimages_2.2.0-2ubuntu1.debdiff http://launchpadlibrarian.net/11229790/driftnet_0.1.6-7ubuntu1.debdiff http://launchpadlibrarian.net/11229884/gdal_1.4.4-1ubuntu1.debdiff  ready for review and upload :) (bug #174252)
[13:52] <ubotu> Launchpad bug 174252 in libungif4 "transition to libgif" [Undecided,In progress] https://launchpad.net/bugs/174252
[13:53] <persia> minghua: Interesting.  My packets are going trans-pacific, and then trans-atlantic to get there.  I don't know why I'd have less latency.
[13:53] <mok0> Ah. dholbach, thanks! :-)
[14:03] <pochu> \sh: that will have to wait, 'cos I'm off to lunch :)
[14:03] <\sh> pochu: np ... just not to forget...wmaker just fixed..simage needs more love then I expected
[14:03] <pochu> \sh: feel free to poke DarkSun88 who is newbie ;)
[14:04] <\sh> but right now, I'm off to the gym...need to get rid of 10kg ;)
[14:05] <tuxmaniac> persia, did you get my message?
[14:06] <persia> tuxmaniac: Not that I noticed.  What did you message me about?
[14:07] <imbrandon> LaserJock: your behind MOTU post is titled " dholbach "
[14:07] <bddebian> Heya gang
[14:07] <imbrandon> looks like that might be incorrect
[14:07] <imbrandon> heya bddebian
[14:07] <tuxmaniac> lintian and linda are complaining about newer standards version is that warning ok persia ?
[14:07] <persia> bddebian: I'm about to be off, but you were looking for me earlier?
[14:07] <bddebian> Hi imbrandon
[14:07] <tuxmaniac> bddebian, boo
[14:08] <imbrandon> heya persia :)
[14:08] <bddebian> persia: Yeah but I forget why :(
[14:08] <bddebian> Hi tuxmaniac
[14:08] <dholbach> imbrandon: I posted it
[14:08] <geser> Hi bddebian
[14:08] <bddebian> Heya geser
[14:08] <emgent> hello there :P
[14:08] <persia> tuxmaniac: If lintian is complaining, you're not using the latest lintian.  You may ignore linda for now when she says that 3.7.3 is too new.  Also check the binary packages by running against $arch.changes
[14:08] <slytherin> tuxmaniac: It is fine
[14:08] <bddebian> persia: Oh I remember.  I'll hit you up "tonight" if you are around
[14:08] <imbrandon> dholbach: ahh ok, it showed up on planet with the wrong title :)
[14:08] <slytherin> tuxmaniac: oops, follow persia
[14:09] <persia> bddebian: Tell me quick, and maybe I'll have a quick answer :)
[14:09] <dholbach> imbrandon: argl....
[14:10] <bddebian> persia: Nah it was more about helping my dumb arse with something again
[14:10] <slytherin> Please give me an advice. I am going to patch source to fix an FTBFS. The problem is due to missing header files from sources. But the function calls that are giving problem are anyway deprecated in latest GTK+. So is it better to replace those call appropriately or should I just go ahead and add header files.
[14:13] <persia> slytherin: I like updating to the newest API: it means you have longer before the next time the package needs a patch, and upstream is usually happier to receive the update patches (if you do a good job).
[14:13] <slytherin> persia: Ok. :-)
[14:15] <slytherin> The functions are deprecated in GTK 2.12. So I guess it will be long before they are actually removed. But I will anyway replace those calls.
[14:39] <bddebian> What TZ is slangasek in?
[14:39] <soren> bddebian: He's on the west coast of the US.
[14:39] <soren> bddebian: I don't know what $TZ that translates into.
[14:39] <bddebian> soren: Ah that's right, thanks
[14:40] <soren> bddebian: np :)
[14:40] <bddebian> A little early yet then :-)
[14:40] <soren> bddebian: Slightly, yes :)
[15:15] <dbmood1> hi got a suggestion re a possible fix for the issue of ubuntu (tis not its fault) managing laptop hd in laptop mode
[15:35]  * rzr updated http://revu.tauware.de/details.py?package=jaaa
[15:50] <apachelogger> dholbach: mail for you
[15:50] <dholbach> apachelogger: gracias
[15:51] <apachelogger> de nada
[15:51] <apachelogger> I think ;-)
[15:52] <jpatrick> ja
[15:54] <apachelogger> jpatrick: très bien
[15:54] <jpatrick> apachelogger: merci
[16:42] <slytherin> yay, one more FTBFS sent down the rabbit hole. :-)
[17:07] <slangasek> bddebian: hi, so two things on the asc upload
[17:07] <bddebian> Uh oh
[17:07] <slangasek> bddebian: 1) omg, who prepared this upstream tarball, it's an embarrassment
[17:08] <bddebian> Uhm, upstream. :)
[17:08] <tjaalton> jdong: could you change the maintainer to MOTU when you upload the next version of gtkpod-aac? thanks :)
[17:08] <slangasek> bddebian: 2) I don't know what the procedure is within the Debian games team for adding new comaintainers.  According to the changelog, you added yourself; was this acked by someone who was an existing uploader, or is there a standing debian-games policy I can refer to in this regard?
[17:09] <slangasek> bddebian: yeah, I know it was upstream, I did compare the tarballs... :)
[17:09] <jdong> tjaalton: aww you don't want to be scapegoat anymore? :D
[17:09] <bddebian> slangasek: Hmm, good question, I don't know that we have a set "policy".  I have usually just been adding myself when uploading.
[17:09] <tjaalton> jdong: right, I don't use it anymore, so.. :)
[17:10] <tjaalton> banshee is a whole lot easier
[17:10] <bddebian> slangasek: BTW, I built it with libparagui1.1 on my sid laptop this morning and everything works fine.
[17:10] <jdong> tjaalton: ok, will do.
[17:10] <slangasek> bddebian: I'd appreciate a clarification on this, then; I don't assume that just because someone has commit access to a repo, they're empowered to mark themselves as an uploader
[17:10] <slangasek> (and this would be a blocker for me sponsoring it to Debian)
[17:10] <bddebian> slangasek: fair enough
[17:11] <tjaalton> jdong: great, thanks!
[17:13] <bddebian> I'm thinking I really should have just stuck with porting Hurd packages..
[17:14] <azeem> there's so many PATH_MAX waiting for you!
[17:15] <bddebian> hah
[17:16] <bddebian> Well let's see if I actually get a response from the Games Team ML this time...
[17:17] <linuxfan> k
[17:51] <LaserJock> bah, dholbach needs to get some real American hours ;-)
[17:53] <geser> LaserJock: you could also adjust to european working hours :)
[17:54] <LaserJock> umm ....
[17:54] <LaserJock> ;-)
[17:55] <DaveMorris> Hi, I'm still looking for a revu of http://revu.tauware.de/details.py?package=libserial (it's a small package to build)
[17:56] <bddebian> LaserJock: Or you can just say screw it like I'm getting closer to doing.. :)
[17:56] <joejaxx> bddebian: lol
[17:58] <joejaxx> slangasek: what exactly is a release wizard? :D
[17:58] <bddebian> I think I'm either going to have to apply for DD or stop trying to work with Debian
[17:58] <azeem> there's this DM thing now as well
[17:59] <slangasek> joejaxx: a modal dialog that walks you through releasing an OS
[17:59] <joejaxx> slangasek: bah :P i mean the contributor position :)
[17:59] <joejaxx> slangasek: haha :P
[17:59] <joejaxx> slangasek: based on ncurse library? :)
[18:00] <joejaxx> azeem: where is the information on DM's?
[18:00] <slangasek> joejaxx: python-glade
[18:01] <bddebian> azeem: Aye, but I'm not sure that is enough
[18:01]  * joejaxx at the developer corner and does not see it
[18:01] <joejaxx> s/at/is\ at/g
[18:01] <joejaxx> slangasek: :P
[18:02] <slangasek> bddebian: if you're talking about asc, I think it would be equally inappropriate for a DD to add themselves to uploaders without consulting the current uploaders (and I have dressed down DDs for this before)
[18:02] <bddebian> slangasek: No, asc is one small part of the picture
[18:05] <bddebian> slangasek: For asc, you might have better access to sam than I.  I can't ever get a hold of him
[18:19] <slangasek> bddebian: did you mail the games team ML then?  I don't see anything in the archive at http://lists.alioth.debian.org/pipermail/pkg-games-devel/2008-January/thread.html, is that not the right list?
[18:22] <bddebian> slangasek: http://lists.debian.org/debian-devel-games/2008/01/msg00107.html
[18:23] <slangasek> ah so
[18:24] <\sh> re
[18:28] <\sh> phew...first time in my life that I entered a gym...now I know what horror means...
[18:29] <geser> that bad?
[18:29] <\sh> geser: if you never did sport for your health...it's that bad, yes :)
[18:30] <\sh> btw...has anybody time to do some sponsor uploads for libgif transition? :)
[18:31] <geser> \sh: I could do some in a few hours (if there are any left)
[18:32] <\sh> geser: yeah there are some...I put them on the bug...
[18:35] <\sh> I wonder what's the best way to fix simage...
[19:05] <Ward1983> if i would like to see something packages, where should i suggest the package?
[19:05] <warp10> I have a weird problem with a .desktop file. It is here: http://revu.ubuntuwire.com/revu1-incoming/tennix-0801042050/tennix-0.5.0/tennix.desktop
[19:05] <Ward1983> * packages = packaged
[19:05] <warp10> It shows fine in Ubuntu, but according to pitti it doesn't in Debian, altough it is installed in the proper directory: http://paste.ubuntu-nl.org/51377/
[19:07] <geser> Ward1983: see https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[19:07] <Ward1983> geser, ty
[19:07] <Kmos> warp10: gnome uses "menu" file
[19:07] <Kmos> ups..
[19:07] <Kmos> warp10: debian i mean
[19:08] <geser> Kmos: doesn't gnome in debian uses both?
[19:08] <Kmos> geser: yes
[19:08] <Kmos> :)
[19:08] <warp10> Kmos: I thought they use both... am I wrong?
[19:08] <Kmos> warp10: nop.. only ubuntu uses .desktop file
[19:09] <slangasek> do you mean "ubuntu only uses the .desktop file"?  because Debian does use both
[19:11] <Kmos> slangasek: right
[19:25] <bddebian> warp10: Do you have a source package somewhere, I'll try it on my unstable machine
[19:27] <warp10> bddebian: orig, diff and dsc that pitti used are in this tarball: http://colangelo.eu/tennix.tar.gz
[19:31] <bddebian> warp10: trying now
[19:34] <bddebian> warp10: One thing.  If you're adding a desktop file you should call dh_desktop in rules
[19:35] <warp10> bddebian: the .desktop file comes from upstream and is installed by Makefile. Should I add dh_desktop anyway?
[19:36] <bddebian> warp10: Hmm, probably.  But either way, it works for me on my unstable laptop :-)
[19:37] <warp10> bddebian: Well, ok. I'll report that to pitti. Thank you so much for your help :)
[19:37] <bddebian> NP
[19:38]  * jpatrick wonders if it's a good idea to subscribe to debian-mentors with a @(k)ubuntu address
[19:38] <bddebian> jpatrick: It shouldn't hurt
[19:39] <jpatrick> bddebian: here goes
[19:41] <pochu> jpatrick: I post to a few debian lists and my packages have my @ubuntu.com address in the Maintainer/Uploader and I haven't seen a flame because of that yet :)
[19:42] <Kmos> warp10: even coming from upstream, you should use dh_desktop
[19:44] <warp10> Kmos: I'm wondering if this could be the source of the problem, but according to the test bddebian just made, it shouldn't be. Anyway, thanks, I'll modify rules :)
[19:45] <norsetto> warp10: dh_desktop is pretty much useless now (unless you register a mime type)
[19:45] <bluekuja> heya norsetto
[19:45] <db-keen> would anyone be willing to help me make my first package?
[19:46] <bluekuja> norsetto, would you please un-assign amachu from me? seems to be disappeared since ages now
[19:46] <bluekuja> :)
[19:46] <jpatrick_> bluekuja: I saw him today on #kubuntu-devel
[19:46] <bluekuja> jpatrick_, really?
[19:46] <norsetto> bluekuja: you tried to get back in contact?
[19:46] <warp10> norsetto: mmm... so looks like I'll leave rules as it is now.
[19:47] <bluekuja> norsetto, not really...I answered him on the I was mentoring him with
[19:47] <jpatrick> bluekuja: /msg seenserv seen amachu
[19:47] <bluekuja> norsetto, and for something like 2 weeks, I got no answers
[19:47] <bluekuja> jpatrick, ty
[19:47] <bluekuja> norsetto, want me to ping him on irc?
[19:48] <norsetto> bluekuja: please
[19:48] <bluekuja> norsetto, ok perfect
[19:48] <bluekuja> :)
[19:48] <norsetto> bluekuja: let me know
[19:49] <bluekuja> norsetto, I will
[19:49] <bluekuja> norsetto, as soon as I get him on irc, seems to be not connected since 2h 12m
[19:49] <bluekuja> norsetto, so he should be around tomorrow
[19:49] <bluekuja> ;)
[19:50] <norsetto> bluekuja: he is in india (or thereabout), so I think he might be gone to bed already
[19:50] <bluekuja> yep
[19:50] <bluekuja> norsetto, are reports  from mentors still up?
[19:51] <norsetto> bluekuja: yes, but nobody bothers and I got tired of reminding
[19:52] <bluekuja> norsetto, I'm happy about hellboy195's work, he's doing good
[19:52] <bluekuja> norsetto, *** that was my report :P
[19:52] <norsetto> bluekuja: glad to hear that
[19:53] <norsetto> bluekuja: I wish I would get even that from the others .....
[19:53] <hellboy195> bluekuja: oh man. do not overstate ;)
[19:53] <norsetto> hellboy195: good is not overstating, he didn't  say exceptionally well ....
[19:53] <hellboy195> norsetto: good is also overstating ;)
[19:54] <bluekuja> lol
[19:54] <hellboy195> let's say it's OK
[19:54] <bluekuja> hellboy195, step by step
[19:54] <bluekuja> anyway off for a shower
[19:54] <bluekuja> bbl
[19:54] <jpatrick> norsetto: my mentee's gone kernel packaging....
[19:54] <hellboy195> bluekuja: hf
[19:54] <bluekuja> hellboy195, ty
[19:55] <bluekuja> heya apachelogger
[19:55] <bluekuja> * apachelogger_
[19:55] <norsetto> jpatrick: good, tell him to package the latest rt2x00 drivers then
[19:56] <norsetto> jpatrick: oh, and tell him to make sure they actually work .....
[19:56] <apachelogger_> ahoy bluekuja
[19:58] <jpatrick> :)
[19:58] <LaserJock> ah ha! I think I figured out how to fix Planet Ubuntu's messed up Behind MOTU titles
[19:59] <pochu> It confused me to see dholbach's interview when I saw the tittle :)
[20:00] <LaserJock> yeah
[20:00] <pochu> title*
[20:00] <LaserJock> it seems to either takes the title of an attached pic or  the author
[20:00] <LaserJock> apparently using Atom instead of RSS fixes it
[20:02] <LaserJock> I guess it's a wordpress bug but I've only seen it cause problems on Planet
[20:02] <blueyed> RAOF: thanks for the nouveau packages in your ppa!
[20:15] <sommer> hey all, if I want to patch a package and I need to change three files, is it better to create 3 patches or 1 patch for all 3 files?
[20:16] <LaserJock> sommer: might depend on if they are related
[20:16] <LaserJock> generally it's fine to do just 1 patch
[20:16] <sommer> LaserJock: gotcha... I don't think you'd apply one patch without the others, if they are in different files that is
[20:16] <LaserJock> and if the reviewer wants them split up they'll request that
[20:17] <sommer> LaserJock: cool, thanks
[20:20] <geser> sommer: one patch or three patch is only relevant if the package uses a patch system
[20:23] <sommer> geser: ah, I'm thinking one patch to rule them all is fine, probably only 12 lines changed between all 3... heh
[20:36] <\sh> bah now I'm stucked again..openscenegraph needs gdal..which is not uploaded for the transition :(
[20:36]  * \sh needs to become a motu again :(
[20:38] <apachelogger> \sh: you shouldn't have left in the first place :P
[20:40] <\sh> apachelogger:heheheh..ha found the sponsor I need ,-)
[20:40] <apachelogger> ohnoes
[20:41] <\sh> well, then I write my application
[20:42]  * apachelogger notes that archive.ubuntu.com is far too slow today, or maybe his alpha3 downloads are blocking everything, whatever it is, it's not good
[20:42] <\sh> apachelogger: it's quite fast for me :)
[20:43] <apachelogger> so, it's alpha3
[20:43]  * apachelogger kicks kget
[20:43] <DarkSun88> Hi all. In debian/changelog there are a Debian old style entries. http://pastebin.ubuntu.com/3419/
[20:43] <DarkSun88> At line 1201 there is the problem and debuild not works.
[20:45] <DarkSun88> In this case, what I do?
[20:47] <soren> DarkSun88: Those don't look like old style entries to me.
[20:48] <DarkSun88> What are?
[20:48] <soren> DarkSun88: Anyhow, what does debuild say exactly?
[20:48] <soren> DarkSun88: I don't understand your question..
[20:48] <DarkSun88> soren: parsechangelog/debian: error: badly formatted heading line, at file debian/changelog line 1201
[20:50] <soren> Hm... Maybe there are other old styles that I am not familiar with.
[20:51] <\sh> DarkSun88: looks like a bug in a newer entry....parsechangelog is not always correct
[20:51] <soren> DarkSun88: I just fetched linkchecker and added a new changelog entry, and ran debuild -S -uc -us. It works fine.
[20:51] <DarkSun88> Ok.
[20:52] <soren> DarkSun88: Hmm... well, I guess those are just old style entries lacking an author field.
[20:52] <soren> I've never seen that before (but I'm not that old, either).
[20:53] <DarkSun88> soren: :)
[20:54] <soren> If a project using python-distutils installs a bunch of stuff in the wrong places, do I edit the setup.py script, or am I supposed to pass a lot of clever arguments to setup.py?
[20:56] <norsetto> Congrats DarkSun88!
[20:57] <DarkSun88> norsetto: Thanks. :)
[20:59] <pochu> soren: if the changes will be accepted upstream you can change it and forward the patch. Otherwise you can pass them with some PYTHON_something variables if you are using CDBS, or in your setup.py call if debhelper
[21:00] <pochu> soren: but upstream will likely accept it, I guess.
[21:00] <\sh> cool...end of business for today :)
[21:00] <soren> pochu: Er, yes, I'm aware of the mechanics of passing arguments, I was just wondering if there was a way to tell it to do this stuff by passing it arguments of if I had to change the script.
[21:00] <\sh> cu tomorrow
[21:01] <bddebian> Later \sh
[21:05] <sladen> win 222
[21:06] <jpatrick> wow
[21:10] <pochu> soren: python setup.py --help install will tell you the options for passing the prefix for the modules, data, scripts...
[21:10] <pochu> soren: is that what you meant? :)
[21:14] <soren> pochu: Ah, I tried --help and --help-commands, but didn't try --help install..
[21:14] <soren> pochu: Er.. no, that still doesn't help me much.
[21:15] <soren> pochu: It sets wwwpath = '/var/www/foobar'. I want to change that to '/usr/share/foobar/www'. How to do?
[21:49] <LaserJock> hmmpf, alpine doesn't do maildir :(
[22:13]  * RainCT would like to know if it's easy to create customized ubuntu CD's, as he's thinking about preparing a live CD for himself (with openbox as window manager and a custom selection of applications)
[22:18] <TheMuso> RainCT: Not really.
[22:18] <TheMuso> RainCT: It requires a bit of work.
[22:18] <TheMuso> RainCT: But it depends on how much you want to customize the CD.
[22:18] <TheMuso> I.e do you want to take an existing image and change, or do you want to build from scratch.
[22:19] <RainCT> do you know about any good documentation about it?
[22:19] <RainCT> (would be based on Ubuntu's image)
[22:20] <TheMuso> RainCT: From scratch, or take existing image?
[22:21] <RainCT> taking an existing one
[22:22] <TheMuso> There is reconstructor or whatever its called.
[22:22] <TheMuso> And I believe there are docs on community.ubuntu.com to help you do what you are wanting to do.
[22:22] <RainCT> cool, thanks
[22:23] <TheMuso> np
[22:26] <Amaranth> anyone feel like handling bug 181604?
[22:26] <ubotu> Launchpad bug 181604 in lsongs "File sharing and MP3 tag processing are broken" [Undecided,New] https://launchpad.net/bugs/181604
[22:26] <Amaranth> it's got a debdiff
[22:26] <Amaranth> oh, but it doesn't use a patch system
[22:27] <tbf> pochu: thanks for bug report, but what is FTBFS?
[22:27] <persia> Amaranth: Patch systems aren't mandatory, as long as you stay in line with Debian packaging.  Also, best to subscribe the sponsors queue to request upload.
[22:27] <persia> tbf: Fails To Build From Source
[22:28] <Amaranth> apparently he is the official lsongs maintainer now :P
[22:29] <Amaranth> i mean, upstream
[22:29] <tbf> persia: thanks
[22:29] <Amaranth> but he can't do a new release yet, some transition stuff happening
[22:30] <Amaranth> he wants me to upload it for him but i don't feel comfortable doing it
[22:30] <Amaranth> eh, I could just blame him if it breaks :)
[22:30] <slangasek> Amaranth: "handle" it how? seems to specifically fail the maintainer spec?
[22:31] <persia> Amaranth: Personally, I believe best practice is to use a patch system unless you are maintaining a VCS that derives from upstream.  If upstream releases a patch with no patch system, and is also the Debian maintainer, it's not an issue to not have a patch system :)
[22:31] <RainCT> Uh.. Now there's something that I don't understand: why are package with "Section: unknown" in debian/control synced successfully but building new Ubuntu revisions of them fails?
[22:35] <RainCT> bug 181624
[22:35] <ubotu> Launchpad bug 181624 in icon-slicer "Build of revision 0.3-1ubuntu1 failed" [Undecided,New] https://launchpad.net/bugs/181624
[22:44] <RainCT> well.. good night all :)
[23:01] <Amaranth> slangasek: I can't seem to find any documentation about that and I don't really remember what is required there
[23:02] <slangasek> Amaranth: https://wiki.ubuntu.com/DebianMaintainerField
[23:05] <pochu> soren: could you point me to the setup.py?
[23:21] <rexbron>  question. When I am compiling openlibs on amd64, it uses lib64 instead of lib. is there a way I can override that?
[23:22] <mok0> I've uploaded the perfect package to REVU. I bet you wont find any errors in it: http://revu.ubuntuwire.com/details.py?package=gpp4
[23:22] <mok0> rexbron: use switch -m32 ?
[23:23] <rexbron> mok0, could you explain what that does?
[23:23] <mok0> rexbron: it compiles a 32 bit binary on a 64 bit platform
[23:23] <rexbron> as well as where to use it
[23:23] <rexbron> mok0, it compile 64 bit binaries like it should
[23:23] <mok0> rexbron: gcc
[23:24] <rexbron> it just installs them to lib64 (which is a symlink, but is not present in the debian build dir)
[23:24] <mok0> rexbron: ah. That must be hardwired in the Makefile somehow
[23:25] <rexbron> :(
[23:25] <mok0> rexbron: grep for it
[23:25] <mok0> find . -type f |xargs grep lib64
[23:26]  * Fujitsu wonders how someone managed to file the same bug 7 times.
[23:26] <ubotu> Launchpad bug 7 in rosetta "Need help for novice translators" [Medium,Confirmed] https://launchpad.net/bugs/7
[23:26] <mok0> hehe
[23:26] <mok0> 42
[23:26] <Fujitsu> 20 minutes from first to last.
[23:27] <mok0> Fujitsu: weird
[23:27] <mok0> No takers for my PERFECT package?
[23:46] <LaserJock> Fujitsu: hmm, impressive. I would've given up after 3 ;-)
[23:46] <StevenK> LaserJock: Ponies!
[23:50] <LaserJock> anybody know if there is no mta installed what happens to system mails?
[23:50] <StevenK> They go nowhere
[23:50] <LaserJock> or even how system mails are done
[23:50] <StevenK> Since there is no /usr/sbin/sendmail to call
[23:51] <LaserJock> I've got msmtp install now
[23:51] <LaserJock> which would give sendmail
[23:51] <LaserJock> but it only works for my user, not root
[23:51] <LaserJock> so do they still go nowhere?
[23:51] <ion_> I’ve been using ssmtp on my desktop boxes.
[23:56] <LaserJock> hmm, I think I can create a systemwide msmtp config file
[23:56] <LaserJock> but how does the system know where to send the email?