[06:48] <dholbach> good morning
[07:07] <ronin___> dholbach: good morning
[07:07] <ronin___> dholbach: may i ask a question?
[07:08] <dholbach> ronin___, sure - but you can just ask everybody in here :)
[07:10] <ronin___> I love to remove esmaeil@esmaeil-Latitude-D630:~$ from mu konsole?
[07:11] <ronin___> Ok I ask this question from all
[07:11] <ronin___> how can i do that?
[07:12] <geser> ronin___: that's more a question for #ubuntu, but edit the variable PS1 in your ~/.bashrc
[07:12] <dholbach> have a look in your ~/.bashrc for the line with PS1 in there
[07:13] <dholbach> (save and "source ~/.bashrc" until you're happy)
[07:14] <ronin___> sorry all but anyone there didn't know unfortunately
[08:12] <tumbleweed> Laney: I put your UDD tables to use http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi
[08:41] <Laney> tumbleweed: nice
[08:41] <Laney> I can't get any results though
[08:43] <dholbach> tumbleweed, I marked the WI about harvest long descriptions as completed, although I know that a bunch of harvest-data feeds still need to be updated
[08:44] <dholbach> but at least it's fixed and working in harvest now
[08:44] <tumbleweed> Laney: hrm
[08:48] <Laney> tumbleweed: but e.g. select changed_by_name from ubuntu_upload_history where signed_by_name = 'Stefano Rivera' and changed_by_name <> 'Stefano Rivera'; works
[08:49] <tumbleweed> Laney: what are you searching for when you can't get results?
[08:49] <tumbleweed> dholbach: I saw, thanks. Sorry I never got anywhere near that one
[08:49] <dholbach> hopefully somebody gets around fixing the data feeds
[08:50] <Laney> tumbleweed: oh, wait.
[08:50] <tumbleweed> dholbach: you are aware that it's not currently possible to debootstrap oneiric? which might make the beginning of ubuntu dev week fun
[08:50] <Laney> do I have to fill in both fields?
[08:50] <Laney> I was expecting just giving a sponsor name to list all sponsorships
[08:50] <tumbleweed> that's easy enough to fix
[08:50] <Laney> or the other way around
[08:50] <tumbleweed> just put an * in for now
[08:50] <Laney> yeah. blank should be equivalent to that
[08:51] <Laney> works now, but shows me my own uploads
[08:51] <dholbach> tumbleweed, no, I wasn't - do you know what the issue is there?
[08:52] <tumbleweed> dholbach: bug 807974 (discussed in #ubuntu-devel earlier, and also on friday (but that might have only been #ubuntu-release))
[08:52] <dholbach> ugh :-(
[08:53] <tumbleweed> if it isn't sorted out, it'd be easy enough to provide some preprepared pbuilder chroot tarballs
[08:53] <dholbach> or for now just ask them to set up a natty pbuilder - I don't think we'll build many packages anyway - and subscribe to the bug
[08:54] <dholbach> tumbleweed, thanks a bunch for the heads-up!
[08:54] <tumbleweed> np
[08:55] <tumbleweed> Laney: I can add signed_by_name <> changed_by_name, but that'll probably miss some
[08:55] <tumbleweed> I assume the one comes from launchpad, the other from the changelog entry
[08:56] <tumbleweed> so they may not be the same
[08:57] <tumbleweed> anyway, done now
[09:04] <tumbleweed> Laney: including origin may be handy, it'd allow identification of syncs. I used to also be able to detect merges from the changelog entries, which can't be done from this data
[09:08] <Laney> yeah
[09:27] <jtaylor> tumbleweed: please ack bug 808688
[09:28] <dupondje> where does requestsync gets its newest version info ?
[09:29] <jtaylor> argh
[09:29] <jtaylor> forget that I filed a dup
[09:29]  * jtaylor must learn to read
[09:31] <tumbleweed> or I should just stay clear of things you've working on :)
[09:41] <Laney> bdrung: how did you get packaging-dev backported? did you ping someone?
[09:53] <papo> hello
[09:55] <papo> I am wondering what is affecting the inclusion of libclang. There is a clang package but for some reason the library was omitted, see bug 785665.
[09:56] <dholbach> directhex, ready for UDW later on?
[09:57] <directhex> dholbach, more or less, yeah.
[09:57] <dholbach> awesome! :)
[09:57] <dholbach> thanks directhex
[10:14] <geser> dupondje: from the Debian "mirror" on LP and/or rmadison (not sure about the first part as I didn't look for some time at the code)
[10:19] <dupondje> its behind a bit but ok :D
[10:19] <dupondje> dh clean --buildsystem=ruby --with ruby
[10:19] <dupondje> dh: unable to load addon ruby: Can't locate Debian/Debhelper/Sequence/ruby.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.12.4 /usr/local/share/perl/5.12.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.12 /usr/share/perl/5.12 /usr/local/lib/site_perl .) at (eval 23) line 2.
[10:20] <dupondje> but I can't seem to find ruby.pm anywhere ...
[10:21] <tumbleweed> dupondje:
[10:21] <tumbleweed> $ apt-file search Debian/Debhelper/Sequence/ruby.pm
[10:21] <tumbleweed> gem2deb: /usr/share/perl5/Debian/Debhelper/Sequence/ruby.pm
[10:22] <dupondje> weird
[10:22] <dupondje> jean-louis@laptop-jl:~/Ubuntu/ruby-tilt-1.2.2$ apt-file search Debhelper/Sequence/ruby.pm
[10:22] <dupondje> jean-louis@laptop-jl:~
[10:22] <tumbleweed> (that was on a debian box, it was what I had at hand)
[10:24] <geser> gem2deb 0.2.5 is in oneiric and published
[10:25] <geser> dupondje: do you have gem2deb installed?
[10:26] <geser> Contents-i386.gz  04-May-2011 05:34  19M (from http://archive.ubuntu.com/ubuntu/dists/oneiric/)
[10:27] <geser> dupondje: ^^ that explains why you can't find it with apt-file (or packages.ubuntu.com)
[10:27] <dupondje> heh ok :)
[10:27] <dupondje> it works with gem2deb installed indeed
[12:24] <jtaylor> urg mcrl2 implements c++ templates in a .cpp file, how did that ever compiel
[12:30] <jtaylor> stupid c++, started two make -j4 builds and now I'm swapping with 4gb ram :(
[12:46] <tumbleweed> dupondje: are you going to request a sync for archivemail?
[12:52] <jtaylor> triage 771014 please
[12:57] <tumbleweed> jtaylor: sounds like you should join bug control
[13:01] <dupondje> tumbleweed: it needs a separate requestsync bug ?
[13:01] <dupondje> :)
[13:02] <tumbleweed> dupondje: it doesn't need to be separate, but it does need to look more like a sync request. I modified it a bit
[13:02] <dupondje> oh ok :)
[15:50] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 1 to kick off in 10 minutes in #ubuntu-classroom
[16:20] <jtaylor> ncbi-blast+ seems hard, 20+ libraries and all are underlinked, probably simpler to just disable as-needed for that one
[17:05] <MysteriousMan> hello how to check if there is Internet connection using c++ ,,, dont  say system(ping -c1..) cuz it slow
[17:09] <Pici> MysteriousMan: ##C++ would probably be a better place to ask your question.
[17:10] <Pici> You'll need to be identified to join there though.
[17:10] <Pici> !register > MysteriousMan
 thanks
[17:24] <jtaylor> will gcc4.4 be included in oneiric?
[17:25] <micahg> jtaylor: I think the answer is yes
[17:25] <jtaylor> 4.6 4.5 and 4.4?
[17:26] <micahg> it seems that way, I asked a couple months ago and that's the answer I got
[17:26] <jtaylor> k thx
[17:50] <bdrung> Laney: no, i waited
[17:53] <Rhonda> hmm
[17:53] <Rhonda> what for is the tag fsys-tarfile-error used in launchpad?
[17:54] <jtaylor> corrupted tarfiles?
[17:54] <jtaylor> I used to get dpkg errors with broken tarfiles last release cycle a lot
[17:55] <Rhonda> So they are common and not a result of some diskspace related issues that they deserve their own tag? What is done about them?
[17:55] <jtaylor> I think there was a problem with tar itself last time
[17:56] <jtaylor> did not have the errors this cycle yet
[19:14] <kamal> Hi MOTU people... is there a script that will generate a "request no-change rebuild" bug report for me?
[19:17] <maxb> I don't think so - but there is very little boilerplate to say in one of those, so I don't think a script would be a help.
[19:17] <kamal> maxb: sure, I guess I'm wondering who I should subscribe to a request like that:  ubuntu-sponsors ?
[19:17] <micahg> kamal: you can just file a bug and subscribe ubuntu-sponsors, add a changelog (use dch -R to create if you want credit in the changelog)
[19:18] <kamal> micahg: I don't care about credit -- do we even actually need a new changelog?
[19:19] <micahg> kamal: if you don't care, just file the bug, adding a changelog to the bug make more work for the sponsor
[19:19] <kamal> micahg: excellent, thanks
[19:20] <micahg> my last comment should've read: you can just file a bug and subscribe ubuntu-sponsors, add a changelog (use dch -R to create), if you want credit in the changelog
[19:22] <kamal> micahg: :-)  got it
[20:35] <tumbleweed> kamal: if it's a whole bunch of related rebuilds, we should rather set up a transition tracker for it
[20:35] <kamal> tumbleweed: it was just one (that I'm aware of)
[20:35] <tumbleweed> oh, ok. You were asking about a script, though :)
[20:36] <kamal> tumbleweed: for future reference ;-)
[20:36] <kamal> tumbleweed: (alternately):  because I'm insanely lazy
[20:37] <tumbleweed> that's a good sign
[20:38] <kamal> https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/808971
[20:42] <tumbleweed> kamal: ah, if the package failed to build, we don't need a no-change rebuild, we can just retry it, or in debian terms "give it back" to the buildds
[20:43] <kamal> tumbleweed: I don't understand the distinction between 'rebuild' and 'retry the build'
[20:44] <tumbleweed> a no-change rebuild is a new source upload
[20:44] <tumbleweed> if it's already built successfully, we can't just retry it
[20:44] <dupondje> bleh, can't create a pbuilder for sid :(
[20:44] <tumbleweed> dupondje: on oneiric?
[20:45] <dupondje> and lucid :s
[20:45] <kamal> tumbleweed:  ah, ok -- then in that case, should I have filed the same request but s/rebuild/retry/  ?   i.e. still goes to ubuntu-sponsors?
[20:45] <tumbleweed> dupondje: I'm suprised
[20:45] <tumbleweed> kamal: I'm rebuilding i386 now
[20:45] <tumbleweed> if it looks happy, I'll do the others
[20:46] <dupondje> http://ftp.de.debian.org/debian/pool/main/c/csh/csh_20110502-2.dsc
[20:46] <kamal> dupondje: I use pbuilder-dist for 'unstable'  (not "sid") on Mav and Natty  just fine
[20:46] <dupondje> wanted to build it on sid
[20:46] <dupondje> :)
[20:46] <dupondje> mmm I used 'sid'
[20:47] <dupondje> lets test with unstable
[20:48] <tumbleweed> I'm tempted to suggest a newer puilder-dist, I did a fair number of improvements to it in 0.107
[20:49] <dupondje> i'm giving you guys some work :p
[20:49] <dupondje> 10 items already in sponsor queue :p
[20:50] <kamal> tumbleweed: if you're involved with the development of pbuilder-dist, please accept my gratitude!  pbuilder-dist brings me joy on a daily basis :-)
[20:50] <tumbleweed> well, it was a little empty :)
[20:50] <tumbleweed> kamal: I just did some recent tweaks, it existed long before I got involved
[20:51] <dupondje> debootstrap is bit broken
[20:51] <dupondje> so :
[20:51] <tumbleweed> dupondje: ah, yeah I just saw it fail too
[20:51] <tumbleweed> "Encountered a section with no Package: header"?
[20:52] <dupondje> I: mounting /proc filesystem
[20:52] <dupondje> mount: /proc already mounted or /var/cache/pbuilder/build//31959/proc busy
[20:52] <dupondje> mount: according to mtab, /proc is mounted on /proc
[20:54] <tumbleweed> dupondje: that's similar to what you were seeing the other day?
[20:54] <dupondje> yep
[20:54] <dupondje> completely broken somehow :s
[20:54] <tumbleweed> dupondje: pastebin your .pbuilderrc?
[20:54] <dupondje> COMPONENTS="main universe multiverse restricted"
[20:54] <dupondje> :P
[20:55] <dupondje> see https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/805886
[21:05] <kamal> tumbleweed: thanks for the cqrlog retries, that did the trick for the platforms where lazarus isn't busted
[21:13] <dupondje> dol.c:865:6: error: ignoring return value of 'write', declared with attribute warn_unused_result [-Werror=unused-result]
[21:14] <dupondje> any idea why I get this on oneiric, but not on debian sid when i'm building csh.
[21:14]  * micahg thought that option was on in sid as well...
[21:15] <micahg> dupondje: ah, debian might not have -Wall by default
[21:15] <micahg> http://lists.debian.org/debian-devel-announce/2011/02/msg00012.html
[21:16] <micahg> err, s/-Wall/-Werror/
[21:17] <dupondje>             (void) write(STDIN_FILENO, short2str(obuf),
[21:17] <dupondje> this line gives the error
[21:17] <dupondje> so better fix that part of the code :D
[21:20] <micahg> dupondje: you can file a bug against the compiler I guess :)
[21:21] <jtaylor> debian does not use compiler hardening so far I know
[21:21] <jtaylor> that includes _wor
[21:21] <micahg> but that doesn't look very robust though
[21:21] <jtaylor> -DFORTIFY_SOURCE=2 I think
[21:23] <kees> jtaylor: debian doesn't do it by default, but individual package maintainers might use it for their packages.
[21:24] <dupondje> why is it a compiler bug ?
[21:24] <jtaylor> its not
[21:24] <dupondje> :)
[21:24] <kees> micahg: it's not a compiler bug. you can compile with -Wno-error=unused-result to avoid it
[21:24] <dupondje> or fix the code ofc
[21:24] <kees> dupondje: the compiler is doing exactly what we asked it to do.
[21:24] <kees> https://wiki.ubuntu.com/CompilerFlags
[21:25] <jtaylor> the (void) indicates upstream wanted to ignore it there, replace it with if (write(...)) {} to silence the warning
[21:25] <micahg> kees: I meant that usage that's flagged, the call is cast to a void, so it shouldn't have a return value, right/?
[21:26] <jtaylor> yes unison failed on armel ._
[21:27] <jtaylor> .
[21:27] <kees> micahg: the compiler is not fooled into ignoring it with (void) casts. upstream says that's not a bug, IIRC.
[21:27] <micahg> kees: ah, smart compiler ;)
[21:27] <kees> micahg: perhaps overly so. I would prefer the (void) trick, but for whatever reason, upstream doesn't like that.
[21:28] <kees> jtaylor: better than just {}ing it, see if it's possible to actually do something interesting in the failure case.
[21:28] <micahg> kees: well, if a function has a return value, then it's meant to do something with it and you end up with non-robust code in general if you ignore it
[21:28] <kees> right
[21:29] <jtaylor> kees: of course, but often you just don't care, and that it has that (void) indicates that it is such a case
[21:30] <jtaylor> hm -2 succeded on arm, with essentially same code
[21:30]  * micahg thinks people need to be taught to care...
[21:30] <jtaylor> and it succeded in debian
[21:31] <dupondje> but doesn't build on oneiric :)
[21:32] <jtaylor> probably time to look into emulating arm ._.
[21:32] <tumbleweed> jtaylor: it works pretty well
[21:33] <tumbleweed> dupondje: I can't debootstrap sid on lucid, but I don't think I'm running into the same bug as you. I can debootstrap wheezy, though, so sid may just be broken atm.
[21:33] <jtaylor> hm no, I think its hopeless, I have no idea of ocaml and arm
[21:35] <dupondje> tumbleweed: squeeze worked here, sid/unstable not
[21:35] <dupondje> its weird :)
[21:35] <jtaylor> is there a arm emu for packaging tutorial?
[21:36] <tumbleweed> jtaylor: pbuilder-dist oneiric arm create
[21:36] <tumbleweed> err armel
[21:36] <tumbleweed> (assuming you are a pbuilder-dist user :P )
[21:37] <jtaylor> hm cowbuilder-dist should work too
[21:37] <jtaylor> nice
[21:37] <dupondje> mmm next issue: pmake: don't know how to make /usr/lib/libc.a. Stop
[21:37] <tumbleweed> why is it trying to statically link to libc?
[21:37] <jtaylor> dupondje: your working on libc? ^^
[21:37] <dupondje> csh :)
[21:38] <tumbleweed> still, statically linking...
[21:38]  * tumbleweed wondedrs what crazy people still use csh
[21:39] <jtaylor> E: Invalid Release file, no entry for main/binary-arm/Packages
[21:39] <tumbleweed> dupondje: anyway, vorlon tagged that multiarch, that should be a good hint
[21:43] <dupondje> tumbleweed: we need new version of pmake :P
[21:45] <jtaylor> any idea whats problem?
[21:45] <dupondje> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626877
[21:52] <slangasek> tumbleweed, dupondje: "don't know how to make" is the generic make message for "you said this was a dependency and I don't know where to get it" - declaring a dependency on libc is a little weird (I don't think I've ever seen non-BSD-y sources do this), but it's valid, supported, and requires patches to pmake to cope with multiarchitude
[21:52] <slangasek> I think Debian unstable has this patch now - I don't know if it's in oneiric yet
[21:54] <dupondje> pmake in unstable has patches indeed
[21:54] <dupondje> and can be synced ...
[21:56] <dupondje> could you sync it ? or do I report a sync request ?
[22:01] <dupondje> slangasek: ?
[22:03] <slangasek> dupondje: sync request, please; the package currently has an Ubuntu delta that I haven't looked at
[22:03] <dupondje> ok
[22:04] <dupondje> done
[22:04] <dupondje> tumbleweed: going tru my requests ? ;)
[22:05] <tumbleweed> dupondje: the easy ones. embedian-crush has a big  delta, so I'll skip it and go to bed
[22:10] <tumbleweed> dupondje: what's the reason for the darcs-monitor sync request? (in fact a few of them could have used better explatations)
[22:11] <tumbleweed> ah, I see it currently ftbfs in oneiric
[22:11] <dupondje> its ftbfs
[22:11] <dupondje> indeed
[22:12] <dupondje> alot of them are ftbfs
[22:12] <dupondje> thats why sync reqs
[22:14] <tumbleweed> dupondje: if helps if you say that in the report. One assumes reporters have good reasons for doing things, but it really does help when evaluating
[22:15] <dupondje> tumbleweed: I'll do that!
[22:16] <tumbleweed> thanks :)
[22:17] <tumbleweed> anyway, I've left you with some to fix up
[22:17] <dupondje> +++ php-ps-1.3.6/debian/ps.ini
[22:17] <dupondje> @@ -0,0 +1,2 @@
[22:17] <dupondje> +; configuration for php ps module
[22:17] <dupondje> +extension=ps.so
[22:18] <dupondje>    * Replace '#' by ';' in ps.ini, because it is deprecated
[22:18] <dupondje> that debian bug can be closed it seems :)
[22:21] <tumbleweed> dupondje: you can do that :)
[22:21] <dupondje> yea done it
[22:32] <papo> hello
[22:32] <papo> I am wondering what is affecting the inclusion of libclang. There is a clang package but for some reason the library was omitted, see bug 785665.
[22:34] <papo> I would offer to provide a patch to build an additional package containing the library but if this is out of question in the first place it's not worth doing it
[22:36] <micahg> papo: see debian 598738
[22:37] <dupondje> but if you install clang
[22:37] <dupondje> you have libclang.so
[22:37] <dupondje> /usr/bin/install -c /build/buildd/clang-2.9/build-clang/Release/lib/libclang.so /build/buildd/clang-2.9/debian/tmp-clang/usr/lib/libclang.so
[22:38] <micahg> papo: you can as Sylvestre if he's interested in patches
[22:38] <micahg> *ask
[22:39] <papo> micahg: Hm OK that bug seems to be about the static libs but goes into the same direction... I'm interested in the .so, though... so the answer is just "it's complicated an needs time" ?
[22:39] <micahg> papo: that bug is for all of it
[22:40] <papo> dupondje: OK interesting, I have to check that quickly. The natty package most certainly does not but maybe it was included later on
[22:41] <micahg> unless I'm not understanding something
[22:42] <papo> micahg: the bug description mentions static libs and some header files but yeah, probably the same issue
[22:44]  * micahg wonders if it's possible to have a -dev package w/out an actual library
[22:44] <broder> micahg: i've seen one where the library wasn't available as a shared lib
[22:44] <jtaylor> possible yes
[22:44] <jtaylor> python-cxx-dev
[22:44] <jtaylor> thats just a bunch of source files as upstream does not provide a library
[22:46] <papo> dupondje: Which version of the clang package are you referring to? I find myself unable to locate the shared lib in clang (2.9-7)
[22:47] <papo> dupondje: or was this from the build log? not everything that is compiled gets packaged (that is actually my problem...)
[22:47] <dupondje> was from build log indeed
[22:48] <papo> hm ok
[22:50] <papo> micahg: well the debian bug report suggests that the library should be packaged, too, but Sylvestre just doesn't have time to do it currently, so I guess patches are welcomed after all
[22:53] <papo> but I'm not quite sure what is supposed to make the thing complicated, the library gets built, it's just a matter of extending some debian/ files as far as I can see... in the end things will not be as the maintainer wants them to be and the time spent will have been in vain :(
[22:55] <micahg> papo: right, that's why I suggested talking to sylvestre
[22:55] <papo> right
[22:56] <papo> micahg: is that guy a regular IRC user by chance?
[22:56] <micahg> he's around some times
[22:56] <papo> OK nice
[22:56]  * micahg has no idea when though
[22:58] <papo> no problem, I'll just hang around... now is the second time this month that I though that having the library at hands could be helpful, a couple of more days and my needs will exceed my lazyness-threshold anyway
[22:59] <micahg> papo: you could send an e-mail :)
[23:00] <papo> yep, or follow-up on the bug report, I know :)
[23:05] <papo> anyway, I guess I'll just dig into it and once I have something that could potentially help him with the bug I'll post it or maybe even be able to catch him here... thank you for your insights, micahg
[23:10] <jtaylor> ScottK: do we really still need this delta: https://launchpad.net/ubuntu/+source/matplotlib/0.99.1.2-2ubuntu2? qt3 is still in the archive
[23:11] <ScottK> jtaylor: No.  It looks like someone from Debian Science may adopt qt3, so it's not going to die as soon as I thought when I did that.
[23:11] <jtaylor> k then I'll sync matplotlib dropping it
[23:11] <jtaylor> I'll quote you in the bug k?