[00:01] TheMuso: the point is, I'd like to get it verified first.. I thought it wasn't a big deal from what you've said.. nevermind.. [00:03] Alright, I'll test build i. [00:03] it [00:07] any wxWidgets fans in here? [00:11] rjmyst3: what's up [00:21] why some packages has as maintainer a @ubuntu.com email? who are that people? [00:22] why dont use motu? [00:23] dcordero: It means that individual has chosen to take responsibility for the package. [00:23] Why varies per person. [00:23] ..or left-overs from dh_make.. [00:24] Although that won't usually give you an ubuntu.com address. [00:24] from DEBEMAIL? [00:25] ok i think that motu has ubuntu.com address [00:25] i was mistake [00:29] blueyed: Pbuilder builds fine without your patch on ppc. [00:30] This is the version in hardy. [00:30] TheMuso: so you've tested 0.176ubuntu1, or the .dsc I've given? Ok.. thanks. [00:30] 0.176ubuntu1. [00:30] Just pulled from repo, and built. [00:30] Note that I am using sbuild. [00:31] hmm.. that might make a difference then.. the bug is for the same version. It's getting ugly.. I'll leave this patch out and request sponsorship for the more important ones. Thanks again. [00:34] np [00:34] Would you say a 2GB ddr2 533mhz module for 39€ is a good buy? Or is it expensive? [00:36] err, offtopic here, sorry [00:37] although I want it to be able to build wxWidgets3.0, so not that offtopic ;) [00:37] pochu: I'd worry more about the quality than price myself. Bad RAM can cause a lot of trouble. [00:37] pochu: still offtopic but I bought 2 x 2 GB DDR2 PC6400 for 90€ [00:38] ScottK2: It's Kingston, which is a good manufacturer, isn't it? [00:38] The prices you guys have overseas makes me jellous. :p [00:38] Although ours aren't too bad. [00:38] Can I do a sid build on the ppa? [00:38] ScottK2: and I have to worry about the price... my money isn't ilimited [00:38] pochu: afair kingston has a good reputation [00:38] mok0: nope [00:39] pochu: didn't think so :-) [00:39] I'd love to be able to provide packages for my Debian friends... [00:40] mok0: report a bug against soyuz [00:41] pochu: I've reported lots of bugs against LP, they tend to be ignored [00:41] I think I'll see if I find this one or something similar cheaper in another store. Otherwise I'll buy it. [00:41] pochu: isn't there a price search site for online shops from your country? [00:41] Thanks for the advice [00:41] geser: not that I know of... [00:41] mok0: not mines [00:42] pochu: ok, I'll do it. Wrt. RAM, I prefer Corsair [00:48] pochu: I don't know how the german prices compare to the spanish ones, but a Kingston KVR533D2N4/2G costs around 35-40€ in german online shops [00:50] mok0: you replied to me earlier, but I had stopped watching, sorry [00:50] rjmyst3: wxwidgets? [00:50] yes [00:50] rjmyst3: you were asking about it [00:51] i'm looking for reviews of my package for a wxWidgets GUI builder - wxformbuilder [00:51] http://revu.tauware.de/details.py?package=wxformbuilder [00:51] rjmyst3: I'm not a motu [00:51] that's too bad [00:52] but, if you like widgets, you might like the software [00:52] wxformbuilder is a good tool [00:52] rjmyst3: is it an IDE? [00:53] mok0: no, it is GUI layout + code generation - it generates C++ and XRC [00:53] rjmyst3: ok, that's an ide ;-) [00:53] mok0: the generated files can then be used on your platform of choice [00:53] Integrated Developemnt Environment [00:53] mok0: ok, then it is :) [00:53] mok0: but it does not compile the code [00:54] rjmyst3: debian/changelog: (LP: #181412) [00:54] rjmyst3: not closes [00:55] mok0: i see you've found a bug already! - I am not sure what you are saying, though [00:56] rjmyst3: In your file debian/changelog, there's a bug in the line with bg#.... it should be like ^^^ [00:57] mok0: is this the correct syntax: "* Initial Release. (LP: #181412)" ? [00:57] yes [00:57] what does LP mean? [00:58] Launchpad. It's Ubuntu's bug tracking system [00:58] oh! [00:58] ubotu, ! Launchpad [00:58] Launchpad is a collection of development services for Open Source projects. It's Ubuntu's bug tracker, and much more; see https://launchpad.net/ [00:58] i'm familiar with Launchpad - I opened the bug [00:58] i just didn't put 2 and 2 together [00:59] rjmyst3: In debian, it's true you write (closes: #nnnnn) [00:59] i was reading the debian policy manual when i wrote that [00:59] i'll fix that right now, thank you [01:00] * ScottK2 says what the heck and uploads. [01:00] rjmyst3: there are a few minor differences. The changelog file is scanned by the build system, and it would not work because Ubuntu adn Debian have different numbers [01:00] bug numbers [01:00] right, I understand [01:00] is there a list of differences for ubuntu that I should read? [01:00] I've never seen one [01:01] Version numbering and bug numbering are the ones that usually matter for packaging. [01:01] .... and the mainainer thing [01:01] I am familiar with the version number and bug numbering (now) - what is the maintainer thing? [01:01] The other major one is that Ubuntu will accept GFDL invariant documentation in it's main repositories. Debian considers them non-free [01:02] ubotu, ! maintainer [01:02] The "Maintainer" field in a package's information (debian/control) should indicate the Ubuntu team responsible for the Ubuntu specific changes to a package (often the !MOTU for !Universe packages). The original maintainer is preserved in the field "XSBC-Original-Maintainer". [01:02] https://wiki.ubuntu.com/DebianMaintainerField [01:02] !MOTU [01:02] motu is short for Masters of the Universe. The brave souls who maintain the packages in the Universe section of Ubuntu. See http://wiki.ubuntu.com/MOTU [01:02] !Universe [01:02] The packages in Ubuntu are divided into several sections. More information at https://help.ubuntu.com/community/Repositories and http://www.ubuntu.com/ubuntu/components - See also !EasySource [01:03] HM [01:03] that bot is cool [01:04] rjmyst3: you should write a man page for wxFormBuilder [01:04] rjmyst3: yeah [01:04] there is a man page [01:04] ah [01:05] in the source tree, it is in install/linux/data/wxformbuilder.1 [01:05] rjmyst3: I will check out the program tomorrow. Right now I am tired (02:00 here) [01:05] (or something) [01:05] but the .deb puts it in th right place [01:05] mok0: sounds good, thanks for your help [01:05] * mok0 is just browsing the source on revu [01:06] rjmyst3: my pleasure :-) [01:09] ScottK2 or mok0: there is no debian package - my ubuntu package is the first [01:09] what should the Maintainer field say? [01:10] Maintainer: Ubuntu MOTU Developers [01:10] "Ubuntu MOTU Developers " ? [01:10] ok [01:10] ... and put your own name in XSBC-Original-Maintainer: [01:10] name [01:11] ok [01:12] while i'm in the control file, should I use the VCS-Browser and VCS-svn fields? - are they worthwhile to anyone? still too new? [01:12] rjmyst3: no [01:12] ok :) [01:12] rjmyst3: they are special to Debian [01:12] oh! [01:12] ok [01:13] rjmyst3: it has to do with the code management system DD's use [01:13] ScottK2: around? [01:14] mok0: ok, the debian policy manual did not make that clear [01:14] rjmyst3: heh, no [01:14] mok0: they implied that a tool like GDebi would show the URL for the end user [01:14] rjmyst3: there's a lot of info on wiki.ubuntu.com, it has a search function [01:15] mok0: lol, i am sufficiently rebuked [01:15] rjmyst3: I don't know too much about how it works [01:15] rjmyst3: hehe [01:16] rjmyst3: I don't know if the Ubuntu developers have similar fields. They use bazaar for code management [01:17] mok0: it didn't look like the fields would be particularly useful to me, i'm just trying to do the right thing [01:17] nxvl_work: Sort of === Ubulette_ is now known as Ubulette [01:17] rjmyst3: I understand [01:18] ScottK2: about the libdb4.2, i only need to check is the packages build, didn't i? [01:18] nxvl_work: No. It's more complex as some are affected by on disk DB format changes. [01:19] So for upgrades, the format change needs to be detected/handled. [01:19] ScottK2: so they may build, but not work as spected? [01:19] Yes [01:20] mm, ok ok [01:21] * mok0 wishes the distribution was not encoded in changelog [01:21] nxvl_work: I wrote the upstream of onak earlier today and he's got dealing with it on his TODO list. [01:22] mok0: It has to be somewhere in the source package to get into .changes. [01:22] i have already change some of them, also correct a mistake you make on the wiki, openldap2.3 was listed 3 times [01:22] ScottK2: Yes but it could be in a separate fiel [01:22] file [01:22] nxvl_work: Thanks for fixing. [01:23] mok0: Yes. Lots of arguing about future source package formats in Debian recently. [01:24] ScottK2: i also make the changes on some of them and listed the LP bugs on the wiki [01:24] ScottK2: I am in the process of building a bunch of my packages for hardy, and it's a drag to have to go in and edit the changelog [01:24] mok0: dch -r can probably solve that for you. [01:25] ScottK2: I'll give it a look. But in principle, it should be possible to tell the ppa to compile the same source packages in the new distribution [01:26] True. [01:26] I have to do it every 6 months.. :-( [01:27] Get them into the official repositories and it's automatic. [01:27] ;-) [01:27] :-D [01:28] That's the plan, of course [01:29] Seems like you're making decent progress on that. [01:29] ScottK2: yes I am quite happy [01:29] I still have 3 sitting in revu, though [01:29] I worried they won't make it for hardy [01:32] Well, time for bed. G'night, everyone! [01:36] nxvl_work: You didn't need to file that openldap bug. For that, efforts are already underway. It's the others I'm worried about. [01:36] heh, i have already file and patch the 2 openldaps :P [01:37] ScottK2: which ones? [01:37] btw [01:37] how would it be with libdb4.2-ruby? [01:37] doesn't need to be upgraded the whole package? [01:39] nxvl_work: There are performance issues with migrating openldap. [01:40] * slangasek links the Debian and Ubuntu bugs... [01:40] hi everyone! What does this mean: Add LP: #xxxxxx, where xxxxxx is needs-packaging bug [01:40] lidbd4.2-ruby will get removed when 4.2 goes. [01:40] It is in my REVU review [01:40] ScottK2: so it need to be move out the list [01:41] Legendario: which is the bug number on LP of your request' [01:41] ? [01:45] nxvl_work, I guess I got it. But i can't find it on LP [01:46] Legendario: what's your lp page? [01:47] nxvl_work, ~kemelzaidan [01:48] Legendario: you are packaging liberation fonts? [01:48] no, odfviewer [01:49] did you fiel the bug? [01:50] file* [01:50] is not on you assigned bugs [01:51] nxvl_work: It needs to be on the list. It's just being worked on already. [01:51] ScottK2: ok [01:52] Legendario: you need to file the bug and put that bug number on the changelog [01:55] ScottK2: so, i need to build them and test? or which are the steps it takes? [01:55] nxvl_work, found it: #95664. How should you write on the changelog. [01:56] bug #95664 [01:56] Launchpad bug 95664 in ubuntu "[needs-packaging] OpenDocument Viewer" [Wishlist,Fix released] https://launchpad.net/bugs/95664 [01:56] hmm, there's no libdb4.6-ruby? [01:56] you need to put at the end of the line (LP: #95664) [01:59] nxvl_work: It doesn't have to be at the end of a line. [01:59] slangasek: It's not like anyone actually uses this newfangled Ruby stuff, right? [01:59] scottK: it's a matter of style [02:00] nxvl_work: Then say "I consider it nice for it to be at the end of the line". It's not an actual requirement AFAIK. [02:00] nxvl_work, great dude. thanks a lot [02:00] are the kubuntu ppa's the preferred place for the kde4 packages for hardy? or are the official ones the regular again? [02:00] ScottK2: ok i will do it next time :D [02:00] the usage of ppas are really throwing me off :\ [02:01] joejaxx: I think for Gutsy. [02:01] joejaxx: for Hardy the archives, for gutsy PPA [02:01] joejaxx: But I'd ask in #kubuntu-devel [02:01] ok [02:01] or rather -backports is good enough [02:01] I can't remember [02:02] I think they're waiting for 4.0.1 to fix backports, but I don't recall for sure. [02:03] ah [02:03] ScottK: well, I sure don't use ruby; and I don't know why you would want more than a single libdb-ruby at a time either :) [02:15] slangasek: Dunno, but I'd guessed so you could use a specific one if you needed to. [02:17] ScottK2: that's where half our problems with bdb have come from.. :) [02:39] polls done yet? [02:39] hah! nice! [02:40] nixternal: persia well done! [02:40] Congrats persia, nixternal. [02:40] What'd I sleep through now? [02:40] polls? [02:42] for MC [02:42] MC [02:43] oh, congrats, new people [02:44] indeed [02:46] Ah congrats persia, nixternal [02:52] congrats guys [02:53] congrats :P [02:55] I for one welcome our new MC overlords ;-) [02:55] * bddebian cowers in fear === asac_ is now known as asac [03:17] Congratulations persia and nixternal [03:17] Better you than me. [03:18] slangasek: I was just looking at the bdb docs on upgrading and it's, um, daunting. [03:25] * TheMuso goes to take care of those ttf-* sync requests. [03:28] umm, thanks :) [03:48] persia: at the next time of your convenience, can you take a look at clutch again? I'd really love for it to meet the FF deadline [04:02] ScottK2: unless you find references to transactions, the upgrade from db4.2 to db.4.6 reduces to "rebuild". :) [04:02] slangasek: Thanks. [04:15] kolab-cyrus-imapd goes on the painful list then [04:19] jabberd2 too [04:21] if we're lucky, some of the transaction-using packages that require handling already have handling in the package that just needs to have the version numbers bumped [04:32] one more question before going to sleep... what if the package i want to pack does not have a make file? [04:38] Legendario: It doesn't matter particularly. You just need to call whatever buildsystem the package has in debian/rules. [04:40] RAOF, what if it is a java program? Any difference? If I don't have a make file, how do i get to know the build dependecies? [04:40] Magic ): [04:41] I very rarely determine the build dependencies from a makefile, anyway :) [04:41] Legendario: Does upstream tell you what you need to build it? [04:42] RAOF, don't believe so... [04:43] An alternative question: *how* do you build it? [04:45] RAOF, what do you mean? [04:46] I mean: You get a source tarball from the website. How do you turn this into a program, and how do you install it? [04:48] RAOF, well usually i install it by "configure, make, make install" but this package doesn't have one... [04:49] Right. [04:49] So, the first thing you need to do is to work out how to build the source. [04:50] Until you can do that, you can't package it, obviously! [04:50] RAOF, they offer a .deb file on the site, but there is a request on LP asking to place it on the universe... [04:51] Legendario: The .deb file is useless. We don't do binary uploads, and the binary debs don't contain any information as to how to build them. [04:51] RAOF, what should i do? Ask the author to include a make file? [04:51] Are there source packages (as in deb-src) anywhere? Where is upstream? [04:52] They obviously can build their source. All you need is for them to share that state secret :P [04:57] RAOF, the source is on sourceforge. I guess there is only a source rpm, besides the tar.gz i've downloaded [04:58] There are other ways of building a project other than make; basically you need to find the "how to build this project" documentation. [04:59] RAOF, where can it be? [05:00] I don't know? On the project's website? [05:02] RAOF, thanks a lot. i'll see what i can do... gotta go to the bed [05:47] RAOF, I was going to switch to svn co's while fixing all the extra debugging stuff in the package and ran into issues with autotools. i'll let you know when i get gmyth resolved [05:49] superm1: If you want some autofoo smashing, I've unfortunately got recent experiecnce with it. [05:50] RAOF, well i'll push what i've got then thus far [05:50] perhaps you'll have some more ideas than I have [05:50] For reference, you're trying to check out svn, run autogen.sh, and make dist? [05:50] yeah [05:50] that's what the newer get-orig-source does in there now [05:55] Is there much value in pulling from svn? [05:55] a few fixes that appear may be necessary for trunk usage [05:55] * RAOF hunts for a web browser that doesn't crash as soon as I close a load/save dialog. [05:55] That seems reason enough. [05:56] and ease to add to trunk patches in the next months [05:56] by a simple new get-orig-source [05:56] Yeah. [05:56] i just uploaded all the trunk stuff today [05:56] I noticed, both on hardy changes and on my myth box ): [05:56] there is stuff that hasn't cleared NEW though yet [05:56] Hm. Not having a good day with smilies. [05:57] i dont want to be a pest, but i hope that archive admins ack the NEW packages sooner rather than later [05:58] i'd like to get the upgrade bugs for people ironed out before FF [05:58] if there are any [05:59] Where have you pushed the gmyth thingy to? [05:59] revu again [05:59] so whenever that revu cron job pulls it in [05:59] Ah, right. [06:00] Hm. What's the status of libgnomevfs2-mythtv WRT gvfs/gio? [06:01] well it just adds an extra handler for myth:// stuff [06:01] just like a uri handler [06:01] and didn't break anything when i used it [06:01] But GNOME is ditching gnome-vfs afaik. [06:01] still worked for now at least. [06:01] Yes, that's what I was referring to. Nautilus isn't built against gnomevfs anymore, right? [06:02] well one sec, let me see if its really gstreamer doing the legwork or if that gnome-vfs piece is necessary then [06:04] yeah totem uses that uri handler when you open a recording [06:04] and passes it on to the appropriate gstreamer handler [06:04] (which comes when gstreamer0.10-plugins-bad is rebuilt against gmyth) [06:05] get a cryptic message like this other wise : "The playback of this movie requires a MYTH protocol source plugin which is not installed." [06:08] Urgh. Autotooling in the build process is generally considered a Bad Thing (tm) [06:08] no you know what, i spoke preemptively [06:08] i had the wrong build installed [06:08] i'm gonna nuke that other upload for libgnomevfs2-mythtv [06:08] its not needed [06:08] You only need the gstreamer-mythtv source built & installed? [06:08] its already in the version we have in apt [06:08] Score! [06:09] ( just needs to be build against gmyth ) [06:10] Why is it += all the way through debian/rules? [06:10] you mean the get-orig-source? [06:10] Yeah; the variables for it. [06:11] that's just the way i do my get-orig-source targets [06:11] because in some apps i chain more lines together [06:11] and debug that way [06:11] doesn't break anything in the process [06:11] (It does the wrong thing, incidentally. It should get the latest version) [06:13] well not necessarily, if someone runs the get-orig-source 5 years from now on this package version, you dont want the latest version [06:13] you want the checkout that was associated with this package version [06:13] That would be a get-pkg-source target. Debian policy says get-orig-source gets the *latest* upstream version. [06:14] (I know that what you've got is useful, it's just not get-orig-source as defined by policy) [06:14] hmph. then i've been doing these wrong for almost a year :) [06:14] I'm sure I've had this discussion with someone here before. Possibly persia? [06:15] but incidently its a two line change in all the apps i use to add the proper rule and checkout either a revision or the latest [06:15] incidentally even [06:15] i'll keep that in mind whenever i'm touching up versions on stuff i've got up already [06:28] Wow. libcurl4-gnutls-dev brings in a big bunch of dependencies. [06:29] Shit. Here I am, waiting three weeks for a review of my package [06:29] only to have a debian developer come in and do the same package all over again [06:30] and in the process making mine obsolete [06:30] RAOF, somehow i had most of them already in my apt cache. sorry in .au :) [06:31] amarillion: That sucks. At least the package you're after should get in, though. [06:31] superm1: Hm. make distcheck fails. Awkward. [06:31] Yeah... but my days of work are practically wasted [06:32] amarillion, but you learned in the process more about packaging that can be applied to other packages hopefully [06:32] hehe, that's right [06:32] amarillion: Well, you've almost certainly learned something. And you can possibly contact the debian maintainer and offer to help maintain it. [06:33] Yeah... you're right. [06:33] Sorry, I just needed to complain a bit [06:33] Certainly. It *is* annoying. [06:33] We could perhaps mention that filing a Debian ITP can be a good idea. [06:34] Or, at least, that since we're going to suggest you get it into Debian anyway you should consider filing an ITP at the start of the process. [06:41] I knew there was a lesson in this somehow [06:45] superm1: You don't mind if I mangle get-orig-source/get-pkg-source into something I'd write? [06:45] RAOF, i'd be open to that [06:45] especially if its an improvement [06:52] Gah. [06:52] superm1: thanks for ipod-convenience :) [06:52] I don't much feel like wrestling with make tonight. [06:52] glad it works for you :) [06:52] superm1: just worked up the effort to jailbreak and am enjoying it [06:53] jdong, did you jailbreak into 1.1.3? [06:53] or 1.1.2 [06:53] superm1: I'd suggest that, rather than svn-exportng, you run a nice simple "make dist" [06:54] RAOF, okay. i'm going to trhow a little more effort at fighting this, but i might end up falling back to that [06:54] superm1: 1.1.3 [06:54] its gotta be somethign silly for why it wont build [06:54] jdong, any issues with ipod-convenience and symlink locations or anything [06:54] superm1: downgrade to 1.1.1, jailbreakme.com, installer.app now has a streamlined automatic 1.1.3 jailbreaker [06:54] since everything runs as the user mobile instead? [06:54] woah really? [06:54] superm1: yep [06:55] without any computer necessary? [06:55] superm1: right [06:55] wow that's incredible [06:55] superm1: only computer interaction was for the initial 1.1.1 [06:55] 1.1.2->1.1.3 too you know? [06:55] or only from 1.1.1 [06:55] superm1: see http://rupertgee.wordpress.com/2008/01/26/jailbreak-ipod-touch-113/ [06:56] superm1: I believe there's also a 1.1.2->1.1.3 jailbreak in installer.app, but I cannot say for sure [06:56] I haven't tested that path [06:56] if so, i'll be doing that shortly :) [06:56] superm1: at any rate, my only bug I noticed with ipod-convenience... [06:56] superm1: I was bold enough to try to do it all separately, so rhythmbox created a virgin ipod_control structure over sshfs [06:56] superm1: What build failure are you seeing? I've just run "./autogen.sh --prefix=/usr && make dist && tar xzvf gmyth-0.4.1.tar.gz && cd gmyth-0.4.1 && ./configure --prefix=/usr && make", and that worked. [06:57] superm1: ipod-touch-mount was not smart enough to detect this scenario and failed to alert me or correct it with a symlink [06:57] RAOF, really? right at autogen.sh it's failing [06:57] Hm. Not for me. [06:57] RAOF, i'll toy it a little more [06:57] maybe i've got a defunct pbuilder here [06:57] Possible. [06:58] jdong, patches welcome :) [06:58] superm1: haha, when are they not? :D [06:59] superm1: actually, I meant to link to http://rupertgee.wordpress.com/2008/01/30/ijailbreak-method/ [06:59] that method is a lot more streamlined [06:59] yeah it is [07:00] no mentions of 1.1.2 ways though [07:00] superm1: I see in installer.app a 1.1.2->1.1.3 entry [07:00] superm1: idn how well it works though :D [07:00] well worst comes to worst, i'll have to dig up a windows disk and setup a vm then to fix things [07:00] but i'm really interested to try this [07:01] i'm gonna run to the car and grab my touch [07:01] superm1: yeah, I'm sure you can do it all from the iPod with a bit of ingenuity [07:01] superm1: Have you by chance included the patch from the pulseaudio site to make mythtv's alsa output work with the alsa pulse plugin? [07:01] superm1: as far as I can tell, the 1.1.1->1.1.3 thing is just a sh script using wget, dmg2iso, and a few other tiny hacks [07:01] TheMuso, it should be in trunk now [07:01] superm1: Ah ok. [07:01] TheMuso, i've had it in the gutsy and hardy builds for a while [07:01] superm1: Ok, just checking. [07:01] and it no longer applied when i switched to trunk today [07:02] TheMuso, pulseaudio and i don't get along though still [07:02] so i'm not able to test for sure [07:02] superm1: oh ok. [07:02]