[00:39] c [00:42] :) [00:48] ugh? === soonick_cancun is now known as adrianancona === adrianancona is now known as soonick_cancun === soonick_cancun is now known as soonick_cancund === soonick_cancund is now known as soonick_cancun [03:13] jdong: You're a forum person, aren't you? [03:13] wgrant: I am. [03:13] jdong: How does one get one's account renamed? [03:13] wgrant: depends on the reason for it being renamed. officially we don't do it, but extenuating circumstances can be evaluated :) [03:14] Ah. Damn. [03:14] jdong: do you want anything else sponsored ever again? If so, you'd better do the rename :P [03:15] wgrant: that extenuating circumstances part was an invitation to PM. [03:15] :) [03:15] jdong: Aha. [03:31] directhex: Rock! monodoc 1.9 [03:56] Hello. [03:56] https://bugs.launchpad.net/bugs/272210 [03:56] Launchpad bug 272210 in ubuntu "Megatunix needs to be packaged and added to the repository." [Wishlist,Confirmed] [03:57] Tetracomm: That's unlikely to see any action until after the Intrepid release. [03:57] Why? [03:58] hello there, I am not sure if this is the right place to ask, but how would I go about helping out with MOTU activies / becomming a MOTU?? [03:58] Tetracomm: FeatureFreeze was months ago. [03:58] Tetracomm: because there's a release in under a month? [03:58] suicideducky: The topic has a good link. [03:58] :( [03:58] Hobbsee: Shh, don't tell the users. [03:58] hahahaa thanks wgrant >.< [03:59] wgrant: oh. my bad. [03:59] I really want to see it packaged. [04:00] Could anyone recommend any software that would help me to create a .deb package? [04:01] There's no magic incantation that will do it. [04:01] !packagingguide [04:01] The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [04:01] There's the software. It runs on your brain :) [04:06] That takes too long. [04:07] Tetracomm: which is precisely why things don't get put into the release, so late, when people are focussing on existing bugs. [04:07] Ok. [04:09] I really want to help, but that looks so complicated, [04:09] . [05:28] jdong: Given the firefox propensity for security problems, I think you either ought to update it in gutsy-backports or remove it. [05:29] ScottK: agreed; I shall work on upgrading it over the weekend. === viviersf{Gone} is now known as viviersf [07:20] NCommander: too much love :) (even by error ^^) [07:21] morning :) [07:21] Hi didrocks [07:46] I have an interesting packaging bug with xorg-server (hardy). A patch (21_glx_align_fixes) modifies ./configure.ac, *but* ./configure is not rebuilt, and ./configure isn't patched to match. This causes a FTBFS for the xdmx module, so that in turn was disabled (debian/rules ... --disable-dmx) as the 'fix' - the real fix would be to either patch ./configure or ship the package with the regenerated ./configure. How should this kind of issue [07:46] be dealt with? [07:48] Also patch configure in the same patch by regenerating ./configure with the *same* autoconf version [07:49] StevenK: Thanks [07:49] regenerate configure, distribute as a patch. that's how the packages i work with do it [07:49] I thought that would be it, but it can get confusing, all the levels of indirection [07:55] 2nd question. In the package, it builds some dbus bits and includes but libdbus-1-dev installs to /usr/include/dbus-1.0/dbus/dbus.h - do all the source-files get patched or is a symlink supposed to have been created in /usr/include/ by libdbus-1-dev ? [07:57] Neither [07:58] A -I flag should be added to gcc calls by autoconf [07:59] ahhh good point :0 [08:01] and finally... 3rd question. The xorg-server source package, as shipped contains a whole bunch of symlinks, obviously accidently put there by some previous packager (e.g. GL/mesa/main/stencil.c -> /home/david/debian/xorg/git/lib/mesa/src/mesa/main/stencil.c) - should they be removed? [08:14] IntuitiveNipple: Nothing in base packages should either generate or depend on anything in /home, as I understand things. Cleaning that up is probably a good idea. [08:14] persia: yeah, that was my thought :) [08:15] IntuitiveNipple: that is probably david nusinow, one of the main debian xorg people [08:15] IntuitiveNipple: You'll be linking your git branch to a bug, and praising it's benefits in #ubuntu-x, right? [08:16] perisa: It *looks* like someone was experimenting, trying to fix the FTBFS for dmx - which is caused by the incorrect 21_glx_align_fix patch [08:16] Burgundavia: Yes, I thought that, having looked at changelog [08:16] persia: Will I? [08:17] #join #ubuntu-x [08:17] oops lol [08:17] IntuitiveNipple: I hope so. [08:17] IntuitiveNipple: Also, where did you stick your patch to get kvm compiling on lpia? I noticed it still FTBFS in the archives a couple days ago, and wanted to push that. [08:18] persia: you've lost me? what git branch?! I don't have the package git externally visible :) [08:18] persia: sheesh! Um, the source of kvm-74 in my PPA (one of the patches I think) [08:18] IntuitiveNipple: You're not basing your xorg-server stuff off the ubuntu git tree? I'll go find it. [08:18] Thanks. I'll see if I can extract it easily. [08:19] persia: let me look locally [08:19] IntuitiveNipple: Thanks. [08:19] persia: 1:72+dfsg-0ubuntu1~ppa4h "Fix: add debian/rules build capability for lpia and ia64" [08:20] persia: Inherited by 1:74 of course [08:21] Right. I'll try that against the current version in the archive. One of my lpia laptops strangely supports vmx, and I'll actually use it. [08:21] persia: If I recall correctly, I added " QEMU_EXE = qemu-system-x86_64" to each of the lpia and ia64 cases [08:21] Looks like the git tree is git://git.debian.org/git/pkg-xorg/xserver/xorg-server : I'm not sure how the Ubuntu branch is stored. [08:22] IntuitiveNipple: Hrm. lpia isn't 64-bit. I'll try that, and in the worst case, try shifting it to x86. [08:22] persia: oh, yeah. I saw the 'packaging' git reference but I've been working on the apt-get source package [08:22] persia: No, there are two cases... the statement is added into both [08:22] Yeah, the apt-get source is a little out of date for X, as X moves pretty quick. [08:22] persia: It doesn't do what it suggests... hence my original confusion when it first came up [08:23] Oh, so x86_64 doesn't actually mean x86_64? [08:23] persia: strangely... no lol - it is just, if I recall correctly, a build dir or something similarly transient [08:24] persia: The build-logs on my PPA will reveal how it is used [08:24] heh. Right. Well, when we last talked about it, my only lpia kit didn't support vmx, but Intel seems to have lost sight of the "L" in lpia, so I've a testbed now. [08:25] (well, it's still low-wattage, but it's dual-core with vmx, which doesn't strike me as trying to save every last joule) [08:25] Power Intel Architecture! [08:28] persia: re xorg-server: hardy ships all the xdmx tools but not the module since it was FTBFS (the ./configure not patched issue), so I'm just fixing it so it will provide the xdmx module (1 or 2 other knock-on effects I'm chasing too). [08:28] I don't suppose you could do that for intrepid? It's more likely to be easy to apply, and more likely to be beneficial to more people. [08:31] persia: It looks as if 1.5.1 (Intrepid) has it fixed [08:31] Oh, cool. No worries then. [08:31] Thanks for checking. [08:31] persia: at least, it has --enable-dmx in debian/rules and I assume it isn't FTBFS [08:31] You'd have to check build logs to verify, but I think someone would notice. [08:32] persia: package xdmx is in universe [08:32] Excellent then :) [08:33] I've been using the Intrepid package as a clue-stick to sort out the hardy 'mess' :) [08:33] persia: xdmx is allowing me to run 5 monitors on the laptop :p [08:37] IntuitiveNipple: USB<->VGA ? [08:38] persia: DFT, VGA, s-video (projector), and xdmx to a dual-matrox 'twinview' [08:38] And the rest of the dual-matrox is just a headless server? [08:39] persia: no, with xdmx the remote xserver becomes an extension of the local desktop [08:40] Right, but I'm guessing the remote computer running the xserver also becomes effectively headless, doesn't it? [08:40] once i'd built the module and got the configuration sorted, I wanted to get the package to build too, so others can use it [08:40] (because it's granted access to the xserver to the remote session) [08:41] persia: oh, I see what you mean... well, it seems there are several ways it can be done, both with the remote logged in, or logging in remotely. right now I've got 'dual-control' [08:41] Ah, so the xserver provides access for both the remote box and a local session? [08:44] Until you mentioned it, I'd not really thought about it! I was just pleased when I finally got it to work :) [08:44] I'll write up a wiki article on it once I'm clear :) [08:47] IntuitiveNipple: Thanks. Now you just have to find a minion who will mine your wiki for all the good bits :) [08:49] persia: It's called 'Google' :) [08:49] and, there's only 'good' bits on my wiki! [08:50] IntuitiveNipple: Well, I'd say 80% : you move quickly enough that there's sure to be a fair bit of bitrot. [08:51] And my only issue with Google is that it doesn't have the patience to push the patches back to Debian and upstream :) [08:52] it's only a matter of time :) [08:53] heh. I suppose. [08:54] funny you should mention that, actually. with the thread on the -devel mailing list I was working out an AI-based upstream patch submitter... give it a couple of 'best practice' bugs to to follow and then it'll figure it out for new bugs that have Ubuntu patches [08:55] \sh: around? [08:55] Nifty. That would certainly solve some of the Ubuntu patch discussions, and probably be of inestimable value to you in not having to forward-port stuff. [09:30] How do I package a program that is distributed in multiple source files? [09:31] volkris: In multiple source packages. [09:32] For example, consider a game that has separate upstream releases for the server, the artwork, the engine, the module, and the sound server. [09:32] This would be 5 different source packages, and probably 7-8 binary packages, depending on the contents of the source packages, and how they should be installed. [09:33] In my example, you could then add new packages for other contributed scenarios or artwork, and it would still work. [09:33] can you think offhand of a package that does this? [09:34] uqm, uqm-content, uqm-voices, and uqm-music. [09:34] I'll read up. Thanks. [09:34] That's multiverse, but it's the package like that I've touched the most. [10:42] DktrKranz: what do you think about bug 275502 ? [10:42] Launchpad bug 275502 in mail-notification "Make mail fetchers recommended instead of suggested" [Undecided,Confirmed] https://launchpad.net/bugs/275502 [11:18] hello, I've followed https://wiki.ubuntu.com/PackagingGuide/HandsOn and I succesfully build a newer version of a package (sympa). dumb question: where is it? debuild -S -sa completed succesfully but I don't see the deb... [11:19] debuild -S is for building source packages [11:19] es: You've successfully built an updated source package. Congratulations. To convert that into a binary package, you'll need to build it. [11:19] look for .dsc and .diff.gz in the parent directory [11:19] Personally I use sbuild, for that, but many people use pbuilder. [11:19] !sbuild [11:19] sbuild is a system to easily build packages in a clean schroot environment. To get started with SBuild, see https://help.ubuntu.com/community/SbuildLVMHowto [11:19] !pbuilder [11:19] pbuilder is a system to easily build packages in a clean chroot environment. To get started with PBuilder, see http://wiki.ubuntu.com/PbuilderHowto [11:20] thanks I'm looking to those links [11:29] Do we have any xorg-server build experts ? [11:33] They tend to live in #ubuntu-devel, xorg-server being fairly core. [11:35] In the package I'm working on I need to extract one tarball of makefiles and such, then another tarball of code that goes into the src/ subdirectory of the first. [11:35] I don't know that this is the situation persia had in mind when he said to distribute separate source pacakges [11:36] The result of the compilation is basically a single executable file, but I don't know how to handle .orig files and such [11:36] does anyone have a clue what the fix for the build problem in https://bugs.launchpad.net/bugs/271919 might be? [11:36] Launchpad bug 271919 in firebird2.1 "Sync firebird2.1 2.1.1.17910-release.ds1-1from debian experimental" [Wishlist,New] [11:37] volkris: Ah. I thought of separate sources that weren't so intertwined. No good suggestions for that : maybe a fiendishly compliex get-orig-source, or some sort of stacked tarball-in-tarball solution? [11:37] I figured some other package somewhere would have dealt with this matter before [11:38] I've packaged on gentoo pretty regularly, and they have ways of extracting to specific places in the source tree [11:38] Could repackaging end up being reasonable in this case? [11:39] volkris: That sounds like the only option, really. [11:39] Maybe, although I'd personally prefer to see layered tarball-in-tarball, as much as I generally dislike that format. repacking breaks md5sum verification against upstream. [11:39] Something in source package format 3.0 might support you more, but nothing accepts it yet. [11:39] RAOF: No. There remain many options, just none pretty. [11:40] is unpacking of tarball in tarball handled through get-orig-source? [11:40] james_w: You might catch NCommander later : seems to be handy with the libtool change. [11:40] volkris: No. get-orig-source would construct your tarball-in-tarball orig.tar.gz. [11:40] I'll look into it [11:41] Then you need to add extra targets in debian/rules to unpack the tarballs in the right way, usually into a ./build/ directory defined in the diff.gz. [11:41] anyone on bug 275502? [11:41] Launchpad bug 275502 in mail-notification "Make mail fetchers recommended instead of suggested" [Undecided,Confirmed] https://launchpad.net/bugs/275502 [11:41] volkris: Be prepared for someone to complain about tarball-in-tarball, but it's slightly less distasteful than repacking. [11:42] This is pretty specialized software for running particle accelerators, so I probably won't worry too much about distribution outside of the lab [11:43] volkris: Perhaps, but I'll encourage you to share it : other labs might find it useful, and I'd guess that having a somewhat standard system would let you actually focus on the problem, rather than managing particle accellerator drivers. [11:44] (plus I want to be able to say "Here's an Ubuntu disk. It gets used for lots of things. It can even run your particle accellerator") [11:44] ha. Well, PPA at least [11:45] Well, PPA for now. Come back in December, and we'll get it in the distro properl. === jscinoz_ is now known as jscinoz === stefanlsd_ is now known as stefanlsd === enyc_ is now known as enyc [13:29] james_w: well, we have to decide if we want an ipe that can handle *normal* ipe files or ubuntu ones :( [13:29] sebner: yeah, it sucks [13:29] I think it's partly the programs fault for using symbolic names in the files [13:30] james_w: ^^, the problem is we started patching ipe with feisty IIRC :\ [13:31] james_w: however, thx for you work :) [13:31] no problem [13:33] james_w: now you are a sponsor of mine :P [13:35] I'm trying to copy a package in my PPA from hardy to intrepid, and I get "The following source cannot be copied: sugar-artwork 0.82.0-1ubuntu1~ppa1 in hardy (same version already has published binaries in the destination archive)" - even though it doesn't exist for intrepid yet. [13:35] How can I see which packages provide an alternative via update-alternatives? [13:42] morgs: PPA questions should be directed to #launchpad. [13:42] ScottK: thanks === thunderstruck is now known as gnomefreak [14:20] persia, geser, soren, nixternal: what's the status of apachelogger's core-dev application? [14:20] * persia checks [14:31] Riddell: Waiting for more review and comments at this point, from the archives. [14:31] huh? I suspect it's had all it's going to get [14:32] I hope not. It needs more input from MC members to get anywhere : it's essentially stuck in limbo right now. [14:33] I think all the sponsors have commented. [14:33] then this process isn't working. if MC is blocking new members it needs to sort itself out or we'll just have to work around it [14:35] I agree the process isn't working. I agree that sorting it makes sense. I think that aside from ArchiveReorganisation, it's not best to work around it. I have opinions about why it doesn't work, but no real understanding. [14:39] * sebner missed the MOTU meeting. did anything special happen? [14:41] sebner: Nobody appears to have attended, or expressed anything. There was no agenda. [14:41] hiya [14:41] persia: kk, thx [14:41] aloha RainCT :) [14:58] Heya gang [15:00] persia, geser, soren: concerning apachelogger's core-dev app, I have already commented and voted [15:01] nixternal: Indeed. In the very beginning of september. [15:01] jeesh, that long ago....what is the hold up? [15:02] The process seems broken. [15:03] slightly [15:04] I don't like the fact we are hung up on apachelogger when Kubuntu really needs him, especially with me being afk so much and not being able to package [15:04] or sponsor his work [15:28] okay, the ffmpeg unstripped version actually seem to work. cool [15:30] siretart: encoding junkies everywhere rejoice :) [15:32] jdong: I just have had an tester next to me. it works with the packages from ~motumedia [15:33] jdong: I'm seriously considering to upload them to ubuntu right now [15:33] jdong: input welcome :) [15:34] siretart: you know, that would solve a lot of the grievances out there but what about the encumberance issues? [15:34] it would also resolve the medibuntu-ubuntu off-sync every time we do a ffmpeg update [15:35] jdong: I think it makes the medibuntu ffmpeg package obsolete [15:36] siretart: agreed. which would be a good thing for both teams [15:36] siretart: and right now we're already half-hypocritical shipping the mpeg4-ASP encoder on by default [15:36] and hell decoding of mpeg4 is already "encumbered" so honestly I think we should just ship it all... [15:36] the question is whether it'd go into restricted or main... [15:38] siretart: how well does it coexist with gstreamer and friends? [15:38] jdong: it would go to multiverse [15:39] jdong: as for gstreamer and friends: it conflict/replaces libavcodec51. [15:39] siretart: sounds reasonable [15:39] I think it'd be a good thing to have [15:39] and I don't think any problems with archive since we've already got implementations of ALL of those encoders in other packages in multiverse [15:40] exactly [15:41] yeah I'd say just do it [15:42] but given the mdz conversation in #u-d... I'd like to hear his response [15:42] siretart: so the only stuff remaining for medibuntu would be amr I guess (since libamr* is currently unredistribuable :]) [15:43] mr_pouit: yes, and I have even for that I have a solution or at least an idea how to fix that [15:43] dlopen()? [15:44] if you "magically" supply a libamr, ffmpeg-evil will find it :D [15:44] norsetto: sugar install and build logs available - see bug 274820. [15:44] Launchpad bug 274820 in sugar "Sugar feature freeze exception" [Undecided,Incomplete] https://launchpad.net/bugs/274820 [15:44] exactly. the altlinux folks have a patch for that [15:44] that way ubuntu's ffmpeg could dlopen() medibuntu's libamr libraries [15:45] mr_pouit: please do have a look at the 'ffmpeg' source package in the ~motumedia PPA [15:45] patches welcome, everything is in PPA under ~motumedia/ffmpeg [15:46] patches welcome, everything is in bzr under ~motumedia/ffmpeg [15:52] ok [16:02] morgs: thanks. Did you check if there is any issue with upgrading? [16:03] norsetto: no, I didn't check, but we will need some slight changes from the debian packages to handle two packages which are renamed: sugar-base -> python-sugar, and sugar-datastore -> python-olpc-datastore [16:04] morgs: right [16:04] morgs: I have no problem to ack this, if you could make sure that upgrades are fine that would be sweet [16:05] YokoZar: you dropping by for UDS/Fosscamp? I see you're basically local [16:05] norsetto: I have a personal interest in making them work, being an upstream dev, so yeah :) [16:05] morgs: I bet ;-) [16:12] sebner: have you seen bug 269301 ? [16:12] Launchpad bug 269301 in wordpress "[CVE-2008-3747] - wordpress before 2.6.1 ssl problem might allow remote attackers to gain administrative access by sniffing the network for a cookie" [Undecided,Won't fix] https://launchpad.net/bugs/269301 [17:06] how is it possible to get a package in the repo's updated to the current version? [17:16] hi folks [17:27] hey sistpoty [17:27] hi siretart [17:29] sistpoty: do you have plans for this weekend? http://lusc.de/ww :) [17:32] siretart: hm... I do have some plans for the weekend already :/ [17:35] superm1: Have you checked latest comment on the bluez 4.x bug? LOL. [17:38] slytherin, lets see. [17:38] Hi [17:40] slytherin, well I would hypothesize that those segfaults are probably null pointer checks, but we'll have to wait for a backtrace [17:40] the important part is whether these are "regressions" :) [17:41] slytherin, would you be able to craft a patch to make tooltips on the icons possibly? [17:41] i'm working on a patch to properly set input devices to trusted mode [17:46] superm1: 1. I will be able to provide tooltips. I will have to check what is the current GTK+ requirement for bluez-gnome. If it >= 2.12 then our life is easier. [17:47] slytherin, well we can easily bump the GTK requirement up if necessary [17:47] slytherin, it's very highly unlikely we'll backport this since it only works with bluez 4.x [17:48] superm1: Ideally shouldn't we ask upstream to fix the tooltip problem? [17:50] slytherin, well we can fix it and submit the patch upstream [17:50] slytherin, they've got very few developers, so it would be fixed a lot quicker that way [17:51] superm1: Ok. Will do tomorrow. [17:51] slytherin, okay great [18:11] superm1: by the way, by latest comment I meant the one by Christoph Langner [18:18] Hi. If upstream doesn't provide an icon for the app, can I package it without menu entry? Or I should use a generic icon? [18:18] (for bug #272210) [18:18] Launchpad bug 272210 in ubuntu "Megatunix needs to be packaged and added to the repository." [Wishlist,Confirmed] https://launchpad.net/bugs/272210 [18:28] fabrice_sp_, [18:28] are you abloe to test megatunix? [18:29] *able [18:29] I was origannly going to package megatunix per a user request but thought i best not when i realised i had no way to really test it [18:29] *originally [18:38] jcastro: Yeah, not much need for sponsorship this year. I can probably crash at a friend's house. [18:39] jcastro: which is lucky for you, as Wine will be in Main for Jaunty. [18:40] I'm new to the ubuntu way of building package, pbuilder fails because the new upstream package has a new directory previusly not present. I specified it to debian/dirs without success, also there path looks weird they go in var/lib/something instead of usr/lib/something of the previously installed package. [18:41] any advice?' [18:42] YokoZar: ok, I was thinking we should invite dan kegel since he's @ google also [18:43] es: if you give the failure message then it may be easier to see what is going on [18:44] james_w: sure thanks:) cp icons/*.png /usr/lib/sympa/static_content/iconscp: target `/usr/lib/sympa/static_content/icons' is not a directorymake[2]: *** [installicons] Error 1 [18:45] var/lib/sympa/static_content/iconsusr/lib/sympa/static_content/icons [18:45] these are specified in dirs [18:46] es: is the cp command in debian/rules? [18:47] yes it's in configure options: --with-iconsdir=/usr/share/sympa/icons [18:47] es: the "cp icons/*.png", is that in debian/rules? [18:47] no [18:48] es: is it in a Makefile? [18:49] no I made a grep -R and I can't find it :/ [18:49] es: can you put the build log in a pastebin please? [18:50] james_w: sure, thanks for your help but err where are the logs usually? [18:51] es: you will have to build again with --logfile, or grab them from the scrollback in your terminal [18:56] james_w: weird the logfile is not created I pasted from the terminal http://pastebin.myrror.net/1938 [18:56] james_w: thanks again for your help :) [18:57] es: so it appears to be the wwsympa directory that has the problematic command [18:58] es: can you pastebin the Makefile from that directory please? [18:59] james_w: http://pastebin.myrror.net/1939 [18:59] line 102 [19:01] es: ah, should have spotted that [19:02] *I* should have spotted that [19:02] es: it's not using $DESTDIR [19:02] ahh! [19:02] es: so it's trying to install in to the real /usr, rather than ./debian/.../usr/ [19:04] yep! so it should be $(DESTDIR)/static_content/icons ? [19:09] es: no, it should be $(DESTDIR)$(DIR)/static_content/icons I think [19:12] * sistpoty is off again... cya [19:13] james_w: yeah, we passed that error! now: cp sympa_soap_server-wrapper.fcgi /tmp/buildd/sympa-5.4.3/debian/sympa/usr/lib/cgi-bin/sympa/cp: cannot stat `sympa_soap_server-wrapper.fcgi': No such file or directory [19:13] guess it's the same problem [19:15] wwsympa-wrapper.fcgi: wwsympa-wrapper.fcgi.c Makefile ../Makefile $(CC) $(CFLAGS) -DWWSYMPA=\"$(WWSYMPA)\" -o wwsympa-wrapper.fcgi wwsympa-wrapper.fcgi.c [19:15] I think that's a different problem [19:15] err no it's another line [19:16] it can't find sympa_soap_server-wrapper.fcgi, does it ever build it? [19:16] james_w: where should I check out? [19:21] james_w: actually I don't see it in the logs [19:22] is it mentioned anywhere else in the Makefiles? [19:24] james_w: nope [19:25] cd sympa-5.4.3/wwsympa && grep sympa_soap_server-wrapper.fcgi Makefile -> none [19:27] csilk: I assume that the user requesting the packaging will be able to test it (I'll put it in my ppa meanwhile). Anyway, I'm able to do some things. [19:28] james_w: it's in soap/Makefile [19:31] fabrice_sp_, that's the only thing that stopped me form packaging it really [19:32] *from [19:32] csilk: apart from a compilation error because of gcc4.3 and the missing icons, it's an easy package. [19:32] If you wan't, you can still package it [19:32] s/wan't/want/ === fabrice_sp_ is now known as fabrice_sp [19:34] Hey, is there any way if I have to make a lot of debian sync requests (we already have FFEs for them) to do it in _one_ bug? [19:35] james_w: well, thanks for your help, tomorrow I'll look into it better. I'm hungry and I my mind isn't working anymore as you can see :) [19:35] fabrice_sp, I wouldn't mind packaging it to be honest, I've been trying to get involved with ubuntu for a while now but it's hard managing a heavy load at university etc etc [19:36] but if you wouldn't mind assiging the bug/request to me I'd love to do it [19:36] *assigning [19:37] lfaraone: can't you just add the missing info for the sync to the FFE bugs? that way all infomation is in one place [19:37] geser: It's one FFE bug. [19:37] csilk: all your's. If you have problem, you can ping me here (if I am online) [19:38] Thanks fabrice_sp [19:38] lfaraone: have you the bug number handy? [19:39] geser: No, but it's against the "sugar" pacakge [19:43] I've found it (bug 274820) [19:43] Launchpad bug 274820 in sugar "Sugar feature freeze exception" [Undecided,Confirmed] https://launchpad.net/bugs/274820 [19:44] lfaraone: how many package are affected? [19:49] doko: Do you plan to fix bug #254368 in intrepid? or is it deferred? [19:49] Launchpad bug 254368 in openjdk "openjdk-6-jdk should depend on libxt-dev" [Low,Triaged] https://launchpad.net/bugs/254368 [19:52] anyone willing to test DVD playback fixes in gstreamer backported form upstream CVS? I am waiting for some feedback before I can submit the debdiff. [20:04] siretart: You around by any chance? [20:19] heya [20:20] Hello emgent === RoAk is now known as RoAkSoAx [20:26] Hey bddebian and congrats! [20:27] Hi iulian, thanks [20:30] Gads, how the heck do you folks use LP anymore? I've obviously been waaay too out of touch lately [20:37] geser: https://wiki.ubuntu.com/SugarTeam/Packages has a list [20:52] bddebian: yes, a bit afk (lug event), but sort-of [20:55] siretart: Any idea what to do about xine-lib in Debian for Lenny? [21:07] anybody have an opinion on bug 275502? [21:07] Launchpad bug 275502 in mail-notification "Make mail fetchers recommended instead of suggested" [Undecided,Confirmed] https://launchpad.net/bugs/275502 [21:09] * cody-somerville takes a look. [21:11] james_w: do you know how common are hotmail/yahoo accounts inside and outside the USA? [21:12] pretty common I believe [21:13] james_w: if you are trying to sponsor it, please don't, see my comment [21:13] james_w: i don't want to have all of those packages i don't need in my system if i'm only using one of them [21:14] nxvl: thanks [21:14] james_w: also i don't have that much experience with that package/tool but from the comments/report i get that you need at least one of them for the tool to work, but all of them is crazy [21:15] thatfor it will be | instead of , if you want to make the change anyway [21:15] i will suggest to talk to the DM better [21:15] I use mail-notification but with mutt and I don't need either of those packages [21:16] They are common, but I don't think they'd rise to needed except in unsual situations (which is the 'recommends' definition). [21:16] I get the impression the tool isn't very good at hinting that you could install other packages to get the functionality [21:17] Suggests is how the package should do that, but it helps if the program does as well [21:18] I could understand to add m-n-evolution to recommends (as evo is the default mua), but I don't know about getlive and fetchyahoo (it would be for me easier to accepts something for googlemail) [21:18] I think gmail is still far smaller in overall usage [21:18] geser: that's why using "m-n-evolution | getlive | fetchyahoo" will be better, by default it will grab m-n-evolution [21:19] james_w: don;t bet [21:19] nxvl: but that doesn't bring any benefit over Suggests, so it's not worth it in my opinion [21:20] is it working with the current version of evo? [21:20] james_w: actually there is some apt option to install suggest by default [21:20] james_w: but yes, i agree with you on that [21:21] Is there atleast one fetcher module thingie installed by default? [21:21] james_w: i'm saying if it will be raised to Recommends, that is the way it should be rised [21:40] bddebian: ? [21:40] too bad, he already left === nm-rocker is now known as asac [21:48] ScottK, ping [21:49] or anyone else from motu-release [21:50] cody-somerville: yes? [21:50] norsetto, bug #262156 [21:50] Launchpad bug 262156 in envyng-gtk "envynggtk.py crashed with ImportError in ()" [Critical,In progress] https://launchpad.net/bugs/262156 [21:50] cody-somerville: yes? [21:51] motu-release I imagine should be responsible for ensuring that gets fixed or envyng gets removed from the archive. [21:52] cody-somerville: indeed, see bug 277126 [21:52] Launchpad bug 277126 in envyng-core "Update EnvyNG to 2.0.1" [Medium,Triaged] https://launchpad.net/bugs/277126 [21:55] ok, thanks [21:55] cody-somerville: np [22:03] norsetto: you making ad for your ppa? nice :) [22:04] sebner: yes, I'd like to provide 0.8.0 to intrepid users [22:04] norsetto: nice :) [22:05] sebner: next version is also coming out pretty nice [22:05] norsetto: ^^, in time for jaunty? [22:05] sebner: absolutely [22:06] norsetto: great to hear :) [22:45] lfaraone: hi, do you have a blanket FFe for the sugar sync requests? [22:46] james_w: They do. [22:47] ScottK: thanks [23:13] james_w: Yes. [23:45] why does the wiki (packaging) not discuss what to do with all the extra files in /debian such as init.d.ex and all the manpage related files? [23:45] etc [23:47] csilk: They are example files. If you need them, you rename them (remove the .ex suffix). If you don't need them, you just delete them. [23:48] nhandler_, I'm not 100% sure what they are to be honest [23:50] csilk: For most basic packages, you can safely remove the files. What are you packaging? Or what type of application is it? [23:52] an app called megatunix, it's a software utility for measuring variious things within a combustion engine [23:52]