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