[00:15] ScottK: I have patches ready but will wait for libclaw to be published so I can testbuild it in clean chroot (it's going to take less time for libclaw to be published then for me to configure pbuilder to use local repository) [00:21] kklimonda: OK. Thanks. Let me know. [01:17] persia: congratulations on the CC appointment [02:09] ScottK: btw, can you take a look at bug 663624? I'd rather not touch boost myself. [02:10] Launchpad bug 663624 in mumble (Ubuntu) "mumble FTBFS with GCC 4.5" [Undecided,New] https://launchpad.net/bugs/663624 [02:13] probably a wise choice [02:14] nice of you to link the patch though [02:14] * ajmitch will have to setup a natty pbuilder to test it out === jussi01_ is now known as Guest48460 [03:05] ajmitch: well, i did build both boost and mumble to see if the fix is correct - it's just that I'd rather not touch boost officially as I don't really understand it. === Guest71947 is now known as kklimonda_ [03:09] kklimonda_: who does :) [03:10] noone sane [03:10] kklimonda_: If no one touched boost without understanding it, the work would never get done. [03:10] ajmitch: I'd be interested in your opinion too. [03:12] ScottK: lol, true. [03:12] whats the change? [03:12] I ran into boosts build system and cried, some years ago [03:12] https://svn.boost.org/trac/boost/changeset/61467 [03:14] ScottK: I'm just doing a test build of it now [03:14] Cool. [03:15] * ScottK has been a bit distracted today trying to get a sewage leak in the house stopped and cleaned up. [03:15] It's just a "small" leak, but given the subject matter, even small is not minor. [03:15] not pleasant in any quantity [03:15] ugh [03:15] ScottK: hope its gone soon [03:16] anyone seen keybuck lately? we so need to get this new release of lvm2 into the repos.... I just did a test dist-upgrade to natty after making a snapshot... reboot... looks good... schedule the snapshot to be merged back in, reboot, and I'm back in maverick [03:16] ScottK: ajmitch: I've read the aptch, bug and bugzilla discussion [03:16] it all scans for me [03:16] lifeless: Should be. The "flow" is stopped and the first round of contractors to start the cleanup were here today cutting holes in walls and ripping stuff out. [03:16] I can get thumper who is more of a C++ head than I to eyeball too if you need, but I don't think thats needed. [03:17] As long as I can say "It's lifeless' fault" I'm happy. [03:17] hah [03:17] sure [03:17] it looked sane enough, with what rusty C++ knowledge I have [03:18] ajmitch: Hey, you're our boost expert. You fixed the last one. [03:18] if that makes me an expert, then we're all doomed [03:21] No. Doomed would be if it were me. [03:24] Nice. Gizmod FTBFS due to not being explicitly linked to boost_system. Turns out it's CMake doesn't even test for it's presence. [03:24] Sigh. [03:31] ScottK: do you want to be the person that touched boost last, or shall I brave an upload? === soren_ is now known as soren [03:42] eww... makes me glad I "only" had a water main leak and had to replumb the whole house recently [03:47] ajmitch: Please upload. [03:58] * ajmitch would love to have the laptop not sound like it's taking off when compiling boost [04:00] * psusi still needs to get someone to review and/or sponsor launchpad.net/e2defrag [04:03] psusi: I'd suggest putting it on revu, but that would require us to actually review it on there :) [04:04] isn't that dead? ;) [04:04] no, just pining for the fjords :P [04:05] well I'd like SOMEONE to review my packaging, so I can make sure I have things down before it's uploaded to universe and I might actually become a motu myself to continue to maintain it ;) [04:06] and it seems that the most interested person, jdong, is too busy these days [04:07] Is it up on revu? I'll give it a once-over. [04:07] no, but it's on launchpad [04:07] launchpad.net/e2defrag [04:07] first thing I'd question is whyt is it a native package? [04:07] because there is no upstream ;) [04:08] not a good enough reason :P [04:08] it was abaonded decades ago and finally dropped from debian and ubuntu I think in 8.04 or 8.10 [04:08] isn't that what native packages are for? is packages with no upstream? [04:08] consider the forking from the old upstream & packaging it in debian/ubuntu as separate activities [04:09] no, it's for packages that would be tightly tied to the distro [04:09] Native packages are for software that doesn't make sense outside of Debian/ubuntu. [04:09] e2defrag seems like it would be useful on any distro & you shouldn't have to do new 'upstream' releases to fix some packaging bugs [04:10] psusi: you aren't listed at all in debian/copyright? [04:10] RAOF: ajmitch: does that include packages that contain upstream stuff but there's no upstream tarball [04:10] hrm.... [04:11] * ajmitch doesn't know what sort of copyright notices you'd put in the source when you've heavily modified it [04:11] micahg: How does that happen? If you're packaging from VCS you generally just create an “upstream” tarball. [04:11] but why should I avoid keeping the proper packaging stuff in debian/ in my upstream release? I just don't see any advantage to that other than allowing me to make more upstream releases WITHOUT uploading new revs to Ubuntu... which I see no reason to bother doing [04:12] RAOF: I'm specifically thinking of thunderbird-locales (which is the upstream xpis + packaging) [04:12] micahg: It should probably not be native. Ship the upstream xpis in a tarball? [04:12] I suppose I could add myself to the copyright file... [04:12] psusi: It's also painful for downstreams that then have to rebuild the entire tarball for trivial changes. [04:13] (which is why we like it when Debian doesn't do this to us) [04:13] RAOF: that's what it was before, but I thought since there's no upstream tarball that it shoudl be native [04:13] having debian/ in the upstream tarball isn't quite as painful as it used to be [04:13] micahg: Nope. You just create an upstream tarball in those cases. [04:13] micahg, that's exactly what I figured [04:14] fairly sure that the 3.0 source format allows proper file deletion now [04:14] RAOF: k, it seems I received wrong information before :), I'll fix it for Natty [04:16] so other than it being native, anything else? [04:17] export DH_COMPAT=4 [04:17] that's somewhat old :) [04:17] and if I were to fix that... do I need to remove the debian/ directory, or can I just make a .orig.tar.gz with an empty diff? [04:18] hehe... well, yea... the package is from the 90s ;) [04:18] it shows - quite ancient build-depends [04:18] I couldn't even find an original upstream tarball source... it was only kept alive afaics in debian for many years [04:19] I hope that we've got rid of autoconf2.13 & automake1.4 in natty [04:19] auto* causes me much consternation [04:19] they're caollectively called autohell for a good reason [04:19] psusi: Is the description accurate? [04:20] RAOF, what do you mean? [04:20] *HIGHLY EXPERIMENTAL* do not use on a filesystem that you care [04:20] 13 [04:20] about as it likely will destroy it. [04:20] If that's accurate, do we even want it in the archive? [04:20] If it's inaccurate, it should be removed :) [04:20] RAOF, yea... it directly manipulates the block device, so quite possible it can trash the fs [04:21] RAOF, that said, I am fairly satisfied that it is working enough for people to test on unimportant or recently backed up filesystems.. I fixed all the bugs I could find so... [04:21] but that doesn't mean there aren't others I didn't find [04:22] So, there are no *known* data-eating bugs? [04:22] correct [04:22] How safe is it with respect to error handling? [04:23] not at all ;) [04:23] if anything goes wrong, your fs is likely toast ;) [04:23] hence the warning [04:23] can you make it work with a slightly modern version of automake? [04:24] Does it duplicate that warning on startup? [04:24] hrm... I dunno... I still don't really know much about autohell ;) [04:24] RAOF, no [04:25] It may be obvious that I think that it should :) [04:25] [04:25] there look to be about 12 source packages in the archive that still build-dep on automake1.4, it'd be nice to not increase that number :) [04:27] hrm... I also still need to figure out how to interface with initramfs-tools to get an alternate initramfs built so you can have a grub boot option to do a defrag of your root fs [04:27] So, it seems like, at this current stage, it's only really useful for developers? [04:28] no... it's useful for anyone who wants to defrag their fs... [04:28] and risk having it chomped [04:28] As long as they don't care about their data. [04:28] exactly [04:28] of course, EVERYONE makes regular backups right? right? ;) [04:28] though it wouldn't be the easiest thing to get testers for [04:30] it might be worth mentioning that when combining the ureadahead pack file list with a good defrag, I was able to get my boot time on a rotational disk down to the 10-12 second range ;) [04:30] by placing all of the files read during boot in order at the start of the disk [04:31] right, then you can promote it in flashy lights on the fourms, omgubuntu, and other places where speed addicts like to congregate [04:31] hehe [04:31] good way to get some testers [04:31] yea... with the big flashing warning BACK UP YOUR DATA YOU FOOLS! ;) [04:32] do you have it available in a PPA? [04:32] eventually I'd like to get it to the point that you can just choose an alternate "optimize" boot option from the grub menu every once in a while that will automatically run a defrag and pack all of the boot files at the start of the disk with the ureadahead list [04:32] yes [04:33] to get to that point, you'd need to convince everyone that it was stable [04:33] that reminds me, I still need to get keybuck to review my ureadahead changes... [04:34] * ajmitch would just like a boot time under 1 min or so :P [04:34] to get it there as a default, sure.. but for those brave/wreakless individuals willing to test it now... hehe ;) [04:34] 1 minute? really? [04:34] maybe a slight exaggeration [04:35] I get like 30 seconds on my slow ass 1 ghz netbook with a default install [04:35] but I've got apache, postgres, other tools installed [04:35] ahh [04:35] they can all add on a bit of time [04:35] how do your bootcharts look? [04:35] no idea [04:35] lots of IO wait time, or cpu pretty much maxed? [04:36] well, if it's IO bottlenecked, a defrag pass with the ureadahead list as input can help a good deal [04:36] probably lots of IO wait time, but I've never looked at bootchart stuff on this laptop [04:36] being a laptop, I believe the hard drive is 5400RPM [04:37] yea.. [04:37] looks like it is from the model number [04:37] I ran it on my netbook and I think I got the boot time down to around 25 seconds... but it's a 5400 rpm drive and only a 1 ghz cpu so it's pretty much cpu bound at this point [04:38] 2.8ghz c2d in this [04:39] then I made some modifications to ureadahead to suck out that 1 second or so of almost 0 disk throughput that is typical for most people [04:40] lots of time staring at blktrace output... [04:41] and debugfs [04:51] * ScottK is learning about how a lot of different build systems specify linker options. [04:52] * ajmitch wonders how many packages just be rebuilt after this boost fix gets uploaded & built [04:53] I'm glad I've got a 3-day weekend coming up [04:54] ok, so if I want to make e2defrag not be a native package, what do I have to do? establish a baseline upstream .orig.tar.gz that does NOT have the debian/ in it, and then add that when packaging it? [04:55] psusi: that would be the preferred option [04:55] I just hate to take something out, only to put it back in.. you know what I mean? [04:56] I can understand that [04:56] so assuming everything in debian/ is pulled out and only added with the .diff.gz, do you see anything else wrong? [04:57] * ajmitch has only taken a quick look for obvious problems so far [04:57] I'd prefer it if the packaging were updated to use tools from this century :) [04:58] it may be possible to simplify it a lot by using debhelper 7 [04:58] what do you mean? [04:58] your debian/rules is a lot of boilerplate text [04:59] it may be simplified to a 3-line debian/rules [04:59] eg http://kitenet.net/~joey/blog/entry/cdbs_killer___40__design_phase__41__/ [04:59] really? [05:00] possibly :) [05:00] having the usual case be this simple is a good thing [05:00] k... I'll have to read that and see if I can apply it when I'm sober ;) [05:01] heh [05:02] now where is sjr hiding? he always seems to vanish from irc for a few weeks after a new release... [05:02] need to talk to him about some of these ubuntu quilt patches to lvm2 I disabled or modified and my modifications to ureadahead [05:04] because being able to revert borked updates is one of the coolest features I've seen in some time [05:06] and bloody hell, I need to get the new rev of gparted going that can supposedly properly understand dmraid disks without you first installing kpartx [05:06] that one has been on my todo list since 2005 === Guest48460 is now known as jussi [08:13] good morning! === dholbach_ is now known as dholbach === debfx_ is now known as debfx === Lutin_ is now known as Lutin [09:54] hi, i'm not quite sure how the MOTU acceptance process works, but I have a couple of packages in my PPA and am looking for approval. could anyone please help? [09:56] Just needs two folk to review and like your package. We generally encourage folk to post something ready for upload directly into Ubuntu on REVU, and post a URL here asking for a review. [09:56] We generally discourage anyone from posting a URL too frequently (more than once a day or so). [09:56] would two URLs now be okay? [09:56] And be prepared for some folk to be busy or otherwise ignore it. [09:56] Sure, but advertise your packages. Describe them in a way that gets people excited. [09:57] You want to end up with a developer who looks at it because they want it working, rather than just having it be out there. [09:57] hm, i'll probably copy the description from my website, with a bit more spice ;D [09:57] delan_: you could also try to get your package into Debian and get it synced to Ubuntu afterwards [09:58] hi, anyway know how to whip the whole disk with zero very quickly, (except dd if=/dev/zero of=/dev/sda, that's so slow) :) [09:58] but I'm not sure if Debian accepts new packages right now because of their freeze [09:58] s/anyway/anyone/ [09:58] raywang, afaik that's the fastest... [09:58] geser, that's true, though i'm 'afraid' of venturing outside of Ubuntu ;) [09:58] three years using Ubuntu and nothing else [09:58] delan_, if I wipe out 160GB, how long will it take? [09:59] raywang, let's assume an average write speed of 50MB/s [09:59] that's 3200 seconds, which is almost an hour [09:59] delan_, can it be 50MB/s? [09:59] raywang, test it by doing: [09:59] I doubt :) [09:59] delan_: Ubuntu largely comes unmodified from debian. universe packages that are ubuntu-only tend to get neglected. If you want to take care of your own package, Debian is a good option (probably the recommended one) [10:00] raywang, my caviar green (slow, 5400rpm) can do 60MB/s write easy [10:00] raywang, What are you seeking to accomplish? zeroing won't block data recovery [10:00] persia, yes, that's what I want [10:00] geser: yes, the Debian NEW queue is currently backed up (got a package in there > 2 months) [10:00] tumbleweed, where should I find specifics to the debian repositories and how to attempt acceptance? [10:00] My possibly faulty understanding is that ftpmasters aren't processing NEW until squeeze releases. [10:01] persia, just want to capture the whole data without noise in the future. [10:01] delan_, how do you test the write speed? [10:01] raywang, [10:01] uh [10:01] persia: that wouldn't suprise me although I haven't seen it announced [10:01] dd if=/dev/zero of=whatever.file bs=512 count=2097152 [10:01] raywang, that'll write a 1GiB file and print the speed [10:01] ok [10:01] Actually, I was thinking that now would be a good time to just work with Ubuntu as Natty has just started [10:02] delan_, is there any application to do this in fast way? [10:03] raywang, that's my favourite [10:03] if you want, you can write a shell script like this: [10:03] #!/bin/bash [10:03] dd if=/dev/zero of=whatever.file bs=512 count=2097152 [10:03] rm whatever.file [10:03] that'll test, print speed and delete the file [10:03] probably best to stick the temporary testing file in /tmp [10:03] ok, but wipe the disk out is just dd if-=/dev/sda of=/dev/sda? [10:04] no [10:04] if=/dev/zero of=/dev/sda [10:04] delan_, oh, ? is just question mark. ;) [10:04] delan_, Now is an excellent time to work on Ubuntu: we just aren't really organised in a way that tends to encourage entry of new code: this team focuses on improving the quality of stuff nobody else is looking at. Most of the other teams focus on preparing specific flavours of Ubuntu. [10:05] to indicate, that was my question. :) [10:05] raywang, i know. you made the mistake of doing if=/dev/sda, when it should be if=/dev/zero [10:05] delan_, oh, my bad. :) [10:05] persia, so, in effect, bug fixes? [10:05] typo [10:10] does anybody know why quilt complains that a patch has been previously applied when it's not? http://pastebin.ubuntu.com/516334/ [10:12] hm, i've uploaded, but it's not on the list. might have to be approved first, hint hint ;D [10:16] actually, it's appeared now. all is fine. [10:24] so, the two packages are at: [10:24] http://revu.ubuntuwire.com/p/getbooru [10:24] http://revu.ubuntuwire.com/p/mathtext [10:52] delan_, Indeed, and for this team, updates to unmaintained packages. We've a list at UEHS. [10:52] !uehs [10:52] Grrr... [10:52] http://qa.ubuntuwire.com/uehs/no_updated.html [10:52] There's 100 packages that need review, update, cleanup, etc. [12:14] the build queue seems slow today, 14 hours to build my package [12:22] adhorden, It's generally slow as releases open. This release is faster than normal, as there's less coming in from Debian. [12:27] hi [12:27] I have been testing locally with pbuilder, but the packages I am working on have dependencies that I am also building packages for, what's the best way for pbuilder to get these dependencies inside the chroot? [12:28] to get vim from debian into ubuntu I should first extract ubuntu changes, then grab latest debian and check which ubuntu changes still apply, then create new source package for ubuntu, build it and then give for review/sponsor? [12:44] adhorden: Use pbuilder login with --save-after-login, install the packages, and then exit. Don't forget to reverse the process later so your pbuilder will be clean for other uses afterwards. [12:45] adhorden: other way is to make local apt repository with your packages and add it as OTHERMIRROR for pbuilder [12:45] hrw: Yes, but if you look at merges.ubuntu.com there should be a draft package ready that is 'pre-merged'. You can use the grab-merge script in ubuntu-dev-tools to grab the relevant bits. [12:45] hrw, Roughly, yes. I think geser was working on that: there may be an opportunity to collaborate. merges.ubuntu.com has some handy prepared stuff (last common ancestor, both source packages, an attempt at an automated merge) that you may find helpful. [12:46] thx guys [12:47] persia, hrw: yes, I'm working on the merging vim [12:48] geser: did you got debian version built at all? it fails on test here [12:48] hrw: I'm almost done, I've included the remaining Ubuntu changes into a new package (and forwarded some of the remaining Ubuntu delta to Debian) and I'm currently waiting on the Debian vim maintainer to help fixing a FTBFS with gcc-4.5 in natty [12:51] hrw: with a "buffer overflow"? yes that's the problem I'm waiting on getting fixed. The resulting binary doesn't work at all because the glibc catches an strcpy that will overflow on purpose [12:52] geser: same [12:52] geser: trying HEAD of vim hg repo now [12:53] geser: 7.3.029 in other words [12:54] debfx: Thanks for taking care of ball. [12:54] (now you can tell what my bug mail latency is at the moment) [12:56] maco: Would you be up for looking into Bug 660363 and seeing if an SRU is appropriate? [12:56] Launchpad bug 660363 in python-qt4 (Ubuntu) "python-qt4 4.7.4 breaks git-cola" [Undecided,New] https://launchpad.net/bugs/660363 [12:56] hrw: unlikely that it will succeed as http://code.google.com/p/vim/source/browse/src/structs.h didn't change since August (the di_key[1] and similar are the problem) [12:57] ok [12:57] hrw: sort of workaround is to build with -O0 or gcc-4.4 (I don't understand why disabling optimization makes gcc-4.5 not catch that "buffer overflow") [13:02] geser: right - same problem [13:13] -O0 seems preferable to 4.4, if that's the only choice. [13:14] If one picked 4.4, it would at least force the issue to be re-addressed later. [13:15] according to the Debian vim maintainer this is a problem with -D_FORIFY_SOURCE=2 and the vim Makefile forces it to < 2 but he overwrites that with CFLAGS in the packaging. He is going to fix it [13:15] Oh, that's a better solution indeed. [13:17] Agreed. [13:18] ScottK: I have prepared a fix for plee-the-bear (bug 663485), built it in natty pbuilder, installed and ran on maverick (as I don't have a natty vm yet). Haven't had any problems [13:18] Launchpad bug 663485 in plee-the-bear (Ubuntu) "plee-the-bear FTBFS with GCC 4.5" [Undecided,New] https://launchpad.net/bugs/663485 [13:19] kklimonda_: Sounds good. I'll have a look. [13:24] geser: ping, I got a mail from you, but its in some language other than English! [13:24] bilalakhtar: german? ^^ [13:24] probably [13:24] silly website === ivoks_ is now known as ivoks [13:25] it's a call for votes for the vacant developer membership board seeat [13:25] -e [13:25] I know, CIVS sent out german mails because my preferred language in my browser is german :( [13:25] Followup to the -devel thread would probably be appropriate [13:25] Oh, right. I just noticed that this mail is in german =) [13:25] * sebner waves at geser [13:26] Laney: ah, there you are, you are also an applicant, right? [13:26] Laney and bdrung :) [13:26] apparently so. :) [13:26] but the website when one follows the link is in English right? [13:26] yes [13:27] * persia waits for the day that !en becomes a factoid sending folk to #ubuntu-uk because the channel expects folk to write in German :) [13:27] !en [13:27] The #ubuntu, #kubuntu and #xubuntu channels are English only. For a complete list of channels in other languages, please visit https://wiki.ubuntu.com/IRC/ChannelList [13:28] persia: its already a factoid :) [13:28] !uk [13:28] Join us for a discussion using the Queen's English in #ubuntu-uk [13:28] hehe [13:28] lol [13:28] pip pip [13:28] Tally ho! [13:28] Neither of those are in the same class as !de [13:28] !de [13:28] In den meisten ubuntu-Kanälen wird nur Englisch gesprochen. Für deutschsprachige Hilfe besuchen Sie bitte #ubuntu-de, #kubuntu-de, #edubuntu-de oder #ubuntu-at. Geben Sie einfach /join #ubuntu-de ein! Danke für Ihr Verständnis. [13:28] * popey fires up google translate [13:29] !za [13:29] hmm, we should add one [13:29] .!learn za is ... [13:29] !sa [13:29] For the Saudi Arabia team : /join #ubuntu-sa : للانظمام الى قناة الفريق السعودي - For Arabic language support, please : /join #ubuntu-arabic : للحصول على الدعم باللغة العربية [13:29] COOL! [13:29] I doubt our IRC channel can support all 11 official languages... [13:29] tumbleweed, heh. [13:29] Anyway, folks playing with the bot ought do it in /msg [13:30] tumbleweed: you can add it yourself, but it would have to be approved by jussi01 [13:30] bilalakhtar: there's nothing to add - we don't have any regular trickle of south africans asking for help in non-za channels [14:10] http://proxy.lib.sun.ac.za:8800/open-access/ [14:10] our university is going opensource [14:11] live video stream of the event === 92AABEL1U is now known as ximion [14:19] openaccessstb: "resource unknown [14:27] geser: heh, I'm not sure whether I voted correctly. List shows: 1. other 2. Ian 3. Benjamin. All 3 options has got value '3'. I chose Benjamin with value 3. is it correct? [14:28] ari-tczew: you should have changed the values: your first choice should get the 1, the second choice the 2 and so on [14:29] ari-tczew: Just rank them , ^^ is right way [14:29] choice with the same value are equal [14:29] * bilalakhtar voted for bdrung [14:29] geser: ehh :/ could you reset my vote and send me new link? [14:29] sorry, I can't [14:29] Anyone got a suggestion - using sbuild to test build and it runs invoke-rc.d: initscript gdomap, action "start" failed. Which fails the sbuild [14:30] brb, have to reboot after updates [14:31] geser: did someone DMB member leave a team, or is it a place for new member? [14:33] ari-tczew: nixternal left a couple months ago, but till now nobody set up the vote (the call for nominees is some weeks old already). So I volunteered to set it up (my first vote) with the known german/english mail :) [14:34] ah, nixternal left? when? [14:34] geser: ^^ [14:34] He attended the September 14 meeting, IIRC [14:34] hmm, I remember that he did a vote for me. [14:34] yea [14:34] Date: Mon, 12 Jul 2010 11:13:11 -0500 [14:35] he helps out sometimes till we find a replacement for him [14:35] aha [14:36] and why did nixternal drop out from UCC? Any idea? [14:36] bilalakhtar: UCC? [14:37] sorry, no idea. But I guess the same reason as from DMB. [14:37] ari-tczew: Ubuntu Community Council === bilalakhtar_ is now known as bilalakhtar [14:37] ari-tczew: Did I answer your query? [14:37] bilalakhtar: geser did that. [14:38] ok [14:56] sladen: btw OpenAccessSTB turned up in our loco channel again and pointed to http://oa.sun.ac.za/instructions.htm - but he didn't really mean his unviersity was going OSS, just Open Access (although they are have some decent-size dual-boot-Ubuntu labs) [14:56] (and that video stream is boring, even though digital repositories is my current research field) [14:57] oh sabdfl has a recorded segment that is about to play in that stream [15:13] ScottK: you're welcome [15:14] ScottK: do you know if boost can be built with threading libs other than pthread? [15:15] I don't. [15:16] the problem is that applications that use boost threads need to link to pthread [15:17] but I doubt unconditionally linking to pthread is the right way [15:26] kklimonda_: plee-the-bear uploaded. Thank you for your contribution to Ubuntu. In the future, there's no need to mention the maintainer change in debian/changelog. [15:44] * chrisccoulson_ must remember to review debfx ff-4.0 merge request for KDE this week [15:46] ScottK: ok, noted :) [16:24] hi all, I have been working on a package for msp430-gcc, a cross compiler based on gcc for the msp430 arch, problem is I keep getting: cd /tmp/buildd/msp430-gcc-4.4.4/debian/msp430-gcc && /usr/bin/make install [16:24] make[1]: *** No rule to make target `install'. Stop any ideas? I checked the paths and they look fine, the rules is here http://paste.ubuntu.com/516877/ thanks [16:24] configure runs in the correct location as well as make [16:40] you sure that the upstream makefile has an "install" target? [16:44] its essentially gcc with a patch applied, so I would hope so and according to the gcc manual make DESTDIR=path-to-rootdir install [16:45] hmm [16:48] I can build it fine from source using essentially the same commands as the ones in the rules files to ensure I did not do something stupid, so I know make install works fine from testing the patches worked before working on the package [16:55] Hi all. How do I go about getting a package upgraded? Debian is on the older one as are we [16:55] xteejx: helpl Debian release squeeze :) [16:55] Latest release of said package was 8th Jan 2010 [16:55] xteejx: which package? [16:56] linthesia - the one we have has probs with libpango [16:58] actually the dev upstream one does too, just compiled it :( [16:58] xteejx: it's actually packaged, see debian 597189 [16:58] Debian bug 597189 in linthesia "Please package latest upstream version" [Wishlist,Open] http://bugs.debian.org/597189 === sebner_ is now known as sebner [16:59] micahg: Seems someone is working on it :) [17:00] bug 663962, it's annoying :( [17:00] Launchpad bug 663962 in linthesia (Ubuntu) "linthesia crashes with GdkGLExt-WARNING **: cannot load PangoFont" [Medium,New] https://launchpad.net/bugs/663962 [17:02] looking at the source, the error is with main_loop.run(window); [17:07] xteejx: if you're interested in an easy FTBFS, you might want to look at pybliographer [17:07] geser: I'd rather get linthesia working at the moment, but I'll take a look at that ftbfs later on :) [17:11] it's not urgent. I know how to fix pybliographer, but it's also a good one for any prospective contributor to gain experience [17:12] Ok geser, I will def look later on :) [17:12] I really wanna fix linthesia. I have dreams of music stardom lol [17:12] Does anyone know if someone from Ubuntu is attending the openSUSE conference, like sabdfl invited in his blog? [17:14] I found the problem!!!!!!!!! [17:14] that was fast [17:14] If the font for linthesia is set with gconf-editor to Serif it works perfectly [17:14] pango can't use the default Arial font === hrw is now known as hrw|gone [17:16] Anyone got a suggestion - using sbuild to test build and it runs invoke-rc.d: initscript gdomap, action "start" failed. Which fails the sbuild. This a sbuild problem? [17:18] who wants to run the initscript? a dependency or the package itself? [17:19] geser: looks like dep during dpkg configure. http://paste.ubuntu.com/516818/ [17:22] I don't about sbuild but in my pbuilder the initscript doesn't get started [17:24] Ok, I'm gonna generate a debdiff for linthesia and attach it, can anyone check it in a min please? [17:24] geser: yeah, figured as much. thanks [17:26] bug 663962, can anyone check everything's ok there for me please? [17:26] Launchpad bug 663962 in linthesia (Ubuntu) "linthesia crashes with GdkGLExt-WARNING **: cannot load PangoFont" [Medium,New] https://launchpad.net/bugs/663962 [17:37] xteejx: done :) [17:38] geser: Jesus christ!! that was quick!! [17:38] Thank you geser, I'll report it upstream to dev and debian in a bit [17:59] Reported upstream to Deb and dev === chrisccoulson_ is now known as chrisccoulson [19:32] lucas: is your merge script pointed to natty? [19:44] where can I find the class RevuKeyUpdater ? [19:51] ari-tczew: I think so [19:53] tumbleweed: i am around. i was at the Ubucon last weekend. [19:53] oh, right, you said something about that [19:56] how does one create a natty pbuilder environment? debootstrap doesn't seem to know about it. [host machine is lucid] [19:57] oh, i guess i can just fake it by creating a symlink in /usr/share/debootstrap/scripts/natty -> gutsy [19:59] * geser copies the pbuilder chroot and dist-upgrades it :) [20:00] geser: why wasn't you at the Ubucon? [20:01] ari-tczew: hi! have you looked at the gnustep stack yet? [20:01] bdrung: when and where was it? [20:01] DktrKranz: Hi. I'm sorry, nope. I'm busy till friday. [20:02] geser: last weekend in Leipzig. [20:03] ari-tczew: no big problem. If you want, I can give it a go myself, I've become used to do them lately :) [20:04] DktrKranz: would be nice! I'm not addicted to this package. I just work on reducing merges. [20:04] ok then, there will be a lot of work to do :) [20:05] geser: http://ubucon.de/ - there was only one Ubuntu developer and no Canonical employee. [20:05] bdrung: a little bit to far for me to get there for one day (or two) (and I was busy till Friday) [20:07] DktrKranz: good luck! [20:08] bdrung: I might be perhaps at OpenRheinRuhr in November (next to the German Ubuntu booth :) [20:09] geser: never heard of it. [20:10] geser: I've picked up the ftbfs on pybliographer - simple d/control fix I think [20:11] bdrung: it's rather small: http://www.openrheinruhr.de/ [20:11] xteejx: yes, you just need to figure what's missing :) [20:12] geser: gnome-doc-utils (>= 0.3.2) in build-dep [20:13] * ari-tczew counts that 47% of remaining merges include new upstream releases [20:13] xteejx: yes, but the version is unneeded as all supported Ubuntu (and Debian) versions have a newer one [20:14] geser: Oops :) hehe does it matter that I've put it in already? [20:15] It's ok I'll rebuild the source package [20:16] geser, please ignore my last email: I've just seen that you sent another email explaining the german email [20:18] fabrice_sp: at least I know that way that people are participating in the vote :) [20:18] :-) [20:22] bug 664108 complete [20:22] Launchpad bug 664108 in pybliographer (Ubuntu) "pybliographer FTBFS" [High,Triaged] https://launchpad.net/bugs/664108 [20:23] xteejx: have you checked that this fixes it? [20:23] xteejx: hint: gnome-doc-utils is not enough [20:28] geser: It builds perfectly fine locally [20:29] just adding that to the build-dep fixed it, tested build before, same failure, and with that in d/c it worked [20:33] * ajmitch wonders where this followup explanation about the german email is :) [20:37] Ich weiss es nicht lol [20:43] ajmitch: ubuntu-devel [20:43] xteejx: in a natty pbuilder? [20:44] geser: no in natty in a vm [20:44] natty is the vm [20:44] minimal vm or desktop? [20:44] desktop [20:44] geser: ok, was just thunderbird being hopeless & not telling me of new mail :) [20:45] xteejx: you might then have one of the other missing dependencies installed [20:45] xteejx: do you have pkg-config and rarian-compat installed in your natty vm? [20:46] huh?? [20:46] i dunno what they are [20:46] those are two other missing build-dependencies [20:46] oh :s [20:47] geser: I'll reinstall the vm, this shouldn't be happening [20:47] xteejx: or use pbuilder inside the vm [20:48] it doesnt work :( [20:48] brb [21:00] * fabrice_sp uses pbuilder in a vm in some cases [21:01] Is it not possible to build natty packages in maverick with pbuilder?? [21:01] of course it is [21:01] oh...why the hell am I running a natty vm then?? lol [21:01] specify natty as distribution in pbuilder params [21:01] * ajmitch is building natty packages on lucid [21:01] only you know the answer to that question :-D [21:01] * xteejx is so dumb [21:02] lol [21:02] it is useful to have a VM for testing though [21:02] thanks :) [21:02] not dumb, just working too hard for the simple answer. :) [21:02] jcastro: hahaha I like that one, I might have to use it in future ;) [21:03] Unrelated question: Is UDS going to be streamed? (I don't have much input, just want to see what happens) [21:03] audio streams always [21:03] video streams likely for the plenary sessions [21:03] jcastro: What are plenary sessions? [21:03] http://uds.ubuntu.com/participate/remote/ [21:04] the big meetings with everyone [21:04] Ohh I see :) [21:05] plus realtime discussion on irc as well [21:05] I don't plan on getting involved, another couple of years maybe ;) [21:06] why wait? [21:07] I don't see an intermediate user like myself has much to say to Canonical about where they're taking Ubuntu [21:08] everyone has a say in how things are done. whether they agree with you is another matter, but you can at least be heard :) [21:08] ajmitch: Hmm, I suppose so [21:08] sudo pbuilder cteate --distribution natty << will that work? [21:08] * ajmitch has been to UDS a few times now & didn't feel like he was ignored [21:08] I think it should work [21:09] If I typed it correctly I mean :P [21:09] Cool :) [21:09] xteejx: take a look at pbuilder-dist [21:09] I was going to say that :-) [21:09] I'll man it [21:11] micahg: That's pretty clever :) Thanks micah [21:12] xteejx: np [21:13] Does pbuilder remove any build-deps for the next build you do? [21:14] every build is done in a clean chroot [21:15] So it's just the base install then? [21:15] yes [21:15] Oh that's good, much easier than doing it in a vm [21:15] yep: the build build is tarball is used as a basis for the build each time [21:15] it does cache copies of build-dependencies, so you don't have to download them for every build [21:15] :) [21:16] xteejx: pbuilder uses a base.tgz (which gets created with "create" :) which gets unpackage before build, chrooted into, build-deps installed, the package build (or not) and thrown away afterwards [21:16] Andif the base files get updated, I just do pbuilder update ? [21:17] exactly [21:17] I think Mr Castro was right...doing things the hard way for an easy solution hehe [21:17] xteejx: for forwarding changes to Debian you could use command: submittodebian [21:17] yep :) [21:18] So another easy way instead of keep emailing them heh [21:18] xteejx: and also "pbuilder-dist natty update" to update the Packages files (for apt) *inside* the pbuilder (so it knows about updated packages) [21:18] I suppose with the repetitive stuff, things have to be made to make it easier :) [21:19] geser: I get it :D [21:19] Well this is definitely going to save time [21:19] xteejx: or send mail to bug tracker in the form: http://paste.ubuntu.com/517032/ attaching patch(es) [21:20] ari-tczew: I've been doing that, well without the tag bit :) [21:20] I use above mail template. It's easier for me than milion questions from submittodebian. [21:20] :D [21:21] or just do it manually if you like hard solutions :) [21:21] hahaha ;) [21:22] Is everyone here cheeky but funny? :P [21:22] no, I don't pretend to be funny [21:22] ;o [21:23] Well it's not working hehe [21:23] or is... [21:23] I hate double negatives, it always comes out wrong [21:23] xteejx: are you going to do another MOTU activities as well? [21:24] ari-tczew: I'm thinking of doing merges, have done 1 small bugfix (mostly luck with that one) [21:24] I don't know really, I suppose I'll see which way the feeling takes me :) [21:25] xteejx: we are looking for new contributors [21:25] ari-tczew: Well I definitely try to muck in and help how I can [21:25] within some days I'll start encourage on Polish forum to contribute to Ubuntu [21:26] I'm not Polish [21:26] xteejx: I just said where I want to look for new contributors. [21:27] Ohh, sorry, I didn't understand :) [21:27] xteejx: I noticed that there is a language problem in your communication. [21:27] * ajmitch should stir up some interested people in the loco channel :) [21:27] as few minutes ago [21:27] Mine? [21:27] My English is perfect [21:28] I was born and live here lol [21:28] heh [21:28] I'm just a little lazy with typing :P [21:29] Am I right in thinking that pbuilder builds the .dsc's? [21:29] xteejx: yes [21:29] ari-tczew: Thank you :) [21:35] If I make changes in the source, how do I create the .dsc to use pbuilder with? [21:36] xteejx: take a look at the options for debuild [21:36] micahg: Is it debuild -S - I just want to ask first before I mess it up [21:36] xteejx: debuild -S [21:37] xteejx: yeah, that'll make a source build [21:37] Thanks guys :) [21:37] you might want to add -us -uc if you don't want to get asked for signing it [21:37] Ok :) [21:38] "sudo pbuilder-dist natty build pybliographer_1.2.14-1ubuntu1.dsc" will test it right? [21:39] yes [21:39] I think I've got the hang of it now :) [21:50] geser: pbuilder is still saying gnome-doc-utils not found [21:50] I used debuild -S [21:51] xteejx: as I said, gnome-doc-utils isn't enough [21:51] look at the check before the check for gnome-doc-utils [21:52] ahhh pkg-config I didn't see that :) [21:52] you should see that it checks for pkg-config but doesn't find it [21:58] hmm - "/bin/sh: scrollkeeper-config: not found" maybe scrollkepper too [21:58] will have to check pkg name [21:58] yes [21:59] is it just scrollkeeper? [21:59] ahh its a transitional pkg [22:00] use packages.ubuntu.com to search which package contains such a named file (or use apt-file) [22:00] ok thanks geser [22:02] rarian-compat - apt-file, another thing being kept and used hehe [22:14] ScottK: sorry, I got distracted by a meeting at work as well this morning ;) [22:14] ajmitch: No problem. [22:16] bug 664108 updated and *really* fixed now :) [22:16] Launchpad bug 664108 in pybliographer (Ubuntu) "pybliographer FTBFS" [High,Triaged] https://launchpad.net/bugs/664108 [22:16] Slow hard drive. Still unpacking ... [22:17] * ajmitch would love an SSD to build on [22:17] * xteejx agrees with ajmitch [22:17] bang, done [22:17] xteejx: putting it in Build-Depends-Indep would be better [22:17] geser: Really? What's the difference? [22:18] Doing it now [22:19] in practice it won't make any difference for this package but Build-Depends are build-dependencies for arch-dependent stuff while B-D-Indep for arch-independent stuff [22:19] geser: Done [22:20] xteejx: you know that you can delete attachments from a bug? [22:20] so b-d-i would be more for python, i.e. xxx.yubuntuz_all packages? === 77CAAAKXA is now known as makl [22:20] Yes. Although anything needed for the clean rule to run goes in b-d and not b-d-i. [22:20] geser: I do now [22:20] Right, got it :) [22:21] xteejx: the last debdiff is now the same as mine (modulo the changelog entry) === makl is now known as ximion1 [22:21] geser: Woohoo, got there eventually ;) [22:22] as usual don't forget to forward it to Debian [22:22] And now I understand *why* it's like that, so it's win-win :) [22:22] geser: Yup, already on it ;) [22:22] will sponsor it tomorrow (if nobody beats me) [22:22] Ok no probs === ximion1 is now known as makl === makl is now known as ximion1 === ximion1 is now known as makl === makl is now known as ximion1 [22:36] ajmitch: Looks like it's not hard coded anymore, so a rebuild should do it. [22:37] yep [22:37] I'm just doing a rebuild locally after adding some patch header info [22:37] Cool. [22:37] won't be long before I upload & you can find & retry those build failures [22:41] xteejx: When you forward a bug to debian please link it to the lp bug. Also this one really should be serious in debian - FTBFS is RC. [22:42] tumbleweed: Oops. RC? [22:42] release critical [22:43] Oh, I didn't realise :S [22:52] Make sure it's FTBFS in Debian too. [22:52] ScottK: it does :) [22:52] ln -f -s 'libboost_python-py27.so.1.42.0' '/tmp/buildd/boost1.42-1.42.0/debian/tmp/usr/lib/libboost_python-py27.so' [22:52] looks like it's building with python 2.7 at least [22:53] still going of course :) [22:56] How do I set critical when filing a bug to deb via email? [22:57] xteejx: BTS is entirely e-mail driven http://www.debian.org/Bugs/ (I've bumped this ones severity for you) [22:57] xteejx: Debian actually has a larger range of Importance than LP, so you'll want to make sure it's actually critical [22:57] So do it manually on the site? [22:58] xteejx: there's a BTS cli utility if you have a mail server set up [22:58] micahg: I don't, and not sure how to do it [22:58] the initial severity, tags, etc are set in the top of the body of your e-mail (psuedo-headers). You can change them later by mailing control@bugs.debian.org [22:58] Too much messing around [22:58] Oh right ok :) [22:59] xteejx: you do run lintian, right? W: pybliographer: debian-changelog-line-too-long line 1 [22:59] ^ that's your entry [22:59] :( [23:01] Can I not just add + and paste it in? [23:01] xteejx: I fixed it on upload. But if I don't tell you about it, you'll never know [23:02] tumbleweed: Ok, I'll check the lintian errors in future, sorry about that [23:03] most packages already cause lintian to complain. You just want to check that none of the (potential) issues are a problem for us, and that you aren't responsible for any of them [23:06] tumbleweed: I understand :) [23:34] bug 664209, another ftbfs fixed, debdiff should be perfect now [23:34] Launchpad bug 664209 in basic256 (Ubuntu) "basic256 FTBFS" [High,Triaged] https://launchpad.net/bugs/664209 [23:49] What is the LDFLAGS for /usr/lib/libHalf.so.6 ? [23:50] xteejx: do you notice that the -dev package for that has a .pc file, you should use that [23:50] tumbleweed: I don't get what you mean [23:52] dpkg -L libilmbase-dev | grep pc <- that file will help you [23:53] tumbleweed: With that /usr/lib/libHalf.so.6 ? [23:53] dpkg -S /usr/lib/libHalf.so.6 says libilmbase6 [23:53] Ohhhh, I thought you meant the bug I filed, sorry not thinking clearly [23:54] So that package provides that file? [23:54] read up on pkg-config [23:55] I'm really confused, its cimg I'm doing now, it's a binutils-gold one [23:55] I thought we had to add the appropriate -lXXX ? [23:56] I haven't looked at this one, but presumaly they aren't using -lHalf like they should, and even the .pc file includes it, so they should probably be using pkg-config [23:56] I don't understand enough about this to know why, or even what it is/does [23:56] :( [23:57] libraries are sometimes a little complex to use, so some provide scripts to output th ecorrect CFLAGS and LDFLAGS to link against them. [23:57] pkg-config attempts to provide a common infrastructure for this [23:58] so pkg-config when used in a package automatically configures the correct flags? [23:59] $ pkg-config --libs IlmBase [23:59] -lImath -lHalf -lIex -lIlmThread -lpthread [23:59] of course not all libraries provide .pc files, and many are simple enough that they probably don't need to. [23:59] do you mean that IlmBase provides those linker flags [23:59] ?