[09:06] <Mirv> mitya57: the qbs is just an omission, I'm meaning to fix it. I just gave some time for release pocket migration to happen but it seems it'll need some release team hinting to get both botan and muparser transitions in at the same time (if I understood correctly)
[09:07] <Mirv> mitya57: hmm, no I'm not aware whether the QtQmlDevTools is really needed, maybe it should be just removed and seen if everything continues to work fine
[10:38] <mitya57> Mirv: I already checked yesterday and the headers can't be easily removed (qttools need that), but can be symlinked (will do that in next Debian upload).
[10:39] <mitya57> Thanks for looking at qtcreator!
[12:28] <pitti> slangasek: I don't know, I don't have any insight into the boottests; just that some packages have never worked
[12:29] <pitti> jdstrand: so click-autopkgtest continues being happy, seems it's specific to a schroot
[12:30] <pitti> jdstrand: presumably because most chroots have the host's /dev/pts bind-mounted; I don't know why it fails precisely, but VM tests don't have such a shared /dev
[14:24] <happyaron> slangasek: protobuf broken for builds in wily?
[14:24] <slangasek> happyaron: see doko's mail to ubuntu-devel-announce.  If you want to build C++ code in wily right now, you need to do it with wily-proposed enabled (like the autobuilders do)
[14:25] <happyaron> ok
[14:25] <happyaron> thx
[14:28] <slangasek> freyes: we have failing puppet autopkgtests in wily that started happening at the time ruby-passenger was uploaded for the g++5 ABI transition.  Is this something that you would be able to look into?  I'm planning to bypass the ruby autopkgtest failure as necessary to un-wedge the large transition, which means puppet may be left broken in wily until someone can look at it (http://autopkgtest.ubuntu
[14:28] <slangasek> .com/packages/p/puppet/wily/amd64/ ...
[14:28] <slangasek> ... http://autopkgtest.ubuntu.com/packages/p/puppet/wily/i386/)
[16:17] <slangasek> happyaron: sorry, I should have mentioned this part earlier as well as you were working on something building with C++ - please note that the main g++5 transition is currently in progress, so uploads of any affected packages (including protobuf) slows down the transition; please avoid uploading these until tomorrow
[16:17] <slangasek> happyaron: (I've just removed the old uim-mozc binaries from wily-proposed, so mozc should now make it in without problems)
[16:19] <happyaron> slangasek: ty! I really need that package to land before feature freeze, and sorry for that
[16:20] <happyaron> slangasek: after striping down uim support, we cleared the way of using mozc as default for Japanese users.
[16:20] <slangasek> happyaron: lots of devs need lots of things to land before feature freeze, but landing them when we're trying to land the transition slows down everyone else's landings :)  but hopefully we'll be able to push this through within just the next couple of hours
[16:21] <happyaron> ic
[20:50] <maqbool> hello guys i am newbie to open source world i want to contribute how can i get started
[20:50] <maqbool> ?
[20:51] <ari-tczew> maqbool: hi. do you want to contribute to open source in general, or stricte to Ubuntu?
[20:52] <maqbool> open source but related to ubuntu
[20:53] <maqbool> I am University undergraduate
[20:53] <ari-tczew> maqbool: well, there is an useful link in the topic, but you might be interested in reading this one https://wiki.ubuntu.com/MOTU/GettingStarted
[20:54] <maqbool> thanks
[20:55] <ari-tczew> maqbool: you don't need to have Bachelor/Master graduated :)
[20:56] <ari-tczew> cyphermox: anyway, would be nice if you could process NM 1.0 till 20th :)
[20:57] <cyphermox> yeah, I'm fixing up a git branch to do this on
[20:57] <ari-tczew> cyphermox: cool