[00:00] <pindonga> hi, I just wanted to know what I need to do to get a package updated for oneiric
[00:01] <pindonga> in particular, how can I get the source pacakge (in ubuntu) track a differnent upstream connection (so that it tracks the one that gets updates)
[00:21] <micahg> pindonga: which package/
[00:22] <pindonga> hi micahg : python-configglue
[00:22] <pindonga> I'm the main dev, and I'd like to get the latest into oneiric
[00:24] <ajmitch> pindonga: I thought that package was being maintained as part of the ubuntuone packages?
[00:25] <ajmitch> mostly because they're the main user of it
[00:25] <pindonga> ajmitch, that's how it started
[00:25] <pindonga> but the proyect evolved
[00:25] <pindonga> and now has it's own life :)
[00:25] <ajmitch> that's good :)
[00:25] <pindonga> at ISD we use it heavily
[00:26] <pindonga> that's why it evolved (actually two projects merged into one, and configglue kept the name)
[00:26] <ajmitch> are there any backwards-incompatible changes that'd break the current packages that use it?
[00:26] <pindonga> it's likely
[00:26] <pindonga> but otoh, the ubuntuone guys are using the latest from a daily ppa
[00:27] <pindonga> for dev
[00:27] <ajmitch> that'll make things tricky then, if U1 is still using 0.9 for oneiric
[00:27] <ajmitch> ah ok
[00:27] <pindonga> is there a way to get the list of all packages that depend on it?
[00:27] <pindonga> so that I can ask around?
[00:27] <ajmitch> apt-cache rdepends python-configglue
[00:27] <pindonga> that on oneiric I guess
[00:28] <ajmitch> yes (which I don't have running right now)
[00:28] <pindonga> me neither
[00:28] <pindonga> let's say I can get an ok from all the users
[00:28] <pindonga> what shall I do next?
[00:28] <ajmitch> I'd be happy to update it, I uploaded it to debian
[00:29] <pindonga> ajmitch, ok, I'll ping you then when I have confirmation from the u1 guys that it works alright in oneiric
[00:29] <pindonga> and maybe from someone else
[00:30] <ajmitch> ok
[00:31] <ajmitch> I'll get an updated package ready for it then
[00:33] <ajmitch> I'm guessing that there shouldn't be many changes needed from what's in the branch
[00:33] <pindonga> ajmitch, cool
[00:33] <micahg> pindonga: I'll give you a list...one sec
[00:33] <ajmitch> micahg: thanks
[00:33] <pindonga> ajmitch, my intention is to get the 1.0 release before oneiric, but since I'm not sure I'll pull it off at least I want it to be a bit more updated
[00:33] <pindonga> :)
[00:33] <pindonga> micahg, cool, thx
[00:34] <pindonga> that's the reason there are many changes since 0.9pre1
[00:34] <micahg> pindonga: http://paste.ubuntu.com/642279/
[00:35] <ajmitch> python-django-configglue, also not updated for a couple of releases
[00:36] <pindonga> ajmitch, yes, that one will get an update too (I'm also the author of that)
[00:36] <ajmitch> alright
[00:36] <pindonga> so, only django-configglue and ubuntuone-client it seems
[00:37] <pindonga> I'll confirm the u1-client tomorrow morning
[00:37] <pindonga> django-configglue will be ready tomorrow too
[00:37] <ajmitch> that should be easy enough to confirm & check
[00:37] <micahg> pindonga: so, to get it updated, file a bug w/a debdiff or prepare a merge proposal into the UDD branch lp:ubuntu/foo
[00:38] <micahg> if you go the bug route, you'll need to subscribe ubuntu-sponsors
[00:39] <ajmitch> micahg: I need to update the package in debian anyway, so I offered to look at it
[00:39] <micahg> ajmitch: ah, cool
[00:40] <pindonga> micahg, ajmitch thanks a lot
[00:41] <pindonga> ajmitch, I'll ping you tomorrow
[00:41] <ajmitch> np
[02:20] <benonsoftware> Hi all
[04:24] <aboudreault> Hi
[04:25] <aboudreault> If we do a security release for our major software versions... can we replace the package in hardy and other dists
[04:25] <aboudreault> or we have to do manual security package with a single patch
[04:31] <micahg> aboudreault: we generally do a minimal patch update for security issues
[04:31] <aboudreault> ok..
[04:32] <micahg> aboudreault: you just need to file a bug, attach a patch, (make it private if the issue is private still), and subscribe ubuntu-security-sponsors
[04:32] <aboudreault> last time, I did the package myself. I guess I can attach a debdiff
[04:33] <micahg> aboudreault: that would be great, there's a security person available most days in #ubuntu-hardened if you have specific questions regarding security updates
[04:33] <aboudreault> alright. thanks
[07:26] <dholbach> good morning
[07:29] <_Dreamer_> Good morning dholbach :)
[07:31] <dholbach> hey _Dreamer_
[07:31] <_Dreamer_> What's up dholbach ?
[07:32] <dholbach> _Dreamer_, still slowly waking up - how 'bout you?
[07:32] <_Dreamer_> I'm looking for Pythin to make my OO concepts strong.
[07:33] <dholbach> nice, good luck with that! :)
[07:35] <_Dreamer_> Thank you dholbach :)
[10:47] <jykae> dev day 2, rock y'all :)
[10:49] <jykae> we will gather locally here in Tampere, Finland
[10:50] <jykae> here http://www.demola.fi
[10:50] <jykae> actually a start for our local meetups :)
[12:15] <dholbach> bdrung, can you review my fix for 798972?
[12:15] <dholbach> bdrung, I mentioned packaging-dev at UDW yesterday!
[12:58] <pindonga> morning ajmitch , k we're good to go with python-configglue
[12:59] <pindonga> the u1 guys said they're going to test it once it landed on oneiric (they're using a custom build of 0.11+r65 right now, so it should work)
[15:37] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 2 starting in 23 minutes in #ubuntu-classroom
[15:40] <dupondje> https://launchpadlibrarian.net/75058147/buildlog_ubuntu-oneiric-i386.libdispatch_0~svn197-3_FAILEDTOBUILD.txt.gz
[15:41] <dupondje> this is something in libc6-dev ?
[15:41] <dupondje> :s
[15:43] <jtaylor> linux-libc-dev
[15:44] <dupondje> but thats included as build-dep
[15:44] <jtaylor> does clang have multi arch support?
[15:44] <bdrung> dholbach: looks good. maybe change the order (but that can be done later)
[15:45] <dholbach> bdrung, thanks
[15:45] <bdrung> dholbach: i wasn't aware that i should reviewed it (unless you said it)
[15:45] <bdrung> s/unless/until/
[15:46] <dholbach> I thought that everybody on the team would get an email about it? or at least the team list?
[15:46] <dupondje> jtaylor: it builds fine on amd64
[15:47] <bdrung> dholbach: i got the bug mails, but no merge proposal
[15:47] <dholbach> hm, weird
[15:50] <tumbleweed> dholbach: packaging-guide team?
[15:50] <dholbach> tumbleweed, yes
[15:51] <dupondje> + if (Distro == DebianWheezy && Arch == getArch())
[15:51] <dupondje> not really cool :P
[15:51] <tumbleweed> dholbach: that has ubuntu-dev as a member, and ubuntu-dev receives no mail from launchpad, IIRC
[15:51] <jasonb1> hi again dholbach = )
[15:51] <tumbleweed> I mean, it doesn't have real members, only ubuntu-dev and ubuntu-core-doc (which probably does get mail)
[15:53] <dholbach> hi jasonb1
[15:53] <dholbach> ah ok
[15:53] <dholbach> still there's a team mailing list :)
[15:54] <tumbleweed> right, /me should probably subscribe
[15:57] <dholbach> yoohoo
[15:57]  * dholbach hugs tumbleweed and bdrung
[15:57] <dupondje> jtaylor: https://bugs.launchpad.net/llvm/+bug/764870 => so clang should be multiarch :s
[15:59] <jtaylor> its incomplete http://launchpadlibrarian.net/72509068/clang_2.9-1~exp1_2.9-1.diff.gz
[15:59] <jtaylor> only search 486 and 686 but not 386
[16:00] <jtaylor> tools/clang/lib/Frontend/InitHeaderSearch.cpp
[16:01] <dupondje> mmm indeed :s
[16:01] <jtaylor> lets see if sylvestre is there
[16:05] <Laney> ScottK: is kdebindings going away in Ubuntu?
[16:05] <ScottK> Laney: It's being split.
[16:05] <Laney> yeah, going away in its current form.
[16:05] <ScottK> Yes.
[16:05] <Laney> great
[16:06] <ScottK> I'm not sure all the existing bindings will get packaged by Debian qt-kde or Kubuntu people.
[16:06] <ScottK> For example, I'm virtually certain no one on either team will do the mono bindings.
[16:07] <Laney> I imagine they would only get done on demand
[16:08] <dupondje> jtaylor: you stalk the maintainer ? :) If I do need to open a bug on debian, let me know :)
[16:10] <jtaylor> dupondje: k
[16:11] <dupondje> thanks for looking btw :)
[19:57] <dupondje> Hi i'm trying to merge mysql++, but I got some issue (http://paste.ubuntu.com/642863/).
[19:58] <dupondje> On Ubuntu its build with 'g++ -o test_ssqls2 test_ssqls2_ssqls2.o    -L. -lmysqlclient   -Wl,-Bsymbolic-functions -L/usr/lib64  -lmysqlpp -lmysqlpp_ssqls2parse '
[19:58] <dupondje> But on Debian with: 'g++ -o test_ssqls2 test_ssqls2_ssqls2.o    -L. -lmysqlclient   -L/usr/lib64  -lmysqlpp -lmysqlpp_ssqls2parse'
[19:59] <dupondje> -Wl,-Bsymbolic-functions should be at the end, but don't know really where to start :)
[19:59] <dupondje> its Bakefile ...
[20:43] <jtaylor> dupondje: its just a ordering issue
[20:43] <jtaylor> mysqlpp_ssqls2parse is a static library
[20:44] <dupondje> thats needs to come in front of -Wl ?
[20:45] <dupondje> or ?
[20:46] <jtaylor> no in front of -lmysqlpp
[20:47] <jtaylor> maybe also move -lmysqlclient to the end just to be save
[20:52] <dupondje> lets see how I can fix this :)
[21:10] <dupondje> aight :D It did build
[21:10] <dupondje> thx jtaylor
[21:11] <dupondje> but small question, how you see its a static lib exactly? And why does it need to be in front :)
[21:11] <jtaylor> it has a .a extension
[21:12] <jtaylor> static libraries are just an archive of object files, so the same rule as for regular object files applies
[21:12] <jtaylor> often static libraries are not linked with -l to distinguish them from shared ones, but thats different from develoepr to developer
[21:14] <jtaylor> instead you just use the full patch, which makes exactly this issue more obvious
[21:31] <dupondje> jtaylor: http://ubuntu.dupondje.be/mysql.debdiff
[21:31] <dupondje> does that looks fine? It builds
[21:34] <jtaylor> dupondje: why build egainst 16-dev? wouldn't -dev do?
[21:35] <dupondje> in previous version it was: debian/control: Explicitly build against libmysqlclient16-dev.
[21:36] <jtaylor> yes, but -dev pulls in 16
[21:36] <jtaylor> I'm unfamilier with mysql versionen, you have to ask somene else
[21:37] <dupondje> well it shouldn't be linked against 15-dev
[21:37] <dupondje> then you can indeed choose -dev or 16-dev
[21:37] <dupondje> both are same
[21:38] <jtaylor> in debian versioned -dev's are being discouraged as they complicate transitions
[21:40] <jtaylor> but mysql might be a special case
[21:40] <dupondje> well shouldn't matter alot no ?
[21:41] <jtaylor> probably not
[21:41] <jtaylor> don't forget to forward the patch to debian
[21:41] <jtaylor> + upstream
[21:41] <dupondje> its not ftbfs on debian ...
[21:41] <dupondje> still forward ?
[21:42] <jtaylor> yes as wishlist
[21:43] <jtaylor> with: User: debian-gcc@lists.debian.org
[21:43] <jtaylor> Usertags: ld-as-needed
[21:44] <dupondje> oki
[21:44] <dupondje> btw a small question, is there a tool to upload files directly to launchpad from commandline ?
[21:45] <dupondje> cause i'm building packages on a build box now :)
[21:45] <Laney> email
[21:45] <dupondje> ah, didn't check launchpad's email api yet :)
[21:45] <Laney> for bug attachments, just email nnn@bugs.launchpad.net and attach the file
[21:50] <pindonga> ajmitch, are you around here?
[21:51] <dupondje> seems like alot of sponsor requests from me :P
[21:51] <dupondje> hehe
[21:51] <ajmitch> pindonga: yes, sort of
[21:52] <pindonga> hey! :)
[21:52] <pindonga> I have the go from the u1 guys for python-configglue
[21:52] <ajmitch> alright
[21:52] <Laney> uh oh
[21:52] <pindonga> ajmitch, they are already using 0.11
[21:52] <pindonga> so it should be alright
[21:52] <ajmitch> Laney: what'd you break this time?
[21:55] <ajmitch> pindonga: is there a release of django-configglue as well to match it?
[22:23] <pindonga> ajmitch, there will be , but not yet
[23:02] <dupondje> allright :) done for today