[01:59] <persia> tumbleweed, bilalakhtar, there are a number of packages in universe that are installed by default for Xubuntu or Ubuntu Studio: take care with these re: UIF
[02:02] <persia> Oh, and Mythbuntu even has some things from multiverse.  Anyway, `apt-cache show ${binary-package}` should show if anything belongs to any tasks: those are the packages to avoid.
[02:26] <wgrant> 3
[02:37] <Byz4nt1n3> Hey there... I am wondering if there is a good place for a complete newbie lean how to be a MOTU.
[02:40] <nigelb> No better place :)
[02:46] <Byz4nt1n3> @nigelb so where do I start
[02:46] <Byz4nt1n3> how does this whole thing work? ;)
[04:14] <lucidfox> http://arstechnica.com/business/news/2010/09/intels-walled-garden-plan-to-put-av-vendors-out-of-business.ars
[04:14] <lucidfox> Free software is doomed? :(
[04:53] <paultag_> Hey MOTU. Anyone know of a way to get package data from a repo without having it in the apt sources file ( read: something that will get the data and output it ).
[04:54] <Pici> paultag_: What sort of data?
[04:54] <paultag_> Pici: really really basic. Package version number, name, perhaps description and dowload location, but not even that matters so much
[04:55] <paultag_> have a command like `magic-command --get-version package domain.tld' return something like 1.1.1-3
[04:56] <Pici> paultag_: You can use the python-debian package/module to parse control files/Packages.gz
[04:56] <paultag_> Pici: I think I'll do that. Just making sure I'm not re-inventing the wheel. Thanks :)
[04:56] <Pici> For quick things I usually just use rmadison to check what package versions we have across our active releases.
[04:57] <paultag_> Aye, can rmadison ( Sheesh, I forgot about that command ) work with any domain / suite?
[04:58] <crimsun_> it'll work with whatever is defined
[04:58] <Pici> It requires some cgi on the server to talk to.
[04:58] <paultag_> Ahha
[04:59] <Pici> The manpage explains more
[04:59] <paultag_> thanks Pici :)
[04:59] <Pici> paultag_: sure thing
[05:33] <lucidfox> Is it okay for the upstream build system to install monochrome indicator icons to ubuntu-mono-dark/ubuntu-mono-light?
[08:38] <\sh> siretart: fai 3.4.2 just landed in maverick...which fixes two bugs...so if you do the backport use this version
[08:42] <siretart> thanks
[09:11] <bilalakhtar> The title still mentions 'Feature Freeze in eff'ect
[09:13] <micahg> bilalakhtar: right
[09:13] <bilalakhtar> though the final freeze is in effect now
[09:13] <micahg> bilalakhtar: no
[09:14] <bilalakhtar> micahg: ??
[09:14] <bilalakhtar> not yet?
[09:14] <micahg> bilalakhtar: when the freeze the archive it will be, they haven't done so yet
[09:14] <micahg> bilalakhtar: usually happens some time during the morning UTC or US
[09:15] <bilalakhtar> :) Timezones matter a lot during freezes!
[09:16]  * micahg still has one more upload for main
[09:54] <AnAnt> Hello
[10:26] <vish> oh main gets frozen today!
[11:03] <tumbleweed> micahg: whoops, gnome-shell SRU doesn't seem to be building. I wonder if the pbuilder I tested in had lucid-updates enabled...
[12:29] <persia> nhandler, Good day.  It appears I've fallen out of ubuntu-sponsors, meaning I can't grant bilalakhtar membership there.  If you wouldn't mind, could you add us both?
[12:39] <nhandler> persia: Done
[12:40] <persia> nhandler, Thanks.  Can you make me an admin again, or does that wait on dholbach?
[12:41] <nhandler> persia: That needs Daniel.
[12:41] <persia> Heh, well, maybe some other folks will get the please add pings for a while :)
[12:41] <persia> Thanks again.
[13:31] <borealis> Hello! I have an opensource java developer package called QtJambi that I want to get into the official package repos of ubuntu. How do I start such a process?
[13:36] <persia> borealis, For java applications, the first step usually involves stripping out all the third party binaries from the .jar and carefully reviewing the licensing.
[13:36] <persia> Much of the time, one ends up having to package a couple of libraries first.
[13:37] <borealis> I do have some experience in writing debian packages, but maybe that's not requested, maybe more a question of listing the jar files/examples that is needed.
[13:37] <persia> If the application builds using ant, packaging is usually fairly straightforward with rules.tiny.  If not, one sometimes has to work around things.
[13:37] <borealis> Well, it's necessary to build a special form of Qt first, and then run ant.
[13:38] <persia> borealis, I'd recommend starting from http://pkg-java.alioth.debian.org/ to find examples.  There's a number of good ones.  Those updated more extensively more recently tend to be better.
[13:38] <persia> a special form of Qt?  That sounds like a recipe for pain, as we try very hard to avoid code duplication (which makes it hard to maintain).
[13:39] <persia> You might want to start by seeing what could be done to system Qt to make it do what you need (whilst not breaking for anyone else)
[13:41] <borealis> Hmm, yeah, I know...
[13:43] <borealis> QtJambi consists of some JNI native so files + jar files containing the classes corresponding to the JNI stubs.
[13:45] <borealis> The most popular way of deploying this so far is by bundling all this in a so called native jar file, that is, both qt so files and qtjambi so files. QtJambi has a special classloader that is able to extract and load native so from these types of jars.
[13:45] <borealis> However, we might look at alternatives to be more "consistent" with how things are setup in a linux packaging regime.
[13:46] <borealis> Saves a lot of space I guess if we could just use system qt.
[13:50] <borealis> The main reason for the need of special compilation of Qt is the configure option -prefix=$PWD. Maybe you're already using this option when building various Qt releated packages?
[13:50] <persia> I'd suggest checking Qt buildlogs
[13:51] <borealis> Ok, where can I find this?
[13:51] <persia> launchpad.net/ubuntu/+source/${package} has links to versions, and each version has links to builds for each architecture, and each build page has a build log.
[13:52] <persia> alternately, check the source packages, depending on whether you prefer to read pithy instructions, or the results thereof :)
[13:54] <bilalakhtar> There, I do my first sponsorship
[13:54] <bilalakhtar> micahg: done
[14:02] <bilalakhtar> tumbleweed: From the code, I am seeing that ack-sync is used to sync packages from Debian, as recent changes are in it. But somewhere, I read that syncpackage should do it (and that DOES it) and there is no such command ack-sync even after I install latest u-d-t from the branch.
[14:02] <tumbleweed> bilalakhtar: ack-sync uses syncpackage internally, and it's in the bzr branch (and source package) but not installed in the binary package
[14:05] <persia> It's really much better not to use syncpackage if it can be avoided.
[14:05] <persia> Better to pass bugs to the archive-admins who can do it cleanly on the archive master server
[14:33] <ari-tczew> can someone ping me for test?
[14:33] <borealis> persia: I've tried https://launchpad.net/ubuntu/+source/libqtcore4 but cannot seem to get any hit...
[14:34] <shadeslayer> ari-tczew: like /ctcp ping ari-tczew ?
[14:35] <ari-tczew> shadeslayer: nope, just I needed highlight
[14:35] <shadeslayer> oh :P
[14:36] <borealis> That is, I find this: https://launchpad.net/ubuntu/lucid/amd64/libqtcore4/4:4.6.2-0ubuntu5
[14:36] <borealis> But, where do I find out about the configure flags from here?
[14:38] <shadeslayer> borealis: one sec
[14:38] <shadeslayer> http://launchpadlibrarian.net/44120364/buildlog_ubuntu-lucid-amd64.qt4-x11_4:4.6.2-0ubuntu5_FULLYBUILT.txt.gz
[14:39] <borealis> aha, great, let's see...
[14:41] <shadeslayer> borealis: also http://bazaar.launchpad.net/~kubuntu-members/qt/ubuntu/annotate/head:/debian/rules
[14:41] <shadeslayer> from line 84
[14:42] <borealis> Hmm... 	            -prefix "/usr" \
[14:42] <borealis> 	            -bindir "/usr/bin" \
[14:42] <borealis> 	            -libdir "/usr/lib" \
[14:43] <borealis> That is maybe worrying for qtjambi building...
[14:44] <borealis> However, I will check with my fellow developer at the project, and test a little myself.
[14:45] <ari-tczew> shadeslayer: could you ping me again?
[14:46] <shadeslayer> ari-tczew: yeah :P
[14:47] <ari-tczew> shadeslayer: test done. thanks!
[14:47] <shadeslayer> np
[15:38] <AnAnt> finalfreeze is for universe too ?
[15:40] <persia> AnAnt, Yes.  This doesn't mean don't fix things, just take appropriate care, etc.
[15:41] <AnAnt> ok thanks
[15:41] <persia> Note that the criteria for FinalFreeze are more critical for packages that end up in some flavour image (regardless of component) than for other stuff, but still.
[15:41] <AnAnt> persia: I want to merge swt-gtk from Debian
[15:42] <persia> Does it fix some important bug?
[15:43] <AnAnt> bugs
[15:43] <AnAnt> persia: http://packages.qa.debian.org/s/swt-gtk/news/20100915T161811Z.html
[15:44] <persia> AnAnt, `for i in $(apt-cache showsrc swt-gtk | grep Binary | cut -d: -f2 | sed s/,//g | head -1); do apt-cache show $i | grep ^Task; done` suggests it's not in any flavours : see https://wiki.ubuntu.com/FinalFreeze
[15:45] <AnAnt> oh, it's in main
[15:47] <persia> main/universe doesn't matter
[15:47] <AnAnt> it means that I need a sponsor
[15:47] <persia> Ah, well that might matter :)
[15:48] <persia> You shouldn't need a sponsor, but LP doesn't understand inverse packagesets yet.
[15:49] <AnAnt> inverse package sets ? what's that ?
[15:50] <persia> Ideally, MOTU ought be able to upload everything that isn't in one of the flavour packagesets.
[15:50] <persia> But there's a bundle of stuff that's stuck in "main" for historical reasons which MOTU can't upload currently.
[15:50] <persia> And there's no good way to identify that right now.
[15:55] <AnAnt> so, I'll still need a sponsor
[16:02] <AnAnt> persia: do I need to file an FFe for it ?
[16:03] <persia> If it breaks FF, yes.  If not, use your own judgement (read: if you're unsure, file a bug)
[16:05] <micahg> tumbleweed: gnome-shell needs the new gjs to build
[16:06]  * micahg is test building
[16:07] <micahg> tumbleweed: I don'
[16:08] <micahg> t see any more lintian warnings, so I'm attaching another debdiff
[16:09] <tumbleweed> micahg: yeah, I assumed as much (after I saw the failures)
[16:09] <micahg> tumbleweed: I'm wondering why I never saw these lintian failures when I ran the build
[16:09] <micahg> maybe because I was using a chroot instead of pbuilder?
[16:10] <tumbleweed> pbuilder is a chroot...
[16:38] <Byz4nt1n3> hello all...
[16:55] <iulian> Hi Byz4nt1n3.
[17:27] <Tetsuo55> Hello, i would like to see the cppcheck packadge updated, what needs to be done for that to happen?
[17:28] <micahg> Tetsuo55: in answer to your question, you can request a sync if it's but fix only
[17:28] <micahg> Tetsuo55: if there are new features, you'll need an FFe
[17:28] <Tetsuo55> what do you mean with " but fix only "
[17:28] <Tetsuo55> oh
[17:28] <micahg> oops
[17:28] <micahg> bug :)
[17:28] <Tetsuo55> so i just missed the regular update window :(
[17:29] <micahg> Tetsuo55: feature freeze was a while ago, if there's a good reason to upgrade, you can still get it in
[17:30] <Tetsuo55> the changelog is only bugfixes
[17:30] <Tetsuo55> the tool is written in such a way that changes to features are transparent to the user
[17:30] <micahg> Tetsuo55: k, then use the requestsync tool from ubuntu-dev-scripts to request a sync from Debian with 1.4.4
[17:32] <Tetsuo55> yeah 1.44 is already better, i use git-head myself, bugs get fixed every day, mostly false positives, error output and crashes
[17:34] <Tetsuo55> im going to have to learn about that requestsync stuff, before i can actualy do it
[17:36] <micahg> Tetsuo55: requestsync -h for help, the script when run walks you through the process
[17:38] <playya_> moin
[17:38] <playya_> is it possible to overtake an inactive project?
[17:39] <playya_> i registered a branch called cornucopia, but it has been added to the cornucopia project
[17:44] <Tetsuo55> im stuck on postfix configuration
[17:45] <Tetsuo55> something about a mail server
[17:45] <micahg> oh, hmm
[17:45] <Tetsuo55> ok got past it
[17:45] <Tetsuo55> turns out i had to use TAB to navigate
[17:48] <Tetsuo55> i need to select a packadge from debian stable i assume?
[17:48] <Tetsuo55> or is unstable allowed too?
[17:49] <micahg> Tetsuo55: any version
[17:49] <micahg> default is unstable
[17:49] <Tetsuo55> ok
[17:50] <Tetsuo55> this one i guess http://packages.debian.org/unstable/main/cppcheck
[17:52] <Tetsuo55> requestsync -d http://packages.debian.org/unstable/main/cppcheck --lp -C
[17:52] <Tetsuo55> tried that but it failed
[17:54] <Tetsuo55> heh i clearly misunderstood how it works :D
[17:55] <Tetsuo55>   -s          Force sponsorship   << what does this do exactly?
[17:57] <Tetsuo55> it looks like i should go for " requestsync --lp -C cppcheck "
[17:57] <Tetsuo55> correct?
[17:57] <micahg> Tetsuo55: shouldn't need -C, but you'll want to edit the report and add the upstream changelog
[17:58] <Tetsuo55> gah need credentials
[17:58] <micahg> Tetsuo55: yes, with --lp
[17:59] <micahg> Tetsuo55: manage-credentials script can help
[17:59] <Tetsuo55> this right  manage-credentials create -c ubuntu-dev-tools -l 2
[18:00] <Tetsuo55> what level of rights does it need?
[18:00] <Tetsuo55> i want to give it the least amount required
[18:01] <micahg> I think just read for this one
[18:01] <Tetsuo55> i got it, change for non private data
[18:03] <Tetsuo55> i have to agree that someone will review the update, thats  correct right?
[18:03] <Tetsuo55> and -s probably forces the packadge to get reviewed
[18:05] <Tetsuo55> changelog for debian was made by official cppcheck dev, so i can keep it i guess? he didnt outright name the bugfixes though
[18:06] <Tetsuo55>  * New upstream release   << thats all it says
[18:06] <Tetsuo55> but 100's of bugs where fixed
[18:15] <Tetsuo55> ok did i do it right?
[18:15] <Tetsuo55> https://bugs.edge.launchpad.net/ubuntu/+source/cppcheck/+bug/640655
[18:24] <micahg> Tetsuo55: yes, but you might want to add the upstream changelog in the descrption as well so the sponsor can make an FFe decision
[18:30] <Tetsuo55> ok
[18:33] <persia> playya_, You might want to ask in #launchpad
[18:33] <playya_> ok
[18:35] <Tetsuo55> i added a comment with the real changelog
[18:52] <Quintasan> jcastro: ping
[18:53] <jcastro> Quintasan: pong
[18:54] <Quintasan> jcastro: mind if I go on /msg?
[18:54] <jcastro> sure
[18:55] <jcastro> I mean sure go ahead, not sure I mind
[19:00] <ari-tczew> launchpad janitor still not working?
[19:08] <ScottK> It's supposed to be fixed.
[19:39] <ScottK> lfaraone: Were you going to ask to have turtleart sync'ed?
[19:40] <lfaraone> ScottK: yeah, I filed bug 637735.
[19:41] <ScottK> OK.  It could have been filed against the package, then it would be easier to find.
[19:41] <ScottK> Oh, wait.  No you cant.
[19:41] <ScottK> The package page exists, but isn't active yet.
[19:41] <ScottK> Nevermind.
[20:17] <fabrice_sp> Hi. I've just uploaded a fixed pythonmagick. As we are in Fina lFreeze, what steps should I follow to get it accepted?
[20:20] <fabrice_sp> ok: I just have to wait :-) Thanks to whoever accepted it
[22:30] <ari-tczew> how can I upload SRU for lucid-proposed through bzr?
[22:39] <geser> you can't
[22:41] <ari-tczew> geser: could you be more verbose? tumbleweed has sponsored for some SRUs through bzr
[22:44] <geser> oh, then this is news to me. I remember that it's only possible to push to existing packaging branches but not create new ones.
[22:48] <geser> an unless things have changed you still need to dput a package even if you committed your changes to the packaging branch
[22:49] <ari-tczew> aha ok
[22:49] <lfaraone> geser: correct on both