=== Amaranthus is now known as Amaranth === chilicui1 is now known as chilicuil === almaisan-away is now known as al-maisan === yofel_ is now known as yofel === al-maisan is now known as almaisan-away [11:40] Hello [11:42] can anyone help me out with something? [11:42] just ask [11:43] ooh I think I might be in the wrong channel [11:43] I'm trying to get a usb wireless dongle to work [11:44] just for wifi in the house [11:45] Chorin: yeah, support is #ubuntu [11:45] awesome thanks [11:45] sorry to bother === ninjak_ is now known as ninjak [15:50] MOTU meeting reminder (10 mins) [15:51] woah [15:51] i did forget! [15:51] * tumbleweed mostly missed the last one [15:51] I assume there are things we should be doing for these meetings that we aren't [15:51] such as preparing beginner tasks [16:12] If anyone want to volunteer to maintain Qt3 so it doesn't get removed, now's your chance (See ubuntu-devel). [16:14] scottK: I think the biggest burden is the LSB, once that's fixed, it can go [16:14] micahg: I claim we don't care. [16:14] ISV's don't target non-LTS releases to any degree anyway. [16:14] 5.0 supposedly doesn't need it [16:17] hrm, okies, Debian seems to have done away with it, but let's see if there's any pushback on -devel [16:20] In Debian lots of people whined, but when asked "Does that mean you're going to maintain it" they all got very quiet. [16:20] I expect the same here. [16:21] well, the source is either in main or it's gone AFAIC, unless someone with significant resources commits to it [16:24] it's a shame we couldn't have laid it to rest before precise was released [16:25] No, I think we needed it for the LTS. There is still significant ISV and science software that's never been ported. [16:25] Right after the LTS though is the perfect time to remove it. [16:25] I agree, but it's still a shame :0 [16:26] The main thing is not to be the next gtk 1.2. [16:26] * micahg guesses gtk2 will still be in 14.04 and maybe even 16.03 [16:26] *16.04 [16:27] same with python2 [16:28] i guess that python2 will live way longer than gtk2 [16:28] well, maybe not 16.04, I think I'd kill both of those with fire if they were still in universe by 16.04 [16:28] especially with 5 year LTSs [16:29] we can leverage backports for stragglers [16:30] Python is used by too many people for local scripts and things to go away anytime soon. [16:30] 4 years away isn't enough? [16:30] No. [16:31] it's not like python will be gone, there will be python3.whatever [16:32] Right, but, for example, I have production python code I haven't touched since 2006. [16:32] well, I guess it'll depend on how much commitment there is for upstream support and how committed Debian is to removal [16:32] scottK: right, but it'll be that code's 10 year anniversary, time for a tune up :) [16:33] or were you planning on skipping 3 altogether and going straight to 4? :) [16:34] I plan on not spending time on it until I have to. [16:34] Although I did look at that particular file and the one bit that's tricky to port I stole from something else that I've already ported. [16:35] It's more that with python it's not packaged software migration you're up against, it's sysadmins trying to get their stuff done. [16:39] Hi all! [16:42] +micahg you needed help with the Chromium PPA yes? [16:42] agrestringere: yes, shall I add you to the list of people to contact when it's started up again? [16:43] +micahg yes I'm a CS major here in NYC and a Linux nutter so I would love to volunteer and learn how it's done... [16:46] I'll connect with you via launchpad === mdomsch_ is now known as mdomsch === margo_ is now known as margo [18:56] scottK: if I approved a backport, but it slipped through the cracks and didn't get uploaded and there's a newer version in quantal, can I upload the older version if it's not RC buggy? [18:56] micahg: Yes, but it's generally better to retest the new one. [18:57] well, this had several reverse dependencies, so I'm reluctant to ask for that [18:57] normally I'd agree, I'll check with the requestor though before uploading [19:00] OK.