[00:00] <Laney> I don't know why they were needed, but I reckon you can go ahead and lose it now
[00:01] <plars> Laney: thanks!
[00:15] <maxb> Is there any standard documentation which says which modes of postinst/prerm should execute update-alternatives?
[01:26] <ScottL> if a package is available in lucid-proposed for a SRU, how many tests are necessary to considered a SRU verified?
[01:27] <micahg> ScottL: 1 or 2
[01:27] <ScottL> micahg, thanks, then i guess i can change the tag from "verification-required" to "verification-done" :)
[01:27] <micahg> ScottL: I think the SRU team does that
[01:28] <ScottL> micahg, what triggers them to change it?  do i need a special keyword in my reply to the bug? or another tag?
[01:31] <micahg> ScottL: https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
[01:32] <micahg> ScottL: not really sure, it says SRU verification team tests, but I've tested and had ubuntu-sru update the tag
[01:33] <ScottL> micahg, groovy, thanks!
[04:00] <hggdh> actually, if you test a SRU and confirm it to be working, you can change the tag to verification-done; if the test failed, then mark it verification-failed
[04:07] <ScottL> thanks hggdh
[08:08] <dholbach> good morning
[09:35] <huats> morning
[11:23]  * Laney is amused that aptitude would rather remove half his desktop than not upgrade gtk+
[11:26] <sebner> Laney: that's why clever people use apt-get :P
[11:26] <Laney> clever people read the output
[11:28] <Laney> third solution was what i wanted
[11:28] <sebner> Laney: you upgrading to maverick?
[11:28] <Laney> long ago
[11:28] <sebner> Laney: stable?
[11:29] <Laney> nothing broke for me!
[11:29] <Laney> !ymmv
[11:29] <tumbleweed> maverick has been good to me (although the intel driver seems to drink at least half my ram)
[11:30] <sebner> time to upgrade then :P
[11:34]  * geser is surprised sebner isn't using maverick already
[11:34] <sebner> geser: you know, at some point in your life you are happy having a stable LTS system which just works. This time it took longer becoming boring :P
[11:35] <dholbach> BlackZ: can you explain how the pyclutter sync worked?
[11:35] <Daviey> Anybody fancy sponsoring a sync for a fake-new package?
[11:35] <BlackZ> dholbach: FTBFS for you?
[11:36] <dholbach> BlackZ: no, but I'm interested which way you worked on it
[11:36] <BlackZ> dholbach: I used the ack-sync script to upload it
[11:36] <Laney> Daviey: if by "sponsor" you mean "ack" then "yes"
[11:36] <dholbach> BlackZ: to upload it?
[11:36] <dholbach> can I see the script?
[11:37] <Laney> it's in ubuntu-dev-tools iirc
[11:37] <BlackZ> dholbach: sure, just a moment
[11:37] <BlackZ> yes Laney
[11:37] <dholbach> nevermind, I see it now
[11:37] <Daviey> Laney,  bug #611218, provided justification why the delta from the (fake) old package can be dropped.  Old package dropped, new package has the same name - same contents.
[11:38] <BlackZ> dholbach: however it uses syncpackage too
[11:38] <dholbach> thanks BlackZ
[11:38] <Laney> Daviey: it provides the same binary packages?
[11:39] <Daviey> Laney, no
[11:39] <Laney> or at least the rdepends will/have taken it into account
[11:39] <Daviey> Laney, now uses version package so $PACKAGE-$VERSION and $PACKAGE is now a meta package
[11:40] <Laney> ok
[11:40] <Daviey> Laney, well put it this way... it has rdepends.. which are currently unsatsified
[11:40] <Daviey> as the original binary was rm'd from the archive
[11:40] <Laney> please ensure the rdeps are updated to use whatever is appropriate
[11:40]  * Laney test builds
[11:40] <Daviey> Laney, old rdepends uses what is now the meta package
[11:40] <Laney> seems like a strange situation
[11:40] <Daviey> yus. exactly :)
[11:42] <sebner> Laney: do you have an nvidia cart by change and can confirm 3D works with maverick?
[11:43] <Laney> sadly not
[11:47] <sebner> Laney: nvm then :)
[11:47] <sebner> geser: what about you?
[11:47] <Sarvatt> depends on your card sebner
[11:48] <Sarvatt> if its using nouveau_dri.so instead of nouveau-vieux_dri.so it's in maverick, but you have to install libgl1-mesa-dri-experimental yourself
[11:48] <sebner> Sarvatt: 8400M GS, nah I'm taking about binary nvidia 3D driver
[11:49] <Sarvatt> oh yeah it works then, same card here
[11:49] <sebner> great
[11:49]  * sebner needs to play nexuiz xD
[11:49] <Sarvatt> you only have a few days of it working though :)
[11:50] <Sarvatt> xserver 1.9 is about to go in
[11:50] <geser> sebner: ATI card and using the free driver
[11:50] <Sarvatt> nvidia's supposed to release a new beta that works with it any day now
[11:50] <sebner> Sarvatt: nvm, thanks for the warning, I just don't upgrade to new xserver then
[11:50] <sebner> poor geser
[11:57] <Daviey> Thanks Laney
[12:40] <ScottL> persia had shown me a link to a FTBFS list that i believe included all the build depends under each item that failed to build, does this ring a bell with anyone?
[12:40] <ScottL> it was an all text web page, no color (so it know it's not the one at qawire)
[12:41] <ScottL> any way the end goal was to investigate FTBFS packages for ubuntu studio
[13:08] <tumbleweed> bdrung: can we not put ack-sync-email.list somewhere out of the way? (i.e. in ~/.ubuntu-dev-tools)
[13:08] <bdrung> tumbleweed: feel free to find a nice place and name for it
[13:08] <tumbleweed> also, how about getting ack-sync to use @ubuntu.com addresses for members?
[13:08] <tumbleweed> that might require a few less manual overrides
[13:08] <bdrung> tumbleweed: good idea, please go ahead
[13:08] <tumbleweed> :)
[13:09] <bdrung> tumbleweed: i am going to work on a script that works similarly on merges and all the rest of it
[13:11] <tumbleweed> cool, that would be useful
[13:16] <bdrung> tumbleweed: how do you like this: http://people.ubuntu.com/~bdrung/sponsoring/
[13:23] <tumbleweed> bdrung: I can't see what's different between that and the qa.ubuntu one
[13:26] <bdrung> tumbleweed: scroll down
[13:27] <tumbleweed> oh I see
[13:28] <tumbleweed> I doubt I'd use those statistics much, but they are a good overview
[13:47] <geser> bdrung: shouldn't the sum over the components equal the total requests?
[13:49] <bdrung> geser: yes
[13:49] <bdrung> geser: or greater (if SRUs target different components)
[13:50] <geser> 141 + 54 + 2 = 197 != 199
[13:52] <bdrung> geser: python can't count :P
[13:53] <sebner> geser: I had to fix the dependency hell 2 times but maverick runs now without problems :D
[13:55] <geser> sebner: of course you filed bugs, right?
[13:55] <tumbleweed> bdrung: things I really want from the sponsor overview: clearer differentiation between main and universe (a fair chunk of sponsors are not core devs), sort by most recent activity (so we can sponsor fairly)
[13:56] <sebner> geser: ohh, and I was just wondering why apport didn't show up :\
[13:56] <bdrung> tumbleweed: that'll be an easy task
[13:57] <tumbleweed> I originally thought I wanted sort by date sponsors were subscribed, but most recent activity is probably the easiest solution to that
[13:57] <geser> bdrung: would it be possible to have a table for each kind of origin? (even if that means that some bugs are listed several times)
[13:58] <geser> so one could jump directly to the list/table of bugs one is interested in
[13:58] <bdrung> geser: this should be doable
[14:13] <vinc-mai> Hi.
[14:23] <micahg> dholbach: I didn't know reasons were needed for syncs before FF
[14:24] <vinc-mai> I do not know if it is a good time for a review but I have uploaded a package on revu, my first. Can someone take a look at it ? It is a ruby librairy design to help developpers to define global hotkeys. http://revu.ubuntuwire.com/p/libglobalhotkeys-ruby1.8
[14:24] <dholbach> micahg: still it makes it a bit easier if you know what's going on
[14:24] <vinc-mai> Comments will help me.
[14:24] <dholbach> micahg: if it involved a major transition or if it's an unstable branch, we probably shouldn't sync
[14:25] <dholbach> micahg: but if it's "a bug fix release" it certainly makes sense to get it in
[14:26] <dholbach> it's just that when I looked at the request I felt like I had no idea what's going on :)
[14:27] <micahg> dholbach: k, I'll keep in mind to add that stuff before FF as well :)
[14:27] <micahg> bdrung: can you show my how to use syncpackage
[14:27] <dholbach> micahg: and it's no strict requirement - it just makes the decision easier :)
[14:27] <bdrung> micahg: if i want to sync xmms2: syncpackage xmms2
[14:27] <micahg> dholbach: k, BTW, did you get my note about a UDD issue?
[14:27] <bdrung> and the dput the changes file
[14:28] <micahg> bdrung: k, what if there's a bug open?
[14:28] <micahg> bdrung: also, is the version in lucid u-d-t ok?
[14:28] <bdrung> micahg: do you want to sponsor one?
[14:28] <micahg> bdrung: yes :)
[14:28] <micahg> for myself actually
[14:28] <bdrung> micahg: then use ack-sync
[14:28] <micahg> ah, ok
[14:29] <bdrung> micahg: if i want to sync xmms2 closing lp bug 123456: syncpackage xmms2 -b 123456
[14:29] <dholbach> micahg: yes, but I'm snowed in under mails and work right now - I'll try to get to it as soon as I can - life's a bit nuts over here right now
[14:29] <micahg> dholbach: k, np
[14:30] <micahg> bdrung: k, is the version in Lucid u-d-t ok, or do I need to use trunk?
[14:30] <bdrung> micahg: lucid doesn't have syncpackage
[14:31] <bdrung> micahg: use either trunk or the latest version from maverick
[14:32] <micahg> bdrung: k, using trunk checkout I get a debian changelog error
[14:32] <bdrung> micahg: paste it
[14:33] <micahg> bdrung: http://pastebin.ubuntu.com/470702/
[14:33] <bdrung> micahg: you need a newer python-debian version
[14:33] <micahg> ah
[14:33] <bdrung> micahg: https://launchpad.net/~bdrung/+archive/backports
[14:34] <micahg> bdrung: thanks
[14:36] <bdrung> micahg: yw
[14:49] <vinc-mai> I have uploaded a package on revu, my first. Can someone take a look at it ? It is a ruby librairy design to help developpers to define global hotkeys. http://revu.ubuntuwire.com/p/libglobalhotkeys-ruby1.8
[14:51] <BlackZ> vinc-mai: don't repeat please, rather than of do that you could try to get it in debian
[14:53] <bdrung> vinc-mai: getting packages into debian first is the preferred way
[14:55] <vinc-mai> Sorry. I will not flood. I am new at packaging. It seems it is "easier" to upload a package to ubuntu than debian. That is why I have proposed it here. I hope to upload to debian after.
[14:55] <vinc-mai> Even if it is more logic to upload to debian!
[14:57] <BlackZ> vinc-mai: mentors.debian.net
[14:59] <vinc-mai> Thanks BlackZ for the link.
[15:09] <coolbhavi> BlackZ, thanks for quick sponsoring of FTBFS sync :)
[15:14] <bdrung> tumbleweed, geser: more stats: http://people.ubuntu.com/~bdrung/sponsoring/
[15:15] <bdrung> tumbleweed: universe ~= unseeded
[15:15] <bdrung> tumbleweed: sort by seed
[15:19] <micahg> bdrung: nice :)
[15:20] <BlackZ> dholbach: sorry, I didn't know you wanted to ACK the pyclutter sync request; I uploaded it first of your ACK
[15:22] <dholbach> BlackZ: no, you couldn't know - we opened the bug at the same time I guess
[15:22] <bdrung> dholbach: http://people.ubuntu.com/~bdrung/sponsoring/
[15:23] <bdrung> dholbach: i just have to correct the component counting and then you get the merge request
[15:23] <dholbach> bdrung: thanks - I'll try to have a look at it soon
[15:26] <BlackZ> dholbach: and sorry if before I understood another thing than what you said, I thought you meant the package building :P
[15:26] <BlackZ> bdrung: how is it going with your script?
[15:26] <bdrung> BlackZ: ~60 lines of codes. it checks the attached patches
[15:26] <BlackZ> bdrung: does it work?
[15:28] <bdrung> BlackZ: it can tell you the attached patches. now i am working on downloading the patch and then i need to download the corresponding source
[15:29] <BlackZ> bdrung: cool!
[15:29] <bdrung> dholbach: do you have a good name for the script that i promised to write?
[15:29] <BlackZ> patch-checker :P
[15:30] <dholbach> bdrung: no, sorry - maybe nigelb does
[15:30] <bdrung> nigelb: do you have a good name for the script that i promised to write?
[15:31] <micahg> bdrung: I have one suggestion for your script for sponsoring
[15:31] <bdrung> micahg: shoot
[15:31] <bdrung> everything is better than "foo"
[15:31] <micahg> bdrung: is it possible to check the series for the packageset to make sure that it's uploadable in that series
[15:31] <micahg> bdrung: i.e. mozilla package set can't upload to <=lucid
[15:33] <bdrung> micahg: open a bug report and ask dholbach
[15:34] <bdrung> micahg: oh, moment, i was thinking of sponsor overview.
[15:34] <micahg> bdrung: k, where should the bug go?
[15:34] <dholbach> that's part of the sponsoring overview code for >= lucid, but not before
[15:34] <micahg> dholbach: ok
[15:34] <bdrung> micahg: https://bugs.launchpad.net/ubuntu-sponsoring
[15:34] <dholbach> and in this very moment I'm not the best person to be asked, I'm terribly behind on almost everything
[15:39] <tumbleweed> bdrung: yeah, unseeded is mostly universe, but the ~ complicates things
[15:39] <bdrung> tumbleweed: do you have an example where it fails
[15:39] <tumbleweed> not on hand, no
[15:40] <bdrung> tumbleweed: let me know once you stumbled upon one
[15:40] <tumbleweed> re sponsor script, my grab-udd-merge does a similar thing for branch sponsorship - but it doesn't go as far as uploading
[15:41] <tumbleweed> bdrung: aah, xchat - it is apparently xubuntu, not unseede
[17:12] <nigelb> bdrung: take a patch, apply and upload to ppa
[17:12] <nigelb> bdrung: I don't remember what nickname we gave it back then
[17:15] <bdrung> nigelb: we didn't have a nick
[17:16] <nigelb> bdrung: aha
[17:38] <ximion_> hi there :)
[17:40] <ximion> I am the Debian maintainer of the package projectm, which is currently in Debian experimental.
[17:40] <ximion> the package is in the sync queue of Ubuntu Maverick at time.
[17:41] <ximion> we put the package into experimental cause it had some serious bugs like some applications were crashing on startup etc.
[17:41] <ximion> we also didn't know how all dependencies of projectm behave and hadn't finished all transitions yet when the package was uploaded to experimental.
[17:42] <ximion> this is all fixed now, but it might take a long time until a new package is uploaded to unstable.
[17:43] <ximion> so, could someone please upload a new "ubuntu-version" of the package?
[17:43] <ximion> I uploaded the new version at revu: http://revu.ubuntuwire.com/p/projectm
[17:43] <Laney> can't you upload the new version to experimental?
[17:44] <ximion> this package also solves a package conflict (which happens with the old package from Debian)
[17:44] <ximion> Laney: No, I need a mentor to do this :-P
[17:44] <Laney> your previous sponsor?
[17:44] <ximion> yes
[17:45] <Laney> sounds like the way to go to me
[17:45] <ximion> And he is currently at debconf, so he might upload this package soon, but he might not.
[17:45] <Laney> then sync from there into maverick
[17:46] <ximion> Laney: Of course, but I don't really know when the package gets published in the official Maverick repositories.
[17:46] <ximion> If it is published, some uses will get problems while upgrading their very old projectm version due to a conflict between projectm-data and libprojectm-data
[17:47] <Laney> has it been uploaded?
[17:47] <Laney> you can just cancel the request
[17:48] <Laney> (if it hasn't been uploaded, that is)
[17:48] <ximion> it is in upload queue, no sync request has been made...
[17:49] <ximion> I tried to reach the developer who uploaded it yesterday, but did not received a reply yet.
[17:49] <Laney> ah, this is easy
[17:49] <Laney> ScottK: Could you please reject projectm? context: ^^^
[17:49] <ximion> I'm not sure how fast the uploads get reviewed in ubuntu.
[17:50] <ximion> Laney: Also a solution -P
[17:50] <Laney> so if your new one doesn't get sponsored to Debian within, say, a week then ping me again and I will upload for you
[17:52] <ximion> Laney: Thanks! It would be nice to have the new version of projectM in Ubuntu Maverick too.
[17:53] <Laney> we'll make it happen
[17:53] <ximion> And if the GStreamer guys apply the OpenGl-vis patch, Totem will be able to use projectm too.
[17:53] <ximion> we'll see :)
[17:55] <ari-tczew> bdrung: could you take this one? bug 611386
[18:24] <ScottK> Laney and ximion: Rejected.  Please discuss this with bdrung, since it was his upload.
[18:27] <ximion> ScottK: I already sent him an email yesterday. I hope a new version of the projectm package can be uploaded soon.
[18:27] <ScottK> OK
[18:30] <Laney> thanks ScottK
[18:30] <ScottK> You're welcome.
[18:33] <ari-tczew> ScottK: got a time?
[18:33] <ScottK> ari-tczew: Not really.
[18:33] <ari-tczew> ScottK: ok so I'll back to you in august/september
[18:34] <ScottK> Today is bad and I'll be offline most of the weekend.  If you're around late tomorrow your time, there's a good chance I'll be available.
[19:37] <ari-tczew> please take a look on bug 595499 thanks
[19:57] <bdrung> ari-tczew: bug 611386 already sponsored by someone else
[19:59] <bdrung> ximion: i saw you took the right way.
[20:00] <ximion> bdrug: I was not really sure how to do...
[20:00] <bdrung> ximion: we should have a version of projectm uploaded to maverick before feature freeze.
[20:01] <bdrung> ximion: you gave me a nice name :D
[20:01] <ari-tczew> bdrung: I know about it
[20:02] <ximion> bdrung: sorry :-P You might want to upload my fixed version of projectM: http://revu.ubuntuwire.com/p/projectm
[20:02] <bdrung> ximion: my initial thought was: better something in the archive than nothing
[20:02] <ximion> this version is exactly the same as in Debian, but it contains bugfixes for all projectM issues I know about.
[20:02] <ximion> yes, true.
[20:02] <bdrung> ximion: what are your plans for debian and the timeline?
[20:03] <ximion> and projectm is something lots of users were looking for.
[20:03] <ximion> I would like to have the new packaging of projectm in unstable asap.
[20:04] <bdrung> ximion: that contains these changes?
[20:04] <ximion> the old packages in debian are orphaned or really old, some also contaon possible security holes.
[20:04] <ximion> bdrug: yes
[20:04] <bdrung> ^ still not correct ;)
[20:05] <ximion> bdrung: My sponsor, siretart, is at Debconf at time. I pinged him on IRC, but even if he answers he might be too buisy to look at this package.
[20:05] <bdrung> ximion: then let's wait for the package to hit unstable and sync this version then. you can either ping me for syncing or use requestsync
[20:06] <ximion> I'll be on holiday for the next two weeks, so I hope someone will upload projectm for me.
[20:07] <Laney> déjà vu!
[20:07] <ximion> (I don't know if I'll have an internet connection, so I can't look at this then)
[20:07] <Laney> ximion: sirtetart will probably be happy to upload to ubuntu for you if you ask
[20:08] <ximion> a sync will be enough.
[20:08] <Laney> I meant that
[20:08] <Laney> saves us forgetting to look at it
[20:08] <ximion> unfortunately I don't think the projectm packaging will make it into the next Debian stable release.
[20:09] <ximion> Laney: I think he'll do it.
[20:09] <siretart> ximion: why not?
[20:09] <bdrung> siretart: are you familiar with syncpackage?
[20:10] <ximion> siretart: Are you a Ubuntu developer?
[20:10] <bdrung> he is
[20:10] <ximion> then there's nothing to worry about :)
[20:10] <siretart> bdrung: I think I can imagine what it does
[20:10] <ximion> siretart: Will you have time to look at the changes I made before I go on vacation?
[20:11] <ximion> (next monday)
[20:11] <siretart> I've just looked at them, they seem fine to me, I'm currently building it
[20:12] <Laney> :)
[20:13] <ximion> I tried to reach upstream for months and didn't receive any message from them. But now, working with them is really great.
[20:14] <ximion> And I think I understand at least all GUI and Qt related stuff of the projectM code. (the Milkdrop algorithms are still a bit weird for me)
[20:15] <siretart> cool!
[20:15] <bdrung> ximion: a good upstream relation is very important
[20:19] <ximion> bdrung: I know... ProjectM was - if I ignore the weird GeoGebra case - one of the more difficult upstream relations I had. (But I don't really have a lot of experience there, cause I do not maintain a lot of packages)
[20:22] <siretart> ximion: did you have a look it the lintian warnings?
[20:22] <siretart> ximion: possible-missing-colon-in-closes Closes #590706, and debian-changelog-line-too-long line 1
[20:24] <ximion> siretart: Whoops...embarrassing. I'll fix this. I did the lintian check before I made changes on the changelog.
[20:27] <ximion> siretart: Changes are committed.
[20:28] <ximion> Have you checked if projectM-pulseaudio works? It shoud either run or display a graphical error box instead of crashing.
[20:37]  * ximion is away for dinner.
[20:56] <ximion> \me is back.
[21:05] <ximion> siretart: Is there anything left to change on projectm-packaging?
[21:08] <siretart> ximion: yes
[21:08] <siretart> but I'm on it
[21:08] <siretart> did you actually test the upgrade?
[21:10] <ximion> yes. it forced a partial upgrade where libprojectm-data got removed.
[21:49] <bluefoxicy> Wait, what
[21:49] <bluefoxicy> why does OpenOffice.org now give me font sizes in percents (110% 115% etc) and offer me typefaces Normal, Cursiva, Nigreta, Nigreta Cursiva
[22:14] <bdrung> ScottK: this time you can accept projectm :)
[22:44] <bdrung> tumbleweed: can you show me your grab-udd-merge?
[23:24] <Quintasan> Anyone knows where sbuild stores downloaded debs (if it stores them at all)?
[23:34] <bdrung> no
[23:34] <bdrung> dunno
[23:48] <tumbleweed> bdrung: I have a ubuntu-dev-tools branch on lp
[23:48] <bdrung> tumbleweed: link
[23:49] <bdrung> ?
[23:49] <tumbleweed> lp:~stefanor/ubuntu-dev-tools/grab-udd-merge
[23:52] <bdrung> tumbleweed: you might want to use python-debian for working on debian/changelog
[23:54] <tumbleweed> bdrung: thanks, I look. don't know python-debian. I'm sure it could use more bzrlib and less calling-out, too
[23:54] <tumbleweed> i'll look