=== asac_ is now known as asac === agrajag| is now known as Agrajag === nigel_nb is now known as nigel_nb_ === nigel_nb_ is now known as nigel_nb === ripps|sleep is now known as ripps [04:15] micahg, did you get the sru ack, and did you subscribed u-u-s for your SRU? [04:35] fabrice_sp: I thought it was already subscribed...let me check [04:35] ack jdong has been pummeled by schoolwork this past week.... [04:36] if anyone has urgent SRU requests please feel free to kick me repeatedly in IRC until I respond. [04:36] fabrice_sp: yes, u-u-s is subscribed [04:36] micahg, bug number? [04:36] bug 477513 [04:36] Launchpad bug 477513 in uim "FireFox crashes routinely karmic i386" [High,Fix released] https://launchpad.net/bugs/477513 [04:36] hey jdong is back :-) [04:36] aaaah! [04:37] "back" but shhhhh don't tell anyone [04:37] jdong: I still don't have a test case though [04:37] lol [04:37] all I know is that it crashes after some time of use for some people [04:37] heh I'd really love to have a testcase, but for some kinds of bugs that's really all you can get. [04:37] jdong: my other sru has a test cae [04:37] considering the patch looks correct and reasonable to me, I've got no objections [04:45] micahg, do you plan to work on the merge/sync of 1.5.7 from Debian? [04:46] fabrice_sp: I can if you want [04:47] it would be nice, but it's as you want [04:47] as you already knows the pacakge, it would easier for than for another [04:49] but I can take care of it, anyway :-D [05:05] fabrice_sp: I only added a patch from upstream :) [05:06] Ohh: I saw you was subscribed to the bug report. I thought you had a special interest in it :-) [05:06] np :-D [05:06] fabrice_sp: only because it causes firefox problems :) [05:07] limited interest, then :-D [05:07] yes [05:42] install -m 755 -t debian/pkgname/usr/bin debian/somefile ; this will install somefile in the target dir specified by the -t option right? [05:45] What is it about the debuild environment that causes warnings about not checking return values of read() and write() and turns them into errors? I have a package (written in C++) I can build only with a large patchset to check all these calls... but a manual build from the unpacked upstream tarball does not have this issue. [05:48] guys why is this install format not working? http://pastie.org/726993 [05:50] jmarsden, it's about the compilation flags that has been hardened in Ubuntu [05:50] fabrice_sp: OK... is there a Wiki page explaining this... esp how to get a non-Ubuntu machine to generate the same set of warnings? [05:50] this warning should be fixed [05:50] hmmm, you could grab the log and see the options [05:51] fabrice_sp: I know, but upstream doesn't want to accept my patchset, and right now they do not even see the warnings ... [05:51] with gcc 4.4? [05:51] Yes. With -Wall -Werror, they say they see no warnings... [05:51] did you tried in Debian? [05:52] Debian should have the same set of errors/warning [05:52] wrapster, no idea. sorry [05:52] No, I could try. But I want to be able to get the same warnings in Fedora... [05:52] do you have the log sowehere? [05:52] so that I can have a look at it? [05:53] Yes... http://crosswire.org/~jmarsden/sword/sword-r2480-buildlog.txt [05:55] did you run also the configure command with the same variables? The line is quite long [05:56] you ahve also to be sure that the gcc version is exactly the same (not only 4.4, but also sub-version) and glibc [05:56] Well, in Fedora 12 the gcc version is 4.4.2 which is newer than Ubuntu's ... [05:56] fabrice_sp: well i found a work around.. it was just a python script that i had to place in /urs/bin/ so i manually copied it to debian/pkgname/usr/bin and chmod 755 it.. good enough... ? [05:57] wrapster: If you are just installing one file why did you use -t ?? [05:57] wrapster, you really want to install it in debian/pkgname, and not in $DESTDIR or similar? [05:58] jmarsden, the configures flags are also important [05:59] fabrice_sp: OK, I'll check them all out... but surely somewhere Ubuntu documents its hardening stuff?? [05:59] https://wiki.ubuntu.com/CompilerFlags ? [06:00] the file mgt errors seems linked to -D_FORTIFY_SOURCE=2 with -O2 [06:00] fabrice_sp: Yes... looks like it is the -D_FORTIFY_SOURCE=2 [06:01] Now I need to see if Fedora has that option too :) Time to create a Fedora12 VM... [06:01] :-D [06:01] a chroot won't work in that case? [06:02] * fabrice_sp doesn't have any idea on that, and it could be a dumb suggestion [06:02] I don't know. I have 10Mbps down Internet connection, so it won't take that long to grab an ISO and create a VirtualBox VM. I don't know how to install Fedora into a chroot. [06:02] ok :-) [06:03] And the sword upstream test everything in VM's [06:03] =) [06:03] in this case, it's just for compiling hte app [06:03] :-) [06:03] xnox: Hmm, then they could test in a Debian VM too... but I think I need to do the work and "prove" the issue is real, at this point. [06:05] Well they fire up VM's and tell you it doesn't work after this change in f7 and never try to help you debug. Simply revert commits or not apply patches..... [06:06] or any other f* [06:06] Is that the same 6months+ patch you are trying to get accepted? [06:08] xnox: Yes, from back in May. 1200 line diff, 100+ individual patches... [06:11] Oh well.... Are they gonna do a release any time soon? [06:14] Yes, that's what got this started again... Troy asked for all my patches and applied some of them... 1.6.1 coming soon, it seems. [06:14] Hmm interesting =) [06:15] jmarsden: -Werror turns warnings into errors. that's not a default. [06:16] kees: No, but it is part of the upstream autotools stuff; I could patch that back out, I suppose. But I already have the patch for all the warnings... I just would prefer upstream to apply it rather than carry it as a packaging patch. [06:17] * xnox is happy finished building 1st package flavor - 2 to go [06:19] jmarsden: ok, cool. I only skimmed the scrollback when I saw mention of the hardening flags. was anything missing from the CompilerDefaults wiki page? I've tried to make that as useful as possible. [06:20] CompilerFlags you mean? Looks fine to me, I just didn't know it existed until fabrice_sp pointed me to it earlier. [06:20] Is it mentioned in the Packaging Guide? if not, should it be? === Lutin is now known as Guest90788 === Guest90788 is now known as Lutin [07:45] <^arky^> hi, any help with bug 491327 ? [07:45] Launchpad bug 491327 in at-spi "No module named pyatspi" [Undecided,New] https://launchpad.net/bugs/491327 [07:48] ^arky^: idk python [07:49] <^arky^> thanks micahg, I'll try to look up for python guys [07:49] ^arky^: oh, sorry, I thought this was the bugs channel... [07:49] :) [07:50] someone in here might have an idea [07:52] <^arky^> :) [07:52] * ^arky^ heads back ubuntu-bugs [07:59] good morning [08:00] <^arky^> morning dholbach [08:00] hi ^arky^ [08:01] <^arky^> dholbach: if you have time please have look at bug 491327 [08:01] Launchpad bug 491327 in at-spi "No module named pyatspi" [Undecided,New] https://launchpad.net/bugs/491327 [08:02] ^arky^: I doubt I will have the time for it right now in this moment, if it's urgent try asking in #ubuntu-desktop [08:03] <^arky^> yes, will do that thanks dholbach [08:03] err [08:03] what is there to sponsor? [08:04] is there any patch/diff/branch/something? [08:04] dholbach: please unsubscribe sponsors [08:04] will do === cjwatson_ is now known as cjwatson [09:58] How do I see whether any changes have been made to a package compared to the debian version? (other than downloading the debian version and running diff) [10:00] Rune: if there's an ubuntu in the version, we have modifications [10:01] Do I have to diff the debian version to see what kind of modifications? [10:02] Rune: 'aptitude changelog ' will download the changelog and display it for you (from http://changelogs.ubuntu.com/) [12:12] what is a template for packaging? Please. [12:12] i know dh-make is used to create template [12:12] i am a noob [12:12] Do you know what a template is? [12:14] soren: c++ template yes, other than this no [12:15] As per wikipedia, a template is a standardized file type used by computer software as a pre-formatted example on which to base other files, especially documents. [12:16] dh-make creates a template for packaging. It creates a bunch of files that you can edit until it does what you expect it to. [12:17] a pre-formatted example ? [12:17] How will i get this format? [12:17] You already know this. [12:17] 13:12:30 < shankhs> i know dh-make is used to create template [12:18] ya i know about dh-make [12:18] So what is your question? I don't quite understand. [12:19] i can go on wihout knowing template . My question is what template is used by ubuntu packages and how this templates are decided? [12:19] of the approximately 18,000 source packages in the archive, a vast variety of templates & helpers are used [12:20] I'm sorry, I don't think I can help you. I don't understand your question. Perhaps someone else can. [12:20] based entirely on the whims of the packager [12:20] so ubuntu doesn't force the templates? [12:20] no, of course not [12:21] Depends on what you mean by templates. [12:21] soren: i am not getting you , for me template is a pre-formatted file(as u mentioned before) [12:21] if it doesnt then how come different packages interoperate? [12:22] 10 seconds ago you didn't know what a template was, so I'm not convinced you're using the word correctly here. [12:22] soren: t think so [12:22] Ubuntu forces a specific directory structure of the filesystem (known as the Filesystem Hierarchy Standard, FHS). [12:22] Is that what you mean? [12:22] Do we force one specific way to generate packages? No. [12:22] soren: i need to read from somewhere can you please give me some resources? I am getting confused [12:23] Do we force a specific format of binary packages? Sure, otherwise dpkg would have to be magic. [12:23] soren: i guess so [12:23] shankhs: What are you trying to do? [12:23] soren: i am learning packaging in ubuntu [12:24] shankhs: Did you read the 'Contributing' link available in channel topic? [12:24] Then you should ask about that instead. [12:24] slytherin: i am reading https://wiki.ubuntu.com/PackagingGuide/Basic [12:25] soren: ya any advice?Please [12:25] shankhs: I advice you to read that link and ask questions when there's something you don't understand. [12:26] shankhs: That is a good starting point. If you have any specific questions then ask them. [12:27] Hm... The intro on that page claims that "[f]irst, we will use no build helper. This approach is usually the most difficult and is not often used in practice but gives the most straightforward look at the packaging process." [12:27] I don't see that anywhere in the body, though. [12:28] soren: very frankly i am not understanding dh-make . The only thing thats neccessary is : Type of package: single binary, multiple binary, library, kernel module or cdbs? [s/m/l/k/b] s [12:28] soren: me too found that one [12:28] what the package has to do with the personal info of dev? [12:28] That will create the template packaging. Keep reading, it will all be explained. You are supposed to edit the files it creates. [12:29] shankhs: "personal info"? [12:29] soren: like email id,name [12:30] I don't understand your question at all. [12:30] soren: i will first read the complete doc...thanx anyways [12:30] Everybody thankyou very much [12:30] soren: thanyou [12:30] shankhs: sure [12:32] shankhs: how are others supposed to know who packaged the software if you don't provide name/email [12:34] slytherin: i am getting it , it seems logical thanx === echidnaman is now known as JontheEchidna [13:12] what's a good/simple packaging example for python software using the setup.py install method? (which should be the preferred one, right?) [13:13] I would say that mercurial could be a good example [13:17] Does anyone know any particular reason why autosyncs are happening with less-than-usual frequency? === menesis1 is now known as menesis [13:27] \o/ http://revu.ubuntuwire.com/p/clang === sommer_ is now known as sommer [14:40] http://revu.ubuntuwire.com/p/happytimer [14:40] Please advise. === Lutin_ is now known as Lutin [15:17] shriekout> commented [15:17] LucidFox, thanks :) [15:20] LucidFox, thank you for your suggestions. [15:24] Now speaking about my packages... who will have the bravery to review the great and mighty clang, mortals? [insert thunder] [15:24] Or perhaps one would prefer to review 2mandvd, juffed, or the simplest of all, fuse-zip? [15:31] dholbach: http://www.miafrica.co.za/product1.html [15:32] LucidFox: What is fuse-zip? [15:32] A console utility to mount zip archives as read-write directories. [15:33] Ok [15:33] is that how the archive manager works? [15:34] In Nautilus? [15:34] maco: Manager or mounter? [15:34] the gnome equivalent of ark [15:34] whatever it's called [15:34] file-roller [15:35] The archive mounter mounts them read-only. [15:35] yes that [15:35] maco: hey :) [15:35] nigel_nb: im at work right now [15:35] unfortunately, I'm leavin for work [15:36] oh, k [15:37] no I don't think ark uses that [15:38] What, fuse-zip? No, nothing in DEs uses that. [15:40] Heh, norsetto advocated his own package. [15:40] Maybe I should do that for mine to get them reviewed sooner? [15:41] LucidFox: You can. [15:43] hello [15:43] I have a question [15:44] pbuilder = pdebuild ? [15:45] man pdebuild\ [15:45] :) [15:46] Basically, as I understand it, the difference is that pbuilder is invoked on the .dsc file, while pdebuild doesn't need a source package, only an unpacked directory. [15:48] highvoltage: hehe, yeah - I saw the MOTU music equipment brand before :) [15:51] http://en.wikipedia.org/wiki/Masters_of_the_Universe <-- Aww, no logo. === rgreening_ is now known as rgreening === yofel_ is now known as yofel [18:54] How long does it normally take for packages to autosync from Debian Testing into Lucid? Hours? Days? Weeks?? [19:03] depends on how often the archive admins start their autosync script [19:03] and with the new format 3.0 package it fails more often than in the past :( [19:08] geser: Thanks. I was imagining some autosync script in a cron.{daily/hourly/whatever} doing the syncing. I'll just be patient, it's not important :) [19:27] It's not cronned. It has to be manually run [20:03] porthose: bug 492155 [20:03] Launchpad bug 492155 in jinja "Merge jinja 1.2-3 (universe) from Debian testing (main)" [Wishlist,New] https://launchpad.net/bugs/492155 [20:03] I think it should be a sync as the package is not in main anymore [20:03] so no need to change dependency from recommend to suggest [20:03] (I think) === RoAk is now known as RoAkSoAx === _stink__ is now known as _stink_ === mathiaz` is now known as mathiaz [20:44] hey. i was wondering how i can request a package removal? libass3 isn't needed anymore since libass4 was added. [20:48] LLStarks: File a bug. Subject should be: RM: -- ROM; And file it against Package: ftp.debian.org [20:49] Oh sorry, wrong channel, I thought I was still in a Debian channel :) [20:55] LLStarks: https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Removing%20Packages [21:37] !help [21:37] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) === mtrudel_ is now known as cyphermox [23:42] is Eclipse Public License DFSG compatible? [23:48] kklimonda: Is Ecplise licensed under it? [23:48] ScottK: that's the question - I just thought abo ;) [23:49] ScottK: looks like it is [23:49] Look and see which component of the archive Ecplise is in then. [23:50] main