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