[00:08] <__iron> hi [00:11] <__iron> folks i m interessed to develop [00:16] hi __iron, I'd suggest you to ask specific questions. [00:21] <__iron> tacone: i know its a meta-question [00:21] <__iron> but i will work who i can useful [00:21] <__iron> -who +where [00:22] I am still missing the point. [00:22] are you asking what you can do ? [00:23] <__iron> the point i'm just a student with c and c++ experience who want help where he can help [00:25] I am not a motu myself, anyway: here are some bugs that needs to be corrected http://daniel.holba.ch/harvest/ . if you don't know anything about packaging you may want to read https://wiki.ubuntu.com/MOTU/GettingStarted to find your way out. [00:25] <__iron> k thx [00:26] that's scaring at first, but when you are stuck you could just come back here to ask your questions. [00:28] <__iron> k ty [00:28] np [00:41] <__iron> tacone: how can i get a mentor ? === asac_ is now known as asac [01:10] __iron: you should request it on the motu mailing list. [01:10] __iron: beware there's quite a queue usually to get a mentor. so one has to wait for some time [01:12] <__iron> i ll try the mailing list [01:13] <__iron> ty [01:17] <__iron> now i'm a mailing list user [01:17] <__iron> *g* [01:35] :-) [01:44] __iron: please see https://edge.launchpad.net/~motu-mentoring-reception [01:47] <__iron> thx: emgent [01:48] __iron: np, the best anyway is mail norsetto@ubuntu.com (for ask mentoring) [01:51] <__iron> emgent: what could be the best way ? [01:52] https://wiki.ubuntu.com/MOTU/Mentoring [01:56] <__iron> k ty [03:20] hello everybody [04:38] Anyone around? [04:40] JDCarroll: 184 of us. [04:40] is it possible to have a chroot of another distro on ubuntu? eg a chroot of fedora in hardy [04:41] Toma-: Sure, although you may not find many tools to automate setting it up. [04:41] hm ok [04:41] Toma-: You might do better with a virtual machine. [04:42] yeh i think i might be [06:46] :( [06:52] ? [06:54] persia, sistpoty and ajmitch expired from Ubuntu members today. [06:56] cody-somerville: Yes, but they continue to retain that membership indirectly. It is just an accounting issue. [06:56] Ah, I hadn't looked [06:56] Good to hear :] [06:57] persia, I'm working what we talked about [06:57] :) [06:57] Sorry for the delay, I got caught at a nice big working house fire :-P [06:58] * NCommander is smoldering [06:58] Ugh. That's not ideal. [06:58] Part of the job of being a firefighter [06:59] I did get to throw a table through a window [06:59] :-) [06:59] Oh. That's not so bad then :) It was the "caught" and "smouldering" that didn't sound ideal, but tables make an effective means of arranging egress. [07:00] Mindless destruction: Good for the soul ;-) [07:00] With bonus fire. [07:01] had a couple WTFs with our water supply [07:01] And I got stuck on cat detial [07:01] Freaking owners had 10 cats [07:01] Four were deepfried, one went ballistic on my parnter and animal control caught the rest === superm1|away is now known as superm1 [07:03] Deepfried... nice [07:03] *creepy voice* now i'm hungry! [07:04] KFC - Kentucky Fried Cats [07:07] how can buildd not find procps [07:07] nxvl: Out of date apt-cache maybe? Perhaps a result of a recent upload? [07:08] persia: but it's a required package [07:08] nxvl: Hrm. Go ask a buildd admin then . [07:09] yep [07:09] also it's a problem just in i386 [07:09] i will try i given-back tomorrow to check if it was a temporal issue [07:09] "required" != "essential", fwiw [07:09] and then ping a buildd admin [07:09] slangasek: right! [07:10] although the definition of "required" is supposed to be "things apt and dpkg depend on", it appears the package manager doesn't actually misses procps if you remove it? :) [07:10] s/misses/miss/ [07:11] evening slangasek [07:11] slangasek: so you suggest i better make the package depend on procps? [07:11] nxvl: yes [07:11] NCommander: 'lo [07:11] ok then [07:11] Well, build-depend. [07:12] persia: yes, that's i meant, sorry [07:12] slangasek, thank you for responding to the dropping architectures post on d-devel, its appreciated someone said something about it [07:13] nxvl: btw, are you any relation to the "Balcarce" whose name is plastered all over Mar del Plata? :) [07:13] slangasek: kind of [07:13] NCommander: sure [07:13] slangasek: at some point of the history the family splited out into peru and argentina [07:13] slangasek: and the name changed a bit in some points [07:13] * slangasek nods [07:14] slangasek: so i think that going back enought will bring us to a common point [07:17] slangasek: are you still at MdQ or already home? [07:31] nxvl: I had two Pisco Sour tonight, thought of you ;-) [07:32] :D [07:32] kirkland: where? [07:33] kirkland: you need to try Pisco Sour IN Peru, it's different [07:43] time to sleep [07:43] read you later [07:50] persia, bah, my laptop hung [07:51] That explains the information-rich nick :) [07:51] i dont think my work in progress saved [07:52] I really hope the graphical issues this machine having is kernel related and not *sigh* hardware related [08:14] Pro tip to upstreams: when your project is gnome-main-menu, don't include a file licensed under "the same license as the subdomain_parser package", particularly when the subdomain_parser package appears to be a part of a combined GPL/non-free program who's website NO LONGER EXISTS. [08:15] Question [08:15] WHo does the actual appointment to the -sru/-release teams in Launchpad? [08:15] (like who throws the magic switch) [08:18] Any administrator of those teams, I believe. [08:20] AAARGH. [08:21] RAOF, ? [08:21] NCommander: gnome-main-menu contains an unlicensed file. [08:22] Or, rather, it contains a file who's license is explicitly "the same as the subdomain_parser package". [08:22] -_-; [08:22] ow [08:22] Which may or may not be GPL. I don't know, because the company that produced that package appears to have died. [08:23] It's in a translation. They're still copyrighted, though. [08:26] RAOF: so, what to do in such cases ? [08:27] tacone: Well, my best guess as to the licence is that its proprietary. I'm going to strip the translation from the tarball, and file a bug upstream. [08:27] "SubDomain is distributed under two licenses: the kernel patches and the kernel module are distributed under the GPL, and the user-level portions of SubDomain are proprietary to Immunix, Inc." [08:28] RAOF: ok, thanks [08:40] persia, I'm growing convienced its a hardware issue with my machine [09:04] *sigh* [09:04] I'm not happy [09:22] my laptop crawls with jus ta single memory stick [09:27] if Ubuntu itrepid already has a latest upstream release packaged that isnt in Debian unstable, can I ask the debian maintainer to sync it from Ubuntu by rising a bug in debian BTS? Is it OK? [09:28] tuxmaniac: Well, Debian doesn't usually sync from Ubuntu (although there are exceptions). Given that Lenny releases in 30 days, I doubt that the Debian Maintainer wants to upgrade now. [09:29] persia:I didnt mean an automated sync. Just informing him that an upgraded package is present in Ubuntu? Yeah Lenny release is close. [09:29] persia, I'm not going to be able to finish working on the wik page tonight [09:29] I had a recent experience with that, and sent email to the development team list (team-maintained in Debian) reporting what work was required to get the new upstream to work with the Debian packaging: this was well received, but it was confirmed there were no plans to upgrade now. [09:29] I'm right now seeing if I can track down the hardware issue with my laptop [09:30] persia: 30 days. Hah. [09:30] NCommander: That's why tomorrow was invented. [09:30] DO you know a reliable way I can stress my video card out [09:30] I think VRAM is what's failing [09:30] wgrant: September 15th is the planned release day. [09:31] persia: Oh, they actually have a date now? [09:31] ooh, when did that happen [09:31] I thought it was still just September. [09:31] Like Etch was. [09:31] persia, can you repost the comments you gave me? [09:31] (I shut that machine down) [09:31] persia: Why I am so careful is the last time I did that by packaging the new release myself and attaching the .diff it was nt well received and it was considered package hijack. But when I cleared it out saying I am the upstream author and as over excited, then the flames settled. So alsways kind of careful :-) [09:32] s/as/was [09:32] tuxmaniac: Yes, being careful is best, and sending small patches and discussion is generally preferred to sending a diff.gz. [09:33] tuxmaniac: Also, if you are upstream, you want to develop fairly close communications with your Debian Maintainer, sharing information about bugs, fixes, etc. [09:39] http://asdfasdf.ethz.ch/~tar/bts/ [09:51] persia, bah, I think compiz was causing the crash, graphical effects got turned on max, and this laptops intel video card isn't fully supported it [09:54] Has anybody seen strip segfault before? [09:54] And that proved it [09:54] Enabled compiz froze my system nice and hard [09:54] wgrant, I've seen it do that on hurd ... [09:55] NCommander: This is on boring amd64 Linux. [09:55] wgrant, I'm running AMD64, I can take a look [09:55] Strip usually only crashs if your working with a malformed binary [09:57] I just hadn't seen it happen before. [09:58] (something FTBFSed because of it) [09:58] wgrant: On the buildds? strip acts special there. [09:59] persia: In the rebuild. [09:59] Ah, hrm. [10:00] So the compiz switch is not stinky ... [10:01] Cause it switched itself back to Extra after the last reboot [10:01] causing yet another crash [10:01] -_-; [10:01] hold on [10:05] well, now it seems "stable" [10:05] If it keeps doing it, I'll have to enable my nvidia graphics card, and use that piece of evil [10:44] wgrant: I think the package qantenna is not under the mOTu science teams purview. It would be great if you could subscribe that to our team so that we can keep track of the bugs and releases. Thanks in advance [10:54] tuxmaniac: Sure, subscribing. [10:57] wgrant: thanks [11:04] persia, remember when I said I fixed my crashing issue? [11:05] heh [11:11] Hi. I am looking at bug 207760. There is patch that fix a few issues submitted by the upsrteam author so that it is taken into the current versions in Ubuntu. Should I just apply the patch and generate a new .diff.gz to be taken for intrepid ? Ofcurse by applying the patch I meant debian/patches [11:11] Launchpad bug 207760 in geda-gnetlist "Broken VHDL and Verilog netlisting backends" [Undecided,New] https://launchpad.net/bugs/207760 [11:12] wgrant: you were the last uploader for that package and I guess might be in a better position to help === mcasadevall_ is now known as NCommander [11:18] Someone can take a look at http://revu.ubuntuwire.com/details.py?package=ircp-tray ? [12:05] asac: can you take a look at https://bugs.edge.launchpad.net/ubuntu/+source/xulrunner/+bug/254618 ? [12:05] Launchpad bug 254618 in xulrunner "Please update xulrunner to 1.8.1.16 version." [Undecided,Confirmed] [14:07] can package upgrades be done still? [14:08] evalles_: sure === evalles_ is now known as effie_jayx === Kopfi|offline is now known as Kopfgeldjaeger === PriceChild is now known as to === to is now known as PriceChild === bddebian2 is now known as bddebian [16:10] geser: do u mind if i work on merging showimg? [17:06] Does anyone know what has replaced xutils - E: showimg source: build-depends-on-obsolete-package build-depends: xutils? [17:12] nxvl: already back home [17:16] stefanlsd: A whole heap of stuff, as part of the modularisation of X. Which utilities do you need? [17:16] (and if you don't know, you might grab an old xutils from launchpad, and see what it provides) [17:25] persia: i am busy merging showimg from debian, and they have it there. How would i work out which piece of xutils showimg actually wants? [17:27] stefanlsd: That's the hard part :) [17:27] persia: hehe. [17:28] +Looking quickly at sid, it appears xutils is a transition package, depending on x11-xfs-utils, x11-utils, x11-xserver-utils, x11-session-utils, xfonts-utils, xutils-dev [17:28] You'll need to look at those, and at what the package needs, and update it. [17:38] hello all. I am not able to upload updated package to REVU since I changed my GPG key. can somebody help me? [17:38] persia: thanks. will remove xutils and try build then add those deps... [17:42] salutis: Did you update your GPG key in your Launchpad account? === Kopfgeldjaeger is now known as Kopfi|offline [17:44] ScottK-laptop: yes, I have 2 keys in launchpad - old key (revoked) and new key. uploading worked with old key, but it's currently revoked and new key seems to not work (sorry for my english) [17:45] ScottK: I'm reminded: about the documentation on the decision making process... [17:46] salutis: What is your LP ID? [17:49] persia: salutis [17:50] persia: Thanks. [17:50] persia: C60968A5 is old revoked key and B0298FA8 is new one which is not working [17:52] Hmm. The REVU keyring only has B0298FA8: C60968A5 doesn't appear. [17:52] I don't see anything in REJECTED. Which package did you upload? What error did you get? [17:54] persia: I received e-mail today at "Sat, 16 Aug 2008 16:25:09 -0000 (18:25 CEST)" with this message: "Rejected: Signer has no upload rights at all to this distribution.". I am trying upload 'thinkingrock' package [17:55] persia: dput finished with message - "Successfully uploaded packages." [17:55] salutis: I suspect you uploaded it somewhere other than REVU then, as REVU doesn't send such mail (or I don't think it does). [17:56] dput just sends stuff over ftp: that being successful has very little to do with whether you can upload. You can probably dput to Debian, but the package will be rejected. [17:57] persia: mail come from "Ubuntu Installer " and at the end of message is this text: "If you don't understand why your files were rejected, or if the [17:57] override file requires editing, please go to: http://answers.launchpad.net/soyuz". maybe I am doing anything wrong [17:57] Right, that would indicate an upload to the primary ubuntu archives, rather than to REVU. Please dput again, and be sure to specify REVU as the target. You may want to delete your .upload file to make this easy. [18:00] persia: upload with target 'revu' is in progress [18:00] persia: it takes some minutes. I will inform you [18:02] salutis: OK. [18:03] stefanlsd: I don't mind, go on with merging it [18:03] geser: thanks :) almost done i think. [18:06] persia: upload finished successfully, but on 'revu.ubuntuwire.com' isn't appeard till now [18:06] What happened to libkonq4-dev? I see my intrepid only has libkonq5-dev... [18:07] stefanlsd: looks like the soversion of libkonq increased [18:08] salutis: It can take a few minutes for the package to get accepted or rejected. That runs every 10 minutes. I'll watch to see if it gets rejected. [18:09] geser: mm. looks like that prefers kdelibs5 also. heh :) [18:10] looking more at it, libkonq4 was for kde 3.5 and libkonq5 is for kde 4. Does somebody know if KDE 3 is still in intrepid? [18:12] persia: it's uploaded successfully. persia, thank you very much for help! thanks, man [18:12] salutis: Your upload was successful. [18:17] persia: perfect! many thanks, persia [18:38] Anyone know anything about libkexif1-dev? It has a depends on kdelibs4-dev (>= 4:3.4.3-2) which prevents my update to showimg which wanted libkong4-dev (which no longer exists in intrepid - so moving to the kde4 stuff - libkonq5-dev) which means kdelibs5-dev... [18:39] I wonder if its easier to get libkonq4-dev back into intrepid... === Kopfi|offline is now known as Kopfgeldjaeger [19:21] good evening :) I have a simple question - I have uploaded my package in MOTU. Should I ask someone for review, or can I just wait for it and do nothing? [19:22] salutis: A link to the REVU page would be a away to get reviewers... linked. [19:39] jpds: sorry, I don't understand. can you explain it bit more? [19:40] salutis: Have you uploaded the package to http://revu.ubuntuwire.com ? [19:41] jpds: yes! [19:42] salutis: What is the package name? [19:43] jpds: thinkingrock [19:44] salutis: Providing a link to this channel like: http://revu.ubuntuwire.com/details.py?package=thinkingrock - would be a good idea. [19:44] jpds: so, it's now provided :) [19:45] jpds: and now I can only wait. right? (this is my first MOTU package, so I am new in this bussiness) [19:48] salutis: Explaining what the package is sometimes gets people interested in reviewing [20:06] Is there a quick way to update the po translations in a source package? The package has a template but the po files haven't been updated in several versions. [20:21] so I fixed what I can at: http://revu.ubuntuwire.com/details.py?package=thinkingrock. if there is something else for fix, leave a comment. thanks for reviews [21:54] I am trying to patch an application. The version in Debian is 0.9.4-1. Ubuntu has version 0.9.4-1build1. What version should I use for my edited version of 0.9.4-1buil1? 0.9.4-1buil2? 0.9.4-1ubuntu1? [21:55] ubuntu1 [21:58] I thought so, I just wanted to be sure since 'dch -i' sets the version to '0.9.4-1build2' === james_w is now known as james_w_ === james_w_ is now known as james_w [22:35] iirc, "build1" is used to force a rebuild of a (unmodified) package; used in both debian & ubuntu [22:35] so if there are now ubuntu changes, then it becomes a ubuntu1 package [22:41] Thanks directhex. The build1 version was an unmodified rebuild. I have used 0.9.4-1ubuntu1 as my version [22:52] That is the right way to do it. [22:53] ScottK: Just some hours I wanted to start with courier and what did I see? BAMMMMMMM [22:54] sebner: You are quite welcome to it. [22:54] ScottK: seems pretty finished to me :P Well, also other stuff todo ^^ [22:55] sebner: Finished except for the actually working part. [22:56] ScottK: working part? [22:57] We have a debdiff, but it doesn't build. [22:57] ScottK: Didn't notice [22:57] If you could figure it out, that's be lovely. [22:59] ScottK: I'll try but you know, I usually suck at making things build/fix stuff [22:59] You can't suck worse than me on this one so far. [23:00] ScottK: well I'll try to apply the debdiff :P [23:00] Thanks. [23:02] ScottK: but I feel bad. You know, before filing a sync bug we should check if we can fix anything but I discovered that I can't fix anything (several times). this made me depressed and led me mass-filing sync bugs(20 xD) :( [23:02] ScottK: from the RC bug list though [23:02] Right. [23:04] ScottK: debdiff applies without problems, btw [23:04] It'll build fine for a long time too and then get to maildrop and die. [23:05] ScottK: I'll start a testbuild [23:05] hi at all [23:05] someone can review this package? http://revu.ubuntuwire.com/details.py?package=ircp-tray [23:05] good evening DnaX [23:07] jpds: in italy it's night ;) [23:08] DnaX: Yep, and I'm about to head off to bed. [23:08] * sebner too [23:09] understand.... [23:10] DnaX: Austria \o/ [23:10] sebner: XD [23:11] so, for that package? [23:11] DnaX: I'm no motu :P [23:13] uhm... someone else? === zwanzigcent_ is now known as zwanzigcent [23:19] ScottK: ping [23:19] Png [23:19] Pong even [23:20] ScottK: there is a problem (or more) with maildrop but it dies later for me with: [23:20] [ ! -f Makefile ] ||-/usr/bin/make clean [23:20] /bin/sh: -/usr/bin/make: not found [23:20] make: *** [clean] Error 127 [23:20] It looks like it needs relibtoolizing. [23:20] jpds can tell you how much fun that is. [23:21] ... pain... [23:22] Perhaps the rule used to be “-$(MAKE) clean” (make clean, ignoring the return value) and someone added the [ ] test in front of it, mistakenly moving the dash along with the rest of the line. [23:23] debian/rules says: [ ! -f Makefile ] ||-$(MAKE) clean [23:24] Make it -[ -f Makefile ] && $(MAKE) clean [23:25] I don’t really see the value of the [ ] test in the first place, but whatever. [23:26] I’d just use -$(MAKE) clean [23:26] well it should be [23:26] [ ! -f Makefile ] || $(MAKE) distclean [23:26] ScottK: can the "-" be the bad thing? [23:26] sebner: "/usr/bin/make: not found" ? [23:26] It is the bad thing, when it is in the wrong place. It should be the first character of the line. [23:28] ion_: not necessarly. http://lintian.debian.org/tags/debian-rules-ignores-make-clean-error.html [23:28] Hm, now that i think of it, that test actually has *some* value: in case Makefile exists and distclean fails, the clean rule fails. [23:28] jpds: cool, hmm? [23:28] Yeah, agreed. [23:29] * sebner is testbuilding again === emgent is now known as emgent` === emgent` is now known as emgent [23:40] \o/ [23:45] ScottK: well, now it dies at maildrop as you said ^^ [23:46] That's where libtool comes in. [23:47] right [23:47] libtool can't find anything [23:47] command not found [23:47] , bla bla bla [23:50] Are there some by-rule-of-thumb-guidelines when asking for becoming an Ubuntu member is not too awkward? [23:50] ScottK: maybe we should ask the debian maintainer for help? :P :P :P [23:50] hello there [23:51] emgent: \o/ [23:51] heya sebner :) [23:52] Kopfgeldjaeger, hi, I'm not sure what you mean, could you expand please? [23:53] Kopfgeldjaeger: ubuntu universe contributor? [23:54] james_w: Well. I think Ubuntu membership is really interesting, but I am not sure if I already really have made a "significant and sustained contribution to Ubuntu and the Ubuntu community"... sebner: Ubuntu Membership [23:54] I guess rather not yet [23:56] Kopfgeldjaeger: depending on what you've done so far [23:56] Kopfgeldjaeger, you could read the logs of a membership meeting to see what other applicants have [23:56] james_w: good idea [23:58] sebner: Well, so far at least one new universe package, 1 main merge, 4 universe merges, i translated the rhythmbox doc (upstream) and am quite active in the german ubuntu community... But I hope I can make many more merges for ubuntu+2 [23:59] I guess that's not really much yet, so I asked what could be a good first aim