[01:13] <jincreator> Hi, everyone. I want to fix package at universe. So, i report it to bug, and upload debdiff patch file. What should I do then?
[01:14] <micahg> jincreator: subscribe ubuntu-sponsors
[01:14] <jincreator> You mean the mailing list?
[01:14] <micahg> jincreator: no, the team in LP
[01:15] <JontheEchidna> to clarify, subscribe the "ubuntu-sponsors" launchpad group to the bug.
[01:15] <jincreator> Is this correct? https://launchpad.net/~ubuntu-sponsors
[01:16] <micahg> yes
[01:17] <jincreator> Umm...how can I subscribe then? There's no link "subscribe" or simillar. Do I miss something?
[01:17] <micahg> jincreator: on the bug page, there's a subscribe someone else link
[01:19] <jincreator> Oh, I got it. I think it must be at ubuntu-sponsers page.
[01:19] <jincreator> Thanks.
[01:20] <micahg> jincreator: thank you for contributing to Ubuntu development
[01:21] <jincreator> :)
[06:59] <dholbach> good morning
[07:40] <hakermania> micahg, how do packages from ubuntu go to debian?
[07:50] <nigelb> hakermania: You'll have to upload it manually
[07:53] <jbicha> hakermania: you need to get a Debian developer to help sponsor it, sorta like you did in Ubuntu
[07:54] <hakermania> nigelb, thanks, I'll do so. Does anybody know why even if in sourceforge's root I have the file wallch_2.1.tar.gz, uscan still reports that the site has till version 2.0?
[07:56] <hakermania> hm, I begin to believe that \d+.[0-9/]+ in watch file reads only the number before dot :(
[13:30] <hrw> N: 918 tags overridden (632 errors, 286 warnings)
[13:31] <hrw> that lintian info looks scary
[13:35] <geser> for your gcc cross compiler package?
[14:14] <paultag> holy jeez hrw
[14:14] <paultag> what package is that
[14:14] <paultag> sadly, we just had 2K+ on debian-mentors. It was in the running for the lintian maximization contest. Usually they're one error over and over like permissions or something
[14:15] <paultag> see how many were unique :)
[14:16] <hrw> geser: exactly
[14:17] <hrw> paultag: armel-cross-toolchain-base generates cross compiler packages. arch:all have armel binaries in them, non standard dirs /usr/arm-linux-gnueabi and /usr/HOST-TRIPLET/ are used and some other overrides
[14:17] <paultag> ahhha
[16:14] <jtaylor> why does bzr have so ridicouls bandwidth requirements, changed maybe 1k of text in three revision and bzr has already pushed 1.1 mb ._.
[16:19] <jtaylor> 2mb in the end ...
[19:45] <jtaylor> what are the differences between debians armel buildd and ubuntus? I'm just looking at pari whichs testsuite failed
[19:45] <jtaylor> in my qemu armel it fails due to unsupported syscall 26 (ptrace I think)
[19:46] <jtaylor> will it be the same on the buildd (logs don't show)
[19:46] <jtaylor> the debian armel testsuite succeded
[20:06] <slangasek> jtaylor: Ubuntu targets armv7 as the baseline, Debian targets armv4t
[20:07] <jtaylor> hm ok the unsupported syscall was not the cause of the failure, that comes from my debugging attempts with gdb
[20:07] <jtaylor> how does one debug on armel :O
[20:07] <jtaylor> without ptrace
[20:15] <slangasek> can't you run an armel gdb under qemu, I think?
[20:16] <slangasek> if it doesn't work under qemu-user-static, then certainly with qemu-system it should work (but slower)
[22:55] <slangasek> jtaylor: fwiw, here's some gdb output for pari running on a native system: http://paste.ubuntu.com/677538/
[23:05] <cjwatson> lfaraone: do you need any help with bug 831063?
[23:06] <cjwatson> sorry to nag but we're getting down to a fairly small number of packages left
[23:08] <micahg> cjwatson: are you looking for libav stuff to take?
[23:10] <cjwatson> yes, I'm working through NBS
[23:10] <cjwatson> looking at gmerlin-avdecoder now
[23:10] <micahg> cjwatson: feel free to take gnash (I was TIL)
[23:10] <cjwatson> oh, I already have a patch for that, I was going to look for a tester
[23:11] <cjwatson> http://paste.ubuntu.com/677544/ if you'd care to give it a try?
[23:12] <micahg> cjwatson: runtime testing as well?
[23:14] <cjwatson> I've build-tested it already
[23:15] <micahg> cjwatson: ok, will test later this week then, too much going on right now
[23:23] <jtaylor> slangasek: thx, it could be a compiler issue, it builds fine with -O0
[23:23] <jtaylor> slangasek: trying -O2 now
[23:23] <cjwatson> micahg: thanks
[23:24] <slangasek> jtaylor: yes, "compiler issue" was my first guess
[23:27] <jtaylor> -O2 works too
[23:27] <jtaylor> so simple solution for now just build arm with O2 or everything with O2
[23:27] <jtaylor> O3 fails
[23:30] <jtaylor> yey for testsuites