[00:02] <_ps_> Hello, i'm new on the package maintaining. Can anyone introduce some packages for me to get started and learn more? [00:09] <_ps_> hellooo? === Guest90030 is now known as captivus [00:38] Where is the magic that is supposed to create me a debian/tmp directory? [00:38] I'm planning to split one source package into multiple binary packages. [00:39] dh_make creates a rules file that tells me to install the stuff to debian/tmp [00:39] but that directory never appears [00:39] and then installing fails [00:40] mkdir it before you call make install [00:40] or its equivalent [00:40] at least autotools knows how to create its own directories [00:40] tell your upstream to fix their buidl system [00:41] ok [00:41] thank you === sttj is now known as stj === yofel_ is now known as yofel [02:08] hello : bug 446838 needs a huge patch http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail?view=rev&revision=13818 for the patch size can this be included ?? if so to start with it [02:08] Bug 446838 on http://launchpad.net/bugs/446838 is private === zachtib is now known as zachtib|beerrun === zachtib|beerrun is now known as zachtib [04:21] I'm trying to find the link to get a mentor - I keep finding pages about being a mentor [04:22] I think I'm finally ready to try this thing out :) [04:30] MTecknology: I think you want https://wiki.ubuntu.com/MOTU/Mentoring [04:31] thanks === micahg1 is now known as micahg [08:01] Hi all... [08:02] Soon, I can celebrate my 2nd month since I am in the reception waiting for a mentor [08:02] Any ways that there is someone here to be my mentor? [08:03] pan1nx: Informally, just ask specific questions here and someone will probably help you out. The Mentoring process is more formalized and there is currently a backlog. [08:04] mentoring yes, but the reception process is not [08:05] MOTU-Mentoring-Reception is a team of people, not a process, unless I am confused. [08:06] hmm, in order to get a mentor you email the reception and wait [08:06] it is part of the mentoring process to email the reception [08:07] Yes. Known issue, I'm not a MOTU, but on behalf of those who are... please be patient, and meanwhile, get started on some practucal stuff here :) [08:07] *practical [08:08] pan1nx: Is there something in particular regarding MOTU work that you have questions about or want help with? [08:08] nope [08:08] OK. [08:08] just want to start the process so I can get to MOTU one day and do the work there [08:09] You do not need to use the mentoring process to become a MOTU :) You just need the skills and experience. [08:09] jmarsden, I've had quite good patience, as 2 months of waiting is not easy :D [08:09] So... if you have no specific questions... dig in and do some work here :) [08:09] good morning [08:09] What specifically are you waiting for? Why not find a bug and fix it and create a debdiff, etc etc. [08:09] jmarsden, ok [08:10] good morning [08:10] dholbach: Good morning [08:10] well, I did that jmarsden... [08:10] and I will continue [08:10] hi jmarsden [08:10] pan1nx: Good :) Then you are not really just waiting... [08:11] ok, I had the wrong impression that it is required to have a mentor... jmarsden [08:11] it looks to me that it is really important when you join that some mentor talks about your achivements... [08:12] but it might be just a wrong assumption... [08:12] https://wiki.ubuntu.com/MOTU/Mentoring says "The mentoring program is in no way compulsory" -- but it might help you figure out where your weaknesses are, what to work on next, etc. [08:16] ok, jmarsden, thank for the corrections... [08:16] No problem. [08:17] pan1nx, the important is to do a good work, dependening on yourself a mentor maybe helpful or not, most of the times asking here on the chan is sufficient [08:20] now Chris is online also (huats)... but I think I can do it just by myself... [08:28] geser: #ubuntu-meeting? [08:29] dholbach: totally forgot the meeting :( [08:30] geser: me too :) === dholbach_ is now known as dholbach === micahg1 is now known as micahg [10:54] . === Tonio__ is now known as Tonio_ === ripps_ is now known as ripps === bdefreese2 is now known as bddebian [13:24] does someone know when ubuntu open week was [13:28] never mind, found it 31 aug - 4 sep [13:37] Can I have an informal FFe for hlint please? It restores functionality on armel and ppc [13:38] and is a leaf package [13:56] Laney: ok with me [13:59] thanks [13:59] ScottK: ^^^? [14:00] Laney: Sure. Don't break stuff. [14:00] i'll try not to === Philip6 is now known as Philip5 [14:08] arg [14:08] pbuilder-satisfydepends-dummy: Depends: libghc6-src-exts-dev (>= 1.1) but 1.0.1-1build1 is to be installed. [14:08] Depends: libghc6-hscolour-dev (>= 1.15) but it is not installable [14:15] both would need FFe [14:15] not sure it's worth it [14:18] is it possible to change the cache location of pbuilder? [14:21] slacker_nl: should be the --aptcache option [14:23] cemc: no i mean, for pbuilder create and update commands, it puts stuff in /var/cache/pbuilder and i want that to be a different dir [14:23] slacker_nl: check the default pbuilderrc, there is an option. [14:24] slytherin: BASETGZ you mean? [14:24] slacker_nl: --basetgz [14:24] http://pb.opperschaap.net/67 [14:27] slacker_nl: that and BUILDPLACE [14:32] slytherin: thnx, seems to work now [14:33] too bad there isn't a PBUILDHOME variable, so everything is relative to that dir [14:55] Is there any change somebody could look at bug 446582? [14:55] Launchpad bug 446582 in claws-mail "[karmic] claws-mail display is broken by GTK+ 2.18" [Undecided,Confirmed] https://launchpad.net/bugs/446582 [14:57] a fix exists for the bug in the package, it just needs to be applied to the ubuntu branch and hopefully applied before karmic release [15:01] MTecknology: extract the patch, attach it to the bug, then subscribe the sponsor team [15:02] * Laney crushes armel haskell breakage [15:08] james_w: does just a diff file between the two debs work? [15:09] yeah [15:09] well, not debs [15:09] debdiff though [15:09] MTecknology: No a diff between two source packages. debdiff 1.dsc 2.dsc [15:09] ok, thanks === thekorn is now known as Guest46897 === yofel_ is now known as yofel [15:29] ScottK: would you be so kind and poke epiphany-webkit that is in bin NEW ... we lack archive admins over here ;) [15:29] err epiphany-browser [15:29] its universe nowadays [15:31] ARGH [15:31] ARGH [15:31] StevenK: ^^ maybe you? [15:31] um... could an archive admin be a sweetie & reject clr-wallpapers from NEW? meant to send it to my ppa... :( [15:31] Laney, no laughing [15:32] directhex: haha is Ubuntu your default upload target? [15:32] jdong, i plead the 5th! [15:32] XD [15:33] directhex: hahahahaha [15:33] oh wait, *no* laughing [15:33] I did that once with ghc6, but it wasn't NEW thankfully [15:33] wait, not thankfully [15:33] unfortunately [15:34] good job there wasn't an offensive comment in the changelog eh [15:34] bob is my default upload target [15:34] I did that once with automatix but it was 4/01 ;-) [15:34] * Laney remembers that [15:35] * Laney also remembers a certain someone falling for it [15:35] bob doesn't like getting packages, and kindly rejects them all [15:35] my default upload target insults me ;-) [15:35] slytherin: how do I do this then? this is what I got from diff - http://pastebin.ubuntu.com/289327/ [15:36] jdong, i just set one that does so [15:38] directhex: has anyone in debian-land packaged monodevelop 2.2's prereleases yet? [15:38] jdong: yeah, directhex and me ;) [15:38] ooh cool [15:39] where may I snatch that from? :) [15:39] still need to remove its moonlight abilities first [15:39] ok, directhex should get the credits [15:39] jdong, it's in packaging git or svn, i forget which [15:39] ok I'll look this afternoon [15:39] MTecknology: you need to use debdiff, not diff [15:40] where do I get debdiff from? [15:40] directhex: btw what's holding back boo? an rdepend I'd guess? [15:40] directhex: jdong svn [15:40] MTecknology: Also you have changed claws-mail upstream version as well which is not correct. [15:40] hu? [15:40] jdong, sick of chasing a completely unstable ABI. need to discuss how to treat boo, given every upload forces a transition [15:41] directhex: haha indeed, what stable ABI... :) [15:42] directhex: evil bounty for a trigger-rdepends-rebuild script? :) [15:42] slytherin: I didn't change anything with there source, I just used 'apt-get source' to pull from their ppa [15:42] directhex: there was no ABI change that I know of between 0.9.1 and 0.9.2 ..... [15:43] jdong, actually... the main reason for opposition to ABI changes is new ABI means new package name means debian NEW queue, but NEW has sped up enormously [15:43] cedricv: we are at 082 [15:43] that far back? i think i packaged 0.9something [15:44] Laney: hmm i thought 0.9.1 was in unstable [15:44] boo (0.9.1.3287+dfsg-1) UNRELEASED; urgency=low [15:44] madison seems to think 0.8 too [15:44] at least 0.9 yeah [15:44] unreleased [15:51] whomever isn't claiming credit: thanks for erasing my shame! [15:53] directhex: your welcome [15:54] MTecknology: if there are other changes then just grab the patch that they specify in the comment and attach that [15:55] ah, a wild james_w! must've been 'im! [15:55] james_w: I'm not too familiar with cvs and afaik, there's not web interface for it [15:55] I dun nuttin [15:57] james_w: so there is a web interface - and cvs is SO simple [15:57] Colin said "The patch is fix_gtk218_issues.patch" [15:57] if you look at the package you downloaded you should find that file [15:58] probably debian/patches/fix_gtk218_issues.patch [15:59] yup :) [16:00] james_w: patch is out there now [16:03] james_w: and now I assign it to motu? [16:10] james_w: it's assigned [16:10] 90 days is a short membership time [16:14] MTecknology: no, subscribe (not assign) ubuntu-universe-sponsors please [16:14] sorry [16:15] done [16:17] james_w: anything else I can do for this? [16:18] MTecknology: just wait for review now [16:18] james_w: any chance this will make it into karmic? [16:19] I would hope so [16:19] I don't like using an extra PPA when there's no need to :) [16:20] wow - I'm hungry - 2hr till class is over [17:00] MTecknology: you haven't attached a debdiff [17:01] randomaction: I was told the patch file is what I need to attach - I don't know how to get the debdiff [17:04] there's a general guide at https://wiki.ubuntu.com/Bugs/HowToFix, and I can help you with specifics if you want to create it yourself [17:11] debdiff oldpackage.dsc newpackage.dsc > newpackage.debdiff [17:11] asac: cjwatson already got it. [17:12] What channel should I use to talk about what seem to be missing dependencies in [17:12] maven2? [17:12] asac: I actually did it around two hours before you asked ;-) [17:15] I guess I should just open a ticket. [17:15] now I'm forwarding maven2 and related to my-ppa [17:15] what are you looking for? [17:17] ari-tczew: I don't know what you mean that you are forwarding maven2. [17:18] I just apt-get dist-upgraded my karmic workstation and "maven2 --version" fails with an exception. [17:18] A bit of googling makes me think that it needs a newer (or older?) version of [17:18] plexus [17:18] I mean "mvn --version" [17:18] http://nexus.sonatype.org/mailing-list-dev-archives.html#nabble-td24954526 [17:19] Ah, I see that it is already reported as #417164. [17:20] Maven is currently pretty broken, but needs manual bootstrapping to be udpated. [17:20] Hm, launchpad pops open a dialog box that says "Just mark me as also affected or subscribe me as well", but I can't make that dialog box go away by clicking on the green check mark. (Using konq in karmic.) [17:20] I guess I should take it to #launchpad? [17:21] Yes. [17:21] bug 444714 [17:21] Launchpad's support of Konqueror took a nose dive in the last release. [17:21] Launchpad bug 444714 in plexus-interpolation "sync request (unstable -> universe) for getting maven built , FFe's granted" [Undecided,New] https://launchpad.net/bugs/444714 === zooko` is now known as zookow [17:22] Could y'all suggest a work-around for me. I'm new to maven, and my co-workers want to know why I'm wasting time debugging Karmic instead of building this Java/Scala code. [17:25] Heya guys. one quick question. I'm about to sponsor an upload, and the contributer has added the Section field for the source in debian/control. However the binary packages in debian/control already have a Section field that are libs and libdevel. So, is it strictly necessary to have that Section field added to the source ? [17:26] no [17:26] Hi. Can some archive admin have a look at bug #446917 [17:26] Launchpad bug 446917 in grsync "Sync grsync 0.9.2-1 (universe) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/446917 [17:26] not from an archive perspective at least [17:26] fabrice_sp: is it urgent? [17:26] james_w, people are getting nervious in Bug #423755 [17:26] Launchpad bug 423755 in grsync "grsync does not start - GTK critical error" [Wishlist,In progress] https://launchpad.net/bugs/423755 [17:27] but it's not a vital issue [17:27] Okay, my co-workers says that the work-around is uninstall the Ubuntu package of maven2 and install maven2 by downloading a java executable... [17:27] well they can keep being nervous for a little while longer [17:27] lol [17:27] ok [17:28] I could spend 5/10 minutes doing it now [17:28] james_w: Thanks for the pointer at the bug. If you'd want to do those sync's, it's be cool. 443292 too. [17:28] or I could do it with in the next batch, which is significantly less effort [17:28] bug 443292 [17:28] Launchpad bug 443292 in ubuntu "sync, merges and FFe's need for getting maven built" [Undecided,Confirmed] https://launchpad.net/bugs/443292 [17:29] what a mess [17:31] james_w, so in this case, I should point to the contributor that it is not strictly necessary to have that change and he can drop it, or should I just accept it and ask to forward the changes to debian? [17:31] RoAkSoAx: I would just drop it if it isn't needed to build the package or fix a bug [17:32] for admins who working on maven: bug 447382 [17:32] Launchpad bug 447382 in libgoogle-collections-java "[FFe] Sync libgoogle-collections-java 0~20080808-3 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/447382 [17:33] RoAkSoAx, I remember seing a lintian about missing section in source [17:33] it may explain why the contributor added it [17:34] FFe approved, needs admin archive bug 427886 [17:34] Launchpad bug 427886 in kadu "[FFe] Sync kadu 0.6.5.3-2 (universe) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/427886 [17:34] james_w, it is not necessary indeed. On the other hand, lintian is also showing other warnings such, howerver I was thinking on asking him to fix this: substvar-source-version-is-deprecated and an error "build-depends-on-obsolete-package". Should I go ahead and ask him to do that? [17:35] the first isn't necessary [17:35] it's mainly something that impacts Debian [17:35] and sometimes isn't broken [17:35] the second might be important [17:35] it might require a change to build properly [17:35] but again, if not then I lean toward minimising change [17:37] james_w, ok so, since the dependency error is a transitional package, we can just leave it as it is for now, right? [17:37] probably [17:40] james_w, Ok. the dependency error is on tetex-bin, which is a transitional pacakge that only depends on texlive, so we can just go ahead and change it ( It is not affecting the build process) [17:41] fabrice_sp, he actually added because in his understanding it was needed, otherwise it won't be accepted in the archive.. but well.. it would be only applicable in debian :) [17:42] RoAkSoAx, ok. So you can just ask him to report to Debian (if not already there :-) ) [17:43] fabrice_sp, yep, I was just planning on drop that change and ask him to report to Debian, however I was doubting on cleaning that lintian error on the dependency :) [17:45] RoAkSoAx, I've seen packages that FTBFS because of a similar error not corrected in previous versions. Anyway, if the package builds fine, it should also be reported to Debian, and not change it (even if I don't like having lintian errors :-) ) [17:46] * fabrice_sp is wondering why all contributors fails to update the maintainer field?! [17:46] at least, debuild remind you to do it [17:47] fabrice_sp: only if you have DEBEMAIL set to an ubuntu.com address [17:47] fabrice_sp: remind -- as in doesn't build ;) [17:47] sistpoty|work, interesting... [17:47] yeah: it's a hard reminder! :-) [17:47] :) [17:59] Wow, ant is totally incompatible with the DESTDIR convention and therefore with GNU Stow. [18:01] Also it takes 1m50s to rebuild even though I just built maven. Argh! Quick! Where's the appropriate channel for bitching about Java software tools sucking? [18:02] haha isn't that generally accepted? :) [18:03] * zookow joins #patentlyobvious [18:06] fabrice_sp: very happy upstream acted so fast on that grsync bug [18:06] that fixes our whole quandry [18:07] sharms, yes! :-) It's easier to sync than patching and merging :-) [18:07] fabrice_sp: thanks a bunch for your help on it [18:07] thanks to you for your work on it :-) [18:10] thnx to james_w for sponsoring drupal's fix [18:12] fabrice_sp: could you consider sponsoring my pidgin-otr bugfix: bug #310769 [18:13] Launchpad bug 310769 in pidgin-otr "Cannot copy keys from authenticate window" [Wishlist,Triaged] https://launchpad.net/bugs/310769 [18:13] I changed it to direct-source patches as you requested [18:14] debfx, ok. I'll have a look a bit later [18:16] Would someone who can manage to change the topic add https://bugs.launchpad.net/ubuntu/+bugs?field.tag=karmic-autotest please? [18:27] ScottK, I thought everyone could modify topic [18:27] Me too, but I've failed when I tried. [18:28] mm..maybe channel flags are set to block someone with no permission to do it [18:28] debfx, which change is or which bugfix? [18:28] it's not #d-devel : / [18:28] s/or/for/ [18:30] fabrice_sp: otr-plugin.c for key generation, gtk-dialog.c for copy fingerprint [18:30] debfx, ok. I'll update the changelog with that info [18:39] fabrice_sp: ok, I hope the debian maintainer switches to a proper patch system, these direct-source patches really are a mess [18:40] pfft, manual zgrepping builds character. [18:40] debfx, uploaded. Sorry about the delay: I didn't saw you updated it :-) [18:48] fabrice_sp: no problem, thanks! [19:24] superm1: I have one question. Should lirc-modules-source be moved to 'Recommends' of lirc instead of 'Suggests'? [19:26] juego de boxeo online http://www.kobox.org/kobox-fande-Nourine.html [19:29] slytherin, no [19:29] all the lirc stuff is provided by the kernel [19:29] that's a stop gap solution if for some reason you need to rebuild the module [19:29] or patch it or anything [19:30] superm1: OK. By the way, the dkms build for lirc-modules-source is failing. Do you want to take a look at log before I file a bug? [19:31] superm1: http://paste.ubuntu.com/289461/ [19:32] slytherin, there is a bug opened on it already. there is a whole lot of lirc stuff that needs to be done. considering moving to lirc 0.8.6 because it fixes a lot of the stuff actually [19:32] but it's gonna take a few hours to sit down and sort out whether it's really a good idea [19:32] what sort of delta it means for the kernel etc [19:33] hmm. I haven't yet started using lirc but if I do in next few days I will report back how it is working. [19:33] Iwill not file bug now. [19:34] just dont use lirc-modules-source [19:34] I will not. === micahg1 is now known as micahg [19:58] anyone up for a practical ftbfs session? starting in a few minutes in #ubuntu-classroom [19:59] sistpoty: me, for some time at least. [19:59] :) [20:01] randomaction: thanks for multisync90 fix, uploaded [20:01] great :) [20:02] sistpoty, lol was about to review it :S xD [20:02] sorry RoAkSoAx [20:02] sistpoty, no prob :) [20:03] randomaction, please follow https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines for claws-mail patch. thank you :) [20:04] RoAkSoAx: ok [20:18] ARGH [20:18] james_w, :( [20:18] james_w, i'm copying a fixed dput.cf to all my machines right this second, promise :( [20:21] * directhex sniffles at his own stupidity [20:23] RoAkSoAx: reposted [20:31] randomaction, awesome! and btw... the Section was indeed necessary, sorry for the confusion. [20:32] ok, you still have the old debdiff [20:32] randomaction, yes, I already uploaded it. thanks a lot for the contribution [20:32] and sorry for misleading you in that one :( [20:33] no problem, debdiffing is cheap :) === shinta42 is now known as soda42 [20:37] :) === fabrice_sp_ is now known as fabrice_sp [20:45] randomaction, btw... you manually copied the claws-mail patch and put it under debian/patches and added a line in debian/patches/series, right? [20:45] yes [20:46] randomaction, ok, well, you should not do that! Do you want a quick quilt session? [20:47] patch - quilt new - quilt add - refresh :) [20:47] I verified that the patch applies (in this case with fuzziness) [20:48] is there a problem with what I did? [20:48] RoAkSoAx: hehe, that's what I do too [20:48] easier than remembering all the files you have to quilt add before applying the patch [20:49] well the patch might not apply cleanly [20:49] I do test that [20:49] I put it in manually then quilt push to it and refresh it [20:50] right, but you usually need to *strip* the patch by upstream and then apply it into Ubuntu [20:51] strip? [20:53] randomaction, for example, in the patch available for claws-mail you have to strip it, for i.e.: http://pastebin.com/m2c9d6e0f [20:54] retrieving revision... etc etc... that should not be there [20:56] I never just copy a patch there, and I always apply it *manually* [20:57] Is there a reason to do this if the patch system is ok with this patch? [21:00] well I don't remember exactly but I've always been told to apply the patches *manually*, I mean, never just copy a patch to debian/patches [21:00] if it applies and unapplies cleanly, then there isn't any need [21:01] do offset hunks count as clean? [21:01] Was thinking of working on bug 445633 but someone else filed it, should I leave it? [21:01] Launchpad bug 445633 in pygobject "FTBFS: automake-1.10 missing" [Undecided,New] https://launchpad.net/bugs/445633 [21:01] randomaction: no (then usually the patch won't unapply cleanly) [21:02] He hasn't assigned it to himself [21:02] funkyHat: feel free to grab it [21:03] funkyHat: that's from the autotests, so anyone to grab it is welcome [21:03] yeah, you can probably grab it if he hasn't assigned himself to it already [21:03] funkyHat: btw., -> #ubuntu-classroom, we're doing a ftbfs session there (interactive, aka everyone grabs a package and asks if problems show up) [21:03] but he's on #ubuntu-devel if you want to ask him [21:03] siretart, what about when the patch contains things like: RCS file: /srv/cvs/claws-mail/claws/src/mimeview.c,v or retrieving revision 1.83.2.156 ? [21:04] @maven2 bug 447526 [21:04] sistpoty: so if I see "Hunk #2 succeeded at 2215 (offset -2 lines).", I should assume that something's wrong? [21:04] randomaction: yes [21:04] randomaction: please refresh patch manually [21:05] well, it's a backported upstream patch, the must have been intermediate revisions [21:05] ari-tczew: ok [21:05] RoAkSoAx: I'll respin the debdiff [21:06] maven2 sync required it bug #447526 [21:06] Launchpad bug 447526 in commons-httpclient "[FFe] Sync libcommons-httpclient-java 3.1-6 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/447526 [21:08] randomaction, ok :) === IVBela1 is now known as IVBela [21:33] we should use bzr, not patches :) [21:35] heh [21:36] Hi [21:37] Is there any mentoring systems available for someone wanting to get involved in MOTU? [21:38] Bodsda, there is indeed: https://wiki.ubuntu.com/MOTU/Mentoring [21:41] RoAkSoAx: thank you -- gimme a few minutes to do some reading and I'll come back :) [21:58] RoAkSoAx: I have sent in an email to motu-mentoring-reception@responses.net --- is it a matter of waiting for a reply now? [21:58] Bodsda, it is. You might wanna check with huats or porthose to see if they received your email :) [21:58] Bodsda, you can contribute without having a mentor (and even become a MOTU) [21:59] it's not mandatory at all [22:00] fabrice_sp: I know, but I have tried a few times before and often get confused. It would be nice to have someone to get me started [22:00] RoAkSoAx: ok, will do, cheers [22:00] Bodsda, you can ask here your questions [22:00] Bodsda, you can always ask here... there's always someone willing to help [22:00] :-D [22:00] xD [22:01] fabrice_sp: RoAkSoAx -- ok thansk guys. So... where to start? I have looked through the packaging guide and the contributing pages a few times. What do you suggest [22:01] ? [22:01] Thanks btw, I appreciate the warm nature of the channel [22:02] Bodsda, fixing bugs :-D [22:02] Bodsda, well right know we are concentrating on fixing FTBFS(Failed to Build From Source Bugs). Many of these bugs already have a fix in Debian or upstream and we can always just apply it in Ubuntu :) [22:02] making small changes to package will aloow you to understand how things works [22:02] fabrice_sp: oh.. I wrote a script for that... fix-bugs --os=ubuntu --amount=all [22:03] RoAkSoAx: ok. So do we have some documentation for this process? [22:03] and it works well? [22:03] fabrice_sp: it just prints "Done" -- Was it supposed to do something else? [22:03] :) [22:04] Bodsda, there was actually a session on FTBFS at #ubuntu-classroom [22:04] you can have a look at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909-karmic.html to see the packages that fails [22:04] find the solutions, and then follow the contribution guide [22:04] !contributing [22:04] Sorry, I don't know anything about contributing [22:04] sistpoty, are there any logs from the previous FTBFS session and/or logs from the session just held at -classroom are going to be published soon? [22:05] fabrice_sp: so, all the packages in red are FTBFS? [22:05] yes [22:05] RoAkSoAx: not too sure actually... iirc dholbach wanted to publish a log [22:05] RoAkSoAx: if you want to take another look at claws-mail patch, it's ready [22:06] randomaction, yep I already did, I'm just finishing my testing to upload :) [22:06] ok [22:06] fabrice_sp: do i need to run karmic in a vbox for building yeah? [22:08] Bodsda: I think you can build a source package on a non-karmic machine and then upload to a launchpad ppa to have it built for karmic. [22:08] Bodsda, you can use a pbuilder [22:09] Darxus: well, I am just starting so probably best to keep it simple :) [22:09] oh [22:09] ok [22:09] RoAkSoAx: is that info in the packaging guide? [22:10] Bodsda, yes [22:10] Bodsda: I think compiling on launchpad is a lot less complicated than setting up a virtual machine. And you'll need to do somewhere in the process anyway. [22:10] Just upgrading to Karmic would be even easier, and it seems pretty stable. [22:11] Darxus: RoAkSoAx -- ok so lemme see if I have this. I need to find a package on this list http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909-karmic.html then attempt to build it as per the packaging guide? [22:12] Bodsda: https://wiki.ubuntu.com/PbuilderHowto [22:12] randomaction: ok, build using that guide, not the packaging one yeah? [22:13] this tells you how to set up and use pbuilder [22:13] randomaction: and what is pbuilder used for? (sorry for all the questions) [22:13] which will build in karmic environment [22:13] oh i see [22:14] I think you'll still need the packaging guide to prepare a package which you'll feed to pbuilder [22:14] Ok, im gonna grab some toast, beer and a cigarette then get stuck in, cheers guys [22:23] randomaction, done :) Btw.. I made a little change in the description of the patch. Instead of using one single line I used two for the description [22:24] ok, thanks [22:24] randomaction, thank you for your contribution [22:24] I'm interested in having claws-mail in good shape ) [22:24] :) [22:36] RoAkSoAx: raw logs of the first ftbfs session are at http://irclogs.ubuntu.com/2009/09/11/%23ubuntu-motu.html (starting around 20.00) === Amaranth is now known as true === true is now known as Amaranth === lukjad007 is now known as lukjad0Q7 === lukjad0Q7 is now known as lukjad007 [23:03] ok, checkinstall works [23:03] So I've been going the wrong way with this package the whole time -.- [23:04] funkyHat: if it's a new upstream version in unstable, it might still be feasable to just introduce the patch you've create for kamirc [23:05] sistpoty, who should I subscribe to bug 447601 [23:05] Launchpad bug 447601 in checkinstall "checkinstall FTBFS due to glibc change" [Undecided,New] https://launchpad.net/bugs/447601 [23:05] debdiff is attached [23:07] sistpoty: sorry you've lost me :D [23:07] I was wondering if I should be filing a sync request for the new upstream version [23:07] funkyHat: what version is in debian, what in ubuntu? [23:07] argh, gnote source includes the gnote tarball, ugly [23:08] sistpoty: ubuntu has 2.18.0-0ubuntu1 and debian has 2.20.0-1 [23:08] joaopinto: patch looks good, test-building [23:09] funkyHat: that means it's a new upstream version, not just a new debian revision. The easy route is to add your patch, otherwise you'd also need to file a FFe [23:09] gnote on debian is 0.6.2, current on karmic is 0.5.2 [23:09] can I simply test and attach a debdiff for the newer version ? [23:09] Oh we're in final freeze, right :D [23:10] funkyHat: not yet, but in FeatureFreeze [23:10] I see the antimono camp coming for gnote missing on karmic [23:10] Ok [23:10] Right, I will stop worrying about what I've submitted to launchpad now then [23:10] joaopinto: it's not mising it just doesn't compile [23:11] sistpoty, from and end user perspective, it's missing [23:11] joaopinto: no, the old binaries are still present for the end user [23:11] joaopinto: however for gnote (no reverse dependencies) I wouldn't mind a new upstream version, but you'd ideally get an ack from seb128 for it [23:12] (he's the delegate for gnome FFe's) [23:12] The Makefile.am is already fixed in 2.20, it seems [23:12] sistpoty, how are FFes relevant for a package that never worked during the dev cycke ? [23:12] cycle [23:13] joaopinto: if it never worked, it'll certainly get accepted... however never worked != fails to build from source (because the binaries from the last working build are still present) [23:14] hum, that was not the case for checkinstall, i was unable to install it [23:14] higher priority FTBFS should be uninstallable packages [23:15] joaopinto: actually I just installed checkinstall from the archive [23:15] ? [23:15] hum [23:16] siretart, must have been my mistake [23:16] so what's the value of fixing FTFBSs at this time ? [23:17] joaopinto: if there's a bug in a package, it can't get fixed unless it's made building again [23:17] joaopinto: this matter much more if we've done the release (noone can try to fix the package until she first fixes the build failure) [23:18] ok, but i don't see that much universe fixes after the release [23:19] moo [23:19] joaopinto: but having it not even buildable means there'll be even less :/ [23:19] ok [23:19] joaopinto: btw, nice work with checkinstall, uploaded, thanks! :) [23:19] joaopinto: Security fixes need to happen quickly, but they cannot if the package fails to build. [23:19] wgrant, that is true but that is something you don't see ofter in universe [23:20] often [23:20] joaopinto: That is a bug. [23:20] And we should not make it even harder. [23:21] joaopinto: oh, just a side note: if you file a bug (e.g. because you need to get sponsored) you can close it by adding LP: #bugnumber in the changelog [23:21] * funkyHat looks for another easyish ftbfs :) [23:21] joaopinto: (i've done that manually now) [23:21] ok, i will ask someone to check my next changelot for the LP close tag [23:21] funkyHat: what about the fix you've been working on? [23:22] anyway, going for the next package, notecase [23:22] joaopinto: it's not a big deal, that way however I get the karma for closing the bug by hand :P [23:22] sistpoty: I'd already attached my debdiff to the bugreport, and after investigating debian, their version is already fixed [23:23] funkyHat: but our version isn't fixed yet? [23:23] bug 445633 [23:23] Launchpad bug 445633 in pygobject "FTBFS: automake-1.10 missing" [Undecided,New] https://launchpad.net/bugs/445633 [23:23] funkyHat: thanks, looking [23:24] Sorry I should have mentioned I'd uploaded a debdiff [23:24] heh, no problem [23:24] brb, baby [23:24] crack, pygobject is in main... must look very careful then *g* [23:31] funkyHat: mind if I mangle your changelog entry a little bit? http://paste.ubuntu.com/289639/ [23:32] sistpoty: not at all [23:32] funkyHat: also I believe autom4te.cache hunks are not needed, I'm trying a test-build w.o. these and would strip them unless you object [23:32] (slightly recalling autotools now) [23:32] Are there guidelines for how to write changelog entries? [23:33] funkyHat: not too sure, but the best guideline is probably: forget everything you know about the package, and try to recall what you did by reading changelog [23:34] funkyHat: at least that's the way I learnt writing changelog entries: I had to do a large number of merges of my own changes, not recalling what I did (and crack, my changelog entries back then were quite crappy) [23:34] no point to add a patch system for adding a few lines of headers, right ? [23:35] joaopinto: general rule of thumb: if the package is from debian, reuse the same patch system as debian (seeing none as a choice for a patch system as well) [23:35] ok [23:36] joaopinto: otherwise for ubuntu originated packages, I don't see a reason to add one for a simple patch, but other developers might have other preferences [23:37] erm, a package linking with it's own zlib copy ? is that allowed ? [23:37] sistpoty, thanks for the logs [23:37] joaopinto: allowed: yes. good: no [23:37] (it's pretty common though, afaict) [23:38] well, not a good time to fix it [23:39] that's also true (unless the diff of the zlib copy and the zlib archive sources is empty) [23:41] the zlib is being compiled ang linked in [23:42] funkyHat: uploaded, thanks! [23:42] yaay :) [23:42] * funkyHat dances === asac_ is now known as asac